Bug 1319584 - squid assertion failure: FwdState.cc:444: "serverConnection() == conn"
Summary: squid assertion failure: FwdState.cc:444: "serverConnection() == conn"
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: squid
Version: 22
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Luboš Uhliarik
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-21 06:28 UTC by Michael Chapman
Modified: 2016-07-19 18:46 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 18:46:36 UTC
Type: Bug


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.