@wayne-workman We ended up consulting our in-house Linux master, the issues we were having went away once we got rid of a bunch of our old kernels, our boot drive was 100% full. Then we ended up re-installing and migrating the config over again and it worked fine. To be honest, I’m not 100% sure how our guy knew that was causing a problem.

Thanks for the insight and assistance guys.

Title says it all, recently completed our update and everything was working fine up until we went to check our imaging log. Where would I look to start troubleshooting?

So I had tried the update process listed here: https://wiki.fogproject.org/wiki/index.php?title=Getting_FOG#Getting_FOG

I decided not to use a dev version so I skipped to https://wiki.fogproject.org/wiki/index.php?title=Getting_FOG#Running_the_installer instead.

The server itself came back fine, but once we edited the dhcpd.conf file through Vi it broke DHCP. It said there was a configuration file error. It gave us an “exited” code and a “status=1/failed” error message.

We reverted snapshot and we’re fine now, but we’re curious as to why this happened. Any ideas?

Thanks.

@wayne-workman Thank you Wayne, the resources you provided were quite extensive.

We’re currently running revision 689680 here, svn 6059, and bzImage 4.9.1. We’re wondering if we had to completely reinstall fog and recapture everything from scratch or if we could perform a simple upgrade directly from the FOG server itself? I ask only because in the past it was understood a complete rebuilding of the server was necessary to upgrade.

Lastly, does the integrity of images in this process depend on how the images were stored in regards to the storage type? NAS/virtual storage etc. We have our server configured with a regular HDD and a RAID 5 configuration.

Thanks guys.