codesite-noreply at google
Oct 16, 2009, 3:34 PM
Post #1 of 9
(120 views)
Permalink
|
|
Issue 606 in cherokee: Cherokee exits for some reason after an interpreter fails to start
|
|
Status: Accepted
Owner: ste...@konink.de
Labels: OpSys-BSD Type-Defect
New issue 606 by ste...@konink.de: Cherokee exits for some reason after an
interpreter fails to start
http://code.google.com/p/cherokee/issues/detail?id=606
What steps will reproduce the problem?
1. most likely have an interpreter spawned that has as an issue such (thus
fails)
2. do a request to start this interpreter
So what we see on the server side is:
[guest[at]shiva ~]$ sudo /usr/local/sbin/cherokee
Cherokee Web Server 0.99.24 (Oct 16 2009): Listening on port ALL:80, TLS
disabled, IPv6 disabled, using poll, 3520 fds system limit, max. 1753
connections, caching I/O, 5 threads, 350 connections per thread, standard
scheduling policy
PID 35938: launched '/bin/sh -c exec /usr/local/bin/php-cgi -b
localhost:47990' with uid=80, gid=80, env=custom
PID 35939: launched '/bin/sh -c exec /usr/local/bin/php-cgi -b
localhost:47990' with uid=80, gid=80, env=custom
PID 35940: launched '/bin/sh -c exec /usr/local/bin/php-cgi -b
localhost:47990' with uid=80, gid=80, env=custom
Server is exiting..
PID 35940: exited re=0
PID 35939: exited re=0
PID 35938: exited re=0
PID 35936: exited re=0
It looks like some sort of child process fails... and the signal arrives at
the parent?
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev
|
