I just installed Redhat Enterprise Linux 6.1 on one HP server. Following error met when rup it on other servers:
SOLUTION:
1)check if all nfs related services are working:
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:
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:
service nfs start
starts the NFS server and the appropriate RPC processes to service requests for shared NFS file systems.
service nfslock start
activates a mandatory service that starts the appropriate RPC processes which allow NFS clients to lock files on the server.
rpcbind
accepts port reservations from local RPC services. These ports are then made available (or advertised) so the corresponding remote RPC services can access them.
rpcbind
responds to requests for RPC services and sets up connections to the requested RPC service. This is not used with NFSv4.
nfs
service and does not require user configuration.
rpc.nfsd
allows 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 the
nfs
service.
lockd
is a kernel thread which runs on both clients and servers. It implements the
Network 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
is started automatically by the
nfslock
service, and does not require user configuration. This is not used with NFSv4.
rpc.rquotad
is started automatically by the
nfs
service and does not require user configuration.
rpc.idmapd
provides NFSv4 client and server upcalls, which map between on-the-wire NFSv4 names (which are strings in the form of
user
@domain
) and local UIDs and GIDs. For
idmapd
to function with NFSv4, the
/etc/idmapd.conf
must be configured. This service is required for use with NFSv4, although not when all hosts share the same DNS domain name.