[RESOLVED] Since version 2.6.0.17177, PXE boot is no longer possible

[t.heroult]

Hello,
since the last update, it's impossible to use WADS; the machines can't find a PXE server.
The wapttftpserver.service is running correctly, and I can't find any error messages.
There's simply no response from the TFTP server.

[dcardon]

Hi Thomas,

is the wapttftpserver service running correctly? Is it on the main server, not a secondary repository? Could you please provide the command line you get with `ps -edf | grep tftp`?

Simon is running a series of internal tests.

Regards,

Denis

[t.heroult]

The wapttftpserver service, I said it was OK in the initial post.
There is no secondary repository.

I did a telnet "server wapt" 69 from another machine and there is no listening.

Result of the command executed on the WAPT server:

Code: Select all

wapt         510       1  0 15:05 ?        00:00:00 /opt/wapt/wapttftpserver.bin --fork --username=wapt --root_dir=/var/www/wads/pxe --verbose

[dcardon]

Hello again Thomas,

The wapttftpserver service, I said it was OK in the initial post.

I was talking about the binary itself, not the systemctl status

There is no secondary repository.

I telneted "server wapt" 69 from another machine and there is no listening.

That's normal, it's UDP. You can test it with a TFTP client on the client

Code: Select all

apt-get install tftp-hpa
tftp 127.0.0.1
tftp> binary
tftp> get ipxe.efi

Simon has managed to reproduce the problem; we'll get back to you shortly. You can retrieve the previous version of wapttftpserver.bin; there is indeed a regression related to log management, apparently...

Sorry,

Denis

[t.heroult]

OK, thank you, I'll wait for the reply

[dcardon]

Hello again Thomas,

The problem has been fixed internally; we'll release a version for this bug sometime this week. In the meantime, you can revert to the previous version of the wapttftpserver.bin binary until we release the update.

Code: Select all

wget https://wapt.tranquil.it/wapt/releases/wapt-2.6.0.16937-7ba7ea7a/bin/linux-x64/wapttftpserver
mv wapttftpserver  /opt/wapt/wapttftpserver.bin
chmod a+x /opt/wapt/wapttftpserver.bin
systemctl restart wapttftpserver

Regarding this glitch, the TFTP server we're using in the continuous integration environment is indeed a wapttftpserver, but not the one from the Wapt server currently being tested for WADS (for various technical and historical reasons). Furthermore, the Wapt binaries hadn't been updated on the machine in question, which serves as the TFTP server for this continuous integration VLAN. We'll try to correct this to prevent it from happening again.

Sorry, sincerely,

Denis

[t.heroult]

Hi,
thanks for the feedback.
I'll wait for the next release. This week we're shutting down the factory, so we're fully focused on the servers!
Mastering the PCs will have to wait. Have

a good day!

[clafon]

Hello,

when is the next release scheduled to fix this issue? Thank you.

[sfonteneau]

Hello,

version 2.6.0.17226 was released yesterday.

Simon