There has been a problem in mounting the directory
on the client.
PROBLEM :-
----------
If the command :
$ mount serverIPaddress:/home /home
is issued, then the output is
mount: RPC: Timed out
INFO THAT MAY BE USEFUL :-
-------------------------
SERVER SIDE :
$ rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
391002 2 tcp 1025 sgi_fam
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100021 1 udp 1027 nlockmgr
100021 3 udp 1027 nlockmgr
100021 4 udp 1027 nlockmgr
100011 1 udp 755 rquotad
100011 2 udp 755 rquotad
100011 1 tcp 758 rquotad
100011 2 tcp 758 rquotad
100005 1 udp 1028 mountd
100005 1 tcp 1030 mountd
100005 2 udp 1028 mountd
100005 2 tcp 1030 mountd
100005 3 udp 1028 mountd
100005 3 tcp 1030 mountd
100024 1 udp 1029 status
100024 1 tcp 1031 status
CLIENT SIDE:
$ rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 32768 status
100024 1 tcp 32768 status
391002 2 tcp 32769 sgi_fam
Here, I explicitly run rpc.lockd (on client)
but still, I do not see lock daemon (nslockmanager or some thing of that
sort) ! Any clue?
---------------------------------------------------
Please, give some way to sort it out...
-suresh
----------------------
SURESH CHADIVE
V Yr,
Dual degree Programme
H9, #319,
Indian Instt. of Technology,
Bombay
e-mail : [email protected]
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
Problems I've run into getting NFS going are IPChains firewall rules
(IPTables logging is a little less cryptic) and not having portmap running
on the client. Also, try "rpcinfo -p <server>" from the client, or
"rpcinfo -u <server> nfs" to see what the client can see.
Additionally, see if you can nfs mount the shared directories from the
server itself, to make sure they are really shared.
Joe
On Wed, 21 Aug 2002, Suresh Chadive wrote:
>
>
> There has been a problem in mounting the directory
> on the client.
>
> PROBLEM :-
> ----------
> If the command :
> $ mount serverIPaddress:/home /home
> is issued, then the output is
> mount: RPC: Timed out
>
>
> INFO THAT MAY BE USEFUL :-
> -------------------------
>
> SERVER SIDE :
>
> $ rpcinfo -p
> program vers proto port
> 100000 2 tcp 111 portmapper
> 100000 2 udp 111 portmapper
> 391002 2 tcp 1025 sgi_fam
> 100003 2 udp 2049 nfs
> 100003 3 udp 2049 nfs
> 100021 1 udp 1027 nlockmgr
> 100021 3 udp 1027 nlockmgr
> 100021 4 udp 1027 nlockmgr
> 100011 1 udp 755 rquotad
> 100011 2 udp 755 rquotad
> 100011 1 tcp 758 rquotad
> 100011 2 tcp 758 rquotad
> 100005 1 udp 1028 mountd
> 100005 1 tcp 1030 mountd
> 100005 2 udp 1028 mountd
> 100005 2 tcp 1030 mountd
> 100005 3 udp 1028 mountd
> 100005 3 tcp 1030 mountd
> 100024 1 udp 1029 status
> 100024 1 tcp 1031 status
>
>
>
> CLIENT SIDE:
>
> $ rpcinfo -p
> program vers proto port
> 100000 2 tcp 111 portmapper
> 100000 2 udp 111 portmapper
> 100024 1 udp 32768 status
> 100024 1 tcp 32768 status
> 391002 2 tcp 32769 sgi_fam
>
> Here, I explicitly run rpc.lockd (on client)
> but still, I do not see lock daemon (nslockmanager or some thing of that
> sort) ! Any clue?
> ---------------------------------------------------
>
> Please, give some way to sort it out...
>
> -suresh
>
>
> ----------------------
> SURESH CHADIVE
>
> V Yr,
> Dual degree Programme
>
> H9, #319,
> Indian Instt. of Technology,
> Bombay
>
> e-mail : [email protected]
>
>
>
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone? Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> NFS maillist - [email protected]
> https://lists.sourceforge.net/lists/listinfo/nfs
>
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
First, a good page to check is:
http://ftp.belnet.be/packages/redhat/redhat-7.1-en/doc/HOWTOS/other-formats/
html/NFS-HOWTO/server.html#SERVICESTART
to get your services started. If you are using Linux, you can also try
this. Issue the command:
chkconfig --list
and a list of services will scroll by. Check to see that portmap, nfs and
nfslock are 'on' on levels 3, 4, and 5. If not, issue the commands:
chkconfig --level 345 portmap on
chkconfig --level 345 nfs on
chkconfig --level 345 nfslock on
and these should be turned on, and will start on reboot. Try this on the
client and see what happens if it looks like it will help. Good luck.
Patrick
----- Original Message -----
From: "Suresh Chadive" <[email protected]>
To: <[email protected]>
Sent: Tuesday, August 20, 2002 7:01 PM
Subject: [NFS] NFS problem
>
>
> There has been a problem in mounting the directory
> on the client.
>
> PROBLEM :-
> ----------
> If the command :
> $ mount serverIPaddress:/home /home
> is issued, then the output is
> mount: RPC: Timed out
>
>
> INFO THAT MAY BE USEFUL :-
> -------------------------
>
> SERVER SIDE :
>
> $ rpcinfo -p
> program vers proto port
> 100000 2 tcp 111 portmapper
> 100000 2 udp 111 portmapper
> 391002 2 tcp 1025 sgi_fam
> 100003 2 udp 2049 nfs
> 100003 3 udp 2049 nfs
> 100021 1 udp 1027 nlockmgr
> 100021 3 udp 1027 nlockmgr
> 100021 4 udp 1027 nlockmgr
> 100011 1 udp 755 rquotad
> 100011 2 udp 755 rquotad
> 100011 1 tcp 758 rquotad
> 100011 2 tcp 758 rquotad
> 100005 1 udp 1028 mountd
> 100005 1 tcp 1030 mountd
> 100005 2 udp 1028 mountd
> 100005 2 tcp 1030 mountd
> 100005 3 udp 1028 mountd
> 100005 3 tcp 1030 mountd
> 100024 1 udp 1029 status
> 100024 1 tcp 1031 status
>
>
>
> CLIENT SIDE:
>
> $ rpcinfo -p
> program vers proto port
> 100000 2 tcp 111 portmapper
> 100000 2 udp 111 portmapper
> 100024 1 udp 32768 status
> 100024 1 tcp 32768 status
> 391002 2 tcp 32769 sgi_fam
>
> Here, I explicitly run rpc.lockd (on client)
> but still, I do not see lock daemon (nslockmanager or some thing of that
> sort) ! Any clue?
> ---------------------------------------------------
>
> Please, give some way to sort it out...
>
> -suresh
>
>
> ----------------------
> SURESH CHADIVE
>
> V Yr,
> Dual degree Programme
>
> H9, #319,
> Indian Instt. of Technology,
> Bombay
>
> e-mail : [email protected]
>
>
>
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone? Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> NFS maillist - [email protected]
> https://lists.sourceforge.net/lists/listinfo/nfs
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
Thank you very much for the support I got. It is
really timely help to me.
The suggestions helped me in making a breakthrough,
however, still the problem persists. I think I have
rounded off the critical thing now.
1) The portmap, nfs, nfslock were off for the levels 345
I rectified it. Now the client also shows all the important
daemons running.
2) - rpcinfo -p on server and client now give all the daemons.
----------------------------------------------------------
- also, the command:
$ rpcinfo -p server
produces the same input as obtained on the server (issuing
---------------------------------------------- rpcinfo -p)
Interesting part is
$ rpcinfo -u server nfs
$ rpcinfo -u server portmap
are getting timed out !!!!. They produce (for the case of portmap):
rpcinfo: RPC: Port mapper failure - RPC: Timed out
program 100000 is not available
Will this give any clue to the problem?
3) The mounting on to the server itself is successful !
Is it that server side is absolutely OK?
Eagerly looking for the final shot...
Best regards,
-suresh
----------------------
SURESH CHADIVE
V Yr,
Dual degree Programme
H9, #319,
IIT Bombay
e-mail : [email protected]
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
>From what I see from the man page of rpcinfo, try a
rpcinfo -s <server>
from the client and see what services are there and what program number they
are associated with. Sure enough my portmap service is program 100000, just
as yours complains about not finding. If the services are showing up when
you issue rpcinfo -p from the server, they should be there and show program
number from the above command. If you generically say:
rpcinfo -u <server> portmap
it may automatically look for program number 100000 and all I can think of
is that your portmap service is not running under that program number. Not
sure why it wouldn't be. If it isn't then substitute the program number for
portmap in the above command and see what you find.
Patrick
----- Original Message -----
From: "Suresh Chadive" <[email protected]>
To: <[email protected]>
Sent: Wednesday, August 21, 2002 1:45 PM
Subject: Re: [NFS] NFS problem
>
> Thank you very much for the support I got. It is
> really timely help to me.
>
> The suggestions helped me in making a breakthrough,
> however, still the problem persists. I think I have
> rounded off the critical thing now.
>
> 1) The portmap, nfs, nfslock were off for the levels 345
> I rectified it. Now the client also shows all the important
> daemons running.
>
> 2) - rpcinfo -p on server and client now give all the daemons.
> ----------------------------------------------------------
> - also, the command:
>
> $ rpcinfo -p server
> produces the same input as obtained on the server (issuing
> ---------------------------------------------- rpcinfo -p)
>
> Interesting part is
>
> $ rpcinfo -u server nfs
> $ rpcinfo -u server portmap
>
> are getting timed out !!!!. They produce (for the case of portmap):
>
> rpcinfo: RPC: Port mapper failure - RPC: Timed out
> program 100000 is not available
>
>
> Will this give any clue to the problem?
>
>
> 3) The mounting on to the server itself is successful !
> Is it that server side is absolutely OK?
>
>
> Eagerly looking for the final shot...
>
>
> Best regards,
> -suresh
>
>
> ----------------------
> SURESH CHADIVE
>
> V Yr,
> Dual degree Programme
>
> H9, #319,
> IIT Bombay
>
> e-mail : [email protected]
>
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone? Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> NFS maillist - [email protected]
> https://lists.sourceforge.net/lists/listinfo/nfs
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs