Issues after Migrating Fog
-
My fog server was running well on version 1.5.0. However we are moving offices, and we were 5 revisions behind so i decided i would migrate the fog server to a newer Vm server at the new building.
i Followed this guide :
https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG
everything seemed to go smoothly. i changed the ip address of the new server to the ip of the old server after turning the old one off. After upgrading my storage nodes there was a db connection issue, that after resetting the fogstorage password on the server seemed to get fixed. but im currently having two issues:the first problem comes when i try to pxe boot a client. it looks to the correct Ip for tftp but it looks to its old address for http and then fails.
https://imgur.com/4ZqHn7Dthe second issue is when i look at the logs for replication, all of the storage nodes continually say " waiting for mysql to become availiable" and im not sure what to do with that or if that is normal now.
-
Changing the IP address after FOG is installed causes some issues. There is a wiki page that shows you how and where to update the IP address: https://wiki.fogproject.org/wiki/index.php/Change_FOG_Server_IP_Address
I would recommend after you follow the steps for version 1.3.0 (only) you rerun the fog install script to ensure all of the bits are updated. Be sure to update the .fogsettings file before rerunning the fog installer. If things are still off with the pxe boot (they shouldn’t be) you will need to manually edit the /tftpboot/default.ipxe file. But only edit it as the last chance to make it work. The steps in the wiki should fix the renumbering.
-
i feel like im just a little off now. a successful pxe boot. but now if i deploy and image from the pxe menu it seems to start the task, but sits at a black screen where it occasionally tells me about how its missing some jiffies.
-
@jherron Probably best if you take a picture of the screen and post here. Helps a lot more than trying to explain what you see.
-
picture to help out
-
@jherron Have you tried scheduling tasks for a couple different hosts? Do they all show those errors? It’s very strange but to me it more sounds as if this might be a hardware issue with this particular client machine.
-
@Sebastian-Roth Thanks! i tried new tasks and it seems to be back in working order. is there a recommended amount of ram i should be using, i have it set to 10gigs and its using almost all of it.
-
@jherron Do you mean on the FOG server? The client error you posted as picture has nothing to do with server RAM and I highly doubt it has to do with client RAM either. How did you get to this conclusion?
-
@Sebastian-Roth on the fog server itself. it is not relevant to the error previosly posted sorry. i saw it when i logged into my vm server.
