SUMMARY: nfs error messages

From: Larry Chin (larry@cch.com)
Date: Mon Oct 05 1992 - 18:41:52 CDT


Original query:

System: Sparc 2
        64 MB of memory running 4.1.2, NIS, C2

today the console on this machine started spewing:

   nfs_server: bad sendreply

error messages and would not allow any interactive login sessions.

I finally had to reboot the machine to get it to a working state again.

If someone out there knows what the cause or solution to this problem
might be could you please let me know.

I will summarize.
===============================================================================

Tally:
        2 replies
        
Thanks to:

ilbeig@cogniseis.com ( Amir Ilbeig )
poffen@sj.ate.slb.com ( Russ Poffenberger )

==============================================================================

Summary:

It turns out the problem was caused by a VAX node being down. We mount an number
of the VAX drives via NFS and when the node went down the drives were mounted.
The drives could not be umounted since the VAX was down, hence the only way
to get rid of the messages was to reboot the SUNs, and when they came up the
VAX drives were not mounted and the messages went away.

Thanks to the two sun-mangers who took the time to reply, your efforts are
greatly appreciated.

The two replies recieved follow.

==============================================================================

I have received the above error messages so far 3 times, last 5 months and each
time I found the problem with the loss cable.

But I never had to reboot the system.
I like to see your summarize list and your discovery.

==============================================================================

 I don't think the error itself is
the cause of the problem but a symptom. It occurs when a client makes an NFS
request, and something happens so that the server cannot send the reply back.
This is usually the result of a routing problem. I would say that the routes
on your sparc-2 got messed up. If it wouldn't let you login, it is possibly
because the NIS server it was bound yo was also not reachable because of
the routing, or something similar.

Larry Chin {larry@cch.com} CCH Canadian Ltd.
System Administrator 6 Garamond Court
Research and Development Don Mills, Ontario.
(416) 441-4001 ext. 349 M3C 1Z5

If you're going to do something tonight that you'll be sorry for
tomorrow morning, sleep late.
                -- Henny Youngman



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:06:51 CDT