FOG Hangouts

@mary-montesanto Have you tried setting irqpoll as Kernel Argument in the host’s settings?

@seniorvodka There seems to be no image defined for the host…

Please make sure the image has an associated storage group.

@NeedLessMacs So far we only seemed to have this issue with Sierra and later versions. See here:

It seems as if the ones that came with Sierra (10.12) pre-installed will not work with iPXE while the ones that had El Capitan (10.11) are OK.

Possibly a Sierra update came out that also broke it. Or we are looking at a different issue here. So far I have only heard of onboard NICs having that issue but if it’s the exact same chip could also be a problem with the thunderbold adapter.

Please read the whole iPXE from above and start by compiling your own debug iPXE binary to test.

https://www.reddit.com/r/sysadmin/comments/a727a8/fog_appreciation_post/

@jgiovann Great you figured this is a spanning treee thing! Seems like I was to focused on the issue might be routing problems that I didn’t notice the message udhcpc: no lease, failing.

In a real production network (where turning off spanning tree is not be allowed), is it therefore possible to re-configure the FOG server to wait longer or retry more times before it gives up the registration retry loop ?

The problem cannot be solved in the registration retry loop I think but we’d need to tell the dhcp client to wait longer. But from my point of view you should be able to solve this by setting the client ports to “port fast”. There er different names for this but what it essentially does is disable spanning tree for particular ports where you surely know there are no other switches connected but only clients. On those ports you never ever need spanning tree because single clients connected to a port can never cause a loop (which spanning tree was invented to prevent from)!

@maouu This tool will re-number your snapin IDs to start at 1 again. Normally, this is not used when you only have one snapin though… It’s normally used when you have created & deleted hundreds of snapins over years, and want a more sane numbering.
https://github.com/FOGProject/fog-community-scripts/tree/master/RenumberSnapinIDs

You can’t, the 2 is the Id as it sits in the database.

@maouu Run getenforce and post output here…

Which server OS do you have?

For snapins you need to check the permissions of /opt/fog/snapins

What version of FOG are you running?

Have you tried troubleshooting FTP information?
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP