[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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



Control: tag -1 confirmed
Control: fixed -1 4.11.6-1

On Tue, 20 Jun 2017 15:12:25 +0200 Charles Leclerc <leclerc.charles@gmail.com> wrote:
> 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.
[...]
> 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:
[...]
> - 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
[...]

Thanks, this makes it pretty easy to reproduce.  I did have to add
':$PWD' to the end of the -cp argument though.

The kernel version in unstable has a later version of the fix and that
*doesn't* cause jsvc to crash.  So we should probably switch to that
version soon.

Ben.

-- 
Ben Hutchings
The most exhausting thing in life is being insincere. - Anne Morrow
Lindberg

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: