Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 176377 - www-servers/lighttpd-1.4.15 fails to stop running with fcgi in use
Summary: www-servers/lighttpd-1.4.15 fails to stop running with fcgi in use
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: www-servers Herd (OBSOLETE)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-28 17:13 UTC by Eric Brown
Modified: 2007-09-19 23:09 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Brown 2007-04-28 17:13:57 UTC
For the past several versions of lighttpd, I have noticed that /etc/init.d/lighttpd stop does not actually kill the server processes.  It seems to be related to the use of the fast-cgi configuration options being used, since non-fcgi machines likely do not experience this problem.

The init script reports [OK] when it fails to stop the processes.  The problem can be worked around with killall lighttpd.

It is also probably related to the design of lighttpd, it probably has a controlling process that lies about the status of its startup and shutdown and simply reports OK when it daemonizes or dies (not sure).

This bug also implies that init.d/lighttpd's restart function also would fail.

I suppose a possible solution might be similar to one suggested in this bug:

http://bugs.gentoo.org/show_bug.cgi?id=112084

Reproducible: Always
Comment 1 Thilo Bangert (RETIRED) (RETIRED) gentoo-dev 2007-08-26 19:38:21 UTC
i can't reproduce the problem, so probably i am doing something wrong. can you please reiterate the exact steps that exhibit the bug?

are you running fastcgi applications using spawn-fcgi? if so, could i perhaps get you to try the spawn-fcgi scripts provided at bug #149467.
thanks
Comment 2 Eric Brown 2007-09-19 23:09:43 UTC
The problem seems to have gone away in newer versions of lighttpd.  I think someone just changed the init script.