Hello,
I thought this was a library issue per workstation for quite awhile.
However, I have narrowed it down to this problem.
I can run programs such as nautilus, staroffice, openoffice as a local
user just fine. However, if I try to run any of the above programs as a
nis user who's home directory is an nfs mount, that program will hang.
for example (staroffice):
todd@ws04~ $ strace -f /usr/local/office/program/soffice
[snip]
[pid 589] open("/home/t/todd/.sversionrc", O_RDONLY) = 3
[pid 589] fcntl(3, F_GETFD) = 0
[pid 589] fcntl(3, F_SETFD, FD_CLOEXEC) = 0
[pid 589] fcntl(3, F_SETLKW, {type=F_RDLCK, whence=SEEK_SET, start=0, len=0}
This of course all occurred as soon as I upgraded debian stable to the
latest packages.
I am not sure how to track this problem any further.
I will add that as a local user there is no problem whatsoever.
but as a nis/nfs user some programs fail with similar results.
mozilla works fine, and obviously that is setup with a local binary, and
the configuration is read over nfs.
Could somebody please help me debug this further, or better yet tell me
what I need do to fix this problem.
I can easily provide more information, if somebody can tell me what would
be pertinent.
I am not a subscriber to the nfs mailing list (yet) so please reply to me
as well as the list please.
Thanks all!
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
Todd Weaver wrote:
>
> I can run programs such as nautilus, staroffice, openoffice as a local
> user just fine. However, if I try to run any of the above programs as a
> nis user who's home directory is an nfs mount, that program will hang.
>
> for example (staroffice):
> todd@ws04~ $ strace -f /usr/local/office/program/soffice
> [snip]
> [pid 589] open("/home/t/todd/.sversionrc", O_RDONLY) = 3
> [pid 589] fcntl(3, F_GETFD) = 0
> [pid 589] fcntl(3, F_SETFD, FD_CLOEXEC) = 0
> [pid 589] fcntl(3, F_SETLKW, {type=F_RDLCK, whence=SEEK_SET, start=0, len=0}
I've seen software hang doing a fcntl(F_SETLKW) on an NFS-mounted file when lockd
was not running or was firewalled off. Essentially the client is asking for a
lock on a file -- which it never gets -- and the app waits forever for lockd to
respond.
I would check that lockd is running on the client and server, with rpcinfo -p,
and that it is not firewalled off.
andrew
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
On Tue, 9 Apr 2002, Andrew Ryan wrote:
> I've seen software hang doing a fcntl(F_SETLKW) on an NFS-mounted file
> when lockd was not running or was firewalled off. Essentially the
> client is asking for a lock on a file -- which it never gets -- and
> the app waits forever for lockd to respond.
>
> I would check that lockd is running on the client and server, with
> rpcinfo -p, and that it is not firewalled off.
Much appreciate the help!
todd@ws04~ $ rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100021 1 udp 1024 nlockmgr
100021 3 udp 1024 nlockmgr
100007 2 udp 791 ypbind
100007 1 udp 791 ypbind
100007 2 tcp 794 ypbind
100007 1 tcp 794 ypbind
100024 1 udp 777 status
100024 1 tcp 779 status
todd@ws04~ $
I'm looking into how to get lockd running. (or can you help with that
too?)
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
On Tue, 9 Apr 2002, Andrew Ryan wrote:
> I would check that lockd is running on the client and server, with
> rpcinfo -p, and that it is not firewalled off.
Here is the output of rpcinfo -p on the Workstation and the Server
Workstation:
ws04:/etc# rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100021 1 udp 1024 nlockmgr
100021 3 udp 1024 nlockmgr
100007 2 udp 791 ypbind
100007 1 udp 791 ypbind
100007 2 tcp 794 ypbind
100007 1 tcp 794 ypbind
100024 1 udp 707 status
100024 1 tcp 709 status
100003 2 udp 2049 nfs
100003 2 tcp 2049 nfs
ws04:/etc#
Server:
todd@ws02~ $ rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100003 2 udp 2049 nfs
100003 2 tcp 2049 nfs
100005 1 udp 946 mountd
100005 2 udp 946 mountd
100005 1 tcp 949 mountd
100005 2 tcp 949 mountd
100004 2 udp 630 ypserv
100004 1 udp 630 ypserv
100004 2 tcp 633 ypserv
100004 1 tcp 633 ypserv
100009 1 udp 632 yppasswdd
600100069 1 udp 634
600100069 1 tcp 636
100007 2 udp 641 ypbind
100007 1 udp 641 ypbind
100007 2 tcp 644 ypbind
100007 1 tcp 644 ypbind
100021 1 udp 2408 nlockmgr
100021 3 udp 2408 nlockmgr
100024 1 udp 997 status
100024 1 tcp 999 status
todd@ws02~ $
I would add that all these programs worked fine before I did an apt-get
update ; apt-get dist-upgrade which upgraded about 35 packages (so I am
not sure what caused the problem).
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
You can try from your client to see if it can talk to the lockd on the
server. This should give you some positive response:
rpcinfo -u <servername> nlockmgr
and likewise you can run this from the server as well.
Also keep in mind what you did to your systems is prone to breakage of all
sorts; arbitrarily upgrading ~35 packages on your system, when you don't
even know what all of those packages are, much less the effect of an
upgrade, you pretty much expect some things to stop working properly. It's
off the scope of this list to go through all the packages you upgraded,
though.
andrew
Todd Weaver wrote:
> On Tue, 9 Apr 2002, Andrew Ryan wrote:
> > I would check that lockd is running on the client and server, with
> > rpcinfo -p, and that it is not firewalled off.
>
> Here is the output of rpcinfo -p on the Workstation and the Server
>
> Workstation:
> ws04:/etc# rpcinfo -p
> program vers proto port
> 100000 2 tcp 111 portmapper
> 100000 2 udp 111 portmapper
> 100021 1 udp 1024 nlockmgr
> 100021 3 udp 1024 nlockmgr
> 100007 2 udp 791 ypbind
> 100007 1 udp 791 ypbind
> 100007 2 tcp 794 ypbind
> 100007 1 tcp 794 ypbind
> 100024 1 udp 707 status
> 100024 1 tcp 709 status
> 100003 2 udp 2049 nfs
> 100003 2 tcp 2049 nfs
> ws04:/etc#
>
> Server:
> todd@ws02~ $ rpcinfo -p
> program vers proto port
> 100000 2 tcp 111 portmapper
> 100000 2 udp 111 portmapper
> 100003 2 udp 2049 nfs
> 100003 2 tcp 2049 nfs
> 100005 1 udp 946 mountd
> 100005 2 udp 946 mountd
> 100005 1 tcp 949 mountd
> 100005 2 tcp 949 mountd
> 100004 2 udp 630 ypserv
> 100004 1 udp 630 ypserv
> 100004 2 tcp 633 ypserv
> 100004 1 tcp 633 ypserv
> 100009 1 udp 632 yppasswdd
> 600100069 1 udp 634
> 600100069 1 tcp 636
> 100007 2 udp 641 ypbind
> 100007 1 udp 641 ypbind
> 100007 2 tcp 644 ypbind
> 100007 1 tcp 644 ypbind
> 100021 1 udp 2408 nlockmgr
> 100021 3 udp 2408 nlockmgr
> 100024 1 udp 997 status
> 100024 1 tcp 999 status
> todd@ws02~ $
>
> I would add that all these programs worked fine before I did an apt-get
> update ; apt-get dist-upgrade which upgraded about 35 packages (so I am
> not sure what caused the problem).
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs