Found a bit of time to look into this. Just in case anyone comes across the Middleware::Response Invalid MAC address format on unregistered clients again. This happens when a MAC address filter (FOG Configuration -> FOG Settings -> FOG Client - Host Register -> QUICKREG PENDING MAC FILTER) is defined so that a newly registering client’s MAC matches the filter.

Just for the record, fog-client auto registration currently works (FOG 1.5.9.200 - fog-client 0.12.2).

@tesparza Its good we can point our finger at low memory as the problem. The small cache space on 4GB is only left 800MB of room so mysql had to commit everything to disk instead of caching it for later. (speculation) I did find it surprising that in the previous top screen shot, you had 4GB of swap space but none was used even when the system was low on ram. It wouldn’t have really helped in your case, but I find it strange that no swap space was used.

Now that you found an acceptable level you can start decreasing your fog client check in time till you find a happy balance between speed and frequency. The only issue I can think of by keeping the check in time to 5 minutes would be during post imaging if the fog client was used to rename the system, connect to AD, or do a scheduled reboot. Its possible the client computer wouldn’t react to the command for about 5 minutes.

@tesparza

I made the same thing with this doc : https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

@tesparza said in Some Hosts are not giving me the option to reset encryption data?:

@sebastian-roth

[17-Oct-2021 14:55:07 UTC] PHP Fatal error: Uncaught Exception: Error multiple hosts returned for list of mac addresses in /var/www/html/fog/lib/fog/hostmanager.class.php:209

Could it be that?

Absolutely! Search the forums for this error and you will find help.

@kvothe88 I suggest you compile iPXE from the latest source code and try again: https://docs.fogproject.org/en/latest/reference/compile_ipxe_binaries.html

@tesparza Fixed by increase the number of connections.

mysql
SET GLOBAL max_connections = 200;
flush hosts;

login as root into the database.

@tesparza said in Kernel update and storage nodes?:

This is a HP ProBook 250 G8
The “no network interface found, kernel missing correct driver” was a Dell optiplex 5080

Well then we are talking about two totally different issues and it would make sense to open separate topics in the forums on the two. The more we keep this together the more missunderstanding and time consuming questions arise.

@sebastian-roth
What is the time frame? Is there a way to reset encryption data on all PCs at once. Im having issues. Snapins are just hanging?

@tesparza Yeah, todays log is full of “No need to sync …” messages. Seems all fine.

The replication process does check file size and checksum of the files on master node and each storage node. In case they don’t match the replication deletes the file on the storage node and resyncs that file over. So in general there shouldn’t be a case where replication is “stuck” with one file not in sync even if it was broken half way.

@george1421 said in Storage nodes or Master nodes?:

Storage nodes can only send images via unicast images.

What’s the technical reason for this? Just wondering. Like, why can’t it be done? Or, has it simply not been implemented?

@tesparza You will need to do a Full Host Registration when you do the network boot.

@tom-elliott
Thank you, will do it that way.

@tesparza Probably a database maintainace might help. Search the wiki or forums to find the instructions.

@george1421 Target is UEFI, image was captured in Legacy VM. Will try again with VM in UEFI mode

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

@sebastian-roth Yup its was, “Is Graph Enabled (On Dashboard)” Working now. thanks.

@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.

@wayne-workman Yes thank you, video answer alot.

I don’t believe this is a Hyper-V issue. We have Fog running in a Hyper-V Ubuntu VM, with 8 CPU and 16g of ram, with no issues. The storage is backed by a hybrid disk array with 10TB of SSD accessed via ISCSI, and network is provided as 4x 40g links in a LACP bond.

Routinely see 13-15g on NVME backed clients, 4-6 on spinners, 3ish on the 5400 rpm spinners.