Bug 4455 - 'FATAL: Received Segment Violation' from ESIInclude::Start
Summary: 'FATAL: Received Segment Violation' from ESIInclude::Start
Status: RESOLVED FIXED
Alias: None
Product: Squid
Classification: Unclassified
Component: other: Edge Side Includes (ESI) (show other bugs)
Version: 3.2
Hardware: HP Linux - All
: P5 normal
Assignee: SQUID BUGS ALIAS
URL:
Depends on:
Blocks:
 
Reported: 2016-03-02 15:12 UTC by bfek-18
Modified: 2024-04-05 01:45 UTC (History)
0 users

See Also:
Browser: ---
Fixed Versions: 4.0.10, 3.5.18
Needs:


Attachments
gdb output (4.58 KB, text/plain)
2016-03-02 15:12 UTC, bfek-18
Details
Squid-3.5 patch (1.18 KB, patch)
2016-04-30 19:58 UTC, Amos Jeffries
Details

Note You need to log in before you can comment on or make changes to this bug.
Description bfek-18 2016-03-02 15:12:12 UTC
Created attachment 3301 [details]
gdb output

crash without giving reasons
Comment 1 bfek-18 2016-03-02 15:50:36 UTC
Version 3.5.14
Comment 2 bfek-18 2016-03-04 08:15:01 UTC
error still prasent in 3.5.15
Comment 3 bfek-18 2016-04-30 15:08:29 UTC
The following data come before the crash squid:

2016/04/30 16:56:23.654 kid1| Esi.cc(753) esiProcessStream: esiProcessStream: Processing thisNode 0x8c6e448 context 0x8c539c8 offset 0 length 0
2016/04/30 16:56:23.655 kid1| Esi.cc(753) esiProcessStream: esiProcessStream: Processing thisNode 0x8c6e448 context 0x8c539c8 offset 0 length 4096
2016/04/30 16:56:23.655 kid1| Esi.cc(753) esiProcessStream: esiProcessStream: Processing thisNode 0x8c6e448 context 0x8c539c8 offset 4096 length 4096
2016/04/30 16:56:23.655 kid1| Esi.cc(753) esiProcessStream: esiProcessStream: Processing thisNode 0x8c6e448 context 0x8c539c8 offset 8192 length 3161
2016/04/30 16:56:23.670 kid1| Esi.cc(753) esiProcessStream: esiProcessStream: Processing thisNode 0x8c6e448 context 0x8c539c8 offset 11353 length 0
2016/04/30 16:56:23.671 kid1| Sequence.cc(193) addElement: esiSequenceAdd: Added a new element, elements = 1
2016/04/30 16:56:23.671 kid1| Sequence.cc(193) addElement: esiSequenceAdd: Added a new element, elements = 2
2016/04/30 16:56:23.671 kid1| Sequence.cc(193) addElement: esiSequenceAdd: Added a new element, elements = 3
2016/04/30 16:56:23.671 kid1| Sequence.cc(193) addElement: esiSequenceAdd: Added a new element, elements = 4
2016/04/30 16:56:23.671 kid1| Sequence.cc(193) addElement: esiSequenceAdd: Added a new element, elements = 5
2016/04/30 16:56:23.671 kid1| Sequence.cc(193) addElement: esiSequenceAdd: Added a new element, elements = 1
2016/04/30 16:56:23.671 kid1| Sequence.cc(193) addElement: esiSequenceAdd: Added a new element, elements = 2
2016/04/30 16:56:23.671 kid1| Sequence.cc(193) addElement: esiSequenceAdd: Added a new element, elements = 3
2016/04/30 16:56:23.671 kid1| Sequence.cc(193) addElement: esiSequenceAdd: Added a new element, elements = 4
2016/04/30 16:56:23.671 kid1| Sequence.cc(193) addElement: esiSequenceAdd: Added a new element, elements = 5
FATAL: Received Segment Violation...dying.
Comment 4 Amos Jeffries 2016-04-30 19:58:39 UTC
Created attachment 3351 [details]
Squid-3.5 patch

Some requests are generated by Squid, not a client. This patch ignores the client connection state setup for internal requests.
Comment 5 bfek-18 2016-05-02 15:34:27 UTC
Thank you very much.
The patch is going well. For three days no crash.
Comment 6 Amos Jeffries 2016-05-03 01:48:31 UTC
Thanks. Applied to Squid-4.
Comment 7 bfek-18 2016-05-03 06:03:04 UTC
please also squid-3.5
Comment 8 Amos Jeffries 2016-05-06 09:14:59 UTC
The cause of this issue seems to exist as far back as 3.2.

Applied to 3.5, 3.4, 3.3, and 3.2.