[Invalid] lighttpd cannot be restarted
Added by gxl5271 about 7 years ago
I have lighttpd 4.25. The system is embeded linux. The system was restarted by watchdog, but never fully come up. I have to press power button to get it restart. You can see these two lines has a time gap since the system has nothing after the first line. The second line is the output after I pressed the power button.
"2017-03-06 04:59:22: (server.c.1503) server stopped by UID = 0 PID = 1
Mar 6 14:16:49 (none) kernel: 08 -> 0x011c"
Do anyone know if the lighttpd server can hang?
The whole output:
2017-03-06 04:59:22: (watchdog.c.215) calling do_shutdown
2017-03-06 04:59:22: (shutdown.c.374) /usr/lib/sendmail does not exist or is not executable (errno = 2)
2017-03-06 04:59:22: (shutdown.c.436) shutting down the system because of error No such file or directory
2017-03-06 04:59:22: (server.c.1503) server stopped by UID = 0 PID = 1 Mar 6 14:16:49 (none) kernel: 08 -> 0x011c
2017-03-06 14:16:53: (log.c.166) server started
2017-03-06 14:16:53: (server.c.954) WARNING: unknown config-key: accesslog.filename (ignored)
2017-03-06 14:16:59: (log.c.69) watchdog started
2017-03-06 14:16:59: (watchdog.c.696) starting daemon: ( 5 . 8 )
2017-03-06 14:16:59: (watchdog.c.705) ping: no machine to check
2017-03-06 14:16:59: (watchdog.c.711) file: no file to check
2017-03-06 14:16:59: (watchdog.c.720) pidfile: /var/run/jetty.pid
2017-03-06 14:16:59: (watchdog.c.720) pidfile: /var/run/lighttpd.pid
Thanks!
Replies (2)
RE: lighttpd cannot be restarted - Added by carpii about 7 years ago
Are you loading mod_accesslog in your lighttpd config?
Without this, you will see the error "unknown config-key: accesslog.filename"
It probably is not the cause of your problems, but I would at least fix that before digging deeper
More likely though, the issue lies in watchdog daemon...
It clearly cannot find sendmail, which is perhaps understandable if its an embedded system...
https://sourcecodebrowser.com/watchdog/5.4/shutdown_8c.html
Fix your lighty config, and then try configuring watchdog so its not trying to send mails, and see what issue you have after that
RE: lighttpd cannot be restarted - Added by gstrauss about 7 years ago
"server stopped by ..."
When you see that, lighttpd is about to exit. Since you see nothing else, it does not appear that anything attempted to restart lighttpd. If rebooting solves the problem, there is unlikely to be anything preventing lighttpd from starting up, or else there would be trace in the lighttpd error log.
Therefore, please check your watchdog config. watchdog.c is not part of lighttpd.