Topics created by jcook

Just in case anyone finds this later, ended up using dnsmasq to make my configuration work using @george1421 's tutorial here: https://forums.fogproject.org/topic/12796/installing-dnsmasq-on-your-fog-server

Mine was a bit more complicated because I’m running an older version on ubuntu, but @george1421 's tutorial is spot once I got all the other weird things I had to do done lol.

Yes you should rerun the installer. The update database gets the system ready for the second phase of the update done back in the linux console. If you stopped the installer waiting for the database update and then happened to hit ctrl-c and exited the installer your system will only be half way setup. There is quite a bit of actions happening after the database is configured.

Good news, I have my 1.2.0 Fog server up again. After building my own ipxe kernel most of my machines can pxe boot properly. I used the bios and uefi @Sebastian-Roth made in that post and both seem to work. Its not asking me for the tftp IP any more and just registered/imaged/deplayed a few machines 😄

Sorry for so many relies, seems to be an issue with mysql, after a restart of the service I’m able to log into the web UI.

Turns out the power outage caused the original (physical) fog server to turn on when the power was restore. I arrive at this conclusion after I removed the network cables form the machine that fog should be on and stopped the another old virtual fog server on another, yet I was still able to PXE boot with fog. After calling the previous tech guy we came to the conclusion that the original fog server had to be on, and it was. It was a combination of miss-information and mother nature. I did find that the original fog servers mysql database was not running and I was unable to start it again. Now the virtual fog server is up and running fine. Thanks for the help and fast responses, sorry wasting your time 😄