topic rpc comm failure in Operating System - HP-UX

rpc comm failure

zebra_2 — Thu, 21 Aug 2008 09:08:12 GMT

We are experiencing rpc comm failure on HP-UX 11.11 server having lan cards. I am seeing that there are 3 addresses assigned to this LAN out of which 2 are virtual addresses. I don't know whether it is the cause of the problem.
I am planning to do the following:
export RPC_SUPPORTED_NETADDRS=ip address [one among the three] and then try starting rpcd

1)Are there any other reasons for RPC comm failure other than rpcd dieing or not binding rpc service to a specific LAN address?
2)Is it a issue if we have multiple addresses assigned to the same LAN card (virtual addresses)... will this cause any issue with rpc comm failure [I tried searching in net but didn't receive any info].
3)Also, is restarting the system compulsory for the address restriction to take effect?

Any help is appreciated.

Re: rpc comm failure

Deepak Kr — Thu, 21 Aug 2008 11:54:19 GMT

Not very sure on error.

Can you paste error messages and details

Re: rpc comm failure

Steven E. Protter — Thu, 21 Aug 2008 12:01:03 GMT

Shalom,

1) NFS and RPC services do not do well when the IP address of a system is changed. These services need to be restarted.
2) Restart nfs.core nfs.server nfs.client
3) No restart is not required but it does simplify things and can be a time saver.

SEP

Re: rpc comm failure

Deepak Kr — Thu, 21 Aug 2008 12:11:17 GMT

Have you recently added these virtual IPs?

If yes then as SEP suggested you recycle nfs services.

/sbin/init.d/nfs.core [stop/start]
/sbin/init.d/nfs.[client/server] [stop/start]

regds...DK

Re: rpc comm failure

zebra_2 — Mon, 25 Aug 2008 02:43:54 GMT

Thanks for the reply,

I would like to elaborate my problem a bit:

We are running OVPA application on one of the system. One of the process "rep_server" is dying constantly on HPUX 11.23 Itanium with ovo agent 08.10.160.

What we saw was that the process "rep_server" is not coming up because perflbd is getting deactivated with llb__lookup_range() call failure error. We feel that this is because of RPC Communications failure.

The following error messages are seen:

07/15/08 09:23:11 perflbd(0xe43): Error 0x36 - Qualifier 0x16c9a0d6: rpc_mgmt_ep_unregister() call failed. (MWA210-54)
07/15/08 18:53:38 perflbd(0x3f24): Error 0x2d - Qualifier 0x16c9a016:

Re: rpc comm failure

skt_skt — Mon, 25 Aug 2008 17:19:56 GMT

try restarting /sbin/init.d/dce