Bug 462060
| Summary: | named service crashes with an assertion failed message | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Adam Tkac <atkac> | ||||
| Component: | bind | Assignee: | Adam Tkac <atkac> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Martin Cermak <mcermak> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 4.7 | CC: | gimre, jwest, mprpic, ofourdan, ovasik, ralph, redhat-bugzilla, tao, william.smargiassi | ||||
| Target Milestone: | rc | Keywords: | ZStream | ||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Under certain conditions, the named daemon could exit due to an assertion failure. The following message was logged to /var/log/messages: named: socket.c:1649:
INSIST(!sock->pending_recv) failed named: exiting (due to assertion failure)
This update provides a fix to the socket module which prevents this assertion from failing, thus resolving the problem.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-02-16 14:04:15 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | 455802 | ||||||
| Bug Blocks: | 552534 | ||||||
| Attachments: |
|
||||||
|
Description
Adam Tkac
2008-09-12 11:22:49 UTC
Created attachment 317192 [details]
proposed patch
I've experienced this crash as well. RHEL 4.5 BIND version: bind-9.2.4-30.el4 (out of date, but I don't patch this system personally) From our logs: Oct 8 18:22:28 mlvv9n1x named[25034]: zone xxx.xxx.209.in-addr.arpa/IN: transferred serial 200307xxxx Oct 8 18:22:28 mlvv9n1x named[25034]: transfer of 'xxx.xxx.209.in-addr.arpa/IN' from xxx.xxx.xxx.132#53: end of transfer Oct 8 18:22:28 mlvv9n1x named[25034]: zone xxx.xxx.209.in-addr.arpa/IN: sending notifies (serial 200307xxxx) Oct 8 18:22:41 mlvv9n1x named[25034]: socket.c:1615: INSIST(!sock->pending_recv) failed Oct 8 18:22:41 mlvv9n1x named[25034]: exiting (due to assertion failure) This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. If you would like this request to be reviewed for the next minor release, ask your support representative to set the next rhel-x.y flag to "?". RHEL 4.7 now. Same bind version which now appears to be up to date? Yep, still happening: Dec 3 17:30:34 mlvv9n1x named[3834]: socket.c:1615: INSIST(!sock->pending_recv) failed Dec 3 17:30:34 mlvv9n1x named[3834]: exiting (due to assertion failure) If I have to request a support ticket, then why do you provide open access to bugzilla? Please reevaluate this bug fix dwhich has caused 2 BIND crashes on our primary internal name server. (In reply to comment #5) > If I have to request a support ticket, then why do you provide open access to > bugzilla? Please reevaluate this bug fix dwhich has caused 2 BIND crashes on > our primary internal name server. Could you fill support ticket, please? Bugs with corresponding support ticket are tracked with higher priority than bugs without support ticket. Direct access to bugzilla is mainly for people who don't use RH support. As this happens just occasionally, I'll stay in ON_QA and SanityOnly state. Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: * under certain conditions, the named daemon could exit due to an assertion failure. The following message was logged to /var/log/messages: named: socket.c:1649: INSIST(!sock->pending_recv) failed named: exiting (due to assertion failure) This update provides a fix to the socket module which prevents this assertion from failing, thus resolving the problem. Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,4 +1,4 @@ -* under certain conditions, the named daemon could exit due to an assertion failure. The following message was logged to /var/log/messages: named: socket.c:1649: +Under certain conditions, the named daemon could exit due to an assertion failure. The following message was logged to /var/log/messages: named: socket.c:1649: INSIST(!sock->pending_recv) failed named: exiting (due to assertion failure) An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0223.html |