On 17/11/17 03:49, Bike dernikov1 wrote:
On Thu, Nov 16, 2017 at 8:58 AM, Amos Jeffries wrote:
On 16/11/17 01:32, Bike dernikov1 wrote:
If i can ask under same title:
Yesterday we had error in logs: syslog, cache.log, dmesg,access.log
segfault at 8 ip ....... sp ..... error 4 is squid
process pid exited due to signal 11 with status 0
Squid restarted, that was at the end of work, and i didn't notice
change while surfing.
I noticed change in used memory, after i went trough logs, and found
segfault.
Can you point me, how to analyze what happened.
Can that be problem with kernel ?
How to retrieve info about these type of things is detailed at
<https://wiki.squid-cache.org/SquidFaq/BugReporting>.
I wasn't sure it is bug, so i didn't want to post it that is a bug.
As you now confirm that it can be bug i will prepare for retriving
infos.
I just hope that bug won't happen at high load in middle of working day.
The how-to are just on that page because if you are reporting that kind
of bug those details are mandatory. You dont have to be reporting a bug
to use the techniques.
That said, segfault is almost always a bug. Though it could be a bug in
the system environment or hardware rather than Squid. The details you
get from looking at the traces should indicate whether those are actual
or not.
NP: If you do not have core files enabled, then the data from that segfault
is probably gone irretrievably. You may need to use the script to capture
segfault details from a running proxy (the 'minimal downtime' section).
I am sure that i didn't enabled it.
Okay, then you will need to for further diagnosis.
Amos
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
