Possible mod_scgi problem

I'm using mod_scgi from the scgi-1.4 package in Apache-2.0.53.
The config I have in httpd.conf is very simple:
    <Location "/myapp/">
        SCGIServer localhost:4000
        SCGIHandler On
    </Location>

Everything works pretty good at first, but I've noticed that after my
quixote scgi application was not running for a while (2 days I think),
mod_scgi stoped working, because even after I started my scgi
application I still couldn't access my application.

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.

I had to 'kill -9' apache, and then start it again, and then everything
was normal again.

Might there be some resource leak in mod_scgi for Apache-2.0??

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