Storage Management not showing my images

[michaeloberg]

So just to make this clear, I don’t wish to import images from the old fog server to the new fog server. I am simply trying to push up my master image from the host to the new fog server, and as I am doing this you can see the storage going down on my new server so I know it is receiving the image. See Pic of dashboard

Here you can see it is uploading

Here you can see some sort of invalid login?

And it fails here:

When I change the storage node back to old Fog Server I can use my new one to push and store the image on the old Storage Node.

[george1421]

@michaeloberg Ah, a picture says much more than words.

The third picture with the FTP errors.

Backgound:
What happens is that the image is uploaded to the FOG server into /images/dev/<mac_address> If you look there you will probably find your uploaded image.

The next thing that happens after the files are uploaded is that the FOS Engine (running on the target computer) connects to the FOG server using FTP, and instructs the FOG server to move the uploaded image from /images/dev/<mac_address> to /images/<image_name>.

What we’ve seen happen is that there is a linux user called fog that gets out of sync with the storage node configuration for the master fog server.

The Fix:
What you need to do is this

1. Look at the storage node configuration for the master FOG server, at the bottom there is a user name of fog and a password. Click on the little eye and copy the password out and paste it into a text editor.
2. On the fog server linux console with a text editor open the following file /opt/fog/.fogsettings there is a field in there called password ensure what you pasted into the text editor in step 1 is the same as in the .fogsettings file. If not update the .fogsettings password field to match the gui.
3. Exit out of the .fogsettings file.
4. Now on the fog server linux console reset the fog user’s linux password with the following command sudo passwd fog set it to the password that was saved in step 1 (fwiw: this linux user has nothing to do with the default web gui user called fog).
5. Now lets confirm that you can log into the fog server from a windows computer using the ftp program, with the user of fog and the password that was saved in step 1. If you can login via ftp with the user fog using the web gui password, then success.

[michaeloberg]

@george1421 It doesn’t seem I have the .fogsettings

Is there another place I should be looking?

[michaeloberg]

@george1421 Again I know little about Linux so maybe I am just not familiar with the syntax to open/edit the .fogsettings
Sorry and thanks for your help, I am loosing sleep over this.

[Tom Elliott]

@michaeloberg the . before a file makes the file “hidden”.

To view the file you would use the command ls -a I would think. Most commonly people use ls -la

[george1421]

@michaeloberg I just sent you a IM look for the little talk bubble on the forum tool tray.

to edit you can use vi (only if you are a crazy old guy like me) or gedit if you are using the graphical front end for linux.

[michaeloberg]

@michaeloberg This is resolved!
Thanks @george1421

[george1421]

@george1421 The short answer was the fog (linux) user and .fogsettings were consistent but the ftp password in the storage node configuration in the GUI was incorrect. We resyn’d everything and tested to ensure that fog could log in with a new putty session to the FOG server.

[michaeloberg]

@george1421 Could you send me the syntax we used today to look @ the .fogsettings as again I am a Linux novice, I am going to make note of this.
Thanks again!
Mike

[george1421]

@michaeloberg well if you just want to look at it more < /opt/fog/.fogsettings

Old guys like me like to use vi vi /opt/fog/.fogsettings but you have to be a bit insane to use vi if you are a linux novice. (hint: esc : q to exit vi)

FWIW in linux terms any file name that starts with a dot ( . ) is a hidden file (i.e. .fogsettings). You can list hidden files with this command in the current directory ls -la that will show you long format ( -l ) and all files ( -a )

[michaeloberg]

@george1421 Thank you guys! This is the simply the best imaging solution out there!

[michaeloberg]

@Tom-Elliott So my FOG server is operating correctly now, what is the upgrade path and how do I go to 1.3.5? most important is this going to mess anything up now that I have everything running?

[george1421]

@michaeloberg use the Git method here to upgrade: https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk
No it shouldn’t mess up your current installation. If you want it to break your current setup, just let me know and I will show you how.