On 12/4/19 1:40 AM, Frank Morawietz wrote:
Some additional information:
I picked the boot files from the local syslinux installation:
- /usr/lib/syslinux/modules/efi32/syslinux.c32 --> syslinux32.efi
- /usr/lib/syslinux/modules/efi64/syslinux.c32 --> syslinux64.efi
- /usr/lib/syslinux/modules/bios/ldlinux.c32 --> ldlinux.c32
- /usr/lib/syslinux/modules/efi32/ldlinux.e32 --> ldlinux.e32
- /usr/lib/syslinux/modules/efi64/ldlinux.e64 --> ldlinux.e64
All boot files are in /srv/tftp/fai/ , with modified names where necessary.
In comparison, the DHCP + TFTP logs of a working installation in legacy BIOS
mode look like this:
Dec 3 14:38:44 sysadm02 dhcpd[12875]: DHCPDISCOVER from 50:9a:4c:43:c1:b7 via
ens9
Dec 3 14:38:44 sysadm02 dhcpd[12875]: DHCPOFFER on 10.250.217.16 to
50:9a:4c:43:c1:b7 via ens9
Dec 3 14:38:48 sysadm02 dhcpd[12875]: DHCPREQUEST for 10.250.217.16
(10.250.217.102) from 50:9a:4c:43:c1:b7 via ens9
Dec 3 14:38:48 sysadm02 dhcpd[12875]: DHCPACK on 10.250.217.16 to
50:9a:4c:43:c1:b7 via ens9
Dec 3 14:38:48 sysadm02 in.tftpd[14209]: RRQ from 10.250.217.16 filename
fai/pxelinux.0
Dec 3 14:38:48 sysadm02 in.tftpd[14209]: tftp: client does not accept options
Dec 3 14:38:48 sysadm02 in.tftpd[14210]: RRQ from 10.250.217.16 filename
fai/pxelinux.0
Dec 3 14:38:48 sysadm02 in.tftpd[14211]: RRQ from 10.250.217.16 filename
fai/ldlinux.c32
Dec 3 14:38:48 sysadm02 in.tftpd[14212]: RRQ from 10.250.217.16 filename
fai/pxelinux.cfg/44454c4c-3200-1056-8052-c
3c04f314c32
Dec 3 14:38:48 sysadm02 in.tftpd[14212]: sending NAK (1, File not found) to
10.250.217.16
Dec 3 14:38:48 sysadm02 in.tftpd[14213]: RRQ from 10.250.217.16 filename
fai/pxelinux.cfg/01-50-9a-4c-43-c1-b7
Dec 3 14:38:48 sysadm02 in.tftpd[14213]: sending NAK (1, File not found) to
10.250.217.16
Dec 3 14:38:48 sysadm02 in.tftpd[14214]: RRQ from 10.250.217.16 filename
fai/pxelinux.cfg/0AFAD910
Dec 3 14:38:48 sysadm02 in.tftpd[14215]: RRQ from 10.250.217.16 filename
fai/vmlinuz-4.9.0-9-amd64
Dec 3 14:38:49 sysadm02 in.tftpd[14216]: RRQ from 10.250.217.16 filename
fai/initrd.img-4.9.0-9-amd64
So it looks like the UEFI tftp connection refused error happened where ldlinux
should be transferred.
So here we see a request for pxelinux.0, then option negotiation, then
request for the pxelinux.0 file; which it looks like happens
successfully. All of this happens in the space of a second.
In the UEFI logs we see a request for syslinux64.efi, a connection
refused error, another request for the file, then negotiations of
options, then a request for the file again.
It almost looks like the connection refused causes a 4 second backoff
until it is retried and then successful... at least the connection
appears successful (being that options are negotiated and the file is
requested again, which is the same order as the legacy log above).
Do you have a longer trace of the UEFI boot? What happens after the
second request after option negotiations? Do you continue to get
connection refused errors?
I don't know what causes your initial connection refused error but it
looks like the second attempt is quasi-successful (without seeing more
of the log).
Did you get a chance to try getting the files manually using a tftp
client? The clients have verbose and packet tracing flags that you can
turn on and maybe get more information.
Cheers,
Merlin.
--
Merlin Hansen
Department of Computing Science
Vancouver Island University
900 Fifth Street
Nanaimo BC V9R 5S5
250-753-3245 x 2321
t...@csci.viu.ca
