Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

strange problem: unable to start 'named'

Status
Not open for further replies.

holdahl

IS-IT--Management
Apr 4, 2006
213
NO
some time ago maintenance was done on our 2 pSeries machines.
nobody remember what was actually done (think it was an upgrade of the OS level (maint level)).
however, after this was done, the 'named' subsystem is unable to start on the second pSeries machine.
on the first machine something was done, and the 'named' subsystem is running on it.

I have tried to find some explanation of the software error code which is sent to the error-log when I try to start the 'named' subsystem.
seems quite hopeless to search google for this error.
have anyone heard of similar problems?
I have tried to restart the subsystem manually, but without any luck.

this is output from errpt -a
----------------------------------------------------------
root@#####:errpt -a | less
----------------------------------------
IDENTIFIER: BC3BE5A3

Date/Time: Wed Dec 13 14:21:46 2006
Sequence Number: 54951
Machine Id: 00513F0F4C00
Node Id: ######
Class: S
Type: PERM
Resource Name: SRC

Description
SOFTWARE PROGRAM ERROR

Probable Causes
APPLICATION PROGRAM

Failure Causes
SOFTWARE PROGRAM

Recommended Actions
MANUALLY RESTART SUBSYSTEM IF NEEDED

Detail Data
SYMPTOM CODE
256
SOFTWARE ERROR CODE
-9017
ERROR CODE
0
DETECTING MODULE
'srchevn.c'@line:'350'
FAILING MODULE
named
----------------------------------------------------------

sH
 
You don't indicate what version of AIX you are on, or what version of the nameserver (bind) you are running. If your system if configured to log all errors (*.debug) to syslog you should take a look there to see what the problem is. If not, then add this line to /etc/syslog.conf and restart the nameserver. Then look to see what it is reporting.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top