Start RPC Daemon if needed FAIL

[opium_den]

Hi All,
On boot up of my C3700 I get a FAIL on 'Start RPC Daemon if needed.' This is the only fail.

My /etc/rc.log file says the following:-
-----------------------------------------------
Start RPC daemon if needed

Output from "/sbin/rc2.d/S590 Rpcd start":

starting the DCE RPC Daemon /opt/dce/sbin/rpcd

EXIT CODE 1

"/sbin/rc2.d/S590 Rpcd start" FAILED
-----------------------------------------------

Can someone please tell me the implications, and perhaps cure?
Thanks for your attention
Ian

[sen_ux · Accepted solution]

ps -ef|grep rpcd

Run /opt/dce/sbin/rpcd manually and check the status.

[avizen9]

could you please follow below forms,
post the result,
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=98164

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=213967

[opium_den]

Hi All,
Thanks for your prompt replies :-) I've run rpcd manually, and 'ps -ef ¦ grep rpcd' gives no output either before or after.

As a note :- ps -ef ¦ grep rpc gives

root 637 10 16:41:17 ? 0:00 /usr/sbin/rpcbind

Any ideas please?

Oh yes, on turn off I get an 'Init command respawning too rapidly.' I'm guessing the problems are related?

Thanks
Ian

[Alex Glennie]

check under /var/opt/dce/svc/logs ...and your syslog.log I'm suspecting something to do with hostname resolution .... is the workstation connected to a network , has it always failed and what is the O/S ?

implications ..... sdux *may* have issues ie swlist, swinstall etc use rpcd I beleive, see man page ?

[opium_den]

Hi Alex,
I did wonder too about the hostname resolution. I originally was going to network it, tried and then restarted during setup. It's running HP UX 11.11 and is a standalone workstation. I'll do as you say and check the syslog.log. If I have to I can easily re install from the CDs. Concerning it's running history I can't tell you as it's a new *second user* machine.
Thanks very much for your help
Ian

[Alex Glennie]

I think it will be down to networking too the dce logs nb fatal.log etc would also be worth looking at too

fyi if you see a status=0x0000ff03. run stdcode 0x0000ff03 for more info see http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1102250