Bug 489660 - Bind exited with assertion related to result variable
Summary: Bind exited with assertion related to result variable
Keywords:
Status: CLOSED DUPLICATE of bug 475202
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: bind
Version: 4.7
Hardware: i686
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Adam Tkac
QA Contact: BaseOS QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-11 09:31 UTC by masevac
Modified: 2013-04-30 23:42 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-11 10:27:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description masevac 2009-03-11 09:31:41 UTC
Hi, 
  I have 8 servers with named which are synchronized using rndc.
  Yesterday, 4 of the 8 server exited at the same time.
  After looking in logs, the only relevant lines I found is
---BEGIN---
Mar 10 13:01:03 server named[3334]: view.c:1116: INSIST(result == 0 || result == 23) failed
Mar 10 13:01:03 server named[3334]: exiting (due to assertion failure)
---END---

  In those server I have two different versions of CentOS (4.7 and 5.2) and so, different versions of named. Anyway 3 servers 4.7 and 1 server 5.2 stopped. The remaining server had not any problem. The also have CentOS versions 4.7 and 5.2, and the same named versions 9.2.4 and 9.3.4-P1
   

Version-Release number of selected component (if applicable):
9.2.4
9.3.4-P1

As far as I know the problem it's not reproducible

  
Actual results:
The named server exited

Expected results:
The named server will continue to run

Additional info:
I checked all named log lines, and there are not any more line relevant in the moment of the "sinchronized" exit. All warnings/errors are usual in log file, they are not only at moment of the exit.

Comment 1 masevac 2009-03-11 09:36:16 UTC
Created bug https://bugzilla.redhat.com/show_bug.cgi?id=489662 for version 5.2

Comment 2 Adam Tkac 2009-03-11 10:27:16 UTC

*** This bug has been marked as a duplicate of bug 475202 ***


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