rup:<servername>: RPC: Program not registered in RHEL6.1

I just installed Redhat Enterprise Linux 6.1 on one HP server. Following error met when rup it on other servers:

$rup coolnjmcl033
rup:coolnjmcl033: RPC: Program not registered

SOLUTION:

1)check if all nfs related services are working:

[root@coolnjmcl033init.d]# rpcinfo -p
   program vers proto   port  service
    100000   4   tcp    111 portmapper
    100000   3   tcp    111 portmapper
    100000   2   tcp    111 portmapper
    100000   4   udp    111 portmapper
    100000   3   udp    111 portmapper
    100000   2   udp    111 portmapper
    100011   1   udp    875 rquotad
    100011   2   udp    875 rquotad
    100011   1   tcp    875 rquotad
    100011   2   tcp    875 rquotad
    100003   2   tcp   2049 nfs
    100003   3   tcp   2049 nfs
    100003   4   tcp   2049 nfs
    100227   2   tcp   2049 nfs_acl
    100227   3   tcp   2049 nfs_acl
    100003   2   udp   2049 nfs
    100003   3   udp   2049 nfs
    100003   4   udp   2049 nfs
    100227   2   udp   2049 nfs_acl
    100227   3   udp   2049 nfs_acl
    100005    1  udp  51310  mountd
    100005    1  tcp  60605  mountd
   100005    2   udp 42799  mountd
   100005    2   tcp 44201  mountd
   100005    3   udp 49544  mountd
   100005    3   tcp 49098  mountd
   100024    1   udp 37035  status
   100024    1   tcp 60898  status
   100001    3   udp  1008  rstatd
   100001    2   udp  1008  rstatd
   100001    1   udp  1008  rstatd

If there is no runningrstatdservice , start it by service rstatd start.

Accordingto RHEL 6 RUP manual:

rup: RPC: Program not registered

Therpc.rstatd(8)daemon has not been started on the remote host.

2) check if package rusers-server-*and rusers-* are installed: rpm –qa|greprusers. If not, install it and then restart service rstatd.

PS:

Other userful commands:

1. rup localhost
2. service rstatd status

According to New Featuresin RHEL6,

1.ext4 file system is introduced.
2. xen isremoved and kernelvirtualizationmachine(KVM) is introduced.
3. neatcommandis removed.
4. portmap service is removed.
5. iscsi is introduced, whichsupportsforSAN.
6. rpmbuild is available, which is used to create our own rpms.
7. File encyption is added.
8. palimpsest is available fordiskmanagement.
9.Virtualmachine willrunonly on 64bit processors.
10. postfix service isrecommendedinsteadof sendmail service.

Accordingto Chapter12.Network File System (NFS),

Theportmapservice wasused to map RPC program numbers to IP address port number combinations inearlier versions of Red Hat Enterprise Linux. This service is now replaced byrpcbindinRed Hat Enterprise Linux 6 to enable IPv6 support. For more information aboutthis change, refer to the following links:

• TI-RPC / rpcbind support:http://nfsv4.bullopensource.org/doc/tirpc_rpcbind.php
• IPv6 support in NFS:http://nfsv4.bullopensource.org/doc/nfs_ipv6.php

Required Services

nfs

service nfs startstarts the NFS server and the appropriate RPC processes to service requests for shared NFS file systems.

nfslock

service nfslock startactivates a mandatory service that starts the appropriate RPC processes which allow NFS clients to lock files on the server.

rpcbind

rpcbindaccepts port reservations from local RPC services. These ports are then made available (or advertised) so the corresponding remote RPC services can access them.rpcbindresponds to requests for RPC services and sets up connections to the requested RPC service. This is not used with NFSv4.

The following RPC processes facilitate NFS services:

rpc.mountd

This process receives mount requests from NFS clients and verifies that the requested file system is currently exported. This process is started automatically by thenfsservice and does not require user configuration.

rpc.nfsd

rpc.nfsdallows explicit NFS versions and protocols the server advertises to be defined. It works with the Linux kernel to meet the dynamic demands of NFS clients, such as providing server threads each time an NFS client connects. This process corresponds to thenfsservice.

lockd

lockdis a kernel thread which runs on both clients and servers. It implements theNetwork Lock Manager(NLM) protocol, which allows NFSv2 and NFSv3 clients to lock files on the server. It is started automatically whenever the NFS server is run and whenever an NFS filesystem is mounted.

rpc.statd

This process implements theNetwork Status Monitor(NSM) RPC protocol, which notifies NFS clients when an NFS server is restarted without being gracefully brought down.rpc.statdis started automatically by thenfslockservice, and does not require user configuration. This is not used with NFSv4.

rpc.rquotad

This process provides user quota information for remote users.rpc.rquotadis started automatically by thenfsservice and does not require user configuration.

rpc.idmapd

rpc.idmapdprovides NFSv4 client and server upcalls, which map between on-the-wire NFSv4 names (which are strings in the form ofuser@domain) and local UIDs and GIDs. Foridmapdto function with NFSv4, the/etc/idmapd.confmust be configured. This service is required for use with NFSv4, although not when all hosts share the same DNS domain name.