Failed to get an IP via DHCP!

jes6309

Hi guys

So, when I boot to fog and select “Perform full host registration…” I get the following (photo attached):

Sending discover…
Sending discover…
Sending discover,…
No lease, failing

I’ve searched for a solution but have come up empty.

I’m running the latest trunk version (7176) on Ubuntu Desktop 14.04LTS.

Never had this happen on earlier versions of fog. Any help is much appreciated. Even if it’s just to tell me what to look for.

Thanks!! photo: (https://drive.google.com/open?id=0BxKRFupXcJ0SRFdUai1QbDFCRm8)

george1421

What is the target computer you are trying to pxe boot.

I understand from the picture you are way past the pxe booting process and are actually in the FOS (Fog OS) kernel. Its possible that the FOS client doesn’t have the network adapter driver, or there is something else going on.

jes6309

Thanks for the reply.

It is a HP Laptop. It definitely has the NIC driver, as it is a fully operational windows 10 laptop.

And yes, I am able to pxe boot successfully. However, once I get to the Fog Menu and select Full Host Reg & inventory, it fails with the error in the image.

Kinda baffling.

george1421

@jes6309 said in Failed to get an IP via DHCP!:

It is a HP Laptop. It definitely has the NIC driver, as it is a fully operational windows 10 laptop.

Just for clarity, the FOG system uses linux so it will be important for the linux (FOS kernel) to have the required driver. Can you please supply the model of this laptop. Since it is running windows 10 it sounds new(ish).

Wayne Workman

Check your patch cable(s). Check them very, very closely. Any misshapen connector, oxidized connector, kinked cable, or loose connection will cause this issue.

Not saying this is your issue, but this is always the very first thing to check - every time.

jes6309

@george1421 oh I see. Unfortunately the laptop is at work and I have left for the day. I will get the model number for you first thing tomorrow.

jes6309

@george1421 HP Model Number: 15-af131dx. Here is the spec sheet http://support.hp.com/id-en/document/c04797004 and here is the hp support/driver page http://support.hp.com/us-en/drivers/selfservice/hp-15-af100-notebook-pc-series/8543365/model/8961406#Z7_3054ICK0K8UDA0AQC11TA930O2.

Thanks again!

jes6309

@Wayne-Workman Thank you. I’ve checked and there doesn’t seem to be an issue with the cable/ports. I’ve also tested with known good cables/ports and the results have been the same.

jes6309

Update: I just noticed that if I go under fog configuration in the management console, nothing is listed for either bzImage nor bzImage32. When I run the kernal update, I receive the following error: Type: 2, File: /var/www/html/fog/lib/fog/fogftp.class.php, Line: 144, Message: ftp_put(/var/www/html/fog/service/ipxe/bzImage): failed to open stream: No such file or directory.

Is this related?

Wayne Workman

@jes6309 I think that’s a separate issue, but easy enough to fix. The FTP credentials used for that are here:
Web Interface -> FOG Configuration -> FOG Settings -> TFTP Server -> FOG_TFTP_FTP_USERNAME & FOG_TFTP_FTP_PASSWORD

If you have only one fog server in your setup, those credentials will be the same as these:
Web Interface -> Storage Management -> [Your storage node] -> Management Username & Management Password

Both of these things and a lot more can be found in the “Troubleshoot FTP” article here:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP

george1421

first I have to get this out of the way: Ugh! this has a realtek lan adapter!!

As for your kernels. I see you are running a trunk version. What I would like you to do is manually register this device in FOG. Then schedule a image deployment to this system, BUT make sure you select a debug deployment. This will push the bzImage to the client and the target will boot but drop you at a command prompt.

From there lets use some hardware diagnostics commands to see what network adapter is built in.

jes6309

@george1421 Ok I’ve taken these steps, but when the laptop boots to the network, it gets up to “init.xz… ok” and just stops.

george1421

@jes6309 (A bit confused now). In your OP you said that when you selected full registration you were getting the “Sending discover…” this should be the FOS kernel running with the virtual hard drive but not able to get a dhcp address. But when you do a debug deploy the system is freezing after the kernel gets the FOS virtual hard drive (init.xz)?

This is a bit inconsistent.

Thinking <…>

jes6309

@george1421 hmmmm

idk if this will help, but when I run Kernel Update (after having fixed the credentials as per Wayne) it gets stuck on “Moving to TFTP server…”. If I close out of the operation and attempt to run Kernel Update again, I receive the “Type: 2, File: /var/www/html/fog/lib/fog/fogftp.class.php, Line: 144, Message: ftp_put(/var/www/html/fog/service/ipxe/bzImage): failed to open stream: No such file or directory.” error. On the fog server, if i check /var/www/html/fog/service/ipxe, “bzImage” is nowhere to be found. Note, it was present before attempting the kernel update. It’s as if the kernel update operation is just deleting the bzImage directory rather than actually updating it. I feel like these bizarre errors I’m getting when booting my client to fog and/or registering it as a host has got to be related to a bad kernel, or, after “updating”, a missing kernel.

I’m just at loss for a fix.

george1421

@jes6309 ok that is now understandable. I missed the part about the failed update. Let me see if I can get the url to manually download the kernels.

george1421

@jes6309

Execute the following commands on the fog server

cd /var/www/html/fog/service/ipxe

wget https://fogproject.org/inits/init.xz
wget https://fogproject.org/inits/init_32.xz
wget https://fogproject.org/kernels/bzImage
wget https://fogproject.org/kernels/bzImage32

This will download the latest (current) kernel and inits.

jes6309

@george1421 Ok that got me past “init.xz… ok”

However, I’m getting the “Sending discover…” message again. This is with the debug deploy task scheduled.

george1421

@jes6309 Good that should eventually time out (I think) and drop you to the linux shell.

jes6309

This post is deleted!

jes6309

@george1421 Yup!

[Thu Apr 14 root@fogclient /]# is what I am seeing. What commands did you want me to run?

I went ahead and ran lshw -short and ethernet controller listed is “RTL8101E/RTL8102E PCI Express Fast Ethernet Controller”

Failed to get an IP via DHCP!

237

12.0k

17.3k

155.2k