Bug 1319584

Summary: squid assertion failure: FwdState.cc:444: "serverConnection() == conn"
Product: [Fedora] Fedora Reporter: Michael Chapman <redhat-bugzilla>
Component: squidAssignee: Luboš Uhliarik <luhliari>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: henrik, jonathansteffan, luhliari, psimerda, thozza
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:46:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Michael Chapman 2016-03-21 06:28:40 UTC
This bug is against squid-3.5.10-1.fc22.x86_64 .

Squid child processes regularly hit an assertion and SIGABRT:

# grep assertion /var/log/squid/cache.log
2016/03/20 12:59:05 kid1| assertion failed: FwdState.cc:444: "serverConnection() == conn"
2016/03/20 13:11:44 kid1| assertion failed: FwdState.cc:444: "serverConnection() == conn"
2016/03/21 15:50:35 kid1| assertion failed: FwdState.cc:444: "serverConnection() == conn"
2016/03/21 17:11:04 kid1| assertion failed: FwdState.cc:444: "serverConnection() == conn"
2016/03/21 17:11:21 kid1| assertion failed: FwdState.cc:444: "serverConnection() == conn"

The child process is restarted by the Squid master process.

Unfortunately I do not yet have a usable core dump -- ABRT seems to be hitting problems with SELinux and throwing away the core dump before I can get to it. I do believe it's the same bug as reported upstream at http://bugs.squid-cache.org/show_bug.cgi?id=4447 though.

Comment 1 Luboš Uhliarik 2016-07-18 10:54:06 UTC
Looks like, it is fixed in version 3.5.15. (http://bugs.squid-cache.org/show_bug.cgi?id=4447).

Comment 2 Fedora End Of Life 2016-07-19 18:46:36 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.