nobaloney
NoBaloney Internet Svcs - In Memoriam †
I've just searched a lot of threads on problems with apache stopping and not restarting but I haven't fund this particular issue:
Found Apache not running on a server (probably because of restart after logrotate). Restarted it; message was that it couldn't restart because other processes were binding to port 80.
Netstat reported syslogd was listening on port 80. I shut it down. Same error on restart. Netstat then reported acpid listening on port 80. I shut it down. Same error on restart.
Rebooted server and apache came up properly.
Has anyone seen this problem before, where if you kill the process listening on port 80 another immediately starts listening on port 80?
Thanks.
Jeff
Found Apache not running on a server (probably because of restart after logrotate). Restarted it; message was that it couldn't restart because other processes were binding to port 80.
Netstat reported syslogd was listening on port 80. I shut it down. Same error on restart. Netstat then reported acpid listening on port 80. I shut it down. Same error on restart.
Rebooted server and apache came up properly.
Has anyone seen this problem before, where if you kill the process listening on port 80 another immediately starts listening on port 80?
Thanks.
Jeff