deb package 1.54 - cannot start service on ubuntu 16.04.2 LTS

[cesmarvin]

Original report by Andy Fisher (Bitbucket: nucfisher, GitHub: nucfisher).

---

After upgrade to 1.54 via apt-get scm-server service doesn't start|stop.

• service scm-server start

No logs, no scm instance in memory

• /opt/scm-server/bin/scm-server start

Log: "Service killed by signal 11"
netstat -nl: nobody listen 18080 (ps shows "-Djetty.port=18080", set in /etc/default/scm-server)

• cd /opt/scm-server/bin && scm-server

works ok. But as root, not as scm

[cesmarvin]

Original comment by Sebastian Andres (Bitbucket: morfey2000, ).

---

We have the same Problem on Debian 8 (Jessie). Is it a Problem of a update from Java-VM?

[cesmarvin]

Original comment by Andy Fisher (Bitbucket: nucfisher, GitHub: nucfisher).

---

I dont know if it is related to JVM.
I have oracle-server-jre-8u131_x64 and JAVA_HOME set in /etc/default/scm-server.

Manual start of /opt/scm-server/bin/scm-server works ok as from root as from scm user.
So I guess the problem relates to launch of jsvc in daemon mode.

[cesmarvin]

Original comment by Ludovic (Bitbucket: Ludovic, GitHub: Ludovic).

---

Hi,

Same problem here, with Ubuntu 16.04.2, with deb package AND with the standalone zip.

Running scm-server start (with any account) : nothing is listening to port 8080, but there is a "jsvc.exec" process running in background.
Running scm-server works perfectly (so it can be run using something like supervisor)

I've tested with openjdk-8-jre and openjdk-9-jre package installed, same problem.

[cesmarvin]

Original comment by Ludovic (Bitbucket: Ludovic, GitHub: Ludovic).

---

Some additional informations.

On a clean 16.04.2 install (in a VM, no updates installed), with scm-server installed via deb packages + openjdk-8-jre-headless, the service starts and listen on port 8080 without any problem

After updating packages (simple apt update; apt upgrade) and a reboot, the service won't start.

I've found the following bug reports on Ubuntu & Debian bug trackers, which can be related to this problem, since the Kernel 4.4.0.81 is part of the upgrade :

• https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1700010
• https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865311

EDIT : It seems to be a regression in the kernel itself.

[cesmarvin]

Original comment by Ludovic (Bitbucket: Ludovic, GitHub: Ludovic).

---

New kernel (4.4.0-83) released for Ubuntu 16.04.2.

Tested it on a VM, everything works again.
@nucfisher, you may run another apt-get update and reboot to see if it solves the problem :)

[cesmarvin]

Original comment by Andy Fisher (Bitbucket: nucfisher, GitHub: nucfisher).

---

@ludovic, it works for me.

I have Ubuntu 16.04.2 LXC container on Proxmox4.
And it was fixed after update host to the following kernel:

root@jira:~# uname -a
Linux jira 4.4.67-1-pve #1 SMP PVE 4.4.67-92 (Fri, 23 Jun 2017 08:22:06 +0200) x86_64 x86_64 x86_64 GNU/Linux

[cesmarvin]

Original comment by Andy Fisher (Bitbucket: nucfisher, GitHub: nucfisher).

---

Since the kernel update is here, I'm requesting to close the issue with an article in KB.

[cesmarvin]

Original comment by Sebastian Andres (Bitbucket: morfey2000, ).

---

Hi,

the SCM-Manager works know, but there was no update from the Kernel (We have
installed Version 3.16, from Debian 8 - Jessie).
But there wasn't any upgrade from any package ... I don't understand why
SCM-Manager actualy work correctly ... :-)

[cesmarvin]

Original comment by Andy Fisher (Bitbucket: nucfisher, GitHub: nucfisher).

---

I guess the trouble was not in kernel itself but somewhere in the init.d subsystem.
Since direct run of /opt/scm-server/bin/scm-server worked ok all the time.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.