maas-agent 3.6.0 crashes if using external DHCP server

hoosainmadhi · 9 July 2025 09:13

I am using MAAS and managed to deploy three minipc’s. However I am now running into a tftp issue : “TFTP Error : FIle not found.” Because of this I cannot pxe boot any longer. I did not make any changes after deploying the three servers. Please help

r00ta · 9 July 2025 09:24

can you extract the rackd logs?

hoosainmadhi · 9 July 2025 10:04

ssh onex@172.17.10.240
onex@maas-minirack:~$ cat /tmp/1.txt
Jul 09 10:00:01 maas-minirack rackd[1177]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.15.1’, port=50446, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.15.1’, port=5252, flowInfo=0, scopeID=0))
Jul 09 10:00:01 maas-minirack rackd[1177]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.15.1’, port=50454, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.15.1’, port=5252, flowInfo=0, scopeID=0))
Jul 09 10:00:21 maas-minirack rackd[1177]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.15.1’, port=35878, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.15.1’, port=5252, flowInfo=0, scopeID=0))
Jul 09 10:00:21 maas-minirack rackd[1177]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.15.1’, port=35888, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.15.1’, port=5252, flowInfo=0, scopeID=0))
Jul 09 10:00:21 maas-minirack sudo[16554]: maas : PWD=/ ; USER=root ; COMMAND=/bin/systemctl status maas-http
Jul 09 10:00:21 maas-minirack sudo[16555]: maas : PWD=/ ; USER=root ; COMMAND=/bin/systemctl status maas-dhcpd
Jul 09 10:00:21 maas-minirack sudo[16555]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:00:21 maas-minirack sudo[16554]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:00:21 maas-minirack sudo[16557]: maas : PWD=/ ; USER=root ; COMMAND=/bin/systemctl status maas-agent
Jul 09 10:00:21 maas-minirack sudo[16557]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:00:21 maas-minirack sudo[16556]: maas : PWD=/ ; USER=root ; COMMAND=/bin/systemctl status maas-dhcpd6
Jul 09 10:00:21 maas-minirack sudo[16556]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:00:21 maas-minirack sudo[16554]: pam_unix(sudo:session): session closed for user root
Jul 09 10:00:21 maas-minirack rackd[1177]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘maas-minirack:pid=1436’ authenticated.
Jul 09 10:00:21 maas-minirack sudo[16555]: pam_unix(sudo:session): session closed for user root
Jul 09 10:00:21 maas-minirack sudo[16557]: pam_unix(sudo:session): session closed for user root
Jul 09 10:00:21 maas-minirack sudo[16556]: pam_unix(sudo:session): session closed for user root
Jul 09 10:00:21 maas-minirack sudo[16563]: maas : PWD=/ ; USER=root ; COMMAND=/usr/share/maas/machine-resources/amd64
Jul 09 10:00:21 maas-minirack sudo[16563]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:00:21 maas-minirack sudo[16570]: maas : PWD=/ ; USER=root ; COMMAND=/usr/share/maas/machine-resources/amd64
Jul 09 10:00:21 maas-minirack sudo[16570]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:00:22 maas-minirack sudo[16563]: pam_unix(sudo:session): session closed for user root
Jul 09 10:00:22 maas-minirack sudo[16570]: pam_unix(sudo:session): session closed for user root
Jul 09 10:00:22 maas-minirack rackd[1177]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘maas-minirack:pid=1436’ authenticated.
Jul 09 10:00:22 maas-minirack sudo[16584]: maas : PWD=/ ; USER=root ; COMMAND=/usr/share/maas/machine-resources/amd64
Jul 09 10:00:22 maas-minirack sudo[16584]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:00:22 maas-minirack sudo[16584]: pam_unix(sudo:session): session closed for user root
Jul 09 10:00:22 maas-minirack rackd[1177]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘tekdkx’ registered (via maas-minirack:pid=1436) with MAAS version 3.6.0-17541-g.561fe1a3ec.
Jul 09 10:00:22 maas-minirack rackd[1177]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘tekdkx’ registered (via maas-minirack:pid=1436) with MAAS version 3.6.0-17541-g.561fe1a3ec.
Jul 09 10:00:23 maas-minirack rackd[1177]: provisioningserver.utils.services: [info] Beaconing process for ens34 started.
Jul 09 10:00:25 maas-minirack sudo[16598]: maas : PWD=/ ; USER=root ; COMMAND=/usr/lib/maas/beacon-monitor ens34
Jul 09 10:00:25 maas-minirack sudo[16598]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:00:25 maas-minirack sudo[16598]: pam_unix(sudo:session): session closed for user root
Jul 09 10:00:26 maas-minirack rackd[1177]: provisioningserver.utils.services: [critical] Beaconing process for ens34 failed.
Jul 09 10:00:26 maas-minirack rackd[1177]: Traceback (most recent call last):
Jul 09 10:00:26 maas-minirack rackd[1177]: Failure: twisted.internet.error.ProcessTerminated: A process has ended with a probable error condition: process ended with exit code 3.
Jul 09 10:00:26 maas-minirack rackd[1177]:
Jul 09 10:00:31 maas-minirack rackd[1177]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.15.1’, port=39466, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.15.1’, port=5251, flowInfo=0, scopeID=0))
Jul 09 10:00:31 maas-minirack rackd[1177]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.15.1’, port=39482, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.15.1’, port=5251, flowInfo=0, scopeID=0))
Jul 09 10:00:51 maas-minirack sudo[16670]: maas : PWD=/ ; USER=root ; COMMAND=/bin/systemctl status maas-http
Jul 09 10:00:51 maas-minirack sudo[16670]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:00:51 maas-minirack sudo[16671]: maas : PWD=/ ; USER=root ; COMMAND=/bin/systemctl status maas-dhcpd
Jul 09 10:00:51 maas-minirack sudo[16671]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:00:51 maas-minirack sudo[16672]: maas : PWD=/ ; USER=root ; COMMAND=/bin/systemctl status maas-dhcpd6
Jul 09 10:00:51 maas-minirack sudo[16672]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:00:51 maas-minirack sudo[16673]: maas : PWD=/ ; USER=root ; COMMAND=/bin/systemctl status maas-agent
Jul 09 10:00:51 maas-minirack sudo[16673]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:00:51 maas-minirack sudo[16671]: pam_unix(sudo:session): session closed for user root
Jul 09 10:00:51 maas-minirack sudo[16672]: pam_unix(sudo:session): session closed for user root
Jul 09 10:00:51 maas-minirack sudo[16670]: pam_unix(sudo:session): session closed for user root
Jul 09 10:00:51 maas-minirack sudo[16673]: pam_unix(sudo:session): session closed for user root
Jul 09 10:00:51 maas-minirack sudo[16679]: maas : PWD=/ ; USER=root ; COMMAND=/usr/share/maas/machine-resources/amd64
Jul 09 10:00:51 maas-minirack sudo[16679]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:00:51 maas-minirack sudo[16680]: maas : PWD=/ ; USER=root ; COMMAND=/bin/systemctl start maas-agent
Jul 09 10:00:51 maas-minirack sudo[16680]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:00:51 maas-minirack sudo[16680]: pam_unix(sudo:session): session closed for user root
Jul 09 10:00:51 maas-minirack sudo[16688]: maas : PWD=/ ; USER=root ; COMMAND=/bin/systemctl status maas-agent
Jul 09 10:00:51 maas-minirack sudo[16688]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:00:51 maas-minirack sudo[16688]: pam_unix(sudo:session): session closed for user root
Jul 09 10:00:52 maas-minirack sudo[16679]: pam_unix(sudo:session): session closed for user root
Jul 09 10:01:02 maas-minirack rackd[1177]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.15.1’, port=48910, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.15.1’, port=5251, flowInfo=0, scopeID=0))
Jul 09 10:01:02 maas-minirack rackd[1177]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.15.1’, port=48918, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.15.1’, port=5251, flowInfo=0, scopeID=0))
Jul 09 10:01:02 maas-minirack rackd[1177]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.15.1’, port=48930, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.15.1’, port=5251, flowInfo=0, scopeID=0))
Jul 09 10:01:02 maas-minirack rackd[1177]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.15.1’, port=48938, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.15.1’, port=5251, flowInfo=0, scopeID=0))
Jul 09 10:01:21 maas-minirack rackd[1177]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.15.1’, port=60552, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.15.1’, port=5251, flowInfo=0, scopeID=0))
Jul 09 10:01:21 maas-minirack sudo[16706]: maas : PWD=/ ; USER=root ; COMMAND=/bin/systemctl status maas-http
Jul 09 10:01:21 maas-minirack sudo[16707]: maas : PWD=/ ; USER=root ; COMMAND=/bin/systemctl status maas-dhcpd
Jul 09 10:01:21 maas-minirack sudo[16706]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:01:21 maas-minirack sudo[16707]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:01:21 maas-minirack rackd[1177]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.15.1’, port=60558, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.15.1’, port=5251, flowInfo=0, scopeID=0))
Jul 09 10:01:21 maas-minirack sudo[16709]: maas : PWD=/ ; USER=root ; COMMAND=/bin/systemctl status maas-agent
Jul 09 10:01:21 maas-minirack sudo[16709]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:01:21 maas-minirack rackd[1177]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘maas-minirack:pid=1430’ authenticated.
Jul 09 10:01:21 maas-minirack sudo[16707]: pam_unix(sudo:session): session closed for user root
Jul 09 10:01:21 maas-minirack sudo[16706]: pam_unix(sudo:session): session closed for user root
Jul 09 10:01:21 maas-minirack sudo[16708]: maas : PWD=/ ; USER=root ; COMMAND=/bin/systemctl status maas-dhcpd6
Jul 09 10:01:21 maas-minirack sudo[16708]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:01:21 maas-minirack sudo[16709]: pam_unix(sudo:session): session closed for user root
Jul 09 10:01:21 maas-minirack sudo[16708]: pam_unix(sudo:session): session closed for user root
Jul 09 10:01:21 maas-minirack sudo[16715]: maas : PWD=/ ; USER=root ; COMMAND=/usr/share/maas/machine-resources/amd64
Jul 09 10:01:21 maas-minirack sudo[16715]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:01:21 maas-minirack sudo[16717]: maas : PWD=/ ; USER=root ; COMMAND=/usr/share/maas/machine-resources/amd64
Jul 09 10:01:21 maas-minirack sudo[16717]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:01:22 maas-minirack sudo[16715]: pam_unix(sudo:session): session closed for user root
Jul 09 10:01:22 maas-minirack sudo[16717]: pam_unix(sudo:session): session closed for user root
Jul 09 10:01:22 maas-minirack rackd[1177]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘maas-minirack:pid=1430’ authenticated.
Jul 09 10:01:22 maas-minirack sudo[16743]: maas : PWD=/ ; USER=root ; COMMAND=/usr/share/maas/machine-resources/amd64
Jul 09 10:01:22 maas-minirack sudo[16743]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:01:22 maas-minirack sudo[16743]: pam_unix(sudo:session): session closed for user root
Jul 09 10:01:22 maas-minirack rackd[1177]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘tekdkx’ registered (via maas-minirack:pid=1430) with MAAS version 3.6.0-17541-g.561fe1a3ec.
Jul 09 10:01:23 maas-minirack rackd[1177]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘tekdkx’ registered (via maas-minirack:pid=1430) with MAAS version 3.6.0-17541-g.561fe1a3ec.
Jul 09 10:01:23 maas-minirack rackd[1177]: provisioningserver.utils.services: [info] Beaconing process for ens34 started.
Jul 09 10:01:26 maas-minirack sudo[16773]: maas : PWD=/ ; USER=root ; COMMAND=/usr/lib/maas/beacon-monitor ens34
Jul 09 10:01:26 maas-minirack sudo[16773]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:01:26 maas-minirack sudo[16773]: pam_unix(sudo:session): session closed for user root
Jul 09 10:01:31 maas-minirack rackd[1177]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.10.240’, port=55688, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.10.240’, port=5253, flowInfo=0, scopeID=0))
Jul 09 10:01:31 maas-minirack rackd[1177]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.10.240’, port=55694, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.10.240’, port=5253, flowInfo=0, scopeID=0))
Jul 09 10:01:51 maas-minirack rackd[1177]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.15.1’, port=55070, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.15.1’, port=5251, flowInfo=0, scopeID=0))
Jul 09 10:01:51 maas-minirack sudo[16893]: maas : PWD=/ ; USER=root ; COMMAND=/bin/systemctl status maas-http
Jul 09 10:01:51 maas-minirack sudo[16893]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:01:51 maas-minirack rackd[1177]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.15.1’, port=55072, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.15.1’, port=5251, flowInfo=0, scopeID=0))
Jul 09 10:01:51 maas-minirack sudo[16894]: maas : PWD=/ ; USER=root ; COMMAND=/bin/systemctl status maas-dhcpd
Jul 09 10:01:51 maas-minirack sudo[16894]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:01:51 maas-minirack sudo[16895]: maas : PWD=/ ; USER=root ; COMMAND=/bin/systemctl status maas-dhcpd6
Jul 09 10:01:51 maas-minirack sudo[16895]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:01:51 maas-minirack sudo[16893]: pam_unix(sudo:session): session closed for user root
Jul 09 10:01:51 maas-minirack sudo[16896]: maas : PWD=/ ; USER=root ; COMMAND=/bin/systemctl status maas-agent
Jul 09 10:01:51 maas-minirack sudo[16894]: pam_unix(sudo:session): session closed for user root
Jul 09 10:01:51 maas-minirack sudo[16896]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:01:51 maas-minirack rackd[1177]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘maas-minirack:pid=1430’ authenticated.
Jul 09 10:01:51 maas-minirack sudo[16895]: pam_unix(sudo:session): session closed for user root
Jul 09 10:01:51 maas-minirack sudo[16896]: pam_unix(sudo:session): session closed for user root
Jul 09 10:01:51 maas-minirack sudo[16902]: maas : PWD=/ ; USER=root ; COMMAND=/usr/share/maas/machine-resources/amd64
Jul 09 10:01:51 maas-minirack sudo[16902]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:01:51 maas-minirack sudo[16910]: maas : PWD=/ ; USER=root ; COMMAND=/usr/share/maas/machine-resources/amd64
Jul 09 10:01:51 maas-minirack sudo[16910]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:01:52 maas-minirack sudo[16902]: pam_unix(sudo:session): session closed for user root
Jul 09 10:01:52 maas-minirack sudo[16910]: pam_unix(sudo:session): session closed for user root
Jul 09 10:01:52 maas-minirack rackd[1177]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘maas-minirack:pid=1430’ authenticated.
Jul 09 10:01:52 maas-minirack sudo[16922]: maas : PWD=/ ; USER=root ; COMMAND=/usr/share/maas/machine-resources/amd64
Jul 09 10:01:52 maas-minirack sudo[16922]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:01:52 maas-minirack sudo[16922]: pam_unix(sudo:session): session closed for user root
Jul 09 10:01:52 maas-minirack sudo[16931]: maas : PWD=/ ; USER=root ; COMMAND=/bin/systemctl start maas-agent
Jul 09 10:01:52 maas-minirack sudo[16931]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:01:52 maas-minirack sudo[16931]: pam_unix(sudo:session): session closed for user root
Jul 09 10:01:52 maas-minirack sudo[16935]: maas : PWD=/ ; USER=root ; COMMAND=/bin/systemctl status maas-agent
Jul 09 10:01:52 maas-minirack sudo[16935]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:01:52 maas-minirack sudo[16935]: pam_unix(sudo:session): session closed for user root
Jul 09 10:01:52 maas-minirack rackd[1177]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘tekdkx’ registered (via maas-minirack:pid=1430) with MAAS version 3.6.0-17541-g.561fe1a3ec.
Jul 09 10:01:52 maas-minirack rackd[1177]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘tekdkx’ registered (via maas-minirack:pid=1430) with MAAS version 3.6.0-17541-g.561fe1a3ec.
Jul 09 10:02:01 maas-minirack rackd[1177]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.10.240’, port=59282, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.10.240’, port=5253, flowInfo=0, scopeID=0))
Jul 09 10:02:01 maas-minirack rackd[1177]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.10.240’, port=59286, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.10.240’, port=5253, flowInfo=0, scopeID=0))
Jul 09 10:02:11 maas-minirack rackd[1177]: provisioningserver.rackdservices.tftp: [info] lpxelinux.0 requested by 172.17.15.196
Jul 09 10:02:11 maas-minirack rackd[1177]: provisioningserver.rackdservices.http: [info] /images/lpxelinux.0 requested by 127.0.0.1
Jul 09 10:02:11 maas-minirack rackd[1177]: provisioningserver.rackdservices.tftp: [info] lpxelinux.0 requested by 172.17.15.196
Jul 09 10:02:12 maas-minirack rackd[1177]: provisioningserver.rackdservices.http: [info] /images/lpxelinux.0 requested by 127.0.0.1
Jul 09 10:02:21 maas-minirack rackd[1177]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.10.240’, port=47124, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.10.240’, port=5253, flowInfo=0, scopeID=0))
Jul 09 10:02:21 maas-minirack sudo[16966]: maas : PWD=/ ; USER=root ; COMMAND=/bin/systemctl status maas-http
Jul 09 10:02:21 maas-minirack sudo[16967]: maas : PWD=/ ; USER=root ; COMMAND=/bin/systemctl status maas-dhcpd
Jul 09 10:02:21 maas-minirack sudo[16967]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:02:21 maas-minirack sudo[16966]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:02:21 maas-minirack rackd[1177]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.10.240’, port=47130, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.10.240’, port=5253, flowInfo=0, scopeID=0))
Jul 09 10:02:21 maas-minirack sudo[16968]: maas : PWD=/ ; USER=root ; COMMAND=/bin/systemctl status maas-dhcpd6
Jul 09 10:02:21 maas-minirack sudo[16969]: maas : PWD=/ ; USER=root ; COMMAND=/bin/systemctl status maas-agent
Jul 09 10:02:21 maas-minirack sudo[16968]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:02:21 maas-minirack sudo[16969]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:02:21 maas-minirack sudo[16967]: pam_unix(sudo:session): session closed for user root
Jul 09 10:02:21 maas-minirack sudo[16966]: pam_unix(sudo:session): session closed for user root
Jul 09 10:02:21 maas-minirack rackd[1177]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘maas-minirack:pid=1434’ authenticated.
Jul 09 10:02:21 maas-minirack sudo[16969]: pam_unix(sudo:session): session closed for user root
Jul 09 10:02:21 maas-minirack sudo[16968]: pam_unix(sudo:session): session closed for user root
Jul 09 10:02:21 maas-minirack sudo[16975]: maas : PWD=/ ; USER=root ; COMMAND=/usr/share/maas/machine-resources/amd64
Jul 09 10:02:21 maas-minirack sudo[16975]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:02:21 maas-minirack sudo[16982]: maas : PWD=/ ; USER=root ; COMMAND=/usr/share/maas/machine-resources/amd64
Jul 09 10:02:21 maas-minirack sudo[16982]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:02:22 maas-minirack sudo[16975]: pam_unix(sudo:session): session closed for user root
Jul 09 10:02:22 maas-minirack sudo[16982]: pam_unix(sudo:session): session closed for user root
Jul 09 10:02:22 maas-minirack rackd[1177]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘maas-minirack:pid=1434’ authenticated.
Jul 09 10:02:22 maas-minirack sudo[16995]: maas : PWD=/ ; USER=root ; COMMAND=/usr/share/maas/machine-resources/amd64
Jul 09 10:02:22 maas-minirack sudo[16995]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:02:22 maas-minirack sudo[16995]: pam_unix(sudo:session): session closed for user root
Jul 09 10:02:22 maas-minirack rackd[1177]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘tekdkx’ registered (via maas-minirack:pid=1434) with MAAS version 3.6.0-17541-g.561fe1a3ec.
Jul 09 10:02:22 maas-minirack rackd[1177]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘tekdkx’ registered (via maas-minirack:pid=1434) with MAAS version 3.6.0-17541-g.561fe1a3ec.
Jul 09 10:02:51 maas-minirack rackd[1177]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.10.240’, port=57414, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:172.17.10.240’, port=5253, flowInfo=0, scopeID=0))
Jul 09 10:02:51 maas-minirack rackd[1177]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘maas-minirack:pid=1434’ authenticated.
Jul 09 10:02:51 maas-minirack sudo[17071]: maas : PWD=/ ; USER=root ; COMMAND=/usr/share/maas/machine-resources/amd64
Jul 09 10:02:51 maas-minirack sudo[17071]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:02:51 maas-minirack sudo[17073]: maas : PWD=/ ; USER=root ; COMMAND=/usr/share/maas/machine-resources/amd64
Jul 09 10:02:51 maas-minirack sudo[17073]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:02:52 maas-minirack sudo[17071]: pam_unix(sudo:session): session closed for user root
Jul 09 10:02:52 maas-minirack sudo[17073]: pam_unix(sudo:session): session closed for user root
Jul 09 10:02:52 maas-minirack rackd[1177]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘tekdkx’ registered (via maas-minirack:pid=1434) with MAAS version 3.6.0-17541-g.561fe1a3ec.
Jul 09 10:03:21 maas-minirack sudo[17114]: maas : PWD=/ ; USER=root ; COMMAND=/usr/share/maas/machine-resources/amd64
Jul 09 10:03:21 maas-minirack sudo[17114]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=111)
Jul 09 10:03:22 maas-minirack sudo[17114]: pam_unix(sudo:session): session closed for user root
onex@maas-minirack:~$

r00ta · 9 July 2025 10:19

ls /var/lib/maas/image-storage/bootloaders/pxe/i386?

hoosainmadhi · 9 July 2025 10:30

ls /var/lib/maas/image-storage/bootloaders/pxe/i386/
cat.c32 cptime.c32 dhcp.c32 elf.c32 hexdump.c32 ifplop.c32 libcom32.c32 linux.c32 meminfo.c32 poweroff.c32 reboot.c32 syslinux.c32 whichsys.c32
chain.c32 cpu.c32 dir.c32 ethersel.c32 host.c32 kbdmap.c32 libgpl.c32 lpxelinux.0 menu.c32 prdhcp.c32 rosh.c32 vesa.c32 zzjson.c32
cmd.c32 cpuid.c32 disk.c32 gfxboot.c32 ifcpu64.c32 kontron_wdt.c32 liblua.c32 ls.c32 pci.c32 pwd.c32 sanboot.c32 vesainfo.c32
cmenu.c32 cpuidtest.c32 dmi.c32 gpxecmd.c32 ifcpu.c32 ldlinux.c32 libmenu.c32 lua.c32 pcitest.c32 pxechn.c32 sdi.c32 vesamenu.c32
config.c32 debug.c32 dmitest.c32 hdt.c32 ifmemdsk.c32 lfs.c32 libutil.c32 mboot.c32 pmload.c32 pxelinux.0 sysdump.c32 vpdtest.c32

r00ta · 9 July 2025 10:35

can you curl -O http://localhost:5248/lpxelinux.0 -v?

hoosainmadhi · 9 July 2025 10:44

curl -O http://localhost:5248/lpxelinux.0 -v

Host localhost:5248 was resolved.
IPv6: ::1
IPv4: 127.0.0.1
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0* Trying [::1]:5248…
Connected to localhost (::1) port 5248

GET /lpxelinux.0 HTTP/1.1
Host: localhost:5248
User-Agent: curl/8.5.0
Accept: /

< HTTP/1.1 404 Not Found
< Server: nginx/1.24.0 (Ubuntu)
< Date: Wed, 09 Jul 2025 10:44:06 GMT
< Content-Type: text/html
< Transfer-Encoding: chunked
< Connection: keep-alive
<
0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0

Connection #0 to host localhost left intact

r00ta · 9 July 2025 10:48

MAAS version? Are you using a proxy?

hoosainmadhi · 9 July 2025 10:57

3.6 - apt install
no proxy

r00ta · 9 July 2025 11:13

mind trying to boot the machine again and after you see the failure on the console you extract journalctl --since “20 minutes ago” --no-pager and you upload it somewhere?

hoosainmadhi · 9 July 2025 11:56

https://jumpshare.com/s/hU8oxrObJ6c8Z7yhyWNK

r00ta · 9 July 2025 12:09

sudo systemctl status maas-* --no-pager?

hoosainmadhi · 9 July 2025 12:15

https://jumpshare.com/s/SQrumIa0Hh47KO59U5Ck

r00ta · 9 July 2025 12:30

The problem is

× maas-agent.service - MAAS Agent daemon
     Loaded: loaded (/usr/lib/systemd/system/maas-agent.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Wed 2025-07-09 12:13:15 UTC; 19s ago
   Duration: 31.619s
       Docs: https://maas.io/docs
    Process: 6454 ExecStart=/usr/sbin/maas-agent (code=exited, status=1/FAILURE)
   Main PID: 6454 (code=exited, status=1/FAILURE)
        CPU: 208ms

Jul 09 12:12:43 maas-minirack systemd[1]: Started maas-agent.service - MAAS Agent daemon.
Jul 09 12:12:43 maas-minirack maas-agent[6454]: INF Logger is configured with log level "info"
Jul 09 12:12:43 maas-minirack maas-agent[6454]: INF Started Worker Namespace=default TaskQueue=tekdkx@agent:main WorkerID=tekdkx@agent:6454
Jul 09 12:12:44 maas-minirack maas-agent[6454]: INF Configuring power-service Attempt=1 Namespace=default RunID=c0bdcec9-6c7c-44d2-bcdf-b670ddcf4d0c SpanID=0000000000000000 TaskQu…
Jul 09 12:13:15 maas-minirack maas-agent[6454]: ERR Workflow configure-agent failed error="workflow execution error (type: configure-agent, workflowID: configure-agent:tekdkx, run…
Jul 09 12:13:15 maas-minirack systemd[1]: maas-agent.service: Main process exited, code=exited, status=1/FAILURE
Jul 09 12:13:15 maas-minirack systemd[1]: maas-agent.service: Failed with result 'exit-code'.

Was it working when you installed MAAS? Or is this a new installation? If it was working, did you change anything before it broke up?

hoosainmadhi · 9 July 2025 12:35

I did a fresh install of MAAS yesterday. Everything worked fine. Commissioned and deployed 3 minipcs. Today I have this issue. Did not make any changes.

r00ta · 9 July 2025 12:36

journalctl -t maas-agent --no-pager?

hoosainmadhi · 9 July 2025 12:46

https://jumpshare.com/v/sp5h347Ve2nDCJ2YsYBA

r00ta · 9 July 2025 12:48

oh ok you are hitting https://bugs.launchpad.net/maas/+bug/2110023 . You can use 3.5 for now or use snap 3.6/edge.

3.6.1 will be released in the next weeks

hoosainmadhi · 9 July 2025 12:50

ok - do I need to reinstall? what about the existing deployed minipcs. will I have to redo it?

r00ta · 9 July 2025 12:51

If you switch to snaps, you can keep the existing database and you don’t have to redo it.

If you switch to 3.5 because you want to use debs, then you have to redo it because we don’t support downgrade.