dns/db: info: Unable to get configuration from eDirectory failed with error 25

  • 7009924
  • 23-Dec-2011
  • 04-Apr-2014


Novell NetWare 6.5 Support Pack 8
Novell Open Enterprise Server 11 (OES 11) Linux
Novell Open Enterprise Server 2 (OES 2) Linux
Novell DNS


Add an A record to a zone and save it to eDir through the DNS/DHCP Management console or through iManager.
Restart the Novell DNS server that is authoritative for the zone you just added the A record to.
Test to see if that DNS server will resolve the newly added A record.
The DNS server is not resolving the newly added A record.

Check the /var/opt/novell/log/named/named.run file for errors:
dns/db: info: Unable to get configuration from eDirectory failed with error 25

Check the /var/log/messages for errors:
[NCPL]: Unable to get Journal Log attribute or SOA sr. no. with error 25
httpd2-worker: IPCCLNT -getCChannel- Channel Initialization failed for socket /var/opt/novell/xtier/xsrvd/srv-socket-2
httpd2-worker: IPCCLNT -SubmitReq- Channel unavailable
httpd2-worker: IPCCLNT -SubmitReq- Will attempt to retry RPC, count = 2
httpd2-worker: XSrvCChannel::connectSocket- Connection creation failed, error = 13
httpd2-worker: XSrvCChannel::init- Connection creation failed, error = 13
Introduced OES Linux into a NetWare tree and DNS starts reporting the same errors, or -601 errors.


DNS is failing to read information from eDir because xtier is failing to create a connection.
DNS uses xtier to talk to eDir

Check to see if the xtier daemons are running
rcnovell-xsrvd status
rcnovell-xregd status

If they are not running load them
rcnovell-xregd start
rcnovell-xsrvd start

Check again to see if they are running.

If they are running test the DNS server again and it will resolve the new record.
You can also verify that the new record has been read into cache and backed up to the file system by looking at the <zonename>.db file found in the /etc/opt/novell/named directory.

If the xtier daemons are not running after starting them then you will have to troubleshoot xtier.

At the time of this TID creation there were a couple of xtier TIDs that were useful:
TID# 3374174 talks about how to recreate the xtier database
TID# 3595588 talks about how to check that the rights to the directories for xtier are correct.
Follow Technical Information Document (TID) 7002316 - How To Recover Corrupt DNS and DHCP
Specifically, make sure all of the pointers are correct in the objects as outlined in the TID.
If that fails, delete and recreate the DNS server object (not the NCP server object).  This can be done in the Java Management Console.
If all else fails the eDirectory (eDir) replicas on the server may be corrupt.  Remove the replicas on the server (if any) and add them back, or try adding a local replica of the eDir containers where the DNS objects reside if there isn't one.  Be sure to run DSREPAIRs after the replica operations to resolve any issues (if any) before testing DNS again.