Bug #1509
closedlighttpd dead but pid file exists
Description
I installed 1.4.18 on CentOS and I frequently run into the following problem:
I start lighttpd as follows:
- service lighttpd start
The status code is 0, and I immediately check the status.
- service lighttpd status
when I get the message "lighttpd dead but pid file exists"
and sure enough there is no trace of the process "lighttpd"
The "/var/log/lighttpd/error.log" does not have any information other
than messages of the form:
(log.c.75) server started
followed immediately by a log message of the form:
server stopped by UID = 0 PID = ....
although I never issued a "service lighttpd stop"
What is puzzling is that if I retry and then after one or more attempts the startup
succeeds and lighttpd stays up (forever, until I shut it down, of coz).
It seems that, in some cases, the lighttpd process starts and immediately exits without leaving an useful trace.
-- sashi
Updated by Anonymous almost 17 years ago
The messages in "/var/log/lighttpd/error.log" are:
2008-01-11 03:59:28: (log.c.75) server started
2008-01-11 03:59:41: (server.c.1470) server stopped by UID = 0 PID = 19676
2008-01-11 04:00:09: (log.c.75) server started
2008-01-11 04:00:22: (server.c.1470) server stopped by UID = 0 PID = 19834
Note that the server stopped message appears and lighttpd process exits even though
I did not type "# service lighttpd stop"
Updated by Anonymous almost 17 years ago
Upon further investigation, this bug seems to be a duplicate of
http://trac.lighttpd.net/trac/ticket/165
I checked out the sources and the patch to server.c that is attached to the bug is not
in the 1.4.18 sources.
I believe lighttpd quits when trying to write this warning:
WARNING: unknown config-key: alias.url
I can workaround the issue by adding mod_alias to server.modules
Updated by glen almost 17 years ago
- Status changed from New to Fixed
- Resolution set to duplicate
Also available in: Atom