RE: [squid-users] Squid dies unexpectedly

Hello,

> > I've got a weird problem... Since today, squid began to die
> due to signal 6.
> > I've made no changes to the system nor to the squid
> configuration - but for
> > increasing the cache_mem to 64 MB and increasing the disk
> space for the
> > cache. The syslogd tells me that squid dies by signal 6
> (SIGABRT on my
> > system - mostly a vanilla RH80):
> >
> > --> cut here <--
> > Jan 7 14:58:27 leningrad squid[23684]: Squid Parent: child
> process 23686
> > exited due to signal 6
> > --> cut here <--
>
> Make sure, for instance, that none of the log files are too big,or
> stated otherwise are enormously big.
> Same for swap.state file(s) in cache directories.
>

Nope. I've had this kind of problem yesterday (logrotate messed up,
therefore access.log was 2GB), and it resulted in signal 25. However, I've
double-Checked all files - nothing that sort... :-(

What's about that assertion? Does anyone know anything about it?

Regards

Dmitri Barski
Serveradministration UNIX

ElectronicPartner Handel GmbH
Mündelheimer Weg 40
40472 Düsseldorf

Tel.: +49-211-4156-6766
Mobil: +49-172-7816303
Fax: +49-211-4156-380
E-Mail: dbarski@electronicpartner.de

> M.
>
> >
> > The squid log itself tells me smth. about:
> > --> cache.log <--
> > 2003/01/07 14:58:27| ftpDataWriteCallback: write error:
> (11) Resource
> > temporarily unavailable
> > 2003/01/07 14:58:27| assertion failed: comm.c:646: "F->flags.open"
> > 2003/01/07 14:58:30| Starting Squid Cache version 2.5.STABLE1 for
> > i686-pc-linux-gnu...
> > 2003/01/07 14:58:30| Process ID 31571
> > 2003/01/07 14:58:30| With 1024 file descriptors available
> > 2003/01/07 14:58:30| DNS Socket created at 0.0.0.0, port 33003, FD 5
> > 2003/01/07 14:58:30| Adding nameserver xxx.xxx.xxx.xxx from
> /etc/resolv.conf
> > [...]
> > 2003/01/07 14:58:32| store_swap_size = 878876k
> > 2003/01/07 14:58:33| storeLateRelease: released 0 objects
> > --> cache.log <--
> >
> > I think, the first two lines are importtant.
> >
> > There is nothing unusual in other logfiles...
> >
> > Does anyone have an idea what could be happening?
> >
Received on Tue Jan 07 2003 - 08:16:56 MST