Bug#865311: jsvc: SIGSEV in child process when starting jsvc

Charles Leclerc leclerc.charles at gmail.com
Tue Jun 20 13:12:25 UTC 2017


Package: jsvc
Version: 1.0.15-6+deb8u1
Severity: important

When trying to start a very simple java daemon on jessie jsvc through systemd we obtain this error message:

 Service killed by signal 11

Then we need to SIGKILL the parent process.

The problem appeared on our servers after the last apt upgrade which installed the following packages (the servers were rebooted after the upgrade):

Upgrade: python-acme:amd64 (0.10.2-1~bpo8+1, 0.10.2-1~bpo8+2), libgnutls-openssl27:amd64 (3.3.8-6+deb8u5, 3.3.8-6+deb8u6), multiarch-support:amd64 (2.19-18+deb8u9, 2.19-18+deb8u10), linux-image-3.16.0-4-amd64:amd64 (3.16.43-2, 3.16.43-2+deb8u1), exim4-base:amd64 (4.84.2-2+deb8u3, 4.84.2-2+deb8u4), libgnutls-deb0-28:amd64 (3.3.8-6+deb8u5, 3.3.8-6+deb8u6), libc-dev-bin:amd64 (2.19-18+deb8u9, 2.19-18+deb8u10), libc-bin:amd64 (2.19-18+deb8u9, 2.19-18+deb8u10), libc6:amd64 (2.19-18+deb8u9, 2.19-18+deb8u10), exim4-daemon-light:amd64 (4.84.2-2+deb8u3, 4.84.2-2+deb8u4), exim4-config:amd64 (4.84.2-2+deb8u3, 4.84.2-2+deb8u4), libzzip-0-13:amd64 (0.13.62-3, 0.13.62-3+deb8u1), linux-libc-dev:amd64 (3.16.43-2, 3.16.43-2+deb8u1), libffi-dev:amd64 (3.1-2+b2, 3.1-2+deb8u1), locales:amd64 (2.19-18+deb8u9, 2.19-18+deb8u10), locales-all:amd64 (2.19-18+deb8u9, 2.19-18+deb8u10), libc6-dev:amd64 (2.19-18+deb8u9, 2.19-18+deb8u10), libgcrypt20:amd64 (1.6.3-2+deb8u2, 1.6.3-2+deb8u3), libffi6:amd64 (3.1-2+b2, 3.1-2+deb8u1)

I've installed a fresh VM to try to reproduce this bug on a new machine :

- installed jessie with ssh and standard utilities
- installed openjdk-8-jre from backports
- installed jsvc
- Created this java file:

-------------------------
import org.apache.commons.daemon.Daemon;
import org.apache.commons.daemon.DaemonContext;
import org.apache.commons.daemon.DaemonInitException;

public class Run implements Daemon {

    private class Runner extends Thread {
        public void run() {
            synchronized(this) {
                try {
                    wait();
                } catch (Exception e) {}
            }
        }
    }

    Runner r = new Runner();

    @Override
    public void init(DaemonContext context) throws DaemonInitException, Exception {}


    @Override
    public void start() throws Exception {
        r.start();
    }

    @Override
    public void stop() throws Exception {
        synchronized(r) {
            r.notify();
        }
    }

    @Override
    public void destroy() {}
}
------------------------

Which basically starts and wait for termination

- compiled with:
 $ javac -cp /usr/share/java/commons-daemon-1.0.15.jar Run.java
- and tried to run with:
 $ /usr/bin/jsvc -nodetach -outfile '&2' -errfile '&2' -pidfile /tmp/jsvc.pid -cp /usr/share/java/commons-daemon-1.0.15.jar -java-home /usr/lib/jvm/java-8-openjdk-amd64 Run
 Service killed by signal 11
 
I would upgrade to stretch but it's not yet supported on our OVH vps.

Thanks for your help !

-- System Information:
Debian Release: 8.8
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages jsvc depends on:
ii  libc6                   2.19-18+deb8u10
ii  libcommons-daemon-java  1.0.15-6+deb8u1

Versions of packages jsvc recommends:
ii  openjdk-8-jre-headless [java2-runtime-headless]  8u131-b11-1~bpo8+1

jsvc suggests no packages.

-- no debconf information



More information about the pkg-java-maintainers mailing list