> From: "Orenstein, Dave" <[EMAIL PROTECTED]> > To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> > Subject: Re: NFS/network card problems (John Dalbec) > Date: Wed, 10 Jul 2002 15:31:14 -0400 > Reply-To: [EMAIL PROTECTED] > > John -- While it may appear that your NFS server went down before the client > NIC > it's possible that the NIC went first. The repeated attempts by the NFS > server > to re-establish of the connection may have caused it to crash. Am I correct > that the server is OK now? The "localhost error" on the client would
The server is OK now. I restarted NFS at 5:03 PM. The server crashed perhaps 30 seconds later. I don't see any nfs messages on the client until after 5:04. The server finished coming up at 5:20. The messages from the client about statd and lockd started after 5:21. Maybe if I had waited long enough it would have cleared up on its own, but I didn't want to wait too long. > indicate > that either the card has failed or the driver has failed. Try pinging the > client from > another host. I'd guess that it isn't going to work. -- Dave I think I wasn't able to ping the client. In any case the client appears to be OK now. I've had some limited exposure to *a* network driver. Could the network card be running out of "buffer memory" (is that even the right name for it)? > > David I. Orenstein > Project Engineer/Maintenance Engineer > ABC Radio Networks > It is our business to collaboratively enhance professional resources so that > we may endeavor to synergistically leverage existing progressive benefits > while maintaining the highest standards *cringe* Thanks, John Dalbec _______________________________________________ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
