FOG FTP Permission Issue
-
root@Fog:/opt/fog# cat /etc/exports /images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0) /images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1) -
@Joe-Gill That’s your problem. Your image task is trying to mount to the server’s
/mnt/bhs/images/directory, but exports only has/imagesexported. You will need to correct the/etc/exportsfile to have the correct paths. Reboot your server after changes to this file (there are ways without rebooting but I’m keeping it simple).AND
Edit the
/opt/fog/.fogsettingsfile to include the correct image path so this doesn’t happen again. -
@Wayne-Workman will this change anything for my other storage nodes? I know this directory is unique to that node.
Thanks!!
-
Also, are their any specific arguments that I should include for that directory? I noticed both of the entries in my /etc/exports have different arguments…
Thanks!
-
@Joe-Gill The arguments should be left the same, just edit the paths. This only needs done on the nodes that has this alternative images directory.
-
@Wayne-Workman I added these arguments on the NFS node and rebooted. I still get the same message. I’ll be out of the office until Monday. I’ll look at it then. It doesn’t seem to affect most of our images. Thanks!
-
@Joe-Gill said in FOG FTP Permission Issue:
It doesn’t seem to affect most of our images. Thanks!
for the node that has the image that has the problem, can you confirm this alternate path is correct? Also, the exports file is case sensitive, so is the image path setting (in the Web UI) for this storage node.
-
@Wayne-Workman I had originally posted the /etc/exports file from the server… It did NOT have the correct settings. This from the freeNAS storage node appears to be correct… I tried adding
/mnt/bhs/data/images -maproot=fog:fogand that did not work…
Exports file from freeNAS node…
/mnt/bhs/data/images/dev -maproot=Free:Free
/mnt/bhs/data/images -alldirs -maproot=Free:Free -network 172.16.1.17/24
-
@Joe-Gill I tried messaging you earlier today (top right- talk bubble). I’d like to help, to figure out what’s going on.
-
@Wayne-Workman Sorry Wayne, I was offline. I left my machine on at the office. I’ll be busy this morning but may be around later this afternoon to work on this. Thanks again!
-
@Joe-Gill What is the status on this issue? Do you still need/want help?
-
I was out of town last week. I’ll look at it again this week. I believe that it’s still an issue though. If I get a chance today I’ll look at it and update this post. Thanks!
Cheers,
Joe
-
@Joe-Gill I have a NAS4FREE server that I used as a node in the past. I just used the GUI to config it, but here’s the exports file for it anyway
/mnt/INSTALLERS -alldirs -mapall=root -network 192.168.1.0 -mask 255.255.255.0But more importantly, I notice your Storage Node page has browser autofill on it, so likely your password is being overwritten with the GUI login.
-
I have tried updating our FreeNAS server exports file to:
[root@freenas ~]# cat /etc/exports /mnt/bhs/data/images -alldirs -mapall=Free:Free -network 172.16.1.0/24 -mask 255.255.0.0I still get the same response in FOG… Mounting image fails.
I can FTP from my servers /images directory into the FreeNAS server and transfer a file to and from the /mnt/bhs/data/images directory. I didn’t start seeing this problem until recent releases of FOG. I’m kind of at a loss here. I’ll be here until 5:30 MST if anyone would like to remote in. Any ideas are greatly appreciated!
Cheers,
Joe
-
@Joe-Gill Do a debug capture, and manually mount the remote NFS share yourself. See what happens. Instructions on this are in the wiki:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_NFS -
@Wayne-Workman Ok. I’ll try that. I disabled that node for right now to get my immediate imaging tasks done. I’ll try that though later this afternoon if I get time. Thanks!!
I think I went through this before but I can’t seem to find my previous posts about it. Ugh…
Thanks!!
Cheers!
