Bug#543480: lighttpd: FastCGI socket handling prevents php configuration changes

2009-10-10 Thread Stefan Bühler
Hi,

you are right: removing the sockets would result in lighty spawning new 
backends. But the problem is that php doesn't die, and if you just remove the 
sockets, you will just create more hanging processes.

If you (or someone else who has the problem, that stopping lighty doesn't kill 
the spawned backends) can find out why that really could help.

I always recommend spawning FastCGI backends with spawn-fcgi from supervise 
(daemontools) or runit; that way you can restart your applications 
independently.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#543480: lighttpd: FastCGI socket handling prevents php configuration changes

2009-08-25 Thread Deny Dias

Package: lighttpd
Version: 1.4.19-5
Severity: important

After install php5-ldap package, I noted that it was not being loaded  
by php instance spawned by lighttpd. I then change some settings in / 
etc/php5/cgi/php.ini, but that changes was not reflected on phpinfo()  
output. I then moved /etc/php5 entirely to another location, I  
restarted lighttpd. Surprinsigly, lighttpd was able to restart cleanly  
even without php core setting files with no error log entries. I then  
enabled fastcgi.debug and again I could verify that it php was being  
loaded correctly even without no initialization files. So I moved php  
files back to its place and then removed /tmp/php.socket manually.  
After that and to restart lighttpd, all my configurantions and modules  
was loaded correctly. I have about 10 lenny boxes where this issue  
present exactly in the same way. Their configuration are very similiar  
with the one from this report.


When this bug first presented to me, I thought it was related to php5- 
ldap itself, so I opened a bug report there that further investigation  
lead to a lighty related thing. Following is the url for this first  
bugreport:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535253

I think that a possible solution could be remove fastcgi parser  
sockets upon stop with lighty init script.


Best,

Deny Dias.

-- System Information:
Debian Release: 5.0.1
APT prefers stable
APT policy: (990, 'stable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages lighttpd depends on:
ii  libattr1   1:2.4.43-2Extended attribute shared  
library
ii  libbz2-1.0 1.0.5-1   high-quality block- 
sorting file co
ii  libc6  2.9-12GNU C Library: Shared  
libraries
ii  libfam02.7.0-13.3Client library to control  
the FAM

ii  libldap-2.4-2  2.4.11-1  OpenLDAP libraries
ii  libpcre3   7.6-2.1   Perl 5 Compatible Regular  
Expressi

ii  libssl0.9.80.9.8g-15+lenny1  SSL shared libraries
ii  libterm-readline-perl- 1.0302-1  Perl implementation of  
Readline li
ii  lsb-base   3.2-20Linux Standard Base 3.2  
init scrip
ii  mime-support   3.44-1MIME files 'mime.types'   
'mailcap
ii  zlib1g 1:1.2.3.3.dfsg-12 compression library -  
runtime


lighttpd recommends no packages.

Versions of packages lighttpd suggests:
ii  apache2-utils   2.2.9-10+lenny2  utility programs for  
webservers
ii  openssl 0.9.8g-15+lenny1 Secure Socket Layer (SSL)  
binary a
ii  rrdtool 1.3.1-4  Time-series data storage  
and displ


-- no debconf information



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org