severity 728144 serious
notforwarded 728144
merge 771778 728144
thanks
I think we have enough hints now to say that the original reports
initiating #771778 and #728144 are the same segfault.
I was wrong about the link to upstream bug #2656 for these two crashes,
that was for the third one that
tags 771778 -unreproducible -wontfix
severity 771778 serious
thanks
I can reproduce this very often.
In my system, it seems to happen around 7:35, most probably triggered
by /etc/logrotate.d/squid3.
[Oct30 07:35] pinger[1959]: segfault at 7a7585d0098 ip 7f4966b96b05 sp
7ffc1a77e4a0
Package: squid3
Version: 3.4.8-6
Followup-For: Bug #771778
Hi, since upgrading to jessie I have noticed pinger segfaulting on three
separate installations. I am using the stock squid3 3.4.8-6 package and
it's dependencies. Initially I had ignored the complaints (kernel
message sent via
On Sun, May 17 2015, Gerald Turner wrote:
Unfortunately my attempts to get a core dump have been futile ...
I finally got a backtrace of pinger with gdb:
#0 0x7fcad0a30107 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x7fcad0a314e8 in __GI_abort ()
Package: squid3
Version: 3.4.8-2
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
5 matches
Mail list logo
