Search squid archive

Re: Squid 3.3.6 FATAL: Received Segment Violation...dying.

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

 



Hey,

Can you please share more info from the cache.log??
when we will have this we can understand more.
If you can get a more verbose log using debug_options ALL,2 or ALL,3 it
will be much helpful then a single line.

If you are up to help debug it please refer to:
http://wiki.squid-cache.org/SquidFaq/BugReporting

Thanks,
Eliezer

On 07/12/2013 04:58 PM, x-man wrote:
> Hi,
> 
> I'm running squid 3.3.6 from a short time with simple TPROXY configuration,
> which was running perfectly with 3.1.19 for a very long time, but now with
> 3.3.6, started with workers 2 - I noticed that workers are dying frequently
> and what I see in the cache.log is 
> 
> FATAL: Received Segment Violation...dying.
> 
> 
> What can be the reason for this behavior, even having in mind that it's very
> low traffic, because I'm testing in office environment with few PCs
> connected only...
> 
> 
> 
> 
> 
> --
> View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-3-3-6-FATAL-Received-Segment-Violation-dying-tp4661026.html
> Sent from the Squid - Users mailing list archive at Nabble.com.
> 





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

  Powered by Linux