Mr. Rikunj a parment solution for this is to use cron to transfer or pargue the access.log periodically, it once hapenned to me and that was a solution
Kajiba > Thankyou once again henrik for guiding in the right direction. > > on passing squid -NCd1, got the error file size exceeded and it broke. > > Checked squid/var/logs and found access.log with 2.1GB size. > moved it to different name and re-ran the squid and it worked. > > Thankyou all who responded to this chain. > > Rp > > > ----- Original Message ----- > From: "Henrik Nordstrom" <[EMAIL PROTECTED]> > To: "Rp" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Thursday, August 12, 2004 4:07 PM > Subject: Re: [squid-users] Squid Crashes every few second!! > > >> On Thu, 12 Aug 2004, Rp wrote: >> >> > Yesterday the squid crashed giving no major clue for what went wrong. >> > The cache was cleaned and rebuild. After rebuilding the cache tried >> to > run >> > it again with no success, it crashes within few seconds. >> > No changes has been made in the configuration file. >> > >> > 2004/08/12 10:40:49| Closing Pinger socket on FD 15 >> > 2004/08/12 10:40:52| Starting Squid Cache version 2.5.STABLE1 for >> > i686-pc-linux-gnu... >> [repeated] >> >> See the Squid FAQ entry on how to report bugs. If you follow the >> procedure >> outlined there in how to get a stack trace if no core is found then more >> information should be available. >> >> Regards >> Henrik >> > > -- [EMAIL PROTECTED] www.esrftz.org
