Quick Registration gets stuck at 'Attempting to register host..'
-
@Tom-Elliott @george1421 Thanks both. I have completed those steps however I don’t see a change in behaviour or any debug info when I run the quick reg, no drop to a command prompt.
-
@TomBagley I was under the impression this was happening with full registration. Can you add the same ‘isdebug=yes’ to fog.reg?
-
@Tom-Elliott Got it, do you need me to run anything in the command line or provide an output?
-
@TomBagley What’s the output of the command
ip addr show
? -
-
@TomBagley And what’s output of
fdisk -l
-
@Tom-Elliott Sorry for delay, is this enough?
-
@george1421 said in Quick Registration gets stuck at 'Attempting to register host..':
@TomBagley Please do the following
- Select the Configuration icon
- iPXE Menu Configuration
- Select the fog.reginput
- Enter the following into the Boot Options field:
isdebug=yes
Be sure to leave a space between manreg and isdebug - PXE boot the target system and select quick reg. This should drop you to a command prompt.
From here I assume that Tom will want you to test something.
![alt text]( image url)
#wiki worthy
Also, pinging @Sebastian-Roth on the OP’s issue - Sebastian is awesome with HDDs, and a lot of other stuff to numerous to list here.
-
@TomBagley Are you still having this issue when trying to register this host? Do you you see this with different hosts? From my understanding the attempt to register a host is failing because there is a network issue. Full registration is propably working because the NIC has enough time to get an IP but not with quick registration I suppose. Can you please connect one of your clients with a dumb mini sctitch between the client and the main switch?
The output of
fdisk
you posted tells me that you might run into other issues with this client at some point. Those DELL recovery partitions are a pain when we try to make assumtions on where your windows system partition is. Please let us know if you run into issues when trying to deploy an image that you uploaded from this client. -
@Sebastian-Roth Apologies for the late reply. It happened with every host, I tried a selection. I have however rebuilt my Fog Server with increased space which has thankfully resolved the issue so I’ll never know for sure . I am now however having issues with the hostnamechanger so will start afresh thread If I cannot resolve.
Thanks all for suggestions the debugging was good learning as was migrating to new hardware.
Tom
-
@TomBagley Thanks for reporting back! Marking this solved then.