Hint: I think the great changeIP script does not handle dnsmasq config changes as this is not a standard setup.
Correct, it doesn’t.
Hello people - let me entertain you with a TV Pilot that I made called Hitchhikers:
@mpatel If you’re saying the images are not showing in the new server’s web interface, this would indicate that the image definitions were not transferred from the old server to the new server. The article covers migrating the database entirely. If you don’t want to do that, you can create the image definitions manually, though this can be error prone.
I’d recommend Debian 9 minimal installation. Historically with fog, Debian has had the least number of issues.
@Wayne-Workman The installer test seems absolutely fine but possibly that’s because you have the package
software-properties-commonpre-installed? Can you check on that? I have had a look at the logs from your installer tests but the package is not mentioned and that’s why I guess you have it pre-installed…
Yes, it’s pre-installed. This is on Ubuntu 18.04 server, minimal installation.
root@ip-10-0-0-165:~# dpkg -l | grep software-properties-common ii software-properties-common 0.96.24.32.7 all manage the repositories that you install software from (common)
@jcabuco No, not realistically. Blame Microsoft for that. They charge money to sign iPXE binaries. With FOG being an incredibly low budget open source project supported by volunteers, Microsoft has pretty much all but barred FOG from playing the SecureBoot game (eyes on you, Microsoft).
You should consider more than just a remote database, you need to scale. You should probably put a few FOG servers behind HAProxy as a load balancer (And have HAProxy do SSL offloading if you use https), and turn sticky on for HAProxy. Then, each of those FOG Servers should point to another HAProxy load balancer that distributes database queries across a Galara MariaDB cluster.
^ I know how to do all that, and can guide you.
A quick google search gives some tutorials:
HAProxy http load balancing:
HAProxy Galara load balancing:
@dooleyrd We need the FOG log from one of the host’s failed attempts before we can tell you anything. It’s normally at
C:\fog.log Please don’t snip a tiny piece from this file, but give us a whole client iteration - or the whole file.