my commissioning failed,which logs supplyed can help me here?

lukexjin · 6 June 2025 10:13

server is SYS-7048GR-TR,mainboard is Supermicro X10DRG-Q

r00ta · 6 June 2025 10:20

It’s a pretty old one. I’d suggest to try using bionic/focal for commissioning

lukexjin · 6 June 2025 15:03

always hang on there,bro
d5f50fb9642e0e7f3bb3e9c29857f19

r00ta · 6 June 2025 15:08

Please enable the debug mode by editing /var/snap/maas/current/rackd.conf and add debug: true. After that restart MAAS with sudo snap restart maas and check if you get more logs on the console while booting

lukexjin · 6 June 2025 15:17

yes,bro,can get more,hangs on here

r00ta · 6 June 2025 15:27

how much memory do you have on this server? Can you check in the BIOS the available RAM?

lukexjin · 6 June 2025 15:39

lukexjin · 6 June 2025 15:40

lukexjin · 6 June 2025 15:43

in fact,this server has a ubuntu 22 in hdd disk and run ok

r00ta · 6 June 2025 15:47

My suggestion would be to

try to factory reset the server BIOS and update all the firmwares
try to install ubuntu from a USB stick
double check the MTU on the MAAS controller node and the switches

Also, if you have another server of another brand you might try to use it, just to exclude a misconfiguration of the MAAS controller node or the network.

lukexjin · 10 June 2025 09:44

after set bios to dual,show more error log,can you help check,bro

r00ta · 10 June 2025 11:22

Looks like you have a TPM module. You might try to disable (or update) it from the BIOS

lukexjin · 18 June 2025 09:01

get some tftp error,tftp always some error,first time error,second time ok.
can you help check further
[BEGIN] 2025/6/18 15:27:16
root@u24maas:~# journalctl -u snap.maas.pebble -t maas-rackd --no-pager -f
Jun 18 15:26:02 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-agent’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:26:02 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-dhcpd’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:26:32 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-dhcpd’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:26:32 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-agent’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:26:32 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-http’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:26:32 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-dhcpd6’ is SERVICE_STATE.OFF and ‘dead’.
Jun 18 15:27:03 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-http’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:27:03 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-agent’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:27:03 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-dhcpd6’ is SERVICE_STATE.OFF and ‘dead’.
Jun 18 15:27:03 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-dhcpd’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:27:32 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-dhcpd6’ is SERVICE_STATE.OFF and ‘dead’.
Jun 18 15:27:32 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-dhcpd’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:27:32 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-http’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:27:32 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-agent’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:28:02 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-http’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:28:02 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-agent’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:28:02 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-dhcpd’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:28:02 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-dhcpd6’ is SERVICE_STATE.OFF and ‘dead’.
Jun 18 15:28:32 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-dhcpd6’ is SERVICE_STATE.OFF and ‘dead’.
Jun 18 15:28:32 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-http’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:28:32 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-agent’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:28:32 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-dhcpd’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:29:01 u24maas maas-rackd[79738]: tftp.protocol: [debug] Datagram received from (‘192.168.204.173’, 1175): <RRQDatagram(filename=b’bootx64.efi’, mode=b’octet’, options=OrderedDict({b’tsize’: b’0’, b’blksize’: b’1468’}))>
Jun 18 15:29:01 u24maas maas-rackd[79738]: provisioningserver.rackdservices.tftp: [info] bootx64.efi requested by 192.168.204.173
Jun 18 15:29:01 u24maas maas-rackd[79738]: provisioningserver.rackdservices.http: [info] /images/bootx64.efi requested by 127.0.0.1
Jun 18 15:29:01 u24maas maas-rackd[79738]: tftp.bootstrap: [debug] Got error: <tftp.datagram.ERRORDatagram object at 0x78e905a33890>
Jun 18 15:29:01 u24maas maas-rackd[79738]: tftp.protocol: [debug] Datagram received from (‘192.168.204.173’, 1176): <RRQDatagram(filename=b’bootx64.efi’, mode=b’octet’, options=OrderedDict({b’blksize’: b’1468’}))>
Jun 18 15:29:01 u24maas maas-rackd[79738]: provisioningserver.rackdservices.tftp: [info] bootx64.efi requested by 192.168.204.173
Jun 18 15:29:01 u24maas maas-rackd[79738]: provisioningserver.rackdservices.http: [info] /images/bootx64.efi requested by 127.0.0.1
Jun 18 15:29:01 u24maas maas-rackd[79738]: tftp.session: [debug] Final ACK received, transfer successful
Jun 18 15:29:01 u24maas maas-rackd[79738]: tftp.protocol: [debug] Datagram received from (‘192.168.204.173’, 1177): <RRQDatagram(filename=b’grubx64.efi’, mode=b’octet’, options=OrderedDict({b’blksize’: b’512’}))>
Jun 18 15:29:01 u24maas maas-rackd[79738]: provisioningserver.rackdservices.tftp: [info] grubx64.efi requested by 192.168.204.173
Jun 18 15:29:01 u24maas maas-rackd[79738]: provisioningserver.rackdservices.http: [info] /images/grubx64.efi requested by 127.0.0.1
Jun 18 15:29:02 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-http’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:29:02 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-agent’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:29:02 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-dhcpd6’ is SERVICE_STATE.OFF and ‘dead’.
Jun 18 15:29:02 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-dhcpd’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:29:03 u24maas maas-rackd[79738]: tftp.session: [debug] Final ACK received, transfer successful
Jun 18 15:29:03 u24maas maas-rackd[79738]: tftp.protocol: [debug] Datagram received from (‘192.168.204.173’, 25300): <RRQDatagram(filename=b’/grub/x86_64-efi/command.lst’, mode=b’octet’, options=OrderedDict({b’blksize’: b’1024’, b’tsize’: b’0’}))>
Jun 18 15:29:03 u24maas maas-rackd[79738]: provisioningserver.rackdservices.tftp: [info] /grub/x86_64-efi/command.lst requested by 192.168.204.173
Jun 18 15:29:03 u24maas maas-rackd[79738]: provisioningserver.rackdservices.http: [info] /images/grub/x86_64-efi/command.lst requested by 127.0.0.1
Jun 18 15:29:03 u24maas maas-rackd[79738]: tftp.bootstrap: [debug] Got error: <tftp.datagram.ERRORDatagram object at 0x78e905a9f320>
Jun 18 15:29:03 u24maas maas-rackd[79738]: tftp.protocol: [debug] Datagram received from (‘192.168.204.173’, 25301): <RRQDatagram(filename=b’/grub/x86_64-efi/fs.lst’, mode=b’octet’, options=OrderedDict({b’blksize’: b’1024’, b’tsize’: b’0’}))>
Jun 18 15:29:03 u24maas maas-rackd[79738]: provisioningserver.rackdservices.tftp: [info] /grub/x86_64-efi/fs.lst requested by 192.168.204.173
Jun 18 15:29:03 u24maas maas-rackd[79738]: provisioningserver.rackdservices.http: [info] /images/grub/x86_64-efi/fs.lst requested by 127.0.0.1
Jun 18 15:29:03 u24maas maas-rackd[79738]: tftp.bootstrap: [debug] Got error: <tftp.datagram.ERRORDatagram object at 0x78e905a9c410>
Jun 18 15:29:03 u24maas maas-rackd[79738]: tftp.protocol: [debug] Datagram received from (‘192.168.204.173’, 25302): <RRQDatagram(filename=b’/grub/x86_64-efi/crypto.lst’, mode=b’octet’, options=OrderedDict({b’blksize’: b’1024’, b’tsize’: b’0’}))>
Jun 18 15:29:03 u24maas maas-rackd[79738]: provisioningserver.rackdservices.tftp: [info] /grub/x86_64-efi/crypto.lst requested by 192.168.204.173
Jun 18 15:29:03 u24maas maas-rackd[79738]: provisioningserver.rackdservices.http: [info] /images/grub/x86_64-efi/crypto.lst requested by 127.0.0.1
Jun 18 15:29:03 u24maas maas-rackd[79738]: tftp.bootstrap: [debug] Got error: <tftp.datagram.ERRORDatagram object at 0x78e905a9e870>
Jun 18 15:29:03 u24maas maas-rackd[79738]: tftp.protocol: [debug] Datagram received from (‘192.168.204.173’, 25303): <RRQDatagram(filename=b’/grub/x86_64-efi/terminal.lst’, mode=b’octet’, options=OrderedDict({b’blksize’: b’1024’, b’tsize’: b’0’}))>
Jun 18 15:29:03 u24maas maas-rackd[79738]: provisioningserver.rackdservices.tftp: [info] /grub/x86_64-efi/terminal.lst requested by 192.168.204.173
Jun 18 15:29:03 u24maas maas-rackd[79738]: provisioningserver.rackdservices.http: [info] /images/grub/x86_64-efi/terminal.lst requested by 127.0.0.1
Jun 18 15:29:03 u24maas maas-rackd[79738]: tftp.bootstrap: [debug] Got error: <tftp.datagram.ERRORDatagram object at 0x78e905a33470>
Jun 18 15:29:03 u24maas maas-rackd[79738]: tftp.protocol: [debug] Datagram received from (‘192.168.204.173’, 25304): <RRQDatagram(filename=b’/grub/grub.cfg’, mode=b’octet’, options=OrderedDict({b’blksize’: b’1024’, b’tsize’: b’0’}))>
Jun 18 15:29:03 u24maas maas-rackd[79738]: provisioningserver.rackdservices.tftp: [info] /grub/grub.cfg requested by 192.168.204.173
Jun 18 15:29:03 u24maas maas-rackd[79738]: tftp.session: [debug] Final ACK received, transfer successful
Jun 18 15:29:03 u24maas maas-rackd[79738]: tftp.protocol: [debug] Datagram received from (‘192.168.204.173’, 25305): <RRQDatagram(filename=b’/grub/grub.cfg-ac:1f:6b:fb:8b:4c’, mode=b’octet’, options=OrderedDict({b’blksize’: b’1024’, b’tsize’: b’0’}))>
Jun 18 15:29:03 u24maas maas-rackd[79738]: provisioningserver.rackdservices.tftp: [info] /grub/grub.cfg-ac:1f:6b:fb:8b:4c requested by 192.168.204.173
Jun 18 15:29:03 u24maas maas-rackd[79738]: provisioningserver.kernel_opts: [debug] quick-hog: kernel parameters — "nomodeset root=squash:http://192.168.204.16:5248/images/6cd63c9/ubuntu/amd64/ga-20.04/focal/stable/squashfs ip=::::quick-hog:BOOTIF ip6=off cc:{‘datasource_list’: [‘MAAS’]}end_cc cloud-config-url=http://192-168-204-0--24.maas-internal:5248/MAAS/metadata/latest/by-id/x3syca/?op=get_preseed ro overlayroot=tmpfs overlayroot_cfgdisk=disabled apparmor=0 log_host=192.168.204.16 log_port=5247 — "
Jun 18 15:29:03 u24maas maas-rackd[79738]: tftp.session: [debug] Final ACK received, transfer successful
Jun 18 15:29:07 u24maas maas-rackd[79738]: provisioningserver.rackdservices.http: [info] /images/bd91c27/ubuntu/amd64/ga-20.04/focal/stable/boot-kernel requested by 192.168.204.173
Jun 18 15:29:12 u24maas maas-rackd[79738]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:192.168.204.16’, port=41304, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:192.168.204.16’, port=5250, flowInfo=0, scopeID=0))
Jun 18 15:29:12 u24maas maas-rackd[79738]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:192.168.204.16’, port=41310, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:192.168.204.16’, port=5250, flowInfo=0, scopeID=0))
Jun 18 15:29:32 u24maas maas-rackd[79738]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:192.168.204.16’, port=48766, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:192.168.204.16’, port=5250, flowInfo=0, scopeID=0))
Jun 18 15:29:32 u24maas maas-rackd[79738]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:192.168.204.16’, port=48768, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:192.168.204.16’, port=5250, flowInfo=0, scopeID=0))
Jun 18 15:29:32 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-http’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:29:32 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-dhcpd’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:29:32 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-dhcpd6’ is SERVICE_STATE.OFF and ‘dead’.
Jun 18 15:29:32 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-agent’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:29:32 u24maas maas-rackd[79738]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘u24maas:pid=79809’ authenticated.
Jun 18 15:29:33 u24maas maas-rackd[79738]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘u24maas:pid=79809’ authenticated.
Jun 18 15:29:33 u24maas maas-rackd[79738]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘k3sw77’ registered (via u24maas:pid=79809) with MAAS version 3.6.0-17541-g.561fe1a3e.
Jun 18 15:29:33 u24maas maas-rackd[79738]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘k3sw77’ registered (via u24maas:pid=79809) with MAAS version 3.6.0-17541-g.561fe1a3e.
Jun 18 15:29:42 u24maas maas-rackd[79738]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:192.168.204.16’, port=36108, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:192.168.204.16’, port=5250, flowInfo=0, scopeID=0))
Jun 18 15:29:42 u24maas maas-rackd[79738]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:192.168.204.16’, port=36116, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:192.168.204.16’, port=5250, flowInfo=0, scopeID=0))
Jun 18 15:30:02 u24maas maas-rackd[79738]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:192.168.204.16’, port=39998, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:192.168.204.16’, port=5250, flowInfo=0, scopeID=0))
Jun 18 15:30:02 u24maas maas-rackd[79738]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:192.168.204.16’, port=40012, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:192.168.204.16’, port=5250, flowInfo=0, scopeID=0))
Jun 18 15:30:02 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-http’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:30:02 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-dhcpd6’ is SERVICE_STATE.OFF and ‘dead’.
Jun 18 15:30:02 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-agent’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:30:02 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-dhcpd’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:30:02 u24maas maas-rackd[79738]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘u24maas:pid=79809’ authenticated.
Jun 18 15:30:03 u24maas maas-rackd[79738]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘u24maas:pid=79809’ authenticated.
Jun 18 15:30:03 u24maas maas-rackd[79738]: provisioningserver.rpc.power: [debug] Power state queried for node x3syca: on
Jun 18 15:30:03 u24maas maas-rackd[79738]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘k3sw77’ registered (via u24maas:pid=79809) with MAAS version 3.6.0-17541-g.561fe1a3e.
Jun 18 15:30:03 u24maas maas-rackd[79738]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘k3sw77’ registered (via u24maas:pid=79809) with MAAS version 3.6.0-17541-g.561fe1a3e.
Jun 18 15:30:12 u24maas maas-rackd[79738]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.10.204.16’, port=56698, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.10.204.16’, port=5251, flowInfo=0, scopeID=0))
Jun 18 15:30:12 u24maas maas-rackd[79738]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.10.204.16’, port=56712, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.10.204.16’, port=5251, flowInfo=0, scopeID=0))
Jun 18 15:30:12 u24maas maas-rackd[79738]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.10.204.16’, port=56728, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.10.204.16’, port=5251, flowInfo=0, scopeID=0))
Jun 18 15:30:12 u24maas maas-rackd[79738]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.10.204.16’, port=56742, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.10.204.16’, port=5251, flowInfo=0, scopeID=0))
Jun 18 15:30:32 u24maas maas-rackd[79738]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.10.204.16’, port=57468, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.10.204.16’, port=5251, flowInfo=0, scopeID=0))
Jun 18 15:30:32 u24maas maas-rackd[79738]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.10.204.16’, port=57470, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.10.204.16’, port=5251, flowInfo=0, scopeID=0))
Jun 18 15:30:32 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-http’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:30:32 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-agent’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:30:32 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-dhcpd’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:30:32 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-dhcpd6’ is SERVICE_STATE.OFF and ‘dead’.
Jun 18 15:30:32 u24maas maas-rackd[79738]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘u24maas:pid=79808’ authenticated.
Jun 18 15:30:33 u24maas maas-rackd[79738]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘u24maas:pid=79808’ authenticated.
Jun 18 15:30:33 u24maas maas-rackd[79738]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘k3sw77’ registered (via u24maas:pid=79808) with MAAS version 3.6.0-17541-g.561fe1a3e.
Jun 18 15:30:33 u24maas maas-rackd[79738]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘k3sw77’ registered (via u24maas:pid=79808) with MAAS version 3.6.0-17541-g.561fe1a3e.
Jun 18 15:31:02 u24maas maas-rackd[79738]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.10.204.16’, port=53868, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.10.204.16’, port=5251, flowInfo=0, scopeID=0))
Jun 18 15:31:02 u24maas maas-rackd[79738]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.10.204.16’, port=53878, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.10.204.16’, port=5251, flowInfo=0, scopeID=0))
Jun 18 15:31:02 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-http’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:31:02 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-dhcpd6’ is SERVICE_STATE.OFF and ‘dead’.
Jun 18 15:31:02 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-dhcpd’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:31:02 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-agent’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:31:02 u24maas maas-rackd[79738]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘u24maas:pid=79808’ authenticated.
Jun 18 15:31:03 u24maas maas-rackd[79738]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘u24maas:pid=79808’ authenticated.
Jun 18 15:31:03 u24maas maas-rackd[79738]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘k3sw77’ registered (via u24maas:pid=79808) with MAAS version 3.6.0-17541-g.561fe1a3e.
Jun 18 15:31:03 u24maas maas-rackd[79738]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘k3sw77’ registered (via u24maas:pid=79808) with MAAS version 3.6.0-17541-g.561fe1a3e.
Jun 18 15:31:12 u24maas maas-rackd[79738]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.10.204.16’, port=34080, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.10.204.16’, port=5253, flowInfo=0, scopeID=0))
Jun 18 15:31:12 u24maas maas-rackd[79738]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.10.204.16’, port=34090, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.10.204.16’, port=5253, flowInfo=0, scopeID=0))

Jun 18 15:31:32 u24maas maas-rackd[79738]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.10.204.16’, port=59470, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.10.204.16’, port=5253, flowInfo=0, scopeID=0))
Jun 18 15:31:32 u24maas maas-rackd[79738]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.10.204.16’, port=59472, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.10.204.16’, port=5253, flowInfo=0, scopeID=0))
Jun 18 15:31:32 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-http’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:31:32 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-dhcpd’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:31:32 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-agent’ is SERVICE_STATE.ON and ‘running’.
Jun 18 15:31:32 u24maas maas-rackd[79738]: provisioningserver.utils.service_monitor: [debug] Service ‘maas-dhcpd6’ is SERVICE_STATE.OFF and ‘dead’.
Jun 18 15:31:32 u24maas maas-rackd[79738]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘u24maas:pid=79811’ authenticated.
Jun 18 15:31:33 u24maas maas-rackd[79738]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘u24maas:pid=79811’ authenticated.
Jun 18 15:31:33 u24maas maas-rackd[79738]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘k3sw77’ registered (via u24maas:pid=79811) with MAAS version 3.6.0-17541-g.561fe1a3e.
Jun 18 15:31:33 u24maas maas-rackd[79738]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘k3sw77’ registered (via u24maas:pid=79811) with MAAS version 3.6.0-17541-g.561fe1a3e.

[END] 2025/6/18 15:31:36

r00ta · 18 June 2025 09:05

looks like it worked fine and the machine was able to boot, right?

lukexjin · 18 June 2025 09:46

The BIOS has many options, and different configuration combinations can lead to different outcomes. The latest error log is shown in the figure below.

lukexjin · 19 June 2025 01:18

already crazy for this issue

r00ta · 19 June 2025 07:06

Do you have secure boot enabled?