Project

General

Profile

Bug #1782

Lighty should not crash if it could not write a log file

Added by Anonymous almost 11 years ago. Updated over 10 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
Category:
core
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Missing in 1.5.x:

Description

Lighty crashes, with no error message at all (not even with an entry in its main error log file), if it could not write one access log file.

So this is a double problem:
  1. It should not crash if it could not write an access log file; it may be acceptable if it didn't have write permission on startup, but never if the permissions change after the server started (I would expect the problem to be reported in the main error log file).
  2. It doesn't provide a useful message to debug the problem; it actually doesn't provide anything at all.

This is the output when one access log file is not writable:


treasure ~: sudo lighttpd -Df /etc/lighttpd/lighttpd.conf            
treasure ~: echo $?
255

So you can only spot this problem with strace:


strace lighttpd -Df /etc/lighttpd/lighttpd.conf

-- gustavo

History

#1

Updated by icy over 10 years ago

  • Target version changed from 1.4.21 to 1.4.22
  • Patch available set to No
#2

Updated by stbuehler over 10 years ago

  • Status changed from New to Invalid
  • Priority changed from High to Normal

I get the errors in my log, so i see nothing wrong with that.

If someone can reproduce it, please attach the strace.

Also available in: Atom