@george1421 Thanks again you’ve been a great help, I went through the install again and was able to PXE boot my first host on the private PXE net.

I had the same issue. For me, the problem was solved by manually creating the fog database and the fog user, and then rerunning the installer. We have a few fog servers and have always used the same mysql password, which is not blank. I don’t know if that’s what caused the failure of the db creation, but I figured I’d mention it, since the default suggestion on the installer is to use a blank password. Also, we are trying to use https, so I ran the installer with the “-S” option.

I hope this solves your issue - though given the recommendation from the developers to use trunk, it’s probably best to do that.

@george1421
Hi,
I reshaped and deployed the image
All is Ok now
thanks for your help

This was a known bug and has been fixed in 1.3.5-RC-13 I believe was the “official” fix.

@MentalBlank This happened because you used the defaults for CentOS 7’s installation. There is a guide here for how to cleanly and properly install FOG on CentOS7: https://wiki.fogproject.org/wiki/index.php?title=CentOS_7

1.3.3 is outdated, I would recommend the latest release candidate of 1.3.5, there are a lot of fixes in it that are worthwhile.

If you don’t want to reinstall the OS, we can help you remove space from /home and put that space into /images. You still need to update to the latest RC though. 1.3 and 1.4 have some problems. We will need the output from the following commands to help you move around the space, please copy/paste the output into a nice code window here:

lsblk df -h pvdisplay vgdisplay lvdisplay fdisk -l

@Tom-Elliott said in Primari mac 02:00:00:00:01:00:

@Tom-Elliott thanks Tom…I’ve done this, and I would make more test during this days and give you an update!

@Tom-Elliott

Oh yes, it’s works with this permission :). Thanks you

@John-Sayce Thanks, will do.

@george1421 We did get this working.

ALthough the problem specifically here with not network booting had to do more with the fact the keyboard was not recognizable.

That’s what we are hoping for. All of us IT people being able to go home without a worry and feeling “accomplished”.

Glad it worked.

For what it’s worth, the new client will also enable your hosts to “re-associate” themselves. There is a little involvement as you will have to “approve” the hosts, but you don’t even need to go through the whole registration process.

@Wayne-Workman I updated to RC12 yesterday. Captured using multi partition and single disk, re-deployed to test both and everything is now working! Thanks for all your hard work on this @Tom-Elliott!

@Tom-Elliott already done 🙂

@Wayne-Workman I got it working. I must have messed up the passwords. I fixed it so the user pass matched the .fogsettings password and replication started working. Thank you.

@rbaldwin Sounds like you found and fixed the issue. Yes PIM (modes) is definitely a good keyword. Marking this solved now. Hope that others might stumble upon this and find it helpful as well.

@Tom-Elliott Thanks, it works!

Thanks,
re-ran through the change over process and all seems to be working, just need to test a deployment etc, Thank You all for your help.

Well if it’s not harmful then that’s great. Wanted to make sure I didn’t break anything.

Ok - found my problem - those dates in the Fog log got me to wondering why there weren’t any recent entries… Service was not starting - I had not updated my SetupComplete.cmd for the new client that I included in the new image:

Old client SetupComplete.cmd command to start the service:

sc config “Fog Service” start= auto

New Client SetupComplete.cmd command to start the service:

sc config “FogService” start= auto

Voila! Working again! Thanks for your input - I will probably rebuild a clean image at some point, but this got my old patchwork image going!

@Jaymes-Driver @Tom-Elliott

Thank you so much for your help. I am up and running now on 1.3.5 RC 11.

@Grizzly Also tested this on an Lenovo X230 image I created in 1.2 that works as well. Thanks for the fixes!