From owner-freebsd-net@FreeBSD.ORG  Fri Apr  1 21:55:27 2011
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id D876E1065679;
	Fri,  1 Apr 2011 21:55:27 +0000 (UTC) (envelope-from freebsd@hub.org)
Received: from hub.org (hub.org [200.46.204.220])
	by mx1.freebsd.org (Postfix) with ESMTP id AA4E98FC19;
	Fri,  1 Apr 2011 21:55:27 +0000 (UTC)
Received: from maia.hub.org (maia-5.hub.org [200.46.204.29])
	by hub.org (Postfix) with ESMTP id F41493250A90;
	Fri,  1 Apr 2011 18:35:31 -0300 (ADT)
Received: from hub.org ([200.46.204.220])
	by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024)
	with ESMTP id 73447-05; Fri,  1 Apr 2011 21:35:32 +0000 (UTC)
Received: by hub.org (Postfix, from userid 1002)
	id BDC453250A8F; Fri,  1 Apr 2011 18:35:31 -0300 (ADT)
Received: from localhost (localhost [127.0.0.1])
	by hub.org (Postfix) with ESMTP id B6DAD3250A8D;
	Fri,  1 Apr 2011 18:35:31 -0300 (ADT)
Date: Fri, 1 Apr 2011 18:35:31 -0300 (ADT)
From: "Marc G. Fournier" <freebsd@hub.org>
X-X-Sender: scrappy@hub.org
To: freebsd-net@freebsd.org, freebsd-questions@freebsd.org
Message-ID: <alpine.BSF.2.00.1104011820380.55888@hub.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: 
Subject: nfs error: No route to host when starting apache ...
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Apr 2011 21:55:27 -0000


I just setup an nfs mount between two servers ...

ServerA, nfsd on 192.168.1.8
ServerB, nfs client on 192.168.1.7

I have a jail, ServerC, running on 192.168.1.7 ... most operations appear 
to work, but it looks like 'special files' of a sort aren't working, for 
when I try and startup Apache, I get:

[Fri Apr 01 19:42:02 2011] [emerg] (65)No route to host: couldn't grab the 
accept mutex

When I try and do a 'newaliases', I get:

# newaliases
postalias: fatal: lock /etc/aliases.db: No route to host

Yet, for instance, both MySQL and PostgreSQL are running without any 
issues ...

So, the mount is there, it is readable, it is working ... I can ssh into 
the jail, I can create files, etc ...

I do have rpc.lockd and rpc.statd running on both client / server sides 
...

I'm not seeing anything in eithr the man page for mount_nfs *or* nfsd that 
might account / corect for something like this, but since I'm not sure 
what "this" is exactly, not sure exactl what I should be looking for :(

Note that this behaviour happens at the *physical* server level as well, 
having tested with using postalias to generate the same 'lock' issue above 
...

Now, I do have mountd/nfsd started iwth the -h to bind them to 192.168.1.8 
... *but*, the servers themselves, although on same switch do have 
different default gateways ... I'm not seeing anything within the man page 
for, say, rpc.statd/rpc.lockd that allows me to bind it to the 
192.168.1.0/24 IP, so is it binding to my public IP instead of my private? 
So nfsd / mount_nfs can talk find, as they go thorugh 192.168.1.0/24 as 
desired, but rpc.statd/rpc.lockd are the public IPs and not able to talk 
to each other?

Thx ...