Re: Possible mod_scgi problem

> > Apache's log was full of 
> > [Wed Jun 29 13:55:15 2005] [warn] (101)Network is unreachable: connect to listener
> > messages, and when I tried to restart it, I couldn't. All of the apache
> > children processes were in status Z (zombie), which suggests that the
> > master process didn't react on SIGCLD signals.
> 
> It does seem possible that the problem could be a fd leak.  However,
> after looking at the code I don't see how that could happen.
> 
> Do you have still have the logs?  Are there any suspicious error
> messages before the "Network is unreachable: connect to listener"
> messages start to appear?

 
[Tue Jun 28 16:29:37 2005] [error] [client 62.162.xx.xx]
(111)Connection refused: scgi: Connection refused: scgi: can't connect to server
[Tue Jun 28 16:29:58 2005] [error] [client 62.162.xx.xx]
(111)Connection refused: scgi: Connection refused: scgi: can't connect to server
[Tue Jun 28 16:54:10 2005] 
[notice] child pid 5354 exit signal Segmentation fault (11)
[Tue Jun 28 17:42:46 2005] [warn] (101)Network is unreachable: connect
to listener

There's not much more in the logs except for some 404 errors that do not
corelate to my quixote app.



-- 
damjan | дамјан
This is my jabber ID --> [email protected] <-- not my mail address!!!