I've encountered the same problem. First if you wanna examine the core
the you have to enable first since the kernel 2.2.1 (& maybe other
versions) doesn't allow core by defaults. This can be easily accomplished
by "ulimit -c unlimited".
But my guess is that the cause for this is either the memory of cpu usage
under allocation of alot of disk space for caching.
First I set 3Gb of HDD for that using only 8MB of RAM, then I increased
the RAM to 15M (as the docs states, 5 megs for each gig of hdd) and the
number of crashes decreased alot. Finally I droppped to 2 partitions on 2
disks of about 100 megs each and since then I had no probs.
C.
On Mon, 8 Feb 1999, Emili Badia wrote:
> We've received the next message from squid:
>
> >You've encountered a fatal error in the Squid Cache version 2.2.PRE2.
> >If a core file was created (possibly in the swap directory),
> >please execute 'gdb squid core' or 'dbx squid core', then type 'where',
> >and report the trace back to squid-bugs@ircache.net.
> >
> >Thanks!
>
> No core file was created. Only have found this message in th cache.log:
>
> FATAL: Received Segment Violation...dying.
>
> Any idea on what's happening?
> Thank you.
>
>
>
Received on Mon Feb 08 1999 - 09:30:21 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:44:29 MST