deb package 1.54 - cannot start service on ubuntu 16.04.2 LTS

Issue #930 new
Andy Fisher
created an issue

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

Comments (11)

  1. Andy Fisher reporter

    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.

  2. Ludovic


    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.

  3. 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 is part of the upgrade :

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

  4. Andy Fisher reporter

    @Brieulle 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

  5. Sebastian Andres


    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 ... :-)

  6. Andy Fisher reporter

    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.

  7. Log in to comment