From owner-freebsd-questions@FreeBSD.ORG Wed Apr 21 01:26:16 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3DA3E106564A for ; Wed, 21 Apr 2010 01:26:16 +0000 (UTC) (envelope-from peter@vfemail.net) Received: from vfemail.net (dotsevenfive.vfemail.net [69.11.239.75]) by mx1.freebsd.org (Postfix) with ESMTP id 827408FC1F for ; Wed, 21 Apr 2010 01:26:15 +0000 (UTC) Received: (qmail 55409 invoked by uid 89); 21 Apr 2010 01:23:36 -0000 Received: from localhost (HELO freequeue.vfemail.net) (127.0.0.1) by localhost with SMTP; 21 Apr 2010 01:23:36 -0000 Received: (qmail 26260 invoked by uid 89); 20 Apr 2010 22:41:41 -0000 Received: from unknown (HELO www-52-2.vfemail.net) (vfemail@172.16.100.52) by FreeQueue with SMTP; 20 Apr 2010 22:41:41 -0000 Received: (qmail 95709 invoked by uid 89); 20 Apr 2010 22:43:57 -0000 Received: by simscan 1.4.0 ppid: 95701, pid: 95706, t: 0.1359s scanners:none Received: from unknown (HELO Bacchus.vfemail.net) (cGV0ZXJAdmZlbWFpbC5uZXQ=@67.101.12.44) by 172.16.100.52 with ESMTPA; 20 Apr 2010 22:43:56 -0000 X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Tue, 20 Apr 2010 17:53:23 -0400 To: freebsd-questions@freebsd.org From: peter@vfemail.net In-Reply-To: References: <20100419152330.42C931065674@hub.freebsd.org> <20100419165048.B6F6C106567C@hub.freebsd.org> <20100420182520.EFF83106564A@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-Id: <20100421012616.3DA3E106564A@hub.freebsd.org> Subject: Re: Request for mount_nfs assistance X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Apr 2010 01:26:16 -0000 I'm not certain what an RPC connection is, but I assume it's some type of flow of data. Nothing referring to RPC appears in either machine's logs. Not a lot of activity occurs on the file server at 192.168.0.244. It's primary purpose in life is to act as a file server for the machine at 192.168.0.252, which is the machine having difficulty connecting. It's worked flawlessly for years. The time-out problem is something that's appeared in the past week. I'm using a stale version of FreeBSD, but why would that cause mount_nfs to suddenly start timing out? ------- At 04:52 PM 4/20/2010, Jon Mercer wrote: >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, 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, 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, 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 >----------------------------------------------------------------------- >_______________________________________________ >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"