- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- rpcbind behaviour
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
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
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
03-28-2003 05:26 AM
03-28-2003 05:26 AM
rpcbind behaviour
svc_tp_create: Could not register prog 536871239 vers 1 on udp.
What could it mean ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2003 05:47 AM
03-28-2003 05:47 AM
Re: rpcbind behaviour
Could you compare the
/etc/nsswitch.conf of a working ws against one of a not working ws.
Robert-Jan.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2003 06:03 AM
03-28-2003 06:03 AM
Re: rpcbind behaviour
No clue what this C prog does or how it works - but I'd check:
1) That any services it requires are listed in /etc/services
2) That any required entries for /etc/inetd.conf are in there - correctly & inetd -c was run.
3) That an rpcinfo query of the localhost & from the serving host to the client (and vice-versa) returns expected results.
4) That any FW between server & client has the appropriate ruleset to allow desired port/protocol through.
HTH,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2003 06:13 AM
03-28-2003 06:13 AM
Re: rpcbind behaviour
in two ws (one working while the other not)
/etc/nsswitch.conf file was not present.
It doesn't seem to depend on it
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2003 07:24 AM
03-28-2003 07:24 AM
Re: rpcbind behaviour
we used rpcinfo on 2 different ws.
On one working ws using command:
rpcinfo -p
we saw our prognum listed. Using command:
rpcinfo -T udp ws 536871239 1
we get msg
program 536871239 version 1 ready and waiting
On a not working ws using command:
rpcinfo -p
we saw our prognum listed. Then using command:
rpcinfo -T udp ws 536871239 1
we got msg:
rpcinfo: RPC: Timed out
program 536871239 version 1 is not available
Then we use command:
rpcinfo -d 536871239 1
to deregister it, we relaunched application and using again command:
rpcinfo -T udp ws 536871239 1
we get msg
rpcinfo: RPC: Program not registered
even if keeping in see it with command
rpcinfo -p
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2003 08:01 AM
03-28-2003 08:01 AM
Re: rpcbind behaviour
now we found out how to register udp protocol but tcp one keeps on returning error:
# rpcinfo -T tcp ws 536871239 1
rpcinfo: RPC: Timed out
program 536871239 version 1 is not available
# rpcinfo -T udp ws 536871239 1
program 536871239 version 1 ready and waiting
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2003 08:08 AM
03-28-2003 08:08 AM
Re: rpcbind behaviour
I'd recommend you bounce - or warm start - rpcbind on that system:
/usr/sbin/rpcbind -w
See if that fixes it.
Rgds,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2003 08:12 AM
03-28-2003 08:12 AM
Re: rpcbind behaviour
Make sure you have BOTH the UDP and TCP entries for this in the /etc/services file.
If you use both, you need both in there.
Rgds,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2003 08:19 AM
03-28-2003 08:19 AM
Re: rpcbind behaviour
Get one in place to eliminate this as an issue.
rpcbind is after all a network(nfs?) program/daemon.
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
03-28-2003 08:31 AM
03-28-2003 08:31 AM
Re: rpcbind behaviour
The behaviour seems to be always the same
# rpcinfo -T tcp ws 536871239 1
rpcinfo: RPC: Timed out
program 536871239 version 1 is not available
# rpcinfo -T udp ws 536871239 1
program 536871239 version 1 ready and waiting
Moreover, each time we register again our prognum vernum we see a different value of port using rpcinfo.
How can we set it in our /etc/services ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-01-2003 03:50 AM
04-01-2003 03:50 AM
Re: rpcbind behaviour
We succedd in solving our problem. The bug was that we didn't use svc_run to get rpc message but we use our proprietary mainloop. We were in select on several file descripitor. The problem was that we had to call
nfds = getdtablesize();
function to get first parameter for select while we use a wrong value so we were not awoken from select.