Problems with SCM Manager installation/start on Ubuntu 20.04

SCM-Manager Bug Reports SCM-Manager
1

Hello together,

I would like to install SCM Manager 2.30.X on a newly installed Ubuntu 20.04. I tried the Quickstart installation, which worked without error messages. Unfortunately, however, the server does not seem to start correctly.

The service seems to start but in the systemd journal I find the following lines:

Feb 09 15:54:54 host systemd[1]: Stopping SCM-Manager Server...
Feb 09 15:54:54 host systemd[1]: scm-server.service: Succeeded.
Feb 09 15:54:54 host systemd[1]: Stopped SCM-Manager Server.
Feb 09 15:54:54 host systemd[1]: Started SCM-Manager Server.
Feb 09 15:54:54 host scm-server[26667]: 2022-02-09 15:54:54.811:INFO::main: Logging initialized @112ms to org.eclipse.jetty.util.log.StdErrLog
Feb 09 15:54:54 host scm-server[26667]: 2022-02-09 15:54:54.963:INFO:oejs.Server:main: jetty-9.4.44.v20210927; built: 2021-09-27T23:02:44.612Z; git: 8da83308eeca865e495e53ef315a249d63b>
Feb 09 15:54:55 host scm-server[26667]: 2022-02-09 15:54:55.826:INFO:oejw.StandardDescriptorProcessor:main: NO JSP Support for /scm, did not find org.eclipse.jetty.jsp.JettyJspServlet
Feb 09 15:54:55 host scm-server[26667]: 2022-02-09 15:54:55.836:INFO:oejs.session:main: DefaultSessionIdManager workerName=node0
Feb 09 15:54:55 host scm-server[26667]: 2022-02-09 15:54:55.836:INFO:oejs.session:main: No SessionScavenger set, using defaults
Feb 09 15:54:55 host scm-server[26667]: 2022-02-09 15:54:55.838:INFO:oejs.session:main: node0 Scavenging every 660000ms
Feb 09 15:54:57 host scm-server[26667]: Feb 09, 2022 3:54:57 PM com.google.inject.servlet.GuiceFilter setPipeline
Feb 09 15:54:57 host scm-server[26667]: WARNING: Multiple Servlet injectors detected. This is a warning indicating that you have more than one GuiceFilter running in your web applicati>

One line says that the JSP support cannot be found. OpenJDK is installed, however:

openjdk version "11.0.13" 2021-10-19
OpenJDK Runtime Environment (build 11.0.13+8-Ubuntu-0ubuntu1.20.04)
OpenJDK 64-Bit Server VM (build 11.0.13+8-Ubuntu-0ubuntu1.20.04, mixed mode)

A check with netstat -tulpn | grep LISTEN shows that the SCM Manager cannot be found under port 8080 or 80.

I also tried a completely manual installation, with the same result. Do you have any ideas for me?

Many thanks and best regards

Christian

2

Hey @christian.pommer,

your logs seem fine to me. You can ignore the warning about no JSP Support. It should still work without issues.

Do you use a reverse proxy? Have you seen the initialization setup via the WebUI?

Regards, Eduard

3

Dear Eduard,
thank you very much for your feedback.
No, I have not yet set up a reverse proxy. The standard config is still valid, via port 8080. The firewall is still deactivated.
No, I could not start the initialisation setup. Neither hostname:8080 nor hostname:8080/scm are reachable.
Many thanks and best regards
Christian

4

Do you have the following lines somewhere in your logs?

2022-02-10 08:33:42.523:INFO:oejs.AbstractConnector:main: Started ServerConnector@7ff95560{HTTP/1.1, (http/1.1)}{0.0.0.0:8080}
2022-02-10 08:33:42.524:INFO:oejs.Server:main: Started @4809ms
5

Unfortunately no, when I look at journalctl, I only find the following about the svm manager, after starting the service

Feb 10 10:27:08 host systemd[1]: Started SCM-Manager Server.
Feb 10 10:27:09 host scm-server[1287]: 2022-02-10 10:27:09.017:INFO::main: Logging initialized @137ms to org.eclipse.jetty.util.log.StdErrLog
Feb 10 10:27:09 host scm-server[1287]: 2022-02-10 10:27:09.182:INFO:oejs.Server:main: jetty-9.4.44.v20210927; built: 2021-09-27T23:02:44.612Z; git: 8da83308eeca865e495e53ef315a249d63ba>
Feb 10 10:27:09 host scm-server[1287]: 2022-02-10 10:27:09.776:INFO:oejw.StandardDescriptorProcessor:main: NO JSP Support for /scm, did not find org.eclipse.jetty.jsp.JettyJspServlet
Feb 10 10:27:09 host scm-server[1287]: 2022-02-10 10:27:09.786:INFO:oejs.session:main: DefaultSessionIdManager workerName=node0
Feb 10 10:27:09 host scm-server[1287]: 2022-02-10 10:27:09.786:INFO:oejs.session:main: No SessionScavenger set, using defaults
Feb 10 10:27:09 host scm-server[1287]: 2022-02-10 10:27:09.788:INFO:oejs.session:main: node0 Scavenging every 600000ms
Feb 10 10:27:11 host scm-server[1287]: Feb 10, 2022 10:27:11 AM com.google.inject.servlet.GuiceFilter setPipeline
Feb 10 10:27:11 host scm-server[1287]: WARNING: Multiple Servlet injectors detected. This is a warning indicating that you have more than one GuiceFilter running in your web applicatio>
6

OK, the good news: I can reproduce this on an Ubuntu 20.04 VM. The bad news: I don’t know why. We’ll look into this and get back to you.

7

Thank you very much for your effort. I also tried it today on a new VM and the problem reappeared.
Should I downgrade to 18.04 lts, or change the distribution?

8

Today I learned something, thank you. Is this a freshly installed server? Than this might be your issue, too: The server simply had insufficient entropy to create the initial setup token.

After following this answer, SCM-Manager started successfully. Simply install “rng-tools” and run them once:

sudo apt-get install rng-tools
sudo rngd -r /dev/urandom

Then restart SCM-Manager. I would love to hear whether this works for you :slight_smile:

9

You are great. Now it works. Thank you very much!

2 Likes
10

I have closed this thread since there was no activity in the last 30 days.