Cool - issue resolved!

This was absolutely an issue on our network, but we’re not sure if it was an old static Rendezvous Point that was configured on our core or if it was our VPC redundancy between our two nexus switches, but we were able to solve it by disabling pim on one of the nexuses and removing that static RP.

Thanks for the help on investigating, everyone. It’s much appreciated.

@Wayne-Workman Good catch - I need to read the manual!

I’ll go through and update everywhere as it states, then try again. Thank you!

Yup that did it! I was in the middle of copying files up to the server when you replied. Put them in that directory and rebooted and the errors went away. We’re good to go.

Thanks for the help @george1421 . Feel free to mark this one as solved.

@george1421 Thanks for the heads-up. I’m not using any USB flash sticks – I’m using a PXE boot setup. So would these need to go in /tftpboot on the server instead? Or another location?

I don’t know if this is helpful or not, but I found some e1000 references in the /var/log/messages file. Did not see a syslog file anywhere.

Thanks @george1421 ! I ran those commands, and I think the /var/syslog might be for RHEL where I’m on Ubuntu 16.04 LTS.

But your point on the kernel version is interesting, as I’m only on version 4.11. I thought I had updated to 4.19 yesterday in the Kernel Update thread.

So to test this a bit further, I ran the FOG kernel update again and rebooted this machine into Debug mode. The kernel update that the FOG management page says I’m installing is 4.19. The update succeeded without error. Rebooted the client into its debug task, and ran uname -a again, and still only see version 4.11.

So I realized if I simply press Enter a few times at that error, I still get the debug prompt. So I tested the commands, as recommended:
ip addr show
lspci -nn|grep -i net

Below are the results of these commands!

Thanks @george1421 . I manually registered the client via Mac Address in FOG and pushed the Debug task to it. When booting into the task, I get the same error message. See the screenshot below. This is what makes me think I need an updated kernel.

EDIT: I’m a dumb-dumb. If I press Enter a few times, I get to the debug prompt as expected.

Hello everyone,

As a follow-up from my previous thread, I am having trouble registering a new model of computer in FOG. Other computers register and images upload and deploy just fine, it’s just this new model. I’m working with the Dell Precision 3630 on this.

I can boot to PXE, obtain an IP Address, and get to the basic FOG menu no problem. From here, we typically do a Full Host Registration and Inventory before attempting to deploy any images, so that we have the host registered and trackable. We also use this for automating items like Hostname Changer and Active Directory domain joining.

Once I get to the basic FOG menu, I select the option for Full Host Registration and Inventory, and I am greeted with the error in the screenshot at the bottom of this post.

At first, I believed this to be related to a kernel, so I did update the kernel as noted in my previous post. This did not correct the error at all.

My kernel is now on version 4.19.36 TomElliott (May 1, 2019) and I’m using FOG version 1.4.4, SVN version 6077.

In the previous thread that I’m migrating this issue from, @george1421 suggested that I cancel any tasks I have assigned to the host and push the “Debug” task to it. I have been unable to do this, as I have not even been able to register the host in order to assign any tasks thus far. I’m just trying to get through host registration first.

EDIT: Typos corrected.

Great! Let’s mark this one as solved. In short, the issue for the kernel update was related to the permissions on the /var/www/fog/service/ipxe folder, which was a confirmed bug in version 1.4.4.

I’ll move the other issue to a new thread. Cheers!

@george1421

Tested the client and it doesn’t look like the kernel update fixed the problem. I installed PC 32-bit and PC 64-bit kernels (both version 4.19.36, last updated May 1, 2019).

So getting to the crux of the issue I was trying to solve, I am getting the error on the client noted in the screenshot at the end of this post.

Now I know that the network and PXE booting are fine, as I can actually PXE boot to the FOG menu without a problem and it gets an IP Address through that on the subnet that I expect. Once I get to the FOG menu, I select “Full Host Registration and Inventory.” I am then welcomed with the below error message. I believed this to be related to the kernel, which was why I was doing the kernel update in the first place. Was I wrong?

Also, if you need me to create a separate thread for this issue, let me know. I’ll mark this as solved and start a new one no problem.

@george1421 Ah thank you – it looks like I got to the same point on that one. I just attempted the command you noted:

sudo chmod -R 777 /var/www/html/fog/service/ipxe

This completed without error, but now I do the command to check:
ls -l /var/www/html/fog/service/ipxe

I get that the directory doesn’t exist. I changed your command to instead be a direct copy/paste from the TFTP Server settings in FOG Settings instead. This location is: /var/www/fog/service/ipxe (note the lack of the /html/ directory in the middle). The commands seemed to work in that case.

Tested the Kernel update again and SUCCESS! Looks like we’re in business.

Side note: I don’t really care about security on this box, as it’s shut down 90% of the time. We only power it on when we need it because we don’t want to worry about hardening it.

Thank you for the help. I’m going to do a test run with a client and see how it goes!