Diagnosing Unexpected Network Error on PXE/HTTP boot

Docs
1

I am attempting to redeploy one of my RPIs and am receiving this error. I did notice this error recently after I upgraded my MaaS rack controller and region+rack controllers to Ubuntu 22.04LTS and MaaS version 3.2.6-12016-g.19812b4da (3.2/stable).

image

    Server IP address is 192.168.20.2
    NBP filename is bootaa64.efi 
    NBP filesize is 0 Bytes 
    PXE-E18: Server response timeout. 
    
    >>Start PXE over IPv6. 
    PXE-E16: No valid offer received.  
    
    >>Start HTTP Boot over IPv4...
    Station IP address is 192.168.20.235 
    URI: http://192.168.20.2:5248/images/bootaa64.efi 
    Error: Could not retrieue NBP file size from HTTP server. 
    Error: Unexpected network error. 
    
    >>Start HTTP Boot over IPv6. 
    Error: Could not retrieve NBP file size from HTTP server. 
    Error: Unexpected network error.

    BdsDxe: No bootable option or device was found. 
    BdsDxe: Press any key to enter the Boot Manager Menu. 

region_rack@regionrackoperator:~$ sudo maas status 
bind9                            RUNNING   pid 2078, uptime 2 days, 20:19:08
dhcpd                            RUNNING   pid 213705, uptime 22:23:02
dhcpd6                           STOPPED   Not started
http                             RUNNING   pid 2668, uptime 2 days, 20:18:30
ntp                              RUNNING   pid 2457, uptime 2 days, 20:18:47
proxy                            RUNNING   pid 238215, uptime 17:08:51
rackd                            RUNNING   pid 2082, uptime 2 days, 20:19:08
regiond                          RUNNING   pid 2083, uptime 2 days, 20:19:08
syslog                           RUNNING   pid 2439, uptime 2 days, 20:18:48

rack@rackoperator:~$ sudo maas status 
bind9                            RUNNING   pid 4870, uptime 2 days, 18:13:31
dhcpd                            RUNNING   pid 1226074, uptime 22:20:39
dhcpd6                           STOPPED   Not started
http                             RUNNING   pid 6852, uptime 2 days, 18:13:12
ntp                              RUNNING   pid 6501, uptime 2 days, 18:13:20
proxy                            STOPPED   Not started
rackd                            RUNNING   pid 4873, uptime 2 days, 18:13:31
syslog                           RUNNING   pid 6502, uptime 2 days, 18:13:20

I did check Troubleshooting Networking Issues but didn’t feel like there was an appropriate section that pertained to this particular problem.

I have been trying to troubleshoot what is causing this and why and am currently stumped. Would appreciate any insight regarding this or the process I could utilize to reverse engineer and troubleshoot the root cause here. Thank you.

2

Did a ping test from the managed switch that connects all the PIs in the cluster to the rack and rack+region controllers and routers as well. See no issues.

Switch to rack controller

PING 192.168.5.2 (192.168.5.2): 46 data bytes
54 bytes from 192.168.5.2: seq=0 ttl=63 time=0.000 ms
54 bytes from 192.168.5.2: seq=1 ttl=63 time=0.000 ms
54 bytes from 192.168.5.2: seq=2 ttl=63 time=0.000 ms

--- 192.168.5.2 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.000/0.000/0.000 ms

Switch to rack+region controller

PING 192.168.20.2 (192.168.20.2): 46 data bytes
54 bytes from 192.168.20.2: seq=0 ttl=63 time=30.000 ms
54 bytes from 192.168.20.2: seq=1 ttl=63 time=0.000 ms
54 bytes from 192.168.20.2: seq=2 ttl=63 time=0.000 ms

--- 192.168.20.2 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.000/10.000/30.000 ms

Switch to moved-gull.maas during PXE (Raspberry Pi 4)

PING 192.168.20.235 (192.168.20.235): 46 data bytes
54 bytes from 192.168.20.235: seq=0 ttl=63 time=0.000 ms
54 bytes from 192.168.20.235: seq=1 ttl=63 time=0.000 ms
54 bytes from 192.168.20.235: seq=2 ttl=63 time=10.000 ms

--- 192.168.20.235 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.000/3.333/10.000 ms

Switch to router

PING 192.168.1.1 (192.168.1.1): 46 data bytes
54 bytes from 192.168.1.1: seq=0 ttl=64 time=0.000 ms
54 bytes from 192.168.1.1: seq=1 ttl=64 time=0.000 ms
54 bytes from 192.168.1.1: seq=2 ttl=64 time=0.000 ms
--- 192.168.1.1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.000/0.000/0.000 ms
3

I did see this post regarding supported Postgres versions but since we arecurrently on 22.04 LTS I assume there should be no reason it is not supported out of the box…

4

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.