Best posts made by Sebastian Roth

@altitudehack Probably a duplicate MAC issue. Search the forums for this to find instructions in how to dig into this.

@altitudehack Maybe this topic is helpful: https://forums.fogproject.org/topic/14392/fog-client-error-middleware-authentication-error-could-not-get-security-token/15

@jonathanho92 said in no configuration method succeed dhcp fail please help:

this happen only when multicast we have no problem with unicast

I don’t think this is the case. The bootup for both multicast and unicast are exactly the same at this early stage.

I guess you are using different devices when multicasting?! Use the exact same physical for unicast and I’d be very sure you see the same error.

@Fog_Newb Thanks for reporting. I just pushed a fix (1.5.9.74).

@Fog_Newb Thanks for the quick test and reply! Would you mind re-running the FOG installer (no git pull) to see if that error on php7.4-mysql was just a hickup?

@bnstv Please post a picture of the error on screen. Which version of FOG do you use?

@bnstv At the end it tells you “Press enter to continue”. Please do so to hopefully get to a shell. Run the following commands, take a picture again:

ip a s
ping -c 1 192.168.15.xx
curl -v http://192.168.15.xx/fog//index.php >/dev/null

Use the correct FOG server IP instead of 192.168.15.xx.

@bnstv Just took another look at the pictures. It keeps saying no lease, failing. This I would think is telling us the client does not get an IP from the DHCP server. We know you have a DHCP in your network and it is working because otherwise you wouldn’t be able to PXE boot up to that point (unless you do manual USB booting - which I think you would have told us).

So question is, why does it get an IP from the DHCP at the first PXE boot steps. Often this is due to spanning tree or energy saving capability of the network driver. Please connect a dumb mini switch between the client machine and your build switch/network plug and try again.

@bnstv said in Fog http wrong:

Putting in the dumb mini switch got past that. Thank you!

Nice, so talk to your networking colleagues to see if they can play with the switch settings. Let them set the port to “port fast” (this is what it is called in Cisco switches, not sure about others) and disable energy saving (EEE) on this port your client is connected to. Do it one setting after the other to find out which one is causing the issue.

@george1421 It’s used to calculate how much space to leave when shrinking a filesystem (in percent). Maybe it does not help but it’s worth a try.

@tesparza said in When do I know if image replication is done on a Storage node?:

Also when installing the Smart Installer client, what IP do i put.

fog-client communicates with the main FOG node.

@tesparza said in When do I know if image replication is done on a Storage node?:

how do I know when that have transferred over to the storage node?

Take a look at the files on the storage node in /images. More detailed information is being logged to /var/log/fog/fogreplicator.log so take a look at this file.

@Bimahi Just did a test on a fresh clean Rocky 8 install and it all worked out of the box. When asked to access the web interface to create the database schema I did not run into a 503 error as you described.

Did you add external repos or even installed PHP beforehand?

@Matthieu-Jacquart I didn’t even know about that FOG setting. Something that was part of FOG long before I joined the dev team and I never stumbled upon this myself by the looks.

The help text is as follows: “This is an experimental feature that will can be used to not set the dirty flag on a NTFS partition after resizing it. It is recommended to you run chkdsk.”

From what I see in the code this setting is piped through to FOS (the FOG Linux OS doing the imaging work) but not use by it. To make a long story short, I have no idea.

For the second option (change hostname early), can i activate it ? because after deployment the temporary name of the workstation appears in WSUS instead of the real name and I have to delete it.

Yes, enable it and give it a try. FOS will try to mount the Windows partition and manipulate registry entries at the end of a deployment to change the hostname before the first Windows boot. Works like a charm from what I have tested not too long ago.

@rhodesj2314 In FOG we use iPXE and auto generated menu code pulled by the hosts via HTTP. So there are no plain text menu files on the server you can look at (like it used to be with pxelinux many years ago.

Well there is one central iPXE config file in /tftpboot/default.ipxe you might want to Check out. If that’s missing the FOG installer did not run all the way to the end!

@xseth said in FOG Client 0.12 Error Could not parse data:

Unexpected character encountered while parsing value: �. Path ‘’, line 0, position 0.

Seems like the response from the FOG server is somehow messed up. Are FOG server and host with fog-client installed on the same subnet? Intermediate firewall/proxy that might cause this?

What do you get when opening the following URL in a browser on that same machine? http://172.16.1.30/fog/service/getversion.php?clientver&newService&json

@tesparza Are you still seeing the issue? I just got around to look into this as I usually don’t have a full setup with storage node in my test environment.

From my point of view this is working as it should. Added a storage node in the web UI manually as well as through setting up a new storage node where the FOG installer script will add the storage node to your DB. Both show up in the drop down menu on the dashboard!

Though you need to make sure Is Graph Enabled (On Dashboard) setting in each of the storage nodes’ settings.

My guess is the checkbox in the storage node settings is not enabled or the master node is not able to contact the storage nodes via HTTP to query information. Either HTTP is blocked between the nodes or the connection times out for whatever reason. In that case the node is not added to the drop down menu on the dashboard page.

You can also check the “FOG Configuration” page. As well you should see an entry for each node (master as well as storages). The entries will be missing if master node is not able to contact the storage, same as on the dashboard.

@tesparza Search the forums for both topics. There are numerous posts on both.

@dashwell said in Partclone freezes or crawls after kernel update:

I updated the fog kernel this morning to version 5.10.50 64

Which kernel version did you use before? What happens when you switch back to the older kernel and try again?

Is this a unicast deploy or multicast?

@exworker9to5 said in Perform Full Host Registration and Inventory - Failed:

Which Version of Linux is better for FOG? Centos, Ubuntu, or Debian?

They all work fine. It’s more a question of personal preference.