All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Ryan <andrewr@collab.net>
To: Todd Weaver <todd@m2n.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: some programs hang when run over nfs.
Date: Tue, 09 Apr 2002 20:11:16 -0700	[thread overview]
Message-ID: <3CB3AD54.791414DB@collab.net> (raw)
In-Reply-To: Pine.LNX.4.33.0204091823080.19524-100000@minstrel.m2n.com

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  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2002-04-10  3:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-10  0:29 some programs hang when run over nfs Todd Weaver
2002-04-10  0:54 ` Andrew Ryan
2002-04-10  1:08   ` Todd Weaver
2002-04-10  1:25   ` Todd Weaver
2002-04-10  3:11     ` Andrew Ryan [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3CB3AD54.791414DB@collab.net \
    --to=andrewr@collab.net \
    --cc=nfs@lists.sourceforge.net \
    --cc=todd@m2n.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.