missing /var/lib/maas/dhcpd.sock in Maas 3.6 on Ubuntu 24.04.2

Discourse
1

Hi,
I am new to Maas and I’m trying to get a small setup working. I have installed Maas 3.6 on Ubuntu 24.04.2. The system is up to date. I have activated DHCP and when booting a node (UEFI), an IP is assigned to the node. However, a message is shown: “MBP filesize is 0 Bytes”.

In /var/lib/maas/dhcpd.sock the following error is reported:

2025-06-20T14:23:37.536033+00:00 maas regiond[8558]: maasserver.ipc: [info] Worker pid:8798 registered RPC connection to ('gsfd6f', '192.168.178.120', 5252).
2025-06-20T14:23:39.619367+00:00 maas dhcpd[12453]: DHCPDISCOVER from ac:1f:6b:e7:cd:90 via eno1
2025-06-20T14:23:40.620489+00:00 maas dhcpd[12453]: DHCPOFFER on 192.168.183.220 to ac:1f:6b:e7:cd:90 via eno1
2025-06-20T14:23:43.443540+00:00 maas dhcpd[12453]: execute_statement argv[0] = /usr/sbin/maas-dhcp-helper
2025-06-20T14:23:43.443712+00:00 maas dhcpd[12453]: execute_statement argv[1] = notify
2025-06-20T14:23:43.443812+00:00 maas dhcpd[12453]: execute_statement argv[2] = --action
2025-06-20T14:23:43.443917+00:00 maas dhcpd[12453]: execute_statement argv[3] = commit
2025-06-20T14:23:43.444035+00:00 maas dhcpd[12453]: execute_statement argv[4] = --mac
2025-06-20T14:23:43.444120+00:00 maas dhcpd[12453]: execute_statement argv[5] = ac:1f:6b:e7:cd:90
2025-06-20T14:23:43.444256+00:00 maas dhcpd[12453]: execute_statement argv[6] = --ip-family
2025-06-20T14:23:43.444377+00:00 maas dhcpd[12453]: execute_statement argv[7] = ipv4
2025-06-20T14:23:43.444449+00:00 maas dhcpd[12453]: execute_statement argv[8] = --ip
2025-06-20T14:23:43.444566+00:00 maas dhcpd[12453]: execute_statement argv[9] = 192.168.183.220
2025-06-20T14:23:43.444663+00:00 maas dhcpd[12453]: execute_statement argv[10] = --lease-time
2025-06-20T14:23:43.444814+00:00 maas dhcpd[12453]: execute_statement argv[11] = 30
2025-06-20T14:23:43.444938+00:00 maas dhcpd[12453]: execute_statement argv[12] = --hostname
2025-06-20T14:23:43.445024+00:00 maas dhcpd[12453]: execute_statement argv[13] = (none)
2025-06-20T14:23:43.445128+00:00 maas dhcpd[12453]: execute_statement argv[14] = --socket
2025-06-20T14:23:43.445251+00:00 maas dhcpd[12453]: execute_statement argv[15] = /var/lib/maas/dhcpd.sock
2025-06-20T14:23:45.016334+00:00 maas sh[12594]: Traceback (most recent call last):
2025-06-20T14:23:45.016468+00:00 maas sh[12594]:   File "/usr/sbin/maas-dhcp-helper", line 157, in <module>
2025-06-20T14:23:45.016552+00:00 maas sh[12594]:     main()
2025-06-20T14:23:45.016597+00:00 maas sh[12594]:   File "/usr/sbin/maas-dhcp-helper", line 153, in main
2025-06-20T14:23:45.016636+00:00 maas sh[12594]:     args.handler(args)
2025-06-20T14:23:45.016676+00:00 maas sh[12594]:   File "/usr/sbin/maas-dhcp-helper", line 100, in notify
2025-06-20T14:23:45.016716+00:00 maas sh[12594]:     conn.connect(args.socket)
2025-06-20T14:23:45.016756+00:00 maas sh[12594]: FileNotFoundError: [Errno 2] No such file or directory
2025-06-20T14:23:45.045614+00:00 maas dhcpd[12453]: execute: /usr/sbin/maas-dhcp-helper exit status 256

There is no /var/lib/maas/dhcpd.sock. Could that be the cause of the problem?

2

Please ensure that all the images are properly in sync (check it from the UI)

3

There is only one image (amd64) that is “Synced”.

4

Could you check the rackd logs? Also, are you using a proxy?

5

/var/log/maas/rackd.log is 0 bytes
No, I’m not using a proxy.

There are two zombie processes “maas-common”. Could that be related to the problem?

6

Use journalctl -t rackd and journalctl -t maas-agent

7

Also, is MAAS the only DHCP on the network? Do you have also a router providing DHCP?

8

It turns out that there was a wrong IP in these two files:
/etc/maas/rackd.conf
/etc/maas/regiond.conf

With the correct IP, the problem is gone.

9

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