lockd problems with 101945-34 ??

lockd problems with 101945-34 ??

Post by Jeff Giacob » Thu, 30 Nov 1995 04:00:00



Hi all-

Just installed kernel patch 101945-34 on our SS1000 (in addition to the other
11 "recommended" patches).

We now seem to be having some trouble with lockd.  Most notably, "mailx"
hangs forever, and SAS refuses to start up (it worked fine yesterday :-( )

Pine only works if a user is logged onto the machine that holds the
/var/mail directory.  All the client machines NFS mount /var/mail from
the server (yes, I know that's not the best way to do things...)  Pine
was working perfectly from the client machines UNTIL I put 101945-34 on
the server.  Now it starts up, and hangs trying to open the Inbox.  I
suspect this is caused by Pine being unable to lock the
/var/mail/"username" file.

My /var/adm/messages file has been filling up with the following
messages, one every five minutes:

Nov 29 16:50:32 pegasus.montclair.edu lockd[175]: nlm1_reply: RPC:
Rpcbind failure
Nov 29 16:55:33 pegasus.montclair.edu lockd[175]: nlm1_reply: RPC:
Rpcbind failure
Nov 29 17:00:35 pegasus.montclair.edu lockd[175]: nlm1_reply: RPC:
Rpcbind failure
Nov 29 17:05:36 pegasus.montclair.edu lockd[175]: nlm1_reply: RPC:
Rpcbind failure

Any thoughts as to whether or not the lockd problem is related to 101945-34?

I know the details I've provided are a bit lacking, but my brain is fried...

Thanks for any and all advice....

--
Jeff

--
--------------------------------------------------------------------
        "There's such a fine line between clever and stupid"
                                                -David St. Hubbins
--------------------------------------------------------------------

 
 
 

lockd problems with 101945-34 ??

Post by Alexandre Khal » Fri, 01 Dec 1995 04:00:00




>Nov 29 16:50:32 pegasus.montclair.edu lockd[175]: nlm1_reply: RPC: Rpcbind failure

  I have been bitten by that one and I was/am on 101945-34.

  One of your clients has corrupted NFS data structures and is hitting back the
server.  Don't touch the server but fix the client.

  In my case, restarting rpc/nfs/autofs [which dismount/remount the nfs drives]
etc.. on the client did *not* work: I had to reboot it.

  To determine which is the bad client, running mail on everyone and dealing with
those that lock might be enough.

  I'd be curious to know how you eventually fix your problem.

--

Electrical Engineering Dpt.            office: Zachry 30G
Texas A&M University                   voice:  (409)845-7530
College Station TX 77843-3128          fax:    (409)845-6259

 
 
 

lockd problems with 101945-34 ??

Post by Carson Gasp » Fri, 01 Dec 1995 04:00:00




>Just installed kernel patch 101945-34 on our SS1000 (in addition to the other
>11 "recommended" patches).
>We now seem to be having some trouble with lockd.  Most notably, "mailx"
>hangs forever, and SAS refuses to start up (it worked fine yesterday :-( )

We are seeing the same behavior here. <sigh> That's _2_ bugs to call in to
Sun tomorrow...

--
--

http://www.cs.columbia.edu/~carson/home.html
<This is the boring business .sig - no outre sayings here>