Ticket #1257 (closed defect: invalid)

Opened 14 months ago

Last modified 10 days ago

There is no per virtualhost error log

Reported by: anonymous Owned by: jan
Priority: normal Milestone: 1.5.0
Component: core Version: 1.4.15
Severity: normal Keywords:
Cc: fox_ibddal@… Blocked By:
Need User Feedback: no Blocking:

Description (last modified by stbuehler) (diff)

I have seen that lighttpd doesn't allow a per domain error-log. i have given this inside a virtual host block:


$HTTPhost? =~ "(www.doc.com|doc.com|dom.com|www.dom.com)" {

server.errorlog = "/home/httpd/doc.com/stats/doc.com-error_log"

}


But lighttpd only honours the LAST errorlog directive, and all the error for all domains are sent to that log. Is this by design? Or is it a bug?

Thanks.

Attachments

Change History

Changed 14 months ago by darix

  • status changed from new to closed
  • resolution set to worksforme

works as designed.

Changed 14 months ago by ligesh

Could you please elaborate. Works as designed? Does it mean that lighty doesn't have a per virtualhost error log, or that it has and does work properly?

Thanks.

Changed 14 months ago by ligesh

Hi,

Without a per virtualhost error log, the entire vhost concept doesn't make any sense. As in, how do you expect a customer in a shared hosting setup to fix errors on his website? Viewing a particular domain's error log is a very critical feature.

Thanks.

Changed 14 months ago by darix

yes lighttpd supports only one error log. but that doesnt render vhosts useless. vhosts work outside of shared hosting environments very well too. yes this is a missing features that makes it harder to use lighttpd in shared hosting environments. but in the end it is your decision if lighttpd will work in your setup or not.

for 1.5 we plan to fix this.

Changed 5 months ago by anonymous

  • cc fox_ibddal@… added
  • status changed from closed to reopened
  • resolution worksforme deleted

Is this in 1.5?

Robin

Changed 10 days ago by stbuehler

  • status changed from reopened to closed
  • resolution set to invalid
  • description modified (diff)

The only thing interesting in the error log for vhosts are the cgi and fastcgi application errors; which the applications could also log somewhere else.

No, it is not in 1.5, and i don't think it will come as the log interface has no connection context parameter.

Anyway, no bug here.

Add/Change #1257 (There is no per virtualhost error log)

Author



Change Properties
<Author field>
Action
as closed
Next status will be 'reopened'
 
Note: See TracTickets for help on using tickets.