PlasticSCM Labs GPG repository key is invalid.

[Barron Kane]

OS: Ubuntu 18.04.4 LTS

Kernel: 4.15.0

The normal plasticscm repository works normally, but the labs repository returns this:

W: GPG error: https://www.plasticscm.com/plasticrepo/labs/ubuntu ./ Release: The following signatures were invalid: EXPKEYSIG DB77511526C083C6 labs OBS Project <labs@obs-api-v2.codicefactory.com>
E: The repository 'https://www.plasticscm.com/plasticrepo/labs/ubuntu ./ Release' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.

I force-trusted the repo, but it still complains that the signature is invalid.

An apt-key list wrought:

pub   rsa2048 2018-01-08 [SC] [expired: 2020-03-18]
      6408 080D 19B3 E5F5 AA6F  B17B DB77 5115 26C0 83C6
uid           [ expired] labs OBS Project <labs@obs-api-v2.codicefactory.com>

Looks like it expired last month.

Furthermore upon searching the repo for versions, only 7.0.16.2031 shows up when the website lists 9.x as current? Is this intentional?

Any and all help is appreciated.

 

Note:

I'm trying to install the Labs version because the base version breaks on my box with a 'thread creation failed' error. I want to try labs before I dig into what's causing that.

[calbzam]

Hi,

The labs repo is only used when we release some major features that we think they may not be stable enough. The last labs version may be 7.0.X while the current production version is 9.0.X

In summary: Always use the stable versions. As you report, even the the repo key is not properly updated

Using the stable repo, are you able to install the last Plastic version, right?

NOTE: You can always force your package manager to install a specific previous version. But I think you want to install the very last version.

Regards,

Carlos.

[Barron Kane]

Thanks for the reply!

 

The good news is that I am able to install from the base repo with no issues.

 

The bad news is that it crashes upon startup.

 

Packages installed: plasticscm-complete plasticscm-cloud

 

Error:

Starting the Plastic SCM server:
Unhandled Exception:
System.SystemException: Thread creation failed.
  at System.Threading.Thread.StartInternal (System.Security.Principal.IPrincipal principal, System.Threading.StackCrawlMark& stackMark) [0x00035] in <8f2c484307284b51944a1a13a14c0266>:0
  at System.Threading.Thread.Start (System.Threading.StackCrawlMark& stackMark) [0x0002d] in <8f2c484307284b51944a1a13a14c0266>:0
  at System.Threading.Thread.Start () [0x00002] in <8f2c484307284b51944a1a13a14c0266>:0
  at Codice.CM.Server.ActivityScheduler.g () [0x0003d] in <c1139098b7c748a69572c506bd8366c3>:0
  at Codice.CM.Server.SystemRunner.a (System.Object A_0) [0x00017] in <c1139098b7c748a69572c506bd8366c3>:0
  at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context (System.Object state) [0x0000e] in <8f2c484307284b51944a1a13a14c0266>:0
  at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x0008d] in <8f2c484307284b51944a1a13a14c0266>:0
  at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <8f2c484307284b51944a1a13a14c0266>:0
  at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x0002a] in <8f2c484307284b51944a1a13a14c0266>:0
  at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00096] in <8f2c484307284b51944a1a13a14c0266>:0
  at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <8f2c484307284b51944a1a13a14c0266>:0
Unable to start the Plastic SCM server. Refer to server log (plastic.FAILED.log.txt) for further details.

The file (plastic.FAILED.log.txt) doesn't exist on my system.

 

If I uninstall cloud and just run the server it works, but the admin panel configuration page shows this: (image attached)

 

I'm at a loss of what to do at this point.

[calbzam]

- Why are you installting both packages? Please install "plasticscm-complete" or "plasticscm-cloud" depending on our needs but not both.

- Plastic cloud edtion doesn't include a webadmin. I guess this is the reason why it's not starting in your enviroment. Even if you uninstalled the cloud edition you may still have some local configuration at "/opt/plasticscm/server". Please uninstall and remove all the configuration and finally perform a clean installation of "plasticscm-complete" (it inlcudes both a  Plastic server and Plastic client).

If after that, the webadmin is still not running, please attach "plastic.debug.log.txt"

Regards,

Carlos.

[Barron Kane]

Thanks for the input,

 

I've tried so many different things. I've wrestled with the server software since I've started for several different things. I only tried also installing the cloud edition because I thought a premise server was provided with the cloud edition but I was wrong and have grabbed a month of team, and started once again from a fresh linux install (5th attempt).

 

Leaving everything default, installing 'plasticscm-server-complete' (this is a headless vm), and not touching anything except going straight into the web admin seems to work.

 

Unfortunately, after running the clserverconfig program, I get a permissions error for the db.conf file. I tried a few different things, but my temporary solution is applying a 777 permissions blanket over the directory (chowning to the plasticscm user did not fix the issue prior). This is very bad practice but at the very least I can now demo plastic scm. I was successfully able to create the repository and begin using it (I still have my other perforce server in case plastic doesn't work out, but I really want to give this a solid attempt).

 

Other than the security implications, everything else seems to be working.

[calbzam]

Ok, if you are apaying customer and you have further issues you can reach us at support@codicesoftware.com and we can arrange a meeting to debug your setup.

Regards,

Carlos.