I replaced the memory (this box can't be out of service for very long)
and tested the memory, it checks out. Also the box still does the same
thing with the new memory. Any more ideas?
This message may contain confidential and/or proprietary information and
is intended for the person/entity to whom it was originally addressed.
Any use by others is strictly prohibited.
--
David "Bear" Bryant MCSE MCSA
Director of Technical Services
City of Ashland OH
bear@xxxxxxxxxxxxxxxx
computerhelp@xxxxxxxxxxxxxxxx
http:\\support.ashland-ohio.com
419-281-5162
Our Mission:To promote the highest quality
of life for our community by
providing leadership, service
and opportunity.
"Good judgment comes from experience, and experience comes from bad
judgment."
-- Barry LePatner --
Thomas wrote:
Hi there.
Something like this tells me it might not be Squid at all. I would
suggest you reboot your machine and run a full memory test on restart.
If that is OK then take it from there.
Regards
Thomas
-----Original Message-----
From: Bear <bear@xxxxxxxxxxxxxxxx>
To: Squid-Users@xxxxxxxxxxxxxxx
Subject: squid stops responding
Date: Fri, 24 Jul 2009 14:55:09 -0400
I have a Debian 2.6.18 box running squid 3.0 and dansguardian 2.8.0.6.
It has been in service almost 3 years without too many problems. When I
came in to work Monday I was informed the internet was inaccessible. The
first thing I did was check that dansguardian had restarted properly
after a logrotate, which it appeared to have. I eventually got around to
doing a restart of squid which worked. Since then squid just randomly
stops responding, the process is running and it's logging page requests
but it never delivers the pages. A restart of squid is the only way to
alleviate the problem. I've looked at the logs and there is nothing
there to indicate what happens, and the log files are not overly large
(one thing I read might cause this to happen). I also pruned the cache.
Any ideas, folks?
