I just noticed a significant error in:
/usr/lib/systemd/system/wapttftpserver.service.
You should have:
--root_dir=/var/www/wads/pxe
, but it should be:
--root_dir=/var/www/html/wads/pxe.
Try replacing `reload / restart`.
Problem accessing the Wapt server on the client side
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
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
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Hello,
I modified the file /usr/lib/systemd/system/wapttftpserver.service and restarted the service.
However, when I run this command, it still fails, so on the Wapt client side, it still fails:
tftp srvwapt3.domain.fr
tftp> binary
tftp> get efi/boot/bootmgfw.efi
Transfer timed out.
tftp>
There seems to be a problem with the wapttftpserver service.
Thank you in advance for your reply.
I modified the file /usr/lib/systemd/system/wapttftpserver.service and restarted the service.
However, when I run this command, it still fails, so on the Wapt client side, it still fails:
tftp srvwapt3.domain.fr
tftp> binary
tftp> get efi/boot/bootmgfw.efi
Transfer timed out.
tftp>
There seems to be a problem with the wapttftpserver service.
Thank you in advance for your reply.
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
I just retested on an AlmaLinux 10 system.
After modifying wapttftpserver.service on my system, I can confirm that it works.
Verify that the correct folder is present here:
`ps aux | grep wapttftpserver.bin`
After modifying wapttftpserver.service on my system, I can confirm that it works.
Verify that the correct folder is present here:
`ps aux | grep wapttftpserver.bin`
It works on my server itself, but not on a client machine. On
the WAPT client side, when I try to boot, I now get the following message:
........................................................................................................................................................................................................................................
PXE-E79: NBP is too big to fit in free base memory
PXE-M0F: Existing Intel PXE ROM
.........................................................................................................................................................................................................................................
I wonder what this means
the WAPT client side, when I try to boot, I now get the following message:
........................................................................................................................................................................................................................................
PXE-E79: NBP is too big to fit in free base memory
PXE-M0F: Existing Intel PXE ROM
.........................................................................................................................................................................................................................................
I wonder what this means
It seems to be switching to UEFI mode, not Legacy mode. It's currently stuck due to a domain name issue when it launches the DOS console:
...................................................................................................................................................................................................................................
VerifyCert: X:\SSL\server\server.crt
Using wads repo URL https://srvwapt3.domaine.fr/wads for our IP 172.16.1.133
wads exe URL: https://srvwapt3.domaine.fr/wads/wads64.exe
DNS resolution has failed for: srvwapt3.domaine.fr .
DNS resolution has failed for: srvwapt3.domaine.fr
DNS resolution has failed for: srvwapt3.domaine.fr .
............................................................................................................................................................................................................................
...................................................................................................................................................................................................................................
VerifyCert: X:\SSL\server\server.crt
Using wads repo URL https://srvwapt3.domaine.fr/wads for our IP 172.16.1.133
wads exe URL: https://srvwapt3.domaine.fr/wads/wads64.exe
DNS resolution has failed for: srvwapt3.domaine.fr .
DNS resolution has failed for: srvwapt3.domaine.fr
DNS resolution has failed for: srvwapt3.domaine.fr .
............................................................................................................................................................................................................................
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Indeed, efi/boot/bootmgfw.efi is for UEFI only
https://www.wapt.fr/fr/doc/wapt-wads.ht ... figuration
In hybrid mode, we use IPXE for legacy systems and efi/boot/bootmgfw.efi for UEFI systems
