https://bugzilla.novell.com/show_bug.cgi?id=388088
User lyeoh@inter-touch.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=388088#c13
--- Comment #13 from Lincoln Yeoh 2008-05-19 10:47:19 MST ---
It's probably as what you say, perhaps it is a race condition and only happens
under load and is related to the size of the logs being rotated (since suse
10.2 runs /etc/init.d/squid reload for each log file - 3 times).
As far as I know it doesn't happen that often on our live sites but it
definitely has happened on more than two sites on different occasions- and
given that squid does continue running (albeit only on 127.0.0.1), I do not
think that somebody did something strange directly to the site.
The other explanation would be the 202.75.242.254 interface going down around
the time of log rotation _and_ somehow coming back up again (since it was
obviously not down). I think this is very unlikely to be the cause.
For what it's worth, I have also noticed that at some sites squid is restarting
the redirectors as root instead of squid!
Anyway, as per comment #6, we are taking measures to avoid requiring squid to
attempt to release and rebind to ports in the first place (which appears to
occur with suse's /etc/init.d/squid reload ). So instead of doing suse 10.2
style of squid -k rotate; sleep 2; squid -k reconfigure potentially for _each_
squid log to be rotated, we will now just do squid -k rotate once for all 3
squid logs.
This should hopefully avoid the following undesirables (estimate in brackets):
1) squid not rebinding on all required ports (very likely to work)
2) squid reloading its config every day when admins might not be around (100%)
3) squid restarting redirector processes as root (might help, but not a big
issue)
However this is also likely to reduce the odds of us reproducing the problem
and doing your suggested debugging.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.