IMHO spinning up a fog server from scratch takes out a lot of variables that may cause issues. The install script for FOG is quite streamlined these days. Though I am a vmware user, I find that templates and pre-builts save you literally just a few minutes at the cost of many potential issues, especially since network environments vary so much.

Thanks @Wayne-Workman for reminding me. Added to the wiki now (see my signature). The article is still missing a lot of details about the boot process and all the issues one might run into.

Yes, correct! Force of habit, I guess, FOG 0.32 didn’t play as nicely with some of the more complicated packages (SPSS, Adobe CC, ArcGIS) but the .sfx method always seemed to work. I occasionally need to include custom .XML files for setup configurations too…

I would like to have a link

Okay, here’s my crude but functional workaround…

Since I figured the problem is that the mysql service was being locked out of a file it needed, and restarting the service completely fixes the issue, I changed my Ubuntu server to stop and start the mysql service after boot up. Fairly simple procedure, just do the following:

[CODE]sudo nano /etc/rc.local
[/CODE]

In this file, above “exit 0”, type “service mysql restart” (no quotes).

Ctrl X to exit, Y to save, Enter to save to same file.

From that point forward, every time your server reboots, it will automatically bring down and up the SQL service, solving the “Unable to connect to database” error.

Hope this helps someone out there, let me know if anything is unclear!