Posts made by Jias94

I am in the process of migrating my old fog master server to a new master server.

Old fog server version 1.5.10.1660
new fog server version 1.5.10.1667

This server is the master server for 25 remote sites each having their own storage node. We installed the fog client on the remote hosts to use the DNS name for the server dc-fog-el. Currently it is in use for the old server but I would like to repurpose it for the new one that has a different IP address. Reading the wiki page for Migrating fog and for Maintain Control Of Hosts When Building New Server I have a question about this process. When migrating the SSL folder from /opt/fog/snapins, it contains files that have the old servers IP address. The wiki says to transfer the SSL folder to the new server and re-install fog. Even though the two servers have different IPs and the fog client is using the domain name for the old server, will the new server maintain control of the existing hosts during this process if I migrate the domain name to the new server?

My goal in all of this is to prevent a lot of headache and work for our tech support team to have to reinstall the fog client on over hundreds of computers. I am working on migrating the database over to the new server. I know there were some config files for mysql/mariadb and php I needed to change and increase the memory and connection limit sizes.

Any help with understanding this migration would be much appreciated!

@george1421 Thanks for the reply! It was something to do with the custom boot menu. Shortly after I made this post and I had my team meeting. One of my co-workers admitted that he was explaining how to make a custom boot option to our field techs and got distracted and forgotten to add the parameters to the custom boot menu. He was going to delete it afterwards but yet again forgot to do it.

I feel embarrassed as I saw that menu item multiple times, but it didn’t click that it was missing some important information to make it work properly… I’ve since removed the broken menu item and the boot menu works as intended.

I think it’s about time I come to the forums for help. Recently I’ve upgraded our Master Fog server to 1.5.10.1660 using the fog kernel 6.6.69 and using Ubuntu 24.04.2 LTS version.

A few days ago, I wanted to try and implement HTTPS for the master fog server and the storage nodes. The upgrade went well and everything was working just fine except for a few driver issues with the keyboard not working during the fog boot menu for certain models of computers we have, but that is a different problem.

My main problem now is that every time I try and get to the fog boot menu, I get an error: “Could not boot: Results too large.” I have since rebuilt the binaries for iPXE, reinstalled fog a few times with HTTPS enabled, Reinstalled fog without HTTPS enabled, rebuilt the fog master from the ground up and I’m still getting this error. I even tried using chatGPT just to see what it would recommend, but it wanted me to completely redo the boot.php file. The two things I haven’t tried diving into was seeing if there are any residual iPXE stuff for HTTPS in the fog database ( which I don’t think there are any iPXE info stored in the database? ) and reinstall the storage nodes from the ground up.

Here are the the amount of storage nodes we have currently connecting to the master node:

The amount of storage nodes might be irrelevant to the problem I’m having, but I’m grasping at straws here. I haven’t tried it yet but if I were to create a task for existing hosts on fog it would deploy an image just fine or capture an image. However, registering new hosts through the fog boot menu isn’t an option until this gets resolved.

Any amount of suggestions or help would be much appreciated!