I'm trying to get FreeNAS (based on FreeBSD) to serve up NFS shares. It keep failing with
nfsd: Can't bind to tcp addr *: Address already in use
Which doesn't make sense. I tried binding to a specific address (the IP address of this server) and I get the same message, but with the IP address instead of *.
No other services are running on this server, other than http (80). Where do I start?
Thanks, Kevin
(I know you know this, but...) It means that nfsd is probably already running. Check the Services tab. If it's not running, SSH in (or use the console) to run netstat -an. I have seen FreeNAS lose track of a service, very rarely - I don't know why.
Hm, wait, there should be a port# after the colon. Go to Services->NFS settings (the wrench icon) and make sure the three "bind port" fields are *really* empty, no spaces or tabs hidden in them.
Make sure NFS is set to "start on boot". Then reboot. Don't rely on freenas' rc service framework when troubleshooting weird stuff like this.
Beyond that... dunno, let us know when you figure it out?
-Adam
On 2018-07-10 09:02, Kevin McGregor wrote:
I'm trying to get FreeNAS (based on FreeBSD) to serve up NFS shares. It keep failing with
nfsd: Can't bind to tcp addr *: Address already in use
Which doesn't make sense. I tried binding to a specific address (the IP address of this server) and I get the same message, but with the IP address instead of *.
No other services are running on this server, other than http (80). Where do I start?
Thanks, Kevin _______________________________________________ Roundtable mailing list Roundtable@muug.ca https://muug.ca/mailman/listinfo/roundtable
Okay, so something *is* listening on port 2049 of <FreeNAS-IP> (confirmed with netstat -an4).
I can ping both ways successfully. Both machines are on the same physical switch. Both are on the same subnet, same netmask, etc. Source (VMware ESXi) says "Unable to contact NFS server" ESXi firewall disabled with " esxcli network firewall set --enabled false " FreeNAS /var/log/messages has three entries like mountd[pid]: mount request successful from <IP> for <mountpoint>
This is really annoying. What else can I try/check?
On Tue, Jul 10, 2018 at 9:02 AM Kevin McGregor kevin.a.mcgregor@gmail.com wrote:
I'm trying to get FreeNAS (based on FreeBSD) to serve up NFS shares. It keep failing with
nfsd: Can't bind to tcp addr *: Address already in use
Which doesn't make sense. I tried binding to a specific address (the IP address of this server) and I get the same message, but with the IP address instead of *.
No other services are running on this server, other than http (80). Where do I start?
Thanks, Kevin
What happens when you run 'showmount -e localhost' on the freeNas box?
-- Wyatt Zacharias
On Tue, Jul 10, 2018 at 10:54 AM, Kevin McGregor <kevin.a.mcgregor@gmail.com
wrote:
Okay, so something *is* listening on port 2049 of <FreeNAS-IP> (confirmed with netstat -an4).
I can ping both ways successfully. Both machines are on the same physical switch. Both are on the same subnet, same netmask, etc. Source (VMware ESXi) says "Unable to contact NFS server" ESXi firewall disabled with " esxcli network firewall set --enabled false " FreeNAS /var/log/messages has three entries like mountd[pid]: mount request successful from <IP> for <mountpoint>
This is really annoying. What else can I try/check?
On Tue, Jul 10, 2018 at 9:02 AM Kevin McGregor kevin.a.mcgregor@gmail.com wrote:
I'm trying to get FreeNAS (based on FreeBSD) to serve up NFS shares. It keep failing with
nfsd: Can't bind to tcp addr *: Address already in use
Which doesn't make sense. I tried binding to a specific address (the IP address of this server) and I get the same message, but with the IP address instead of *.
No other services are running on this server, other than http (80). Where do I start?
Thanks, Kevin
Board mailing list Board@muug.ca https://muug.ca/mailman/listinfo/board
Permissions. No joke... Root isn't root when NFS is involved. Don't bother trying to get ESXi to try operating as non-root, as easily fly to the moon by flapping your arms. Instead configure a host-specific override on FreeNAS mapping root to a real user on FreeNAS that owns the volume/subvolume/share. Manually chown/chmod if necessary.
(Storage -> select the shared volume, then the left-most icon at the bottom is "Change Permissions".)
-Adam
On 2018-07-10 10:54, Kevin McGregor wrote:
Okay, so something *is* listening on port 2049 of <FreeNAS-IP> (confirmed with netstat -an4).
I can ping both ways successfully. Both machines are on the same physical switch. Both are on the same subnet, same netmask, etc. Source (VMware ESXi) says "Unable to contact NFS server" ESXi firewall disabled with " esxcli network firewall set --enabled false " FreeNAS /var/log/messages has three entries like mountd[pid]: mount request successful from <IP> for <mountpoint>
This is really annoying. What else can I try/check?
On Tue, Jul 10, 2018 at 9:02 AM Kevin McGregor kevin.a.mcgregor@gmail.com wrote:
I'm trying to get FreeNAS (based on FreeBSD) to serve up NFS shares. It keep failing with
nfsd: Can't bind to tcp addr *: Address already in use
Which doesn't make sense. I tried binding to a specific address (the IP address of this server) and I get the same message, but with the IP address instead of *.
No other services are running on this server, other than http (80). Where do I start?
Thanks, Kevin
Roundtable mailing list Roundtable@muug.ca https://muug.ca/mailman/listinfo/roundtable
Odd.
I have an unprivileged account in FreeNAS ("vmware") and corresponding group. I removed all of the volumes/NFS shares, then recreated them and used the "Change Permissions" button like you suggested to assign "vmware" the permissions and ownership. Then I changed the NFS configuration to map all NFS access to vmware/vmware.
I still get mountd logging "mount request succeeded", and ESXi reports "Can't connect to NFS server".
showmount -e shows /mnt/data/stuff Everyone
I tried configuring the share to "Map root user to..." and alternately tried "Mapall users to...", and nothing changed.
Surely it's something trivial I've overlooked?
On Tue, Jul 10, 2018 at 11:36 AM Adam Thompson athompso@athompso.net wrote:
Permissions. No joke... Root isn't root when NFS is involved. Don't bother trying to get ESXi to try operating as non-root, as easily fly to the moon by flapping your arms. Instead configure a host-specific override on FreeNAS mapping root to a real user on FreeNAS that owns the volume/subvolume/share. Manually chown/chmod if necessary.
(Storage -> select the shared volume, then the left-most icon at the bottom is "Change Permissions".)
-Adam
On 2018-07-10 10:54, Kevin McGregor wrote:
Okay, so something *is* listening on port 2049 of <FreeNAS-IP> (confirmed with netstat -an4).
I can ping both ways successfully. Both machines are on the same physical switch. Both are on the same subnet, same netmask, etc. Source (VMware ESXi) says "Unable to contact NFS server" ESXi firewall disabled with " esxcli network firewall set --enabled false " FreeNAS /var/log/messages has three entries like mountd[pid]: mount request successful from <IP> for <mountpoint>
This is really annoying. What else can I try/check?
On Tue, Jul 10, 2018 at 9:02 AM Kevin McGregor kevin.a.mcgregor@gmail.com wrote:
I'm trying to get FreeNAS (based on FreeBSD) to serve up NFS shares. It keep failing with
nfsd: Can't bind to tcp addr *: Address already in use
Which doesn't make sense. I tried binding to a specific address (the IP address of this server) and I get the same message, but with the IP address instead of *.
No other services are running on this server, other than http (80). Where do I start?
Thanks, Kevin
Roundtable mailing list Roundtable@muug.ca https://muug.ca/mailman/listinfo/roundtable
Board mailing list Board@muug.ca https://muug.ca/mailman/listinfo/board
On July 10, 2018 1:42:28 PM CDT, Kevin McGregor kevin.a.mcgregor@gmail.com wrote:
Odd.
I have an unprivileged account in FreeNAS ("vmware") and corresponding group. I removed all of the volumes/NFS shares, then recreated them and used the "Change Permissions" button like you suggested to assign "vmware" the permissions and ownership. Then I changed the NFS configuration to map all NFS access to vmware/vmware.
I still get mountd logging "mount request succeeded", and ESXi reports "Can't connect to NFS server".
showmount -e shows /mnt/data/stuff Everyone
I tried configuring the share to "Map root user to..." and alternately tried "Mapall users to...", and nothing changed.
Surely it's something trivial I've overlooked?
On Tue, Jul 10, 2018 at 11:36 AM Adam Thompson athompso@athompso.net wrote:
Permissions. No joke... Root isn't root when NFS is involved.
Don't
bother trying to get ESXi to try operating as non-root, as easily fly
to
the moon by flapping your arms. Instead configure a host-specific
override
on FreeNAS mapping root to a real user on FreeNAS that owns the volume/subvolume/share. Manually chown/chmod if necessary.
(Storage -> select the shared volume, then the left-most icon at the bottom is "Change Permissions".)
-Adam
On 2018-07-10 10:54, Kevin McGregor wrote:
Okay, so something *is* listening on port 2049 of <FreeNAS-IP>
(confirmed
with netstat -an4).
I can ping both ways successfully. Both machines are on the same physical switch. Both are on the same subnet, same netmask, etc. Source (VMware ESXi) says "Unable to contact NFS server" ESXi firewall disabled with " esxcli network firewall set --enabled
false "
FreeNAS /var/log/messages has three entries like mountd[pid]: mount request successful from <IP> for <mountpoint>
This is really annoying. What else can I try/check?
On Tue, Jul 10, 2018 at 9:02 AM Kevin McGregor
wrote:
I'm trying to get FreeNAS (based on FreeBSD) to serve up NFS shares.
It
keep failing with
nfsd: Can't bind to tcp addr *: Address already in use
Which doesn't make sense. I tried binding to a specific address (the
IP
address of this server) and I get the same message, but with the IP
address
instead of *.
No other services are running on this server, other than http (80).
Where
do I start?
Thanks, Kevin
Roundtable mailing list Roundtable@muug.ca https://muug.ca/mailman/listinfo/roundtable
Board mailing list Board@muug.ca https://muug.ca/mailman/listinfo/board
Hm. Probably, yes, but I can't think what offhand. Maybe do tcpdump on the freenas server and then inspect it, to find out that all ESXi is *trying* to do to FreeNas (in addition to the bits that are succeeding). Dunno, sorry. -Adam
Sigh.
Turns out the 'solution' was to upgrade from FreeNAS 11.1-U4 to FreeNAS 11.1-U5. It worked fine after that.
On Tue, Jul 10, 2018 at 2:36 PM Adam Thompson athompso@athompso.net wrote:
On July 10, 2018 1:42:28 PM CDT, Kevin McGregor < kevin.a.mcgregor@gmail.com> wrote:
Odd.
I have an unprivileged account in FreeNAS ("vmware") and corresponding group. I removed all of the volumes/NFS shares, then recreated them and used the "Change Permissions" button like you suggested to assign "vmware" the permissions and ownership. Then I changed the NFS configuration to map all NFS access to vmware/vmware.
I still get mountd logging "mount request succeeded", and ESXi reports "Can't connect to NFS server".
showmount -e shows /mnt/data/stuff Everyone
I tried configuring the share to "Map root user to..." and alternately tried "Mapall users to...", and nothing changed.
Surely it's something trivial I've overlooked?
On Tue, Jul 10, 2018 at 11:36 AM Adam Thompson athompso@athompso.net wrote:
Permissions. No joke... Root isn't root when NFS is involved. Don't bother trying to get ESXi to try operating as non-root, as easily fly to the moon by flapping your arms. Instead configure a host-specific override on FreeNAS mapping root to a real user on FreeNAS that owns the volume/subvolume/share. Manually chown/chmod if necessary.
(Storage -> select the shared volume, then the left-most icon at the bottom is "Change Permissions".)
-Adam
On 2018-07-10 10:54, Kevin McGregor wrote:
Okay, so something *is* listening on port 2049 of <FreeNAS-IP> (confirmed with netstat -an4).
I can ping both ways successfully. Both machines are on the same physical switch. Both are on the same subnet, same netmask, etc. Source (VMware ESXi) says "Unable to contact NFS server" ESXi firewall disabled with " esxcli network firewall set --enabled false " FreeNAS /var/log/messages has three entries like mountd[pid]: mount request successful from <IP> for <mountpoint>
This is really annoying. What else can I try/check?
On Tue, Jul 10, 2018 at 9:02 AM Kevin McGregor < kevin.a.mcgregor@gmail.com> wrote:
I'm trying to get FreeNAS (based on FreeBSD) to serve up NFS shares. It keep failing with
nfsd: Can't bind to tcp addr *: Address already in use
Which doesn't make sense. I tried binding to a specific address (the IP address of this server) and I get the same message, but with the IP address instead of *.
No other services are running on this server, other than http (80). Where do I start?
Thanks, Kevin
Roundtable mailing list Roundtable@muug.ca https://muug.ca/mailman/listinfo/roundtable
Board mailing list Board@muug.ca https://muug.ca/mailman/listinfo/board
Hm. Probably, yes, but I can't think what offhand. Maybe do tcpdump on the freenas server and then inspect it, to find out that all ESXi is *trying* to do to FreeNas (in addition to the bits that are succeeding). Dunno, sorry.
-Adam
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-
Adam Thompson -
Kevin McGregor -
Wyatt Zacharias