Hello,
I'm using WAPT 2.6, I have a secondary repository, and I want to boot via PXE for imaging purposes.
When I launch the PXE boot on a machine, I get:
Station IP address is [IP address OK]
Server IP address is [IP address OK]
NBP filename is efi/boot/bootmgfw.efi
NBP filesize is 0 bytes
PXE-E23: client received TFTP error from server.
Can you help me?
Sincerely.
[SOLVED] PXE Boot
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
-
dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hi Benoit,
at first glance it seems to be a mismatch between UEFI and legacy boot. Could you please verify that you are indeed using UEFI on both sides (desktop and PXE)?
Regards,
Denis
at first glance it seems to be a mismatch between UEFI and legacy boot. Could you please verify that you are indeed using UEFI on both sides (desktop and PXE)?
Regards,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Hello,
I probably should have started with this, but I'm using Oracle Linux 10.1, based on RHEL.
I disabled wapttftpserver and installed tftp-server for testing purposes. I realized that managing and configuring tftp-server under RHEL10 is significantly different
from that under RHEL9 (systemctl uses tftp-socket instead of server, and the files are no longer located under /etc/xinited...). I was leaning towards an incompatibility issue.
I'll look at your solution, but I admit I don't know how to proceed. Could you explain how to verify this?
Thank you for your help.
Best regards.
I probably should have started with this, but I'm using Oracle Linux 10.1, based on RHEL.
I disabled wapttftpserver and installed tftp-server for testing purposes. I realized that managing and configuring tftp-server under RHEL10 is significantly different
from that under RHEL9 (systemctl uses tftp-socket instead of server, and the files are no longer located under /etc/xinited...). I was leaning towards an incompatibility issue.
I'll look at your solution, but I admit I don't know how to proceed. Could you explain how to verify this?
Thank you for your help.
Best regards.
-
dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hi Benoit,
there's a problem in the unit systemd file under RHEL. The path /var/www/html/pxe isn't correctly reflected in it, see viewtopic.php?p=16949#p16949 . You can correct the file manually; it should work afterward. This bug will be fixed in the upcoming 2.6.1 release.
Regards,
Denis
there's a problem in the unit systemd file under RHEL. The path /var/www/html/pxe isn't correctly reflected in it, see viewtopic.php?p=16949#p16949 . You can correct the file manually; it should work afterward. This bug will be fixed in the upcoming 2.6.1 release.
Regards,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
When I run `sudo systemctl status wapttftpserver`, I get:
`/opt/wapt/wapttftpserver.bin --fork --username=root --root_dir=/opt/wapt/repository/wads/pxe --verbose --log-path=/dev/stdout`.
This seems to indicate that the repository I configured in `wapt-get.ini`, `local_repo_path=/Depot`, is not being used.
Can you tell me how to modify the repository path so that `wapttftpserver` uses the correct path?
Sincerely.
`/opt/wapt/wapttftpserver.bin --fork --username=root --root_dir=/opt/wapt/repository/wads/pxe --verbose --log-path=/dev/stdout`.
This seems to indicate that the repository I configured in `wapt-get.ini`, `local_repo_path=/Depot`, is not being used.
Can you tell me how to modify the repository path so that `wapttftpserver` uses the correct path?
Sincerely.
-
dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hi Benoit,
thanks for the feedback,
I'm marking the topic as resolved.
Denis
thanks for the feedback,
I'm marking the topic as resolved.
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
