Search squid archive

Re: Squid segfaults

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 18/03/2014 7:15 a.m., Eliezer Croitoru wrote:
> What cache dir? aufs?
> What OS?
> HW specs?
> 

More importantly:
 what do the Squid logs have to say about this? Squid always logs
something more useful than a random memory location in your specific
hardware.
 If you have somehow disabled cache.log. This is why it should always be
used even if set to "ALL,0" for minimal output, and/or written into syslog.


> On 17/03/2014 20:08, Alfredo Rezinovsky wrote:
>> segfault at 0 ip 00000000005929d3 sp 00007fff7756b068 error 4 in
>> squid[400000+318000]
>>
>> When this happens It segfaults again after restarting unless I remove
>> and rebuild the cache_dirs

Does it do the same if you only erase the swap.state from AUFS/diskd/UFS
cache_dir types?


>>
>> The proxy then works perfectly for a day or a whole month after crashing
>> again.
>>
>> Squid Cache: Version 3.3.11-20131212-r12669

Can I entice you to upgrade to 3.3.12 or even 3.4.4 ?
 Perhapse with the small possibility that the crash may have come from
one of the many bugs fixed in the later versions?

Amos




[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux