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,
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|
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
