Found and fixed - the .fogsettings file was clearly corrupted causing this issue. Very sure this was due to manual editing.

@george1421 Thanks for the information on this. Also, what is the process for updating the kernel? I know it is on the GUI side of FOG but not sure if the is a specific process to avoid any unexpected errors. I have 2 storage servers and not sure if this would affect the connection or settings.

Another thing is that I have already set up Windows 10 on this Dell 3410 laptop using the RAID settings on the BIOS. So how can I fix Windows 10 since when changing to AHCI I get a blue screen?

Any tips or suggestions would be greatly appreciated.

Thanks

@sebastian-roth thank you!

@mrawesome987 that is crazy obsecure, but I’m glad you found it.

This sounds like a perfect tip to add to the wiki @Wayne-Workman

@jacques-olivier said in Installation of FOG with external MySQL base:

Do you mean we can’t have a priviledge root user with another name to access our external database ? For example we would like to use theboss instead of root as this priviledge user already exists.

The FOG installer is programmed to do all the DB user and database setup for you. It will ask your root DB password (but not store it anywhere!) just to set the user and database up for you.

With the installer we try to help people and sometimes we have gone “too far”. I can see this is not perfect for people like you who have a custom setup and know what they are doing.

Looking through the installer scripts I think I found a way for you to get around this:

Create the database on your other server - e.g. named ourfogdb Create a DB user with all rights on that DB: GRANT ALL PRIVILEGES ON ourfogdb.* TO 'theboss'@'x.x.x.x'; Create a less privileged DB user called fogstorage (sorry this is still hard coded) that would be used by external storage nodes - you might not need that but the installer will check for it, sorry. Grant access rights for the fogstorage DB user: GRANT SELECT ON ourfogdb.* TO 'fogstorage'@'%' ; GRANT INSERT,UPDATE ON ourfogdb.hosts TO 'fogstorage'@'%' ; GRANT INSERT,UPDATE ON ourfogdb.inventory TO 'fogstorage'@'%' ; GRANT INSERT,UPDATE ON ourfogdb.multicastSessions TO 'fogstorage'@'%' ; GRANT INSERT,UPDATE ON ourfogdb.multicastSessionsAssoc TO 'fogstorage'@'%' ; GRANT INSERT,UPDATE ON ourfogdb.nfsGroupMembers TO 'fogstorage'@'%' ; GRANT INSERT,UPDATE ON ourfogdb.tasks TO 'fogstorage'@'%' ; GRANT INSERT,UPDATE ON ourfogdb.taskStates TO 'fogstorage'@'%' ; GRANT INSERT,UPDATE ON ourfogdb.taskLog TO 'fogstorage'@'%' ; GRANT INSERT,UPDATE ON ourfogdb.snapinTasks TO 'fogstorage'@'%' ; GRANT INSERT,UPDATE ON ourfogdb.snapinJobs TO 'fogstorage'@'%' ; GRANT INSERT,UPDATE ON ourfogdb.imagingLog TO 'fogstorage'@'%' ;

Now with that being prepared you should be able to call the FOG installer like this (untested, keeping my fingers crossed I did not overlook the obvious):

mysqldbname='ourfogdb' snmysqlhost=‘192.168.1.1’ snmysqluser=‘theboss’ snmysqlpass='password_of_theboss_db_user' snmysqlstoragepass='password_of_the_fogstorage_db_user' ./installfog.sh

@lukekfrost the FOG install doesn’t like it when the ip address of the imaging interface is changed after FOG is installed. There are several locations where the static IP address is recorded. You linked to the wiki page, also this post addresses the same issue as you have today. https://forums.fogproject.org/topic/15112/changed-ip-reinstalling-not-an-option

My unoffical instructions are to

Update the hidden file /opt/fog/.fogsettings fix the IP address in there. Update the IP address in /tftpboot/default.ipxe Update the IP address in the web ui under fog configuration->fog settings->expand all. search for the old IP address and replace it with the new address. In the fog storage node default, change the IP address in there. Back in the fog server linux console, rerun the FOG installer to fix the remaining bits.

I ended up finding the fix.

Step 1: Change IP Address, then deactivate and activate the network interface.

Step 2: Run the UpdateIP.sh within the fog-community-scripts-master.zip found here https://github.com/FOGProject/fog-community-scripts

Step 3: Rerun the installer.
If you have NO INTERNET CONNECTION, like myself in this case,
rerun with the -X option like so,

./installfog -X

I verified it worked with my new subnet and I was able to boot off my Fog Server, register new hosts, as well as capture and deploy an encrypted Linux image.

This was successfully done on a Rhel 7.9 VM with no internet connection FYI.

@seppim said in Advanced Login:

I guess I need to set the “Advanced menu command”? But why is this not out of the box working?

Yes, you need to add some custom advanced menu that you want to see after the login. There is no default.

Here is some example code you can start working on:

menu item --gap -------------- iPXE advanced boot menu -------------- item DBAN Boot and Nuke item SHELL iPXE Shell item RETURN Return to previous menu choose --default RETURN --timeout 10000 target && goto ${target} :DBAN kernel ${boot_url}/dban/dban.bzi nuke="dwipe" silent vga=785 boot goto MENU :SHELL shell || goto MENU :RETURN chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} || prompt goto MENU autoboot

Here is more stuff if you need: https://forums.fogproject.org/topic/7329/sub-menu-within-fog-advanced-menu

Well rebooting the switch does seem to have had some effect, this batch are now multicasting at 2Gb/min. I’ll look at getting it replaced, it’s a noisy beast anyways.

@danieln Correct as long as bzImage and bzImage are what you want then the proper kernels will boot.

@george1421 Everything is OK now. What we missed that our fog servers have different from the labs NAT and we needed to add rules for every NAT address in the Firewall on 80 and 443 ports. You can close the topic. Thanks

@phm2000 I don’t know that model but I did find that your switch does support “green ethernet” mode. I’m not saying that this IS the problem but if your only solution is to disable STP then I would look to see if green ethernet is enalbed on your switch. According to this article its disabled by default: https://community.hpe.com/t5/Comware-Based/How-to-disable-IEEE-802-3az-Energy-Efficient-Ethernet-feature-on/td-p/6896946# Look at the accepted solution.

Disabling STP on user facing ports is not the best choice. You may need to get with a switch engineer to understand why turning on RSTP does not solve your problem (because turning off STP solves the net booting). From your description it sounds like the port is in standard STP mode even if you set it to RSTP. I assume (with RSTP on) placing a dumb (unmanged) cheap switch between the building switch and the pxe booting computer will also mask the problem. We will typically recommend this for people to test to see if the problem is spanning tree or not without changing the switch settings.

Edit the file /opt/fog.fogsettings and replace the IP address there.

Then edit the /tftpboot/default.ipxe file

in the fog settings and default storage node change the IP there.

Finally rerun the fog installer once again to fix the rest of the bits.

@sckendall said in Fog ProxyDHC with Fog and Pfsense on the same network:

Well, the question is whether it is possible to have two independent fog servers on the same network.

Well this sentence changes everything.

If you want to pxe boot on your laptop you will need an isolated network or if you are running a hypervisor on your laptop then you can create an internal network.

I just think of an idea. Its possible if on your main FOG server, you create a custom FOG iPXE menu that links the fog server on your laptop. Then normal pxe booting to main fog server, then chain (ipxe command) to your FOG server. That is possible.

hello,
I found the solution.
looking at the databases, there are 5 fields on the fog 1.2.0 base and there are 9 fields for version 1.5.9.
so the hots don’t appear.
by importing the database on the new server and importing the csv host everything is ok.
the export of the csv on the 1.2.0 server was with the separator ,
I reworked the file with free office to put it in ;
it works.
I leave the solution here for old fogs who want to migrate to a new machine 🙂

@george1421 That did the trick!

I had previously added the images2 *(ro etc;etc;etc;) but did not run the sudo -exportfs -a command.

I knew it was something simple. Thanks so much for your help!

@aschaffer What do you mean by “needs to be touched”?

By the way, this topic is years old and you might want to create a new one and post all your specific details there like version and a detailed description…

@rogalskij The FOG developers are expecting the Linux kernel developers will take 5.10.x to LTS status. When they do the FOG developers will make 5.10.x the standard kernel in FOG. ref: https://www.kernel.org/

FWIW, there was quite a few new drivers added to 5.9.x series (almost as many as was added to 5.5.x), so 5.10.x LTS can’t come fast enough because FOG will start running into that hardware soon.

@sebastian-roth said in ipxe/boot.php and bzImage running very slow:

@danieln said in ipxe/boot.php and bzImage running very slow:

The only change was that I added one additional storage node.

Storage node being in the same subnet as well?

Correct. I double checked and it is on the same subnet.

@geardog Two things from the tutorial I just want to point out:

Make sure its at least version 2.76 by issuing this command at the fog server’s linux command prompt sudo dnsmasq -v. The version needs to be 2.76 or later.

and as George already mentioned here:

Be sure to replace <fog_server_ip> exactly with the IP address of your fog server. Be aware that <fog_server_ip> appears multiple times in the config file.