Unable to register hosts

[Wayne Workman]

This could be a kernel issue, as the process made it to the kernel, or it could be network related.

Do you have a dumb-switch, aka a mini-switch? Use that and see if there is any difference.

[Matthieu Jacquart]

@Wayne-Workman tested, no difference, but you mean to plug mini-switch on ethernet port on the wall or directly on fog server ?
Cause FOG server is a VM, so I just plug mini-switch on ethernet port in the wall…

[Wayne Workman]

@Matthieu-Jacquart for the problematic host, run it through the mini switch.

Laptop -> mini-switch -> building network.

[Matthieu Jacquart]

@Wayne-Workman yes, that’s what I did
But same error

[Tom Elliott]

The thing I notice is it’s not seeing the nic.

[Matthieu Jacquart]

@Tom-Elliott great… so is there anything to do ?

[Tom Elliott]

@Matthieu-Jacquart Can you add isdebug=“yes” to the registration task menu item?

[Matthieu Jacquart]

@Tom-Elliott Sorry but I didn’t find this menu ?

[Tom Elliott]

@Matthieu-Jacquart It’s under FOG Configuration Page->iPXE Menu Configuration->fog.reginput

[Matthieu Jacquart]

@Tom-Elliott ok, in fog.reginput in “Boot options” there is : mode=manreg isdebug=yes
Need to add isdebug=yes somewhere else (in parameters ?)

[Tom Elliott]

@Matthieu-Jacquart isdebug shoudl go in the boot options, yes.

Is this what was there, or you added the isdebug=yes?

[Matthieu Jacquart]

@Tom-Elliott it as already typed

[Sebastian Roth]

@Matthieu-Jacquart You have all the interesting and uneasy hardware around man.

Thank god we have been through this about two month ago already. Check out this posts…

Solution: Add pci=noacpi as a kernel parameter to the host (Host Configuration).

Guess we could add this to the #wiki at some point…

[Wayne Workman]

@Sebastian-Roth Where would it best fit? Troubleshoot downloading ? Troubleshoot Registration ? Troubleshoot upload ? Maybe just an article about helpful kernel arguments?

[Matthieu Jacquart]

@Sebastian-Roth ARgh, I began to search before opening thread but didn’t find this one…
Thanks Seb, I’ll try it tomorrow !

[Sebastian Roth]

@Wayne-Workman said:

Where would it best fit? Troubleshoot downloading ? Troubleshoot Registration ? Troubleshoot upload ? Maybe just an article about helpful kernel arguments?

I thought about simply adding this machine to our “known working hardware” list including the kernel parameter in the comments.

[Matthieu Jacquart]

@Sebastian-Roth I’ve just read the topic, it’s a semi good news because… We have to entered manually our 40 hosts into fog interface before putting kernel parameter to the host ??? what a mess.
But once it’s done, we will be tranquil

EDIT : bad news, it seems not working…
If I put pci=noacpi in Host Kernel Arguments, no change, same error message.
If I put pci=noacpi in Host Kernel, I’ve got this error :

I use undionly.kpxe

[Sebastian Roth]

@Wayne-Workman Nevermind, I just saw that you added the 3350 latitude including the kernel parameter back when we figured this out.

@Matthieu-Jacquart You could import the 40 hosts via CSV but seems like we need to figure this ugly hardware issue out before. Definitely needs to be in “Host Kernel Arguments” not “Host Kernel”! Are you absolutely sure you had it set in Host Kernel Arguments when testing with one of your machines - set in the correct one? Have you read through the whole story I posted the link to?
You can try other kernel parameters like acpi=off or pci=routeirq (described here).

[Tom Elliott]

@Matthieu-Jacquart Host Kernel (no arugments) is the kernel file. The message you see below is because it’s looking for a file named pci=noacpi

[Matthieu Jacquart]

@Sebastian-Roth Hi, So I have imported my 40 hosts with csv file after looking for mac adress on each bios, but indeed even with pci=noacpi in host kernel arguments there no difference.
I’ll try other arguments on monday ! Have a nice weekzend