Date: Tue, 20 Apr 2010 21:52:49 +0100 From: Jon Mercer <jon.mercer@achean.com> To: freebsd-questions@freebsd.org Subject: Re: Request for mount_nfs assistance Message-ID: <s2y6f8779041004201352za6cbfc45ue9ba5a17d1e6b45a@mail.gmail.com> In-Reply-To: <20100420182520.EFF83106564A@hub.freebsd.org> References: <20100419152330.42C931065674@hub.freebsd.org> <y2w6f8779041004190900v58366413laa3cc1dc36df0358@mail.gmail.com> <20100419165048.B6F6C106567C@hub.freebsd.org> <x2z6f8779041004200042pefabcff5kd89eb9d13bc8a945@mail.gmail.com> <20100420182520.EFF83106564A@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Do you have anything relating to RPC connections inbound on the server logs? It may also be time to look at which version of FBSD you are running. On 20 April 2010 19:06, <peter@vfemail.net> wrote: > > I deleted the unnecessary line from the /etc/exports file and rebooted both > machines. Connecting from the client to the server using an > "/sbin/mount_nfs 192.168.0.244:/usr/home1 /home1" command took forever . . > . well, somewhere between a half-hour and an hour. It used to be speedy. > Nothing mount-related has been logged in either server's /var/log/messages > file. > > I'm at a loss to know where to start to track down what's causing the slow > connection. > > ------ > > At 03:42 AM 4/20/2010, Jon Mercer wrote: > >Peter, > > > >The two lines shouldn't create a conflict, but it would seem to me to be > >more normal to append the second IP after the first, e.g.: > > > >/usr/home1 -maproot=root 192.168.0.252, 192.168.0.253 > > > >On the other hand, if the 253 machine doesn't need access it would be wise > >to remove the second line altogether and reduce any potential attack > arising > >from that machine on the mount. > > > >Have you checked /var/log/messages and any other files to see why the > server > >(maybe) didn't start after the last reboot? That could prevent any > >recurrence. > > > >Jon > > > >On 19 April 2010 17:48, <peter@vfemail.net> wrote: > > > >> > >> 192.168.0.244's /etc/exports file says: > >> > >> /usr/home1 -maproot=root 192.168.0.252 > >> /usr/home1 -maproot=root 192.168.0.253 > >> > >> 192.168.0.252 is the machine that should have access to 192.168.0.244's > >> drive, but was having difficulty obtaining it. I'm kind of surprised to > see > >> the entry for 192.168.0.253, because I don't think that machine has any > need > >> for access to the drive. > >> > >> Do these two entires in the /etc/exports file create a conflict? > >> > >> I don't believe there were any recent network-related changes. > >> > >> ------- > >> > >> At 12:00 PM 4/19/2010, Jon Mercer wrote: > >> >What information is contained in the /etc/exports file on the NFS > server? > >> If > >> >that changed between NFS Server restarts that _could_ be the cause. > >> > > >> >Also, has there been any simultaneous change in the network across > which > >> the > >> >servers speak? Especially with regard to port 111. > >> > > >> > > >> > > >> >On 19 April 2010 15:38, <peter@vfemail.net> wrote: > >> > > >> >> > >> >> I have two servers funning FreeBSD. For the past four years, an: > >> >> > >> >> /sbin/mount_nfs 192.168.0.244:/usr/home1 /home1 > >> >> > >> >> command has successfully allowed one server access to data on the > other > >> >> server's hard drive. > >> >> > >> >> This morning, following reboots of both servers, the mount_nsf > command > >> >> fails, returns: > >> >> > >> >> 192.168.0.244:/usr/home1: RPCPROG_MNT: RPC: Timed out > >> >> > >> >> error messages. > >> >> > >> >> Each server can ping the other and connect via ssh; the hardware's > >> working > >> >> fine; I don't believe anything's changed on either server recently; > and > >> the > >> >> find command doesn't indicate that any system files have been altered > in > >> the > >> >> past week. > >> >> > >> >> I'm at a complete loss for any explanation of the failure, and I'm > >> >> uncertain how to diagnose and fix the problem. > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> _______________________________________________ > >> >> freebsd-questions@freebsd.org mailing list > >> >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >> >> To unsubscribe, send any mail to " > >> >> freebsd-questions-unsubscribe@freebsd.org" > >> >> > >> > > >> > > >> > > >> >-- > >> >----------------------------------------------------------------------- > >> >Jon Mercer Director Achean Limited > >> > > >> > http://www.achean.com > >> > http://uk.linkedin.com/in/jonmercer > >> >----------------------------------------------------------------------- > >> >_______________________________________________ > >> >freebsd-questions@freebsd.org mailing list > >> >http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >> >To unsubscribe, send any mail to " > >> freebsd-questions-unsubscribe@freebsd.org" > >> > >> _______________________________________________ > >> freebsd-questions@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >> To unsubscribe, send any mail to " > >> freebsd-questions-unsubscribe@freebsd.org" > >> > > > > > > > >-- > >----------------------------------------------------------------------- > >Jon Mercer Director Achean Limited > > > > http://www.achean.com > > http://uk.linkedin.com/in/jonmercer > >----------------------------------------------------------------------- > >_______________________________________________ > >freebsd-questions@freebsd.org mailing list > >http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" > -- ----------------------------------------------------------------------- Jon Mercer Director Achean Limited http://www.achean.com http://uk.linkedin.com/in/jonmercer -----------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?s2y6f8779041004201352za6cbfc45ue9ba5a17d1e6b45a>