FS#9841 - lighttpd: multiple server.errorlogs break rc.d script

Attached to Project: Arch Linux
Opened by Thomas Cyron (nano) - Saturday, 15 March 2008, 13:57 GMT
Last edited by Aaron Griffin (phrakture) - Wednesday, 09 April 2008, 19:09 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Kieslich (tobias)
Architecture All
Severity Medium
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Multiple server.errorlogs defined in lighttpd.conf break the rc.d script. In /etc/conf.d/lighttpd DEAMON_ERRLOG is determined by filtering out all server.errorlog definitions. These errorlog file(s) are then used as the destination where all the output from lighttpd is redirected to. If multiple errorlogs are defined, this fails.

Package version: 1.4.19-1
Steps to reproduce: add multiple server.errorlog options into lighttpd.conf and (re)start lighttpd via /etc/rc.d/lighttpd
This task depends upon

Closed by  Aaron Griffin (phrakture)
Wednesday, 09 April 2008, 19:09 GMT
Reason for closing:  Not a bug
Additional comments about closing:  This is in the lighttpd docs. See last comment.
Comment by Jason Pierce (pierce.jason) - Thursday, 03 April 2008, 06:22 GMT
Lighttpd can not use more than one errorlog. It will produce a fatal error in configfile.c at lighttpd startup if it gets past the problem in rc.d.

Isn't the purpose of /var/log/daemon.log to record starting and stopping of daemons though?
Comment by Thomas Cyron (nano) - Thursday, 03 April 2008, 13:21 GMT
You can’t define multiple errorlogs in the same scope, but you can use different ones in each scope. For example, you can set an own errorlog file for each $HTTP["host"] block.
Comment by Jason Pierce (pierce.jason) - Monday, 07 April 2008, 01:37 GMT
http://trac.lighttpd.net/trac/wiki/server.errorlogDetails
"server.errorlog option...NOTE: This directive should be used only once within a configuration and NOT for each virtual host (if any)"

Only one of the server.errorlog declarations gets honored in the case of being inside a vhost block, and is used daemon-wide. I do not positively remember which server.errorlog declaration will be used, but I believe it is the last one seen by the config parser at daemon startup.

For multiple-file error logs, you could try server.errorlog-use-syslog and having syslogd seperate the logs.

Loading...