https://redmine.lighttpd.net/https://redmine.lighttpd.net/favicon.ico?13667327412010-04-13T19:06:41Zlighty labsLighttpd - Bug #2186: lack of output when lighttpd fails to starthttps://redmine.lighttpd.net/issues/2186?journal_id=68822010-04-13T19:06:41Znitrox
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Need Feedback</i></li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li></ul><p>This is sounds more like a support question, but anyway...</p>
<p>Your error.log hasn´t been updated for a year now, so it never worked?</p>
<p>Reason for that might be:<br />- permission problem (you run lighty as user/group? log directory is owned by?)<br />- several error.log´s defined (only one error.log is allowed!)?</p>
<p>To debug use:<br /><pre>strace -ff -s 1024 -o foo.txt lighttpd -Df /etc/lighttpd/lighttpd.conf</pre><br />This might either write sth. more to the screen or hopefully sth. useful to foo.txt.</p>
<p>1.4.22 is quite a few versions behind, current is 1.4.26.</p> Lighttpd - Bug #2186: lack of output when lighttpd fails to starthttps://redmine.lighttpd.net/issues/2186?journal_id=68842010-04-13T21:01:10Zlightning
<ul></ul><p>I don't have strace available, this is a minimal embedded installation but your suggestion of -D does show the problem.<br /><code><br /> lighttpd -Df /etc/lighttpd/lighttpd.conf<br />configfile.c.828: 0, (null)<br />2010-04-13 17:42:24: (log.c.84) opening errorlog '/www/apache/logs/error_log' failed: Permission denied<br />2010-04-13 17:42:24: (server.c.893) Opening errorlog failed. Going down.</code></p>
<p>But as I posted in the original report that log file has a+w permissions. This was the most obvious thing to check.</p>
<p><code> ls -ail /www/apache/logs/error_log<br /> 1249 -rw-rw-rw- 1 root root 29779 May 10 2009 /www/apache/logs/error_log</code></p>
<p>However, for some reason, in copying the fs image to the flash device, the root directory was created without x permission for all users. I'll look into why that happens.</p>
<p>chmod a+x /</p>
<p>fixed!</p>
<p>Very simple once I had enough output for the program to know why it was failing. This is what I stated as being point of this bug report, not "user help".</p>
<p>What I needed to know was that -D would give me more console output: the output that I was expecting from a program that fails before it gets off the ground.</p>
<p>lighttpd -h<br /> -D don't go to background (default: go to background)</p>
<p>So probably the conclusion to this issue is maybe it needs to find out whether it does actually <em>start</em> before going into background and ceasing to send it's output anywhere where it may be of use.</p>
<p>So finally, thanks for replying with the -D suggestion. Though I was aware of that option it did not seem relevant to this issue.</p>
<p>best regards.</p> Lighttpd - Bug #2186: lack of output when lighttpd fails to starthttps://redmine.lighttpd.net/issues/2186?journal_id=87532016-02-13T08:30:18Zgstrauss
<ul></ul><p>Please close ticket.</p>
<p>Unable to reproduce problem with current version of trunk.</p>
<p>When I <code>chmod a-x tmp</code> and manually run lighttpd (without -D)<br />2016-02-13 03:27:12: (log.c.148) opening errorlog '.../tests/tmp/lighttpd/logs/lighttpd.error.log' failed: Permission denied</p>
<p>Running lighttpd -D is still a good step to take when troubleshooting startup problems.</p> Lighttpd - Bug #2186: lack of output when lighttpd fails to starthttps://redmine.lighttpd.net/issues/2186?journal_id=87592016-02-13T08:56:54Zstbuehler
<ul><li><strong>Status</strong> changed from <i>Need Feedback</i> to <i>Fixed</i></li></ul>