[RESOLVED] IPXE Problem: Network unreachable

Share your tips or issues concerning the WAPT Console or WAPT Agent here
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Locked
User avatar
t.heroult
Messages: 307
Registration: December 8, 2020 - 10:13 AM

September 9, 2022 - 9:41 AM

Good morning

Since this morning, we've been experiencing strange behavior when booting from PXE.
We tried it with VMs and physical machines and it always gives the same result:
ipxe.png
ipxe.png (19.11 KiB) Viewed 4059 times
Even after restarting the WAPT server, nothing changes.

Any ideas?

Sincerely,
Tom

EDIT: Problem with DHCP server desynchronization
Last edited by t.heroult on 12 Sep 2022 - 16:17, edited 1 time.
Server: WAPT Enterprise 2.6.1.17786 on Debian
Consoles: Windows 10 & 11
Infrastructure: Windows

Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
High
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :
Contact Sfonteneau

September 9, 2022 - 9:57 AM

Hello,

the IPXE has been successfully retrieved, so the first step is OK (TFTP part).

Now the IPXE is retrieving its configuration (it's making another DHCP request to get the IPXE script URL).

Has this already worked for you, or is this a new setup?

Simon
High
User avatar
t.heroult
Messages: 307
Registration: December 8, 2020 - 10:13 AM

September 9, 2022 - 12:57

It's been in place for a while now, we've already mastered a few machines with it.
Server: WAPT Enterprise 2.6.1.17786 on Debian
Consoles: Windows 10 & 11
Infrastructure: Windows

Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
High
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :
Contact Sfonteneau

September 9, 2022 - 6:40 PM

t.heroult wrote: ↑09 Sep 2022 - 12:57 It's been in place for a while now, we've already mastered a few machines with it.
Interesting, has anything changed on your end in the meantime? A Wapt upgrade? A DHCP configuration modification?

Do you see anything in the nginx logs on the wapt server?

Code: Select all

tail -f /var/log/nginx/access.log
High
User avatar
t.heroult
Messages: 307
Registration: December 8, 2020 - 10:13 AM

September 12, 2022 - 10:06 AM

Hello Simon
No, there are no changes in our system or in WAPT.
That's what's really weird...

Here is the result of the command:

Code: Select all

root@SRVWAPT:~# tail -f /var/log/nginx/access.log
172.18.0.7 - - [12/Sep/2022:10:02:15 +0200] "POST /update_host HTTP/1.1" 200 1204 "-" "wapt/2.2.2"
172.16.2.173 - - [12/Sep/2022:10:02:28 +0200] "HEAD /ping HTTP/1.1" 200 0 "-" "wapt/2.2.2"
172.16.2.173 - - [12/Sep/2022:10:02:30 +0200] "POST /update_host HTTP/1.1" 200 1276 "-" "wapt/2.2.2"
172.16.2.103 - - [12/Sep/2022:10:02:37 +0200] "HEAD /waptwua/wsusscn2.cab HTTP/1.1" 200 0 "-" "wapt/2.2.2"
172.16.10.69 - - [12/Sep/2022:10:02:38 +0200] "HEAD /ping HTTP/1.1" 200 0 "-" "wapt/2.2.2"
172.16.10.69 - - [12/Sep/2022:10:02:40 +0200] "POST /update_host HTTP/1.1" 200 1276 "-" "wapt/2.2.2"
172.17.1.35 - - [12/Sep/2022:10:02:46 +0200] "HEAD /ping HTTP/1.1" 200 0 "-" "wapt/2.2.2"
172.17.1.35 - - [12/Sep/2022:10:02:47 +0200] "POST /update_host HTTP/1.1" 200 1270 "-" "wapt/2.2.2"
172.17.1.19 - - [12/Sep/2022:10:02:58 +0200] "HEAD /ping HTTP/1.1" 200 0 "-" "wapt/2.2.2"
172.17.1.19 - - [12/Sep/2022:10:02:59 +0200] "POST /update_host HTTP/1.1" 200 1270 "-" "wapt/2.2.2"
172.16.1.127 - - [12/Sep/2022:10:03:19 +0200] "GET /rules.json HTTP/1.1" 200 2 "-" "wapt/2.2.2"
172.16.1.127 - - [12/Sep/2022:10:03:19 +0200] "HEAD /waptwua/wsusscn2.cab HTTP/1.1" 200 0 "-" "wapt/2.2.2"
172.16.1.127 - - [12/Sep/2022:10:03:19 +0200] "GET /licences.json HTTP/1.1" 200 2658 "-" "wapt/2.2.2"
172.16.1.127 - - [12/Sep/2022:10:03:19 +0200] "HEAD /wapt/Packages HTTP/1.1" 200 0 "-" "wapt/2.2.2"
172.16.1.127 - - [12/Sep/2022:10:03:19 +0200] "GET /wapt/Packages HTTP/1.1" 200 134009 "-" "wapt/2.2.2"
172.16.1.127 - - [12/Sep/2022:10:03:20 +0200] "HEAD /wapt-host/xxxxxxxxxxx.local.wapt HTTP/1.1" 200 0 "-" "wapt/2.2.2"
172.16.1.127 - - [12/Sep/2022:10:03:20 +0200] "GET /rules.json HTTP/1.1" 200 2 "-" "wapt/2.2.2"
172.16.1.127 - - [12/Sep/2022:10:03:20 +0200] "HEAD /waptwua/wsusscn2.cab HTTP/1.1" 200 0 "-" "wapt/2.2.2"
172.16.1.127 - - [12/Sep/2022:10:03:20 +0200] "GET /licences.json HTTP/1.1" 200 2658 "-" "wapt/2.2.2"
172.16.1.127 - - [12/Sep/2022:10:03:20 +0200] "HEAD /wapt/Packages HTTP/1.1" 200 0 "-" "wapt/2.2.2"
172.16.1.127 - - [12/Sep/2022:10:03:20 +0200] "HEAD /wapt-host/xxxxxxxxxxx.local.wapt HTTP/1.1" 200 0 "-" "wapt/2.2.2"
172.16.1.127 - - [12/Sep/2022:10:03:20 +0200] "HEAD /ping HTTP/1.1" 200 0 "-" "wapt/2.2.2"
172.16.1.127 - - [12/Sep/2022:10:03:21 +0200] "POST /update_host HTTP/1.1" 200 1270 "-" "wapt/2.2.2"
172.16.10.69 - - [12/Sep/2022:10:03:31 +0200] "HEAD /ping HTTP/1.1" 200 0 "-" "wapt/2.2.2"
172.16.10.69 - - [12/Sep/2022:10:03:33 +0200] "POST /update_host HTTP/1.1" 200 1276 "-" "wapt/2.2.2"
172.16.3.11 - - [12/Sep/2022:10:03:48 +0200] "HEAD /ping HTTP/1.1" 200 0 "-" "wapt/2.2.2"
172.16.3.11 - - [12/Sep/2022:10:03:50 +0200] "POST /update_host HTTP/1.1" 200 1268 "-" "wapt/2.2.2"
172.16.2.89 - - [12/Sep/2022:10:03:56 +0200] "HEAD /ping HTTP/1.1" 200 0 "-" "wapt/2.2.2"
172.16.2.89 - - [12/Sep/2022:10:03:57 +0200] "POST /update_host HTTP/1.1" 200 1274 "-" "wapt/2.2.2"
172.16.1.201 - - [12/Sep/2022:10:04:00 +0200] "HEAD /ping HTTP/1.1" 200 0 "-" "wapt/2.2.2"
172.16.1.201 - - [12/Sep/2022:10:04:02 +0200] "POST /update_host HTTP/1.1" 200 1276 "-" "wapt/2.2.2"
172.17.1.19 - - [12/Sep/2022:10:04:09 +0200] "HEAD /ping HTTP/1.1" 200 0 "-" "wapt/2.2.2"
172.17.1.19 - - [12/Sep/2022:10:04:10 +0200] "POST /update_host HTTP/1.1" 200 1269 "-" "wapt/2.2.2"
172.16.1.219 - - [12/Sep/2022:10:04:10 +0200] "HEAD /ping HTTP/1.1" 200 0 "-" "wapt/2.2.2"
172.16.50.144 - - [12/Sep/2022:10:04:11 +0200] "HEAD /ping HTTP/1.1" 200 0 "-" "wapt/2.2.2"
172.16.50.144 - - [12/Sep/2022:10:04:12 +0200] "POST /update_host HTTP/1.1" 200 1265 "-" "wapt/2.2.2"
172.16.1.219 - - [12/Sep/2022:10:04:12 +0200] "POST /update_host HTTP/1.1" 200 1264 "-" "wapt/2.2.2"
172.17.1.16 - - [12/Sep/2022:10:04:12 +0200] "HEAD /ping HTTP/1.1" 200 0 "-" "wapt/2.2.2"
172.17.1.16 - - [12/Sep/2022:10:04:13 +0200] "POST /update_host HTTP/1.1" 200 1270 "-" "wapt/2.2.2"
172.16.1.161 - - [12/Sep/2022:10:04:14 +0200] "HEAD /ping HTTP/1.1" 200 0 "-" "wapt/2.2.2"
...
Server: WAPT Enterprise 2.6.1.17786 on Debian
Consoles: Windows 10 & 11
Infrastructure: Windows

Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
High
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :
Contact Sfonteneau

September 12, 2022 - 10:41

Code: Select all

cat /var/log/nginx/access.log |grep -i pxe
will be better for searching for PXE in access.log
High
User avatar
t.heroult
Messages: 307
Registration: December 8, 2020 - 10:13 AM

September 12, 2022 - 11:52

There are no results there.
Server: WAPT Enterprise 2.6.1.17786 on Debian
Consoles: Windows 10 & 11
Infrastructure: Windows

Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
High
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :
Contact Sfonteneau

September 12, 2022 - 1:16 PM

Same answer as here:

viewtopic.php?p=10982#p10982

It's strange that it crashes without any changes (no Wapt upgrade, no DHCP configuration modification).
High
User avatar
t.heroult
Messages: 307
Registration: December 8, 2020 - 10:13 AM

September 12, 2022 - 2:44 PM

Unfortunately, that doesn't help.

The entire DHCP configuration seems OK; a test returns the correct filename (ipxe.efi) and the correct IP address.
The file is correctly located in /var/www/wads/pxe (dated 5/8/22).
I don't know what to check next.
Server: WAPT Enterprise 2.6.1.17786 on Debian
Consoles: Windows 10 & 11
Infrastructure: Windows

Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
High
User avatar
t.heroult
Messages: 307
Registration: December 8, 2020 - 10:13 AM

September 12, 2022 - 3:04 PM

Update: By pausing at the beginning of the boot process, it seems that the file is successfully retrieved
ipxe.png
ipxe.png (9.92 KB) Viewed 3994 times
The file size matches what I see in filezilla on the Wapt server.
Server: WAPT Enterprise 2.6.1.17786 on Debian
Consoles: Windows 10 & 11
Infrastructure: Windows

Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
High
Locked

Return to "WAPT usage (Console, Agent) / WAPT usage (Console, Agent)"


  • To go further with WAPT