VM not accepted by NFS server -

[poma]

On 24.07.2014 01:23, Rick Stevens wrote:
> On 07/23/2014 04:14 PM, Bob Goodwin - Zuni, Virginia, USA issued this
> missive:
>>
>> On 07/23/14 17:28, poma wrote:
>>>
>>> First you adjust the debug logging directed to syslog, then it is
>>> applied, and with the journalctl, you can monitor server events. ;)
>>>
>>>
>>> poma
>>
>> Well this appears to be the area of interest however I don't know how to
>> interpret it?
>>
>> Jul 23 16:51:45 localhost.localdomain systemd[1]: Starting NFS Mount
>> Daemon...
>> Jul 23 16:51:45 localhost.localdomain systemd[1]: Started NFS Mount Daemon.
>> Jul 23 16:51:45 localhost.localdomain systemd[1]: Starting NFS Server...
>> Jul 23 16:51:45 localhost.localdomain rpc.mountd[5596]: Version 1.3.0
>> starting
>> Jul 23 16:51:45 localhost.localdomain kernel: NFSD: starting 90-second
>> grace period (net ffffffff819a09c0)
>> Jul 23 16:51:45 localhost.localdomain systemd[1]: Started NFS Server.
>> Jul 23 16:51:45 localhost.localdomain systemd[1]: Starting NFSv4 ID-name
>> mapping daemon...
>> Jul 23 16:51:45 localhost.localdomain systemd[1]: Starting NFS Remote
>> Quota Server...
>> Jul 23 16:51:45 localhost.localdomain systemd[1]: Started NFS Remote
>> Quota Server.
>> Jul 23 16:51:45 localhost.localdomain systemd[1]: Started NFSv4 ID-name
>> mapping daemon.
>> Jul 23 16:54:04 localhost.localdomain dhclient[1081]: DHCPREQUEST on
>> eth0 to 192.168.122.1 port 67 (xid=0xa15c2e7)
>> Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: DHCPREQUEST
>> on eth0 to 192.168.122.1 port 67 (xid=0xa15c2e7)
>> Jul 23 16:54:04 localhost.localdomain dhclient[1081]: DHCPACK from
>> 192.168.122.1 (xid=0xa15c2e7)
>> Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: DHCPACK from
>> 192.168.122.1 (xid=0xa15c2e7)
>> Jul 23 16:54:04 localhost.localdomain dhclient[1081]: bound to
>> 192.168.122.14 -- renewal in 1474 seconds.
>> Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: bound to
>> 192.168.122.14 -- renewal in 1474 seconds.
>> Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: <info>
>> (eth0): DHCPv4 state changed renew -> renew
>> Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: <info>
>> address 192.168.122.14
>> Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: <info>   plen
>> 24 (255.255.255.0)
>> Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: <info>
>> gateway 192.168.122.1
>> Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: <info> server
>> identifier 192.168.122.1
>> Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: <info> lease
>> time 3600
>> Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: <info>
>> nameserver '192.168.122.1'
>> Jul 23 16:54:04 localhost.localdomain dbus[665]: [system] Activating via
>> systemd: service name='org.freedesktop.nm_dispatcher
>> Jul 23 16:54:04 localhost.localdomain dbus-daemon[665]: dbus[665]:
>> [system] Activating via systemd: service name='org.freedes
>> Jul 23 16:54:04 localhost.localdomain systemd[1]: Starting Network
>> Manager Script Dispatcher Service...
>> Jul 23 16:54:04 localhost.localdomain dbus-daemon[665]: dbus[665]:
>> [system] Successfully activated service 'org.freedesktop.n
>> Jul 23 16:54:04 localhost.localdomain dbus[665]: [system] Successfully
>> activated service 'org.freedesktop.nm_dispatcher'
>
> Bob, get on the NFS server and verify that it's allowing mounts from the
> DHCP domain. It appears your VM is using DHCP to get an IP and it may be
> that your NFS server isn't exporting to the network or IP your client
> got via DHCP.
>
> The fact you got it mounted this time may just indicate that THIS TIME
> you got an IP allowed by the server. Next time, you may not be so
> lucky. :-/

192.168.122.1 could be DHCP server on Tomato,
192.168.122.14 could be DHCP client & NFS server on Fedora 20 host machine,
not NFS client on Centos7 VM.
However Bob can set up a Static DHCP on Tomato if it is,
http://en.wikibooks.org/wiki/Tomato_Firmware/Menu_Reference#Static_DHCP
so DHCP can be excluded from the context.


nfsd fan club