> Lighttpd seemed to detect the changed time condition and attempted to > restart itself to handle it, but it just stopped instead of restarting.
This can happen for a number of reasons, including using chroot, or using relative paths to important files which are not valid after lighttpd daemonizes and chdirs to '/'. Your description of lighttpd stopping instead of restarting differs from the title of this bug: "lighttpd crashes instead of restarting on time change" If lighttpd is crashing, please provide more details, such as a gdb backtrace on the core file. If lighttpd is not crashing, then the title is misleading. If lighttpd is not crashing, but is instead exiting instead of restarting, then check your lighttpd error log or journalctl to see why lighttpd was unable to restart. If those do not provide enough details, then you can strace -p the lighttpd pid while you send a SIGUSR1 to the lighttpd process to trigger a graceful restart. Look at the system calls which fail.
