@cojohnson Ok, the HPStream14 image replicated… I suppose I just needed to wait a day or two! for it to replicate! (After changing to the working branch)

@cojohnson Well, just let us know when you need further help on this.

@joe-schmitt I like this idea very much.

@Tom-Elliott I reran the installer script a second time on the nodes and that seemed to fix my problems! I want to thank everyone for your support and ideas! Much Appreciated!

@george1421 I actually ended up testing on the last batch of HP Streams! (28 to be exact!) Everything went very smooth! Thanks for your help George!

@Tom-Elliott Thanks Tom, I had the same problem and this fixed it for me!

@cojohnson For the moment, let’s stop worrying about imaging, and just focus on the fog client. The goal is to fix the errors in the log. Try uninstalling it and reinstalling it first.

From your picture of All Storage Nodes, there is no storage node in a group called “Green”. That may be related to your issue.

What’s the host’s location setting set to?

And, I see several storage nodes, but only two locations. Both locations are set to DefaultMember. This probably isn’t right.

Can you just verbally describe what servers are where and maybe we can help get the locations sorted?

@cojohnson said in FOG Registration Error. Hostname with that name already exists:

It renamed and started working properly after i reset encryption data. However, I have had to do that every time

This time isn’t the same if you followed what I asked, because you said you previously had to press the reset button twice, I asked you to press it once.

@Wayne-Workman sure! Thanks for your help!

@cojohnson The message Image failed to restore and exited with exit code 0 usually means that something went wrong when running partimage. Can you please get your camera ready for when the blue partimage window comes up. Take a quick picture or possibly a (steady) video) of the error you see on that blue partimage window. That probably will help us a lot.

@Tom-Elliott Did i read somewhere not too long ago that the svn way is going away??? We would have to use git?

The important thing is that you upgrade your server. Until you do that the clients won’t be able to talk to it. When you do update it, your clients will automatically upgrade to 0.11.2 if that feature is enabled.

0.32 images would be in partimage format, so you’d set this per image I think in FOG Trunk, or in fog settings somewhere in 1.2.0. I’d suggest as soon as you’re able to download those images, to re-upload them so they are in the new format.

@cojohnson said:

It makes it through partclone then fails to update the database.

Well that sounds strange. Could you do a debug upload and check the connection to the server (ping x.x.x.x and wget http://x.x.x.x/fog/service/Post_Stage3.php) to see if the connection is really gone after the upload finished. Do you see the image being properly uploaded / moved to /images/<imagename> on the server?

@Quazz I can FTP into my fog server. I don’t think that is the issue. However, I rebooted the server and am trying the upload again.

@cojohnson What do you mean?

Logs would be VERY useful.

Firstly, remove the last two storage nodes one by one and see if it returns to normal.

But most likely, you goofed the FTP credentials or MySQL credentials.

Also, as a side note to you and future readers, it’s absolutely not necessary to install 1.2.0 first. You can go straight to FOG Trunk! And preferably, use a newer distribution of Linux!

@cojohnson You have a very unique troubleshooting style.

@Sebastian-Roth Just for reference: I could never make that work correctly on 2008. I may have missed something or two, but I messed with trying to get it to work for a day or so and gave up. Maybe someone else better than me can get it working.