Date: Fri, 12 Oct 2007 10:34:39 -0500 From: Derek Ragona <derek@computinginnovations.com> To: Michael Smith <mksmith@adhost.com>, questions@freebsd.org Subject: Re: Questions about HUP'ing nfsd Message-ID: <6.0.0.22.2.20071012103232.023cb5b0@mail.computinginnovations.com> In-Reply-To: <2BBC6552-76B0-4D22-9F68-BEC9E46C0FFB@adhost.com> References: <2BBC6552-76B0-4D22-9F68-BEC9E46C0FFB@adhost.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 10:25 AM 10/12/2007, Michael Smith wrote:
>Hello All:
>
>We have a NAS that's running 6.2 with nfds, mountd, rpc_statd,
>rpcbind and rpc_lockd. Last night we had a scenario where nfs
>clients, once disconnected, couldn't reconnect to the NAS, reporting
>RPC timeouts.
>
>We attempted to restart all of the services above in various orders,
>but we were not able to get the clients reconnected. We ultimately
>rebooted the NAS server and all was well.
>
>My question is, in troubleshooting this sort of thing, is there a
>proper sequence for stopping and restarting the various services
>associated with nfs? Any hints would be greatly appreciated.
>
>Regards,
>
>Mike
I wouldn't know the right order, and even if you did stop and start
everything in the right order, it may not fix the problem. Your problem
could be in the network stack, or someplace else. That is why I usually:
"If in doubt, reboot it out"
Your users already couldn't connect correctly, so no real harm in a reboot.
-Derek
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.0.0.22.2.20071012103232.023cb5b0>