Re: [squid-users] Segment violation and assertion failed messages

On Thursday 01 May 2003 19.09, Scott Hudson wrote:
> Hi all,
>
> I'm running squid 2.5stable1 on Red Hat 7.3 with 2GB memory and the
> following messages continually rotate through my cache.log,
> separately, about every 5-10 minutes. The cache restarts after each
> of these messages and squid stays running.
>
>
> FATAL: Received Segment Violation...dying.
>
> 2003/05/01 08:17:12| assertion failed: store_client.c:201:
> "sc->callback == NULL"
>
> 2003/05/01 08:34:21| assertion failed: MemPool.c:275:
> "pool->meter.idle.level <= pool->meter.alloc.level"

Hmm.. a bit too many odd errors to be normal.. maybe a hardware
problem such as bad memory or similar. Try to run some hardware
tests.

  * memtest86 is a good free tool for testing memory.

  * Stress testing the system by continously rebuilding
    the Linux kernel is also a vary good test and may
    catch some issues memtest86 fails to detect.

If the hardware checks out okay, then first try to upgrade to
2.5.STABLE2. There has been a number of important bugs fixed and
maybe your symptoms is sideeffects of one of these already fixed
bugs.

If upgrading to 2.5.STABLE2 does not help, see

   Squid FAQ 11.19 Sending in Squid bug reports
   <url:http://www.squid-cache.org/Doc/FAQ/FAQ-11.html#ss11.19>

Regards
Henrik

-- 
Donations welcome if you consider my Free Squid support helpful.
https://www.paypal.com/xclick/business=hno%40squid-cache.org
If you need commercial Squid support or cost effective Squid or
firewall appliances please refer to MARA Systems AB, Sweden
http://www.marasystems.com/, info@marasystems.com