httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hugh Beaumont <>
Subject [users@httpd] start/stop scripts + problems with user spawned processes blocking server restart
Date Wed, 08 Jan 2003 17:33:33 GMT

I have searched the archives and not been able to find the solution to 
the following problem. I would be very grateful if someone here could
help or provide some pointers.

The basic problem is this:

Our apache server will not start if there are system processes running
that were spawned from apache's last invocation (ie. spawned from
cgi's, mod_php system() calls, etc.). It dies with "cannot bind to ip_address_here port 80",


We restart our servers every so often via crontab in order to reload
modified conf files, etc.  However it appears that if
a user has spawned a process from mod_php, cgi, etc. that the server will
not restart until those processes are killed off manually. 

The worst cases are when badly wrote user scripts allow an attacker to
upload scripts that bind to a port and attempt to make network access, etc.
(I would love to disallow users from having uploads to the server but 
that is not currently an option).

Does anyone have any suggestion on how to automagically kill these

Does anyone have their own favorite recipe for stopping/starting apache
in an automated fashion.

Right now these situations result in downtime for users and a pager in
the middle of the night to me! I would very much like to stop this :)

Thanks much!

Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message