NFS problems after upgrade to trunk

[Wayne Workman]

@John-Sartoris Ok. I guess the next thing to check is probably the most simple, but I just didn’t think about it. Check permissions.

ls -lahRt /images

Do that on both the master and storage node. Compare results.

to set permissions on the images directory recursively, it’s just:

chmod -R 777 /images

We recommend 777 for troubleshooting.

[John Sartoris]

@Wayne-Workman

Ok, I didn’t expect that considering Thursday both sites were working fine. I’ll try making the master match storage and see what happens.

Storage - working

/images/Win10BaseR1:
total 18G
-rwxr-xr-x  1 fog  fog   18G Feb  4 15:06 sys.img.000
drwxr-xr-x  2 fog  fog  4.0K Feb  4 15:03 .
-rwxr-xr-x  1 fog  fog  299M Feb  4 15:03 rec.img.000
-rwxr-xr-x  1 fog  fog     0 Feb  4 14:33 d1.original.swapuuids
-rwxr-xr-x  1 fog  fog   259 Feb  4 14:33 d1.original.partitions
-rwxr-xr-x  1 fog  fog    15 Feb  4 14:33 d1.original.fstypes
-rwxr-xr-x  1 fog  fog     2 Feb  4 14:33 d1.fixed_size_partitions
drwxrwxrwx 18 root root 4.0K Feb  4 12:22 ..

Master - not working

/images/Win10BaseR1:
total 18G
drwxrwxrwx 18 fog  root 4.0K Feb  4 15:02 ..
-rwxrwxrwx  1 root root  18G Feb  4 15:02 sys.img.000
drwxrwxrwx  2 root root 4.0K Feb  4 14:33 .
-rwxrwxrwx  1 root root 299M Feb  4 14:33 rec.img.000
-rwxrwxrwx  1 root root   15 Feb  4 14:32 d1.original.fstypes
-rwxrwxrwx  1 root root    0 Feb  4 14:32 d1.original.swapuuids
-rwxrwxrwx  1 root root  259 Feb  4 14:32 d1.original.partitions
-rwxrwxrwx  1 root root    2 Feb  4 14:32 d1.fixed_size_partitions

[Wayne Workman]

@John-Sartoris also, chown -R fog:root /images may help as well. But you still need 777 perms from the earlier command.

[John Sartoris]

@Wayne-Workman

I was already at 777 on the master but after resetting own:group and perms for good measure, and restarting nfs-kernel-server, still no luck on the deploy.

[Sebastian Roth]

You mentioned creating .mntcheck files. Are you sure they are properly in place?

[Wayne Workman]

@John-Sartoris said:

I can now mount the master from storage.

Fog deploy still however still has the same issue when trying to use the local master node. If I point to the cross wan storage node deployment works.

make sure you have the right IP for the main server. Make sure the image path and FTP path are correct inside storage management. If all looks good, click save anyways just to push the settings. Sometimes the auto-fill feature in web browsers really screw with this area.

It’s just not typical for NFS to break in this manner, that’s why I ask you to check these things.

[John Sartoris]

@Sebastian-Roth

Same places as the working node.

/images:
total 72
drwxrwxrwx 18 root root 4096 Feb  4 12:22 .
drwxr-xr-x 26 root root 4096 Feb  8 09:01 ..
-rwxrwxrwx  1 root root    0 Jul 29  2014 .mntcheck

/images/dev:
total 8
drwxrwxrwx  2 root root 4096 Jul 29  2014 .
drwxrwxrwx 18 root root 4096 Feb  4 12:22 ..
-rwxrwxrwx  1 root root    0 Jul 29  2014 .mntcheck

[Wayne Workman]

@John-Sartoris Are you using the location plugin?

[John Sartoris]

@Wayne-Workman said:

@John-Sartoris Are you using the location plugin?

Yes, I am using the location plugin. Is there a known issue?

I completely understand. When it doesn’t make sense double check things the wouldn’t make sense…

IP addresses and Paths are correct. Re-saved, I also double checked and re-saved the node choice in the location plugin.

Still no luck. Is there anyway I can get more detail on the client machine to see exactly what is erroring? It just says “An error has been detected!”, it doesn’t specify.

[Wayne Workman]

@John-Sartoris Do a debug download. on the task confirmation page, the debug option is a checkbox. This boots the target host into a shell. On the target host, there is a variable dump initially on the screen, it can be quite valuable to see what it says.

Additionally, I would recommend removing the location plugin entirely (via plugin management) and then reinstalling it and re-setting it up for your various locations.

[John Sartoris]

@Wayne-Workman

From the client in debug…

mount: mounting 10.2.yyy.xxx:/images on images failed: Connection refused

sounds to me like it’s still a permissions or acl type issue.

[Wayne Workman]

@John-Sartoris refused is different than denied… Have you checked for IP conflicts?

[george1421]

I didn’t read all of the posts here, but could you do a showmount -e 127.0.0.1 This will show us what you have NFS shared on your FOG server. You could then do the same command but use your FOG servers external IP address instead of the loopback interface. It could be a firewall issue.

[John Sartoris]

@george1421 said:

I didn’t read all of the posts here, but could you do a showmount -e 127.0.0.1 This will show us what you have NFS shared on your FOG server.

That’s shows that the exports are proper and they do actually work from the storage node cross site, but a client on the local site can’t connect.

[John Sartoris]

@Wayne-Workman said:

@John-Sartoris refused is different than denied… Have you checked for IP conflicts?

I haven’t specifically checked, but this server is configured in the same way as the rest in our environment. DHCP with a reservation. This is the only server that should get this address. Access ports are not configured in this vlan. I have not had any issues connecting to the server expect via NFS. Ping and SSH work from debug client.

[Wayne Workman]

@John-Sartoris I’m thinking it is probably something network related.

[John Sartoris]

@Wayne-Workman

I understand and agree with the assessment, but nothing has changed on the LAN in weeks other that the fog server updates. Firewalls are disabled and allowed for good measure. I even just tried added iptables rules without success.

[Wayne Workman]

@John-Sartoris can you quickly throw together a CentOS 7 VM and install fog trunk to test?

[george1421]

@Wayne-Workman I’m in a meeting right now (yeah its a bit boring) so I can’t test. But from a debug (boot) session, is the showmount command installed in FOS? It would be interesting to know from the client perspective if the FOG server is showing its mount information.

[edit] The other thing would be to try to do a manual nfs mount from the FOS client to the FOG server. If it maps then there is a parameter setup incorrectly (somewhere) in the FOG GUI. The mount command would be something like mount <fog_server_ip>:/images /img (or what ever the local directory is called on the FOG client) [/edit]

[John Sartoris]

@george1421

I’m trying to manually mount from the FOG Client now, and I’m receiving a connection refused.

@Wayne-Workman
Configuring another VM would be possible, but quite a heavy bit of work for what sure seems to be a firewall config or NFS ACL issue that happen during OS or Fog upgrade.