Solved lighttpd process disappears

mro

mro

Hi pkubaj, after

Code: 
$ tail /var/log/messages
2023-11-06 19:27:44: (/wrkdirs/usr/ports/www/lighttpd/work/lighttpd-1.4.71/src/server.c.465) warning: clock jumped 3601 secs
2023-11-06 19:27:44: (/wrkdirs/usr/ports/www/lighttpd/work/lighttpd-1.4.71/src/server.c.473) attempting graceful restart in < ~5 seconds, else hard restart
2023-11-06 20:27:45: (/wrkdirs/usr/ports/www/lighttpd/work/lighttpd-1.4.71/src/server.c.1216) [note] graceful shutdown started
2023-11-06 20:27:45: (/wrkdirs/usr/ports/www/lighttpd/work/lighttpd-1.4.71/src/server.c.2308) server stopped by UID = 80 PID = 753

it doesn't come back up. I set the timezone https://www.cyberciti.biz/faq/howto-set-date-and-time-timezone-in-freebsd/ without change. Meanwhile I mitigate via server.feature-flags += ( "server.clock-jump-restart" => 0 ).

I'm on FreeBSD 13.2-RELEASE-p4.

How would I address this issue properly?
 
> So my problem is solved, but is lighttpd not coming back a thing to report to upstream?

How is lighttpd started? Is it chroot'd? (Is `server.chroot` set in lighttpd.conf?)
How is the lighttpd daemon managed on your system? If lighttpd exits gracefully, do a service manager restart it?
 
  • Thanks
Reactions: mro
maybe pkubaj knows better, but I know

Code: 
$ service lighttpd start

and

Code: 
$ /usr/local/etc/rc.d/lighttpd

seems to use /usr/local/sbin/lighttpd

No chroot.
 
You must log in or register to reply here.
Back
Top