Problem with 'permission denied' after FOG server restart

[haste347]

Hello again, I have been using FOG for about a month or so with great success. I have uploaded about 30 different images to the server without a problem…until now.

I restarted the FOG server to install an internal back-up drive. I received the TFTP timeout, but then remembered to restart tftpd-hpa which resolved that issue.

I was able to register a new host, but now receive “Permission Denied” on the host when attempting to mount the /images folder on the server.

Most issues I see with this are when people move their /images folder to a different location. I have not made any changes other than the drive (which I have not mounted) and the restart.

I have tried a few fixes with no luck.

So far I have made sure the firewall is turned off, and /etc/exports looks like this…

/images *(ro_sync,no_wdelay,insecure_locks,no_root_squash,insecure)
/images/dev *(rw,sync,no_wdelay,no_root_squash,insecure)

This is on Ubuntu 14.04 with FOG 1.2.0

Again, this has been running well until the restart. Being so new to this, is there anything else I should check that a restart may have done?

Thank you again for your help!

[url=“/_imported_xf_attachments/1/1716_IMAG2053.jpg?:”]IMAG2053.jpg[/url]

[Wayne Workman]

Maybe take the drive out and see if the error goes away??

That’d be step one of troubleshooting, IMO.

[Sebastian Roth]

What are the permissions on your directories (ls -al /images && ls -al /images/dev)?

Please try to mount the NFS share from another computer and report about any errors you see:
[CODE]mkdir -p /mnt/nfstest && mount -v 10.0.2.250:/images /nfstest
umount /nfstest
mount -v 10.0.2.250:/images/dev /nfstest
umount /nfstest && rmdir /nfstest[/CODE]

[haste347]

Wayne, I have disconnected the drive, no change.

Frank, I have attached the output of the permissions. I am loading another PC with Ubuntu to help with testing.
The FOG setup should have made the share able to be mounted even after a restart, correct?

Thank you again, for your help. Getting into Linux has a decently steep learning curve and I appreciate your help!

[url=“/_imported_xf_attachments/1/1721_IMAG2054.jpg?:”]IMAG2054.jpg[/url]

[Sebastian Roth]

[quote=“haste347, post: 42908, member: 28447”]Frank, I have attached the output of the permissions. I am loading another PC with Ubuntu to help with testing.
The FOG setup should have made the share able to be mounted even after a restart, correct?[/quote]
Permissions look pretty good to me! Yes, FOG should setup NFS properly even if running it a couple of times and restarting the server doesn’t hurt either (as nfs server is being started as a service at boot time). Keep us posted how you go with mounting NFS from your new test machine.

[mecsr]

I am having a similar problem so I tried mounting on another computer. I attached a screenshot of the output.
It said permission denied, so I tried with sudo and it says only root can do that.
Thoughts?

[url=“/_imported_xf_attachments/1/1722_mount fail.PNG?:”]mount fail.PNG[/url]

[Sebastian Roth]

Forgot to say that mounting can usually only be done by root! So use [B]sudo[/B] with all these commands…

[mecsr]

I also get this error when I try to start a job with an image that worked fine with 1.2
I made sure all the options in the image management are the same as they were before and all that jazz.
I also tried the mounting again with just mounting in one command and got a wrong fs type, bad option, bad superblock error.
Screenshots attached.
Thanks again for all the help.

[url=“/_imported_xf_attachments/1/1723_job from fog.PNG?:”]job from fog.PNG[/url][url=“/_imported_xf_attachments/1/1724_tried again.PNG?:”]tried again.PNG[/url]

[Sebastian Roth]

Please run ‘sudo exportfs -a’ on the FOG server. Error message like the one you see in the web interfaces occour if there is no image stored in ‘/images/<name-of-image>’. Maybe you never uploaded one or it went missing. ‘ls -al /images’…

EDIT: And please make sure nfs client is installed (debian/ubuntu: sudo apt-get install nfs-common) on that machine that you run the tests from!

[mecsr]

The image files are all there right sizes and all.
exportfs -a gave a bunch of errors

[url=“/_imported_xf_attachments/1/1725_exportfs -a.PNG?:”]exportfs -a.PNG[/url]

[mecsr]

I just installed nfs-common on mount test machine and I got a more detailed failure.

Edit: Oh an my permissions are currently set to 777 for the /images folder for the sake of testing.
Typically I have them set to 775
owner and group is fog
I have also tried setting the group to www-data

[url=“/_imported_xf_attachments/1/1726_mount attempt.PNG?:”]mount attempt.PNG[/url]

[mecsr]

Well I feel dumb,
I just had to edit the etc/exports file after updating to say
/images …
and
/images/dev…
instead of
y…
and
y/dev…

Not sure why it changed itself to y as the images directory, it looks like everything is working now. Thanks again for all your help.

Thanks,
-JJ

[Sebastian Roth]

Who would’ve thought that it were wrong entries in /etc/exports… Sounds a bit like you hit the wrong keys when installing FOG. When the installer asked for the path you gave ‘y’ for ‘yes’ maybe…

[haste347]

Alright, from a workstation on the same subnet I tried the commands you listed…here are the results.

root@VEI-3000D:~# sudo mkdir -p /mnt/nfstest && mount -v 10.0.2.250:/images /nfstest
mount: no type was given - I’ll assume nfs because of the colon
mount: mount point /nfstest does not exist

root@VEI-3000D:~# sudo umount /nfstest
umount: /nfstest: not found

root@VEI-3000D:~# sudo mount -v 10.0.2.250:/images/dev /nfstest
mount: no type was given - I’ll assume nfs because of the colon
mount: mount point /nfstest does not exist

root@VEI-3000D:~# umount /nfstest && rmdir /nfstest
umount: /nfstest: not found

And, just for further testing to eliminate the folder not being there, I tried to mount to the /images folder.

root@VEI-3000D:~# sudo mount -v 10.0.2.250:/images
mount: can’t find 10.0.2.250:/images in /etc/fstab or /etc/mtab
root@VEI-3000D:~#

Thank you again for your help!!!

[Sebastian Roth]

Was probably pretty late when I wrote this post… My fault, shoud be like this:
[CODE]mkdir -p /mnt/nfstest && mount -v 10.0.2.250:/images /mnt/nfstest
umount /mnt/nfstest
mount -v 10.0.2.250:/images/dev /mnt/nfstest
umount /mnt/nfstest && rmdir /mnt/nfstest[/CODE]
Can you see the difference? By the way… what is the IP address of your FOG server?

[B]And please make sure that ‘nfs-common’ (debian/ubuntu) or ‘nfs-utils’ and ‘nfs-utils-lib’ (centos) packages are installed before you try this!![/B]

[mecsr]

[quote=“Uncle Frank, post: 42937, member: 28116”]Who would’ve thought that it were wrong entries in /etc/exports… Sounds a bit like you hit the wrong keys when installing FOG. When the installer asked for the path you gave ‘y’ for ‘yes’ maybe…[/quote]

Well I actually just used the script I had posted in these forums that I made when .33b was still the dev.
I guess something changed in the installer for the images path not defaulting to /images with a y?

[Tom Elliott]

It’s a default to set /images or whatever value you type in.

[haste347]

My fog servers IP is 10.0.2.250

Yes! There is now a difference with those commands. They seem to be working now! (I did have to install nfs-common on the workstation).

root@VEI-3000D:/home/administrator# sudo mkdir -p /mnt/nfstest && mount -v 10.0.2.250:/images /mnt/nfstest
mount: no type was given - I’ll assume nfs because of the colon
mount.nfs: timeout set for Wed Mar 4 11:14:44 2015
mount.nfs: trying text-based options ‘vers=4,addr=10.0.2.250,clientaddr=10.0.2.153’

root@VEI-3000D:/home/administrator# sudo umount /mnt/nfstest

root@VEI-3000D:/home/administrator# sudo mount -v 10.0.2.250:/images/dev /mnt/nfstest
mount: no type was given - I’ll assume nfs because of the colon
mount.nfs: timeout set for Wed Mar 4 11:15:30 2015
mount.nfs: trying text-based options ‘vers=4,addr=10.0.2.250,clientaddr=10.0.2.153’

root@VEI-3000D:/home/administrator# sudo umount /mnt/nfstest && rmdir /mnt/nfstest
root@VEI-3000D:/home/administrator#

[Sebastian Roth]

Are you sure you still get the same error when booting into FOG??

From what I can see NFS seems to be alright. But please run another test:
[CODE]sudo mkdir -p /mnt/nfstest && sudo mount -v 10.0.2.250:/images /mnt/nfstest
sudo ls -al /mnt/nfstest
sudo umount /mnt/nfstest[/CODE]

[haste347]

Below are the results of the commands.

root@VEI-3000D:/home/administrator# sudo mkdir -p /mnt/nfstest && sudo mount -v 10.0.2.250:/images /mnt/nfstest
mount: no type was given - I’ll assume nfs because of the colon
mount.nfs: timeout set for Thu Mar 5 08:41:21 2015
mount.nfs: trying text-based options ‘vers=4,addr=10.0.2.250,clientaddr=10.0.2.153’

root@VEI-3000D:/home/administrator# sudo ls -al /mnt/nfstest
total 12
drwxrwxrwx 22 root root 4096 Feb 27 09:45 .
drwxr-xr-x 3 root root 4096 Mar 5 08:37 …
drwxrwxrwx 2 root root 4096 Feb 19 16:54 dev

root@VEI-3000D:/home/administrator# sudo umount /mnt/nfstest
root@VEI-3000D:/home/administrator#

Oddly enough, I have done some testing and I am able to capture images via FOG. However, I receive the ‘permissions denied’ error any time I try to deploy an image using various workstations and images. Any ideas on why this is happening?

Thanks again!