New Fog Server - /images location
-
@Technolust said in New Fog Server - /images location:
Web GUI -> Fog Configuration -> Fog Settings -> Expand all -> there is no /images location
Sorry I wrote that post from memory since I didn’t have immediate access to a fog console to verify.
also change the FTP path to /fogserver/images from /images?
Right you need to change everywhere you would see /images to the new images path.
It looks good for the export list.
If you updated the .fogsettings file in step 1 then no, it should be automatic moving forward.
-
@Technolust What does the content of the default storage node look like?
Also did you reboot the fog server after you made all of those changes? Some values are only loaded at boot time.
-
@george1421 Thanks, I did make the change for the ftp path and I did update the .fogsettings in step 1 as well as rebooted the server. Only thing now is the Storage Node not coming online.
/fogserver/images/
[root@fogserver images]# ls -lrt
total 12
drwxrwxrwx. 3 fog root 4096 Jan 22 09:21 dev
drwxrwxrwx. 2 fog root 4096 Jan 22 09:21 postdownloadscripts
drwxrwxrwx. 2 fog root 4096 Jan 22 10:03 T470-Win10 -
@Technolust I don’t have a clue about the storage node on the home screen. But from your ls command you are missing 2 check files. If you run
ls -laon the old /images directory you will see a file called.mntcheckand the second one of the same name needs to be in /images/dev. Those will need to be recreated in your new location paths. You can simply do:
touch /fogserver/images/.mntcheck
and
touch /fogserver/dev/images/.mntcheckits ok if they are already there, that touch command will just update the last time the file was access, or create it if it wasn’t there.
-
@george1421 said in New Fog Server - /images location:
touch /fogserver/dev/images/.mntcheck
Ok looks like /fogserver/dev/images doesn’t exist. Is this supposed to be /fogserver/images/dev?
If so I ran touch touch /[root@fogserver images]# ls -la /fogserver/images/
total 20
drwxrwxrwx. 5 fog root 4096 Jan 22 10:03 .
drwxr-xr-x. 3 root root 4096 Jan 22 09:16 …
-rwxrwxrwx. 1 fog root 0 Jan 22 10:25 .mntcheck
drwxrwxrwx. 2 fog root 4096 Jan 22 10:03 T470-Win10
drwxrwxrwx. 3 fog root 4096 Jan 22 09:21 dev
drwxrwxrwx. 2 fog root 4096 Jan 22 09:21 postdownloadscripts
[root@fogserver images]# ls -la /fogserver/dev/images/
ls: cannot access /fogserver/dev/images/: No such file or directory
[root@fogserver images]# ls -la /images/
total 16
drwxrwxrwx. 4 fog root 4096 Jan 22 09:10 .
dr-xr-xr-x. 22 root root 4096 Jan 22 09:36 …
-rwxrwxrwx. 1 fog root 0 Jan 22 09:10 .mntcheck
drwxrwxrwx. 3 fog root 4096 Jan 22 09:10 dev
drwxrwxrwx. 2 fog root 4096 Jan 22 09:10 postdownloadscripts
[root@fogserver images]#[root@fogserver images]# touch /fogserver/images/dev/
[root@fogserver images]# ls -la /fogserver/images/dev/
total 12
drwxrwxrwx. 3 fog root 4096 Jan 22 10:28 .
drwxrwxrwx. 5 fog root 4096 Jan 22 10:03 …
-rwxrwxrwx. 1 fog root 0 Jan 22 09:21 .mntcheck
drwxrwxrwx. 2 fog root 4096 Jan 22 09:21 postinitscripts
[root@fogserver images]# -
@Technolust said in New Fog Server - /images location:
touch /fogserver/dev/images/.mntcheck
Ok looks like /fogserver/dev/images doesn’t exist. Is this supposed to be /fogserver/images/dev?
OK its time for either another cup of coffee or for me to just go back to bed. The path
/fogserver/dev/imagesis of course wrong. I should have typed/fogserver/images/devIt looks like you have the check file in the proper paths from your
lscommand. But after a reboot your storage node is still showing off-line? -
@george1421 No worries at all I figured that’s what you meant. My coffee needs coffee today! Just did another reboot. Node is still offline.
-
@Technolust Does the IP address in the default storage node configuration point to the right IP address?
I would do a test capture to ensure the image capture process completes correctly. If it does then do a deploy back to the same computer. If both work then we’ll bring the devs in to see if there is something “under the hood” wrong.
-
@george1421 Ok cool let me get that up and see. Will report after.
-
@george1421 Here is something strange, I RSYNC’d two images from the old Fog server to this new one and when I open the images link and select all images. No images show up. It’s appears to be acting like the Web GUI can’t see the /fogserver/images directory.
-
@george1421 Ok George, looks like I need another cup of coffee… I figured out why the Storage was not online. Two issues.
-
Selinux - Looks like I ran the script earlier without putting Selinux in Permissive mode so yeah it was breaking things. Found out when I tried to actually pull an image.
-
Permissions - Permissions for /fogserver dircetory needed to change ownership (was root:root needs to be fog:root) Recursively along with 777 so the /fogserver/images directory had the correct permissions but not the /fogserver dircetory.
Looks like things are good. I am Rsyncing the images back over from the old fog server and will try it again when they come over.
-
-
@Technolust Ah the fog prerequisites were not met. OK, good you had that bit figured out as well as the permissions.
So are you 100% good now?
-
@george1421 Just about. I can’t get the fog server to see the images I RSYNC’d over. Not sure how to get them to show up. I moved over two images to the /fogserver/images directory. Do you know how to move images from one Fog Server to another?
-
@Technolust Remember (or know) that with FOG there are 2 parts to the image.
- Raw data files stored in /images
- The metadata in the database.
You can rsync the files over, but you will need to create the metadata by going in and manually create a new image definition in the new FOG server. Create it manually by copy and pasting from the source FOG server. I would say export and import but I don’t know the impact of changing the /images directory when you import. Its just easy enough to copy and paste between the two servers.
Just call up the old server and the image definition and then create a new server definition on the new server and copy between.
-
Sweet, I’m just not sure I completely understand how to copy the metadata in the database.
“create the metadata by going in and manually create a new image definition in the new FOG server”Do you know the location of the below?
“Create it manually by copy and pasting from the source FOG server.”I setup samba on both servers so I can do in GUI or I can scp the files…
-
@Technolust said in New Fog Server - /images location:
I setup samba on both servers so I can do in GUI or I can scp the files…
It’s not just the files! What George is saying is that you need to create the image definitions (also can be called metadata) in the web UI of the new server as well. This can either be done through database export (old server) and import (new server) or just manually. The later is way easier to do if it’s just a couple or dozen of image definitions you have. Simply open the web UI of both your servers in two browser windows. Now edit one of the image definitions on the old one and click create image on the new one. Set all options exactly like they were on the old server. Save and go to the next.
-
@Technolust said in New Fog Server - /images location:
I setup samba on both servers so I can do in GUI or I can scp the files…
How very windows-ick way of thinking. On both the source and destination servers the /images directories are shared via NFS. No need for samba, just mount the remote nfs share.
I’m just messing with you, do what ever you need to get the job done. If samba was your answer and it did what you needed, it was the perfect fit.
-
@Sebastian-Roth How do I edit the image definition?
-
@Technolust said in New Fog Server - /images location:
How do I edit the image definition?
Open the FOG web UI, click images icon in the top menu, click “List all Images” on the left, click the Image name to see and edit the image defintion/settings.
-
@george1421 I was able to figure it out. After RSYNC’ing the directories you have to export the images off the old server and then on the new server you have to import the images. Tested an image to a laptop and it worked.
Thank you for all the help. All good now.
