Hello Michael, Friday, October 19, 2001, 1:49:48 PM, you wrote:
MS> I've found this in /var/log/httpd/error_log: MS> [Fri Oct 19 18:14:18 2001] [crit] (98)Address already in MS> use: make_sock: could not bind to port 80 IIRC, Apache will only "bind" itself to a specified port upon start/restart/reload. MS> Around that time the server was idle for over an hour according to MS> access_log. I haven't touched it since then. It is still working, MS> bound to port 80 with several childs. I don't recall having seen MS> that error before. And I don't understand why it would try to bind MS> to port 80 when there haven't been any requests. But I suspect it MS> could be related to the latest updates. Did you see a message to the tune of: [DATE] [notice] "SIGHUP received. Attempting to restart " before the [crit]? Maybe something tried to "kill -HUP" your Apache and failed for some reason or another? It happens to me once in a while -- stubborn children not exiting completely before the restart/reload. Other than that, sounds like it might have been something / someone trying to start Apache w/o checking to see if it was already running. Have you tried to restart Apache just to make sure everything _is_ working as intended? -- Best regards, Brian Curtis _______________________________________________ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
