Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 115933 - named starts and then returns error
Summary: named starts and then returns error
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: bind
Version: rawhide
Hardware: athlon
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks: FC2Blocker
TreeView+ depends on / blocked
 
Reported: 2004-02-17 09:15 UTC by Eric N. Ebert
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-02-20 05:54:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Eric N. Ebert 2004-02-17 09:15:49 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.2; Linux) (KHTML, like Gecko)

Description of problem:
When I start named from system-config-services it gives me a message saying that 'named start successfully'. However the following appears in the status box.

rndc:decode base 64 secret: bad base 64 encoding

When I try and stop named the following occurs:

named failed. The error was: stopping named: rndc: decode 
base 64 secret: bad base 64 encoding
[FAILED]

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

How reproducible:
Always

Steps to Reproduce:
1.Run /usr/bin/system-config-services
2.start named	
3.
    

Actual Results:  error noted above is returned

Expected Results:  named should start successfully

Additional info:

Comment 1 Eric N. Ebert 2004-02-20 05:54:48 UTC
This issue seems to have resolved itself. I'm running 
caching-nameserver 7.2-11 and bind 9.2.3-7 
 
 


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