Sounds known :)))))))
I faced this behaviour with 3.5 all time, which is forced me to jump to
4.x. 3.5 dies on my platform every shutdown, so this made it completely
unusable in production.
But 4.x has the similar issue:
http://bugs.squid-cache.org/show_bug.cgi?id=4438
10.03.16 16:16, Amos Jeffries пишет:
On 10/03/2016 4:41 p.m., Alex Samad wrote:
Hi
running
rpm -qa squid
squid-3.5.14-1.el6.x86_64
doing a restart saw this
2016/03/10 14:36:28 kid1| Squid Cache (Version 3.5.14): Exiting normally.
FATAL: Received Segment Violation...dying.
2016/03/10 14:36:28 kid1| storeDirWriteCleanLogs: Starting...
in cache.log
and message log
Mar 10 14:29:38 alcdmz1 squid[31939]: Squid Parent: will start 1 kids
Mar 10 14:29:38 alcdmz1 squid[31939]: Squid Parent: (squid-1) process
31941 started
Mar 10 14:36:28 alcdmz1 kernel: squid[31941]: segfault at 124c ip
000000000076bfd6 sp 00007ffff50359c0 error 6 in squid[400000+613000]
Thank you.
You will need to get a backtrace to find out if this is a known issue or
not. Either from a core generated already by that SEGFAULT, or by
running Squid in a debugger and repeating the issue.
Amos
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
