Project

General

Profile

Bug #624

Lighttpd hangs or fails to start through SSH

Added by Anonymous over 10 years ago. Updated about 8 years ago.

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

0%

Missing in 1.5.x:

Description

I believe my problem is related to this debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355865

No idea whether that patch would work for me as I am using a custom restart script written in Ruby. I have tried forking a new thread to start lighttpd and then detaching it but that hasn't worked.

Basically, when starting lighty through SSH it tends to hang. I have been deploying a Rails app with Capistrano. In this circumstance sometimes Capistrano will not hang, but instead the process will start successfully and then immediately stop. Either way I tend to have to intervene when deploying which is of course not ideal.

The development server I've been using is Ubuntu Breezy, and the deployment server is FC1. I have the problem on both.

Let me know if I can provide any more information.

Thanks

-- turnip

Associated revisions

Revision 93e7167f (diff)
Added by stbuehler about 8 years ago

Implement a clean way to open /dev/null and use it to close stdin/out/err in the needed places (#624)

- as stderr gets redirected to /dev/null before exec in childs, we cannot
write to the log afterwards, so disabled that log messages too.

git-svn-id: svn://svn.lighttpd.net/lighttpd/branches/lighttpd-1.4.x@2163 152afb58-edef-0310-8abb-c4023f1b3aa9

History

#1 Updated by moo over 10 years ago

that means lighttpd may not detach correctly (in case u don't use -D)
workaround: lighttpd -f conf </dev/null >/dev/null 2>&1.

i'll keep this ticket open..

#2 Updated by Anonymous almost 9 years ago

I just came across this exact problem, but on FreeBSD (on textdrive). I was using vlad, not capistrano, so odd ssh issues are out of the question as well. I can confirm that moo's workaround indeed works. It would be nice if lighttpd detached properly.

-- ryand-ruby

#3 Updated by stbuehler over 8 years ago

  • Status changed from New to Fixed
  • Resolution set to fixed

I cannot reproduce it in current version, so i guess this was fixed.

Please give more details if you disagree (attach config)

#4 Updated by stbuehler about 8 years ago

Darix told me i am wrong, so i looked at it again; it seems that (at least) debian has a workaround in the ssh server for this, so i had to use lsof to see lighty having the files still open.

I hope i fixed that problems in r2163 now.

Also available in: Atom