[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [suse-security] Squid crashing

This isn't the forum for this, but I happen to be a squid admin..

What version of squid? 
Anything in cache.log? grep for fatal or FATAL.
Are you doing logrotation (I think logs >2GB cause problems).

> -----Original Message-----
> From: Watson, Michael [mailto:MWatso@xxxxxxxxxx]
> Sent: Thursday, May 20, 2004 12:31 PM
> To: suse-security@xxxxxxxx
> Subject: [suse-security] Squid crashing
> Greetings,
> I'm not entirely sure this is the right place to post a 
> question like this,
> but if anyone has any suggestions, I'd love to hear them.
> I'm running squid on suse 9.0 professional, and have run into 
> a problem.
> Every couple of days, squid seems to stop working. Users 
> attempt to connect
> to the web through squid, but never see their target webpage. 
> If I reboot
> the system, squid starts working again, but a few days later, 
> the same thing
> seems to happen all over again. I ran squid for a couple of 
> years on red
> hat, and never ran into this problem--it started when I made 
> the move to
> suse. 
> I am looking into adjusting squid's error logging to help 
> track down this
> problem, but in the meantime I thought I'd also ask if anyone 
> is aware of
> any known issues running squid on suse 9.0.
> Thanks,
> Mike Watson
> mwatso@xxxxxxxxxx

This electronic message transmission is a PRIVATE communication which contains
information which may be confidential or privileged. The information is intended 
to be for the use of the individual or entity named above. If you are not the 
intended recipient, please be aware that any disclosure, copying, distribution 
or use of the contents of this information is prohibited. Please notify the
sender  of the delivery error by replying to this message, or notify us by
telephone (877-633-2436, ext. 0), and then delete it from your system.

Check the headers for your unsubscription address
For additional commands, e-mail: suse-security-help@xxxxxxxx
Security-related bug reports go to security@xxxxxxx, not here