Re: squid 1.1.21 dies with signal 6 every hour

> To me it looks like it is dying every hour (same second each hour).
>
> I strongly suspects that you have something running from crontab that
> makes Squid die.

Hmm, my crontab has 2 entries: one at 4:00 am and one at 0:00 at
the first day of every month...

>
> Signal 6 is SIGABORT, and this indicates that Squid detected a fatal
> error and exited. Check your cache.log for information on what error
> Squid detected.

Here are some extracts of the logfile. Apparently, it gets a SIGSEGV.
I think, the hardware is okay since 1.1.20 never showed these problems
and they startet from the moment I installed 1.1.21...

FATAL: Received Segment Violation...dying.
1998/03/26 14:00:01| storeWriteCleanLog: Starting...
1998/03/26 14:00:02| 4096 lines written so far.

--
FATAL: Received Segment Violation...dying.
1998/03/26 16:00:02| storeWriteCleanLog: Starting...
1998/03/26 16:00:02|      4096 lines written so far.
--
FATAL: Received Segment Violation...dying.
1998/03/26 17:00:02| storeWriteCleanLog: Starting...
1998/03/26 17:00:02|      4096 lines written so far.
--
FATAL: Received Segment Violation...dying.
1998/03/27 09:00:01| storeWriteCleanLog: Starting...
1998/03/27 09:00:02|      4096 lines written so far.
--
FATAL: Received Segment Violation...dying.
1998/03/27 10:00:03| storeWriteCleanLog: Starting...
1998/03/27 10:00:03|      4096 lines written so far.
--
FATAL: Received Segment Violation...dying.
1998/03/27 11:00:02| storeWriteCleanLog: Starting...
1998/03/27 11:00:02|      4096 lines written so far.
--
FATAL: Received Segment Violation...dying.
1998/03/27 12:00:01| storeWriteCleanLog: Starting...
1998/03/27 12:00:02|      4096 lines written so far.
--
FATAL: Received Segment Violation...dying.
1998/03/27 14:00:08| storeWriteCleanLog: Starting...
1998/03/27 14:00:08|      4096 lines written so far.
--
FATAL: Received Segment Violation...dying.
1998/03/27 15:00:02| storeWriteCleanLog: Starting...
1998/03/27 15:00:02|      4096 lines written so far.
--
FATAL: Received Segment Violation...dying.
1998/03/27 16:00:02| storeWriteCleanLog: Starting...
1998/03/27 16:00:02|      4096 lines written so far.
--
FATAL: Received Segment Violation...dying.
1998/03/27 18:00:02| storeWriteCleanLog: Starting...
1998/03/27 18:00:02|      4096 lines written so far.
--
FATAL: Received Segment Violation...dying.
1998/03/27 20:00:01| storeWriteCleanLog: Starting...
1998/03/27 20:00:01|      4096 lines written so far.
--
FATAL: Received Segment Violation...dying.
1998/03/27 22:00:02| storeWriteCleanLog: Starting...
1998/03/27 22:00:02|      4096 lines written so far.
> ---
> Henrik Nordström
> Sparetime Squid Hacker
> 
> 
> Dancer wrote:
> > Well, it's not actually dying _every_ hour, if I read it
> > correctly...It's dying after 60 minutes of operation, which
> > is something quite a bit different.
> 
> Andre Albsmeier wrote:
> > No, I rotate my logfiles once a month (Yes, they are big :-)).
> > Also, it doesn't happen always but only if there is activity.
> > For example, last friday it happend nearly every hour during
> > daytime but from friday night until now (sunday) it happend never.
> ....
> > Mar 27 09:00:08 curry.top.tld kern.info /kernel: pid 6821 (squid), uid 510: exited on signal 6
> > Mar 27 10:00:09 curry.top.tld kern.info /kernel: pid 11063 (squid), uid 510: exited on signal 6
> > Mar 27 11:00:08 curry.top.tld kern.info /kernel: pid 11304 (squid), uid 510: exited on signal 6
> > Mar 27 12:00:08 curry.top.tld kern.info /kernel: pid 11614 (squid), uid 510: exited on signal 6
> > Mar 27 14:00:15 curry.top.tld kern.info /kernel: pid 11970 (squid), uid 510: exited on signal 6
> > Mar 27 15:00:08 curry.top.tld kern.info /kernel: pid 12545 (squid), uid 510: exited on signal 6
>