Operating System - HP-UX
1833788 Members
2402 Online
110063 Solutions
New Discussion

Networker daemons will not start after reboot/shutdown

 
Ian Cameron
Frequent Advisor

Networker daemons will not start after reboot/shutdown

Hello everyone,

I apologize if this shows up after the original post but I sent it in yesterday afternoon and still have not seen it on list.

I have three installations running Networker 5.5.1 build 115 running on c-class servers backing up 10 - 20 HP and NT clients. Almost every time, at all sites, when we shutdown and restart or even just reboot the server the daemons will not restart either with the init.d script or manually. It runs for a few seconds and the stops with an RPC error in the log files:

01/18/01 17:51:36 nsrd: server notice: started
01/18/01 17:51:40 nsrmmdbd: media db is cross checking the save sets
01/18/01 17:51:40 nsrmmdbd: media db is open for business
01/18/01 17:51:42 nsrindexd: RPC error, Unknown host
01/18/01 17:51:42 nsrd: unable to start nsrindexd
01/18/01 17:51:42 nsrd: shutting down
01/18/01 17:51:42 nsrd: successful shutdown

Legato is working on this and we have tried all their recommended steps for the possibility of corrupt indexes and/or volumes. Our network and dns all check out too.

Has anyone out there run into this situation before or have any ideas...

Thanks,
Ian
2 REPLIES 2
Berlene Herren
Honored Contributor

Re: Networker daemons will not start after reboot/shutdown

Try this:

add the follwing entry in the nsswitch.conf file:
hosts: files [NOTFOUND=countinue]DNS[NOTFOUND=continue] nis

Berlene
http://www.mindspring.com/~bkherren/dobes/index.htm
Ian Cameron
Frequent Advisor

Re: Networker daemons will not start after reboot/shutdown

Sorry for the delay in assigning points Berlene. I had actually removed my entries from resolv.conf and successfully restarted nsrd etc. I have not had time to reboot the server again but I have updated the nsswitch file so that when I do I will see if it corrects the issue.

Legato has posted a large patch file but there is nothing in the readme that indicates a problem similar to what I have been experiencing.

Thanks again, if/when I reboot again I will post success or no.

Ian