I've succeedig in getting a bit further ... by the time I got to the
bottom of my original, I started to think in terms of rpc more, and had
overlooked lookign at thte rpcbind man page, which *does* have a -h option
... setting that fixes things perfectly *almost* ...
The last issue I seem to be hitting *might* be a 6.x NFS client against a
7.x server issue ... ?
Postfix generates:
postfix/showq[65261]: fatal: select lock: Permission denied
The only post I found about this was:
http://lists.freebsd.org/pipermail/freebsd-questions/2010-April/215284.html
But there didn't appear to be any responses ... so either all responses
were private to Robert, or ... ?
This is my last 6.x box, so it is not overly critical, but would be nice
if I could get it to work properly ...
On Fri, 1 Apr 2011, Marc G. Fournier wrote:
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 ...
_______________________________________________
freebsd-...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
----
Marc G. Fournier Hub.Org Hosting Solutions S.A.
scra...@hub.org http://www.hub.org
Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scra...@hub.org
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
