On 04/10/10 01:54, Alvaro Lopez Ortega wrote:
On 03/10/2010, at 16:28, David Taylor wrote:
Any hints/suggestions on what I should do?
There's an internal "!debug = 1" flag that you could set in the information
source. It will log the interpreter stderr output in the error log file. It only works
when the 'File' and 'Standard Error' logging back-ends.
I hope that will shed some light on what this issue might be about.
With logging disabled Cherokee fails to exec spawn-fcgi and I see the
following output at the command line:
r...@hal:~# /usr/sbin/cherokee --admin_child -C /etc/cherokee/cherokee.conf
Cherokee Web Server 1.0.8 (Aug 18 2010): Listening on port ALL:80, TLS
disabled,
IPv6 enabled, using epoll, 4096 fds system limit, max. 2041 connections,
caching I/O, 20 threads, 102 connections per thread, standard scheduling
policy
PID 22960: launched '/bin/sh -c exec /usr/bin/spawn-fcgi -n -a 127.0.0.1
-p 53993 -- /usr/share/moin/server/moin.fcg' with uid=33, gid=33,
env=inherited
PID 22960: exited re=1
PID 22961: launched '/bin/sh -c exec /usr/bin/spawn-fcgi -n -a 127.0.0.1
-p 53993 -- /usr/share/moin/server/moin.fcg' with uid=33, gid=33,
env=inherited
PID 22961: exited re=1
PID 22962: launched '/bin/sh -c exec /usr/bin/spawn-fcgi -n -a 127.0.0.1
-p 53993 -- /usr/share/moin/server/moin.fcg' with uid=33, gid=33,
env=inherited
PID 22962: exited re=1
PID 22963: launched '/bin/sh -c exec /usr/bin/spawn-fcgi -n -a 127.0.0.1
-p 53993 -- /usr/share/moin/server/moin.fcg' with uid=33, gid=33,
env=inherited
PID 22963: exited re=1
PID 22964: launched '/bin/sh -c exec /usr/bin/spawn-fcgi -n -a 127.0.0.1
-p 53993 -- /usr/share/moin/server/moin.fcg' with uid=33, gid=33,
env=inherited
PID 22964: exited re=1
With logging enabled Cherokee is able to exec spawn-fcgi and I see the
following output at the command line:
r...@hal:~# /usr/sbin/cherokee --admin_child -C /etc/cherokee/cherokee.conf
Cherokee Web Server 1.0.8 (Aug 18 2010): Listening on port ALL:80, TLS
disabled,
IPv6 enabled, using epoll, 4096 fds system limit, max. 2041 connections,
caching I/O, 20 threads, 102 connections per thread, standard scheduling
policy
PID 22799: launched '/bin/sh -c exec /usr/bin/spawn-fcgi -n -a 127.0.0.1
-p 53993 -- /usr/share/moin/server/moin.fcg' with uid=33, gid=33,
env=inherited
... and the following in my cherokee.error log:
2010-10-04 14:00:57,540 WARNING MoinMoin.log:120 using logging
configuration read from built-in fallback in MoinMoin.log module!
2010-10-04 14:00:58,513 INFO MoinMoin.config.multiconfig:90 using farm
config: /etc/moin/farmconfig.pyc
2010-10-04 14:00:58,518 INFO MoinMoin.config.multiconfig:124 using wiki
config: /etc/moin/cloudartisan.pyc
I have tested this with and without the !debug = 1 flag -- it does not
affect the behaviour I described above.
I have tested this repeatedly with and without error logging. It is
reproducible every time. With error logging disabled, "/bin/sh -c exec
spawn-fcgi ..." does not work. With error logging enabled, "/bin/sh -c
exec spawn-fcgi ..." works.
I've CC'd the package maintainer for spawn-fcgi. I'm using spawn-fcgi
on Debian Lenny from the testing repository:
Package: spawn-fcgi
Priority: extra
Section: web
Installed-Size: 96
Maintainer: Jérémy Lal <[email protected]>
Architecture: i386
Version: 1.6.3-1
Depends: libc6 (>= 2.1)
Filename: pool/main/s/spawn-fcgi/spawn-fcgi_1.6.3-1_i386.deb
Thanks Alvaro. Technically there's still some problem under the hood,
but for now I have a fix and hopefully someone working on Cherokee
and/or spawn-fcgi has enough information to reproduce the problem and
fix it.
Cheers guys,
David.
--
Octality
http://www.octality.com/
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee
