SYMMARY: rpc not port mapping legato client deamons

From: Brehl, Blake <Blake.Brehl_at_anritsu.com>
Date: Fri, 08 Sep 2000 14:38:47 -0700

Hello Admins,
        Original message below. Problem: Legato couldn't communicate to
it's clients because the client deamons "nsrexecd" (x2) wasn't rpc mapping
to a port.

        It's inconclusive, but now rpc is mapping nsrexecd to a port. What
is associated, (...but only associated!!) is that there was a DNS client
share mounted where the export server service was unavailable. While this
was happening, the command df wouldn't respond. Once I executed the umount
on the client share, df started working, and nsrexec deamon mapped to the
port ( actually the umount hung, but the df came back). It may be that NFS
requests filled and held ports????

        I don't quite understand it. Compaq tech support did say that if
you wanted to stop and start rpc, you would first have to take an inventory
of the services running (rcpinfo -p) and then 1) stop portmap, 2) start
portmap, 3) make sure that you re-start all of the services. That started
to look like a tossup to do that or an off hours reboot.

Thanks to William Magill and Chan Cao for replies. They specified to confirm
the DNS, hosts file, NSR client aliases, and clarified that of the 2
nsrexecd deamons, one listens and one talks.

Best Regards, Blake






*********ORIGINAL MESSAGE BELOW***********************
Hello Guru's,
        were having a problem with the Legato client permissions (the server
is trying to back up itself), as rpc is not mapping a port for the 2 client
"nsrexecd" daemons. The /etc/rpc entry for nsrexec is:

nsrexec 390113 nsrexecd

When you start the nsr deamons, 2 of the "nsrexecd" threads appear in ps
-ef.

A rpcinfo -p reveals all of the other nsr ports/deamons

    390103 2 tcp 10001 nsrd
    390109 2 tcp 10001 nsrstat
    390110 1 tcp 10001 nsrjb
    390103 2 udp 10002 nsrd
    390109 2 udp 10002 nsrstat
    390110 1 udp 10002 nsrjb
    390107 4 tcp 10062 nsrmmdbd
    390107 5 tcp 10062 nsrmmdbd
    390104 105 tcp 10075 nsrmmd
    390105 5 tcp 10092 nsrindexd

Another server secures the port but some of the deamons have other port #s.

    390103 2 tcp 10001 nsrd
    390109 2 tcp 10001 nsrstat
    390110 1 tcp 10001 nsrjb
    390103 2 udp 10002 nsrd
    390109 2 udp 10002 nsrstat
    390110 1 udp 10002 nsrjb
    390113 1 tcp 7937 nsrexec
    390107 4 tcp 7939 nsrmmdbd
    390107 5 tcp 7939 nsrmmdbd
    390104 105 tcp 7940 nsrmmd
    390105 5 tcp 7941 nsrindexd

Is there a problem involving security of the port? ...with availibility of
secure vs unsecure? Is there a way to restart rpc? We have 200 active
clients. Can a restart of rpc be done with any disruption?

AS4100
Tru64UNIX 4.0F pk3
Legato Networker 5.5 Build.38 Turbo/10

Best Regards,

Blake Brehl
Senior Database Administrator
Anritsu Company United States
Morgan Hill, CA 95037
blake.brehl_at_anritsu.com
Received on Fri Sep 08 2000 - 21:41:13 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:41 NZDT