srp@babar.mmwb.ucsf.edu (Scott R. Presnell) (09/28/90)
I am having problems with statd and lockd in a local network of SGIs (4D'/20G running 3.3.1). There are also sun sparcs on the same local net. Without running rpc.statd and rpc.lockd everything is fine. I've narrowed it down to this: Two hosts running both statd and lockd (checked registration with rpcinfo). The /usr/mail direcory is on host A, I am on host B (no MX records in the nameserver entry). /usr/mail is NFS mounted onto host B. I send mail to myself on host B. I don't get it. "mail" process exists but isn't going anywhere (appear stuck). There's a lock file for me (srp.lock) in the mail directory. On host B (babar) the SYSLOG says: Sep 27 16:21:21 babar unix: lock-manager: RPC error: Can't decode result On host A (celeste) the SYSLOG repeats until process death: Sep 27 17:03:45 celeste rpc.lockd[3673]: cannot contact local statd Sep 27 17:03:45 celeste rpc.lockd[3673]: req discard due to status monitor problem (rpc.statd is indeed running on this host and is rpc registered) Has anyone else experienced this sort of a problem? Can anyone provide a clue? Thanks for your help. - Scott -- Scott Presnell +1 (415) 476-9890 Pharm. Chem., S-926 Internet: srp@cgl.ucsf.edu University of California UUCP: ...ucbvax!ucsfcgl!srp San Francisco, CA. 94143-0446 Bitnet: srp@ucsfcgl.bitnet
slevy@poincare.geom.umn.edu (Stuart Levy) (10/03/90)
Yes, we did see something similar. Upon enabling rpc.{statd/lockd} on our SGI
3.3 NFS clients, we found that mail (actually /usr/bsd/Mail) would hang when we
tried to exit after reading mail. Our mail directory is shared as yours is;
the file server in our case is a Sun running 4.0.3.
The SGI technical support person I talked to didn't seem to know about this
problem; he tried to get me to check sendmail.cf and so forth, not too helpful.
I couldn't tell what was causing this, and we didn't desperately need NFS
file locking, so turned it off. Mail continued to hang even after the
statd/lockd daemons were killed, but rebooting the client seemed to
clear things up.
So you're not alone but I have no help to offer.
Stuart Levy, Geometry Group, University of Minnesota
slevy@geom.umn.eduamys@ncsa.uiuc.edu (Amy Swanson) (10/04/90)
slevy@poincare.geom.umn.edu (Stuart Levy) writes: >Yes, we did see something similar. Upon enabling rpc.{statd/lockd} on our SGI >3.3 NFS clients, we found that mail (actually /usr/bsd/Mail) would hang when we >tried to exit after reading mail. Our mail directory is shared as yours is; >the file server in our case is a Sun running 4.0.3. >The SGI technical support person I talked to didn't seem to know about this >problem; he tried to get me to check sendmail.cf and so forth, not too helpful. >I couldn't tell what was causing this, and we didn't desperately need NFS >file locking, so turned it off. Mail continued to hang even after the >statd/lockd daemons were killed, but rebooting the client seemed to >clear things up. >So you're not alone but I have no help to offer. > Stuart Levy, Geometry Group, University of Minnesota > slevy@geom.umn.edu We have been told by our SGI office that this problem will be fixed in the next maintenance tape release - 3.3.2? - which is supposed to be out this month. Can anyone at SGI confirm this? We are delaying the installation of 3.3 until this tape is released as many of the users depend on NFS mounted mail partitions for their email use. Amy amys@ncsa.uiuc.edu