- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: rpc comm failure
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2008 02:08 AM
08-21-2008 02:08 AM
rpc comm failure
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2008 04:54 AM
08-21-2008 04:54 AM
Re: rpc comm failure
Can you paste error messages and details
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2008 05:01 AM
08-21-2008 05:01 AM
Re: rpc comm failure
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
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2008 05:11 AM
08-21-2008 05:11 AM
Re: rpc comm failure
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2008 07:43 PM
08-24-2008 07:43 PM
Re: rpc comm failure
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:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2008 10:19 AM
08-25-2008 10:19 AM