Bug #1238
closedlogfile mixup with vhosts - possibly residing in mod_simple_vhost
Description
I'm running 4 hosts on my webserver, using mod_simple_vhost. The other day I found that the logfile of one vhost contains error messages belonging to another vhost. I verified my config file to see that I hadn't mixed up the paths to the logfiles in my vhosts, and found no error - everything in the config is totally OK, and each host is served to visitors perfectly fine as always.
A snip from the lighttpd.error.log belonging to "my_vhost":
------
2007-06-04 14:28:58: (mod_fastcgi.c.2502) FastCGI-stderr: PHP Notice: Undefined index: HTTP_REFERER in /web/my_other_vhost/www/redir.sd on line 2
2007-06-05 10:58:35: (mod_fastcgi.c.2502) FastCGI-stderr: PHP Notice: Undefined index: HTTP_REFERER in /web/my_other_vhost/www/redir.sd on line 2
2007-06-11 11:48:12: (mod_fastcgi.c.2502) FastCGI-stderr: PHP Notice: Undefined index: HTTP_REFERER in /web/my_other_vhost/www/redir.sd on line 2
------
The error messages above weren't found in duplicate places, ie. they were not found in the lighttpd.error.log belonging to "my_other_vhost" where they really should be.
Running lighttpd non-chroot, on OpenBSD4.1/i386.
Updated by Anonymous almost 18 years ago
Also noticed another behaviour now - not sure if it's related to this bug or intentional: the "(log.c.135) server stopped/started" messages appear in the error-log of the last defined vhost in the config file, which also happens to be my "my_vhost" where the misplaced error messages end up.
Updated by hoffie almost 18 years ago
Multiple error logs are currently not supported, so yes, this is more or less the expected behaviour. Just don't set multiple error logs.
Updated by jan almost 18 years ago
- Status changed from New to Fixed
- Resolution set to invalid
As hoffie says. Multiple errorlogs are not support yet.
Also available in: Atom