Linux

Hi guys,
The RPC problem is appearing on the screen while starting the portmap service,take a look of the real..

[root@kickstart-server ~]# service portmap restart
Stopping portmap: [ OK ]
Starting portmap: [ OK ]
Cannot register service: RPC: Timed out
not registered: 100000 2 tcp 111 portmapper

And network is also is appearing wrong..

Please help me out

[root@kickstart-server ~]# service network restart
Shutting down interface eth0: [ OK ]
Shutting down loopback interface: [ OK ]
do_ypcall: clnt_call: RPC: Unable to send; errno = Invalid argument
do_ypcall: clnt_call: RPC: Unable to send; errno = Invalid argument
do_ypcall: clnt_call: RPC: Unable to send; errno = Invalid argument
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0:

There seems to be a problem with portmap. After service portmap restart, does it actually get to the process table?? The service init script uses a program called pmap_set to load the previous known state of the portmapper. But if portmap fails for some reason, pmap_set will complain and you get the above error. So it could be a problem with /etc/rpc. You don't really need RPC unless you're running a network and using it for NFS.

The interface problem is related. ypcall and RPC all relate back to the portmapper. If the portmapper isn't working, none of its dependencies.