Re: [squid-users] Fw: squid crashes after running for a while

On Wed, May 27, 2009 at 4:08 AM, goody goody <thinkodd_at_yahoo.com> wrote:
>
> in addition to previous email, i am also receiving following messages in cache.log.
>
> comm_old_accept: FD 14: (53) Software caused
>> connection abort
>
> httpAccept: FD 14: accept failure: (53) Software
>> caused connection abort
>
> My current kernel entries are as follow. also suggest if still need to increase it. i have 2GB ram.
>
> kern.ipc.nmbclusters=32768
> kern.ipc.somaxconn=1024
> kern.maxfiles=32768
> kern.maxproc=8192
>
> Thanks,
> --- On Wed, 5/27/09, goody goody <thinkodd_at_yahoo.com> wrote:
>
>> From: goody goody <thinkodd_at_yahoo.com>
>> Subject: squid crashes after running for a while
>> To: squid-users_at_squid-cache.org
>> Date: Wednesday, May 27, 2009, 1:06 PM
>> Dear members,
>> I have setup a proxy on squid 3.0 stble 14 on freebsd 7.
>>
>> my proxy is behaving abnormally, it runs for afew hours and
>> then squid process closes unexpectdly (message displayed),
>> when i restart the squid it fails again until i dont restart
>> machine. after restarting it works well for a period then it
>> does the same. i am unable to identify the problem my cache
>> log gives the following messages.
>>
>> *********************************************************************
>> 2009/05/27 01:08:56| UFSSwapDir::doubleCheck: ENTRY SIZE:
>> 3342, FILE SIZE: 389
>> 2009/05/27 01:08:56| UFSSwapDir::dumpEntry: FILENO
>> 00000004
>> 2009/05/27 01:08:56| UFSSwapDir::dumpEntry: PATH
>> /cache1/00/00/00000004
>> 2009/05/27 01:08:56| StoreEntry->key:
>> B016EFEF1F5BDD7F96CC09CF4F64B217
>> 2009/05/27 01:08:56| StoreEntry->next: 0
>> 2009/05/27 01:08:56| StoreEntry->mem_obj: 0
>> 2009/05/27 01:08:56| StoreEntry->timestamp: 1243365627
>> 2009/05/27 01:08:56| StoreEntry->lastref: 1243365627
>> 2009/05/27 01:08:56| StoreEntry->expires: -1
>> 2009/05/27 01:08:56| StoreEntry->lastmod: 1221873935
>> 2009/05/27 01:08:56| StoreEntry->swap_file_sz: 3342
>> 2009/05/27 01:08:56| StoreEntry->refcount: 1
>> 2009/05/27 01:08:56| StoreEntry->flags:
>> CACHABLE,DISPATCHED
>> 2009/05/27 01:08:56| StoreEntry->swap_dirn: 0
>> 2009/05/27 01:08:56| StoreEntry->swap_filen: 4
>> 2009/05/27 01:08:56| StoreEntry->lock_count: 0
>> 2009/05/27 01:08:56| StoreEntry->mem_status: 0
>> 2009/05/27 01:08:56| StoreEntry->ping_status: 0
>> 2009/05/27 01:08:56| StoreEntry->store_status: 0
>> 2009/05/27 01:08:56| StoreEntry->swap_status: 2
>> 2009/05/27 01:08:56|   Completed Validation
>> Procedure
>> 2009/05/27 01:08:56|   Validated 97720
>> Entries
>> 2009/05/27 01:08:56|   store_swap_size =
>> 776190
>> 2009/05/27 01:08:56| assertion failed:
>> store_rebuild.cc:120: "store_errors == 0"
>> 2009/05/27 01:08:59| Starting Squid Cache version
>> 3.0.STABLE14 for i386-unknown-freebsd7.0...
>>
>> *********************************************************************
>>
>> df -i results
>>
>> Filesystem  1K-blocks    Used
>> Avail Capacity iused   ifree %iused
>> Mounted on
>> /dev/da0s1a  10154158  246910  9094916
>>    3%    2763 1316147
>> 0%   /
>> devfs
>>    1       1
>>       0   100%
>>    0       0
>> 100%   /dev
>> /dev/da0s1f  76168552  837956 69237112
>>    1%   56201 9788533
>>   1%   /cache1
>> /dev/da0s1g  76168552       4
>> 70075064     0%
>>    2 9844732
>> 0%   /cache2
>> /dev/da0s1e  40622796 2540572 34832402
>>    7%  312023 4940071
>> 6%   /usr
>> /dev/da0s1d  60931274  225310 55831464
>>    0%     337
>> 7889581    0%   /var
>>
>> I have specfied  cache size : cache_dir diskd /cache1
>> 60000 16 256 Q1=72 Q2=64
>>
>>
>> I dont know what to do, pls help me out.
>> An early reponse is requested, pls.
>> Regards,
>> .Goody.

Have you turned on the core dump functionality and set a core dump directory?

Using gdb to trace back through the core dump can help diagnose the
specific problem in more detail.

-- 
-george william herbert
george.herbert_at_gmail.com