topic Re: rpcbind behaviour in Operating System - HP-UX

rpcbind behaviour

siaemic — Fri, 28 Mar 2003 13:26:18 GMT

We develop a C application using rpc library. Only on some ws we are getting errors in executing our program. Once we got an error in syslog reporting info:
svc_tp_create: Could not register prog 536871239 vers 1 on udp.
What could it mean ?

Re: rpcbind behaviour

Robert-Jan Goossens — Fri, 28 Mar 2003 13:47:30 GMT

Hi,

Could you compare the
/etc/nsswitch.conf of a working ws against one of a not working ws.

Robert-Jan.

Re: rpcbind behaviour

Jeff Schussele — Fri, 28 Mar 2003 14:03:42 GMT

Hi,

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

Re: rpcbind behaviour

siaemic — Fri, 28 Mar 2003 14:13:00 GMT

Robert,

in two ws (one working while the other not)
/etc/nsswitch.conf file was not present.
It doesn't seem to depend on it

Re: rpcbind behaviour

siaemic — Fri, 28 Mar 2003 15:24:24 GMT

Jeff,

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

Re: rpcbind behaviour

siaemic — Fri, 28 Mar 2003 16:01:10 GMT

Jeff,

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

Re: rpcbind behaviour

Jeff Schussele — Fri, 28 Mar 2003 16:08:41 GMT

Hi,

I'd recommend you bounce - or warm start - rpcbind on that system:

/usr/sbin/rpcbind -w

See if that fixes it.

Rgds,
Jeff

Re: rpcbind behaviour

Jeff Schussele — Fri, 28 Mar 2003 16:12:05 GMT

OH....one other thing.
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

Re: rpcbind behaviour

Steven E. Protter — Fri, 28 Mar 2003 16:19:31 GMT

You actaully need an nssswitch.conf file for your networking to work right. On both workstations.

Get one in place to eliminate this as an issue.

rpcbind is after all a network(nfs?) program/daemon.

SEP

Re: rpcbind behaviour

siaemic — Fri, 28 Mar 2003 16:31:17 GMT

Jeff,

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 ?

Re: rpcbind behaviour

siaemic — Tue, 01 Apr 2003 11:50:47 GMT

Thanks to all for your cooperation.

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.