Bug 78904 - bind crashes after a bunch of reloads under high load
bind crashes after a bunch of reloads under high load
Product: Red Hat Linux
Classification: Retired
Component: bind (Show other bugs)
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Daniel Walsh
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2002-12-03 05:07 EST by Kirill Pushkin
Modified: 2007-04-18 12:48 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-01-16 16:01:54 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Kirill Pushkin 2002-12-03 05:07:37 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:

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

How reproducible:

Steps to Reproduce:
1. Configure name server with >= 800 zones
2. Reload it every 30 minutes with rndc reload (add or delete zones)
3. Wait 1-3 day(s)

Actual Results:  Dec  3 06:01:39 x-files named[6769]: adb.c:1746: fatal error:
Dec  3 06:01:39 x-files named[6769]:
s[bucket]))) == 0) ? 0 : 34) == 0) failed
Dec  3 06:01:39 x-files named[6769]: exiting (due to fatal error in library)

Expected Results:  It must work without crashes

Additional info:

RedHat Linux 7.2 with latest updates
Comment 1 Daniel Walsh 2003-01-07 11:34:20 EST
Named seems to be having a problem in multi-threaded smp environments.  ISC
seems to be recommending that you download the latest named package and build it
with threading turned off.  You could attempt this an see if the problem goes
away.  Red Hat has not decided how we are going to approach these problems yet.

Comment 2 Daniel Walsh 2003-01-16 16:01:54 EST
We believe this might be solved by the new threads library.  Please attempt this
with the latest Beta release of 8.1.


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