Bug 476581 - dnssec-signzone fails sporadically
dnssec-signzone fails sporadically
Product: Fedora
Classification: Fedora
Component: bind (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Adam Tkac
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-12-15 16:22 EST by Olle Liljenzin
Modified: 2013-04-30 19:42 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-07-14 11:00:32 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
core file (159.32 KB, application/x-tar)
2008-12-16 07:52 EST, Olle Liljenzin
no flags Details

  None (edit)
Description Olle Liljenzin 2008-12-15 16:22:01 EST
Version-Release number of selected component (if applicable):

Steps to Reproduce:
1. dnssec-signzone foo
2. dnssec-signzone foo
3. dnssec-signzone foo
task.c:311: REQUIRE(task->references > 0) failed.

Additional info:

dnssec-keygen -a rsasha1 -r /dev/urandom -b 1024 foo

foo	IN SOA	bar. root.bar. ( 1 1H 1H 1W 1H )
	IN NS	bar.
xyz.foo	IN A
$INCLUDE Kfoo.+005+37116.key
Comment 1 Adam Tkac 2008-12-16 06:34:56 EST
Could you please attach core dump? If you are using bash run

$ ulimit -c unlimited
$ dnssec-signzone foo

and upload core.XXXX file. Make sure you check "private" checkbox on attachment page if you are working with production DNSSEC keys.
Comment 2 Olle Liljenzin 2008-12-16 07:52:22 EST
Created attachment 327098 [details]
core file
Comment 3 Olle Liljenzin 2008-12-22 06:13:00 EST
To reproduce on a single core system:
'dnssec-signzone -n 2 foo'

And with one thread it never fails:
'dnssec-signzone -n 1 foo'

In other words I found a workaround that works for me. :-)
Comment 4 Bug Zapper 2009-06-09 23:25:50 EDT
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 5 Paul Wouters 2009-06-25 19:31:14 EDT
I've never seen this happen myself.....
Comment 6 Bug Zapper 2009-07-14 11:00:32 EDT
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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.

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.