[pkg-lighttpd] Bug#838473: lighttpd: Not reliably stoppable using systemd service file

[Stefan Bühler]

Hi,

On 09/21/2016 12:22 PM, Lukas Martini wrote:
> Package: lighttpd
> Version: 1.4.35-4+deb8u1
> Severity: normal
> 
> When running 'systemctl stop lighttpd', sometimes the command will seemingly
> complete successfully, but doesn't actually stop lighttpd. Similarly, after
> 'systemctl restart lighttpd' the same instance will just continue running
> (as the old one isn't stopped and systemd's attempt to start lighttpd
> again obviously fails as the ports are in use).
> 
> I haven't properly debugged this issue in any way, but I've seen it across
> various servers using lighttpd. My first guess for the cause would be 
> that no pidfile is specified in the systemd service and systemd is left guessing
> for the main task, but I could be wrong.

On receiving the first signal lighttpd will stop accepting new requests
and try to close pending ones; connections in keep-alive "wait" mode
should get closed immediately, but active connections might take a while.

When sending a second signal lighttpd should drop all connections and
exit immediately.

systemd shouldn't need the pid file, as it should start lighttpd in "no
detach/daemonize" mode (using the "-D" argument).

A "systemctl status lighttpd.service" output is probably the minimum to
even start debugging - I see no reason to keep this bug open without any
data in it.

cheers,
Stefan