provisioningserver.utils.services: [critical] Beaconing process for failed

Hi All, I’m facing an issue where the “Beaconing process” consistently fails across all available interfaces. Additionally, I’m having trouble deploying the machine with 22.04, as it fails with a “datasource not found” error. I’m uncertain if this is related to the Beaconing process. Any input would be appreciated.

root@director:~# snap list maas
Name Version Rev Tracking Publisher Notes
maas 3.6.0-17541-g.561fe1a3e 39328 3.6/stable canonical✓ -
root@director:~# lsb_release -a
Distributor ID: Ubuntu
Description: Ubuntu 22.04.5 LTS
Release: 22.04
Codename: jammy

Logs:

Apr 26 22:56:44 director maas-regiond[1982]: maasserver.rpc.regionservice: [info] Connection baad2390-9617-43fd-b55d-87a0ebb68fd2 is trusted and ready to respond/serve commands.

Apr 26 22:56:44 director kernel: [ 1269.894871] audit: type=1400 audit(1745708204.747:539): apparmor=“DENIED” operation=“open” profile=“snap.maas.pebble” name=“/etc/gss/mech.d/” pid=1982 comm=“python3” requested_mask=“r” denied_mask=“r” fsuid=0 ouid=0

Apr 26 22:56:44 director maas-regiond[1982]: maasserver.rpc.regionservice: [info] Rack controller authenticated from ‘::ffff:192.168.122.1:56800’.

Apr 26 22:56:44 director maas-regiond[1982]: maasserver.rpc.regionservice: [info] Connection 8b80fd61-e723-44fd-a945-af5737967104 is trusted and ready to respond/serve commands.

Apr 26 22:56:44 director maas-regiond[1982]: maasserver.rpc.regionservice: [info] Rack controller authenticated from ‘::ffff:192.168.122.1:56808’.

Apr 26 22:56:44 director maas-regiond[1982]: maasserver.rpc.regionservice: [info] Connection d2c86623-0ee1-4604-830a-b2d776cb1a89 is trusted and ready to respond/serve commands.

Apr 26 22:56:44 director maas-rackd[1807]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘director:pid=1982’ authenticated.

Apr 26 22:56:45 director maas-rackd[1807]: message repeated 3 times: [ provisioningserver.rpc.clusterservice: [info] Event-loop ‘director:pid=1982’ authenticated.]

Apr 26 22:56:45 director maas-rackd[1807]: provisioningserver.rackdservices.dhcp_probe_service: [info] Probe for external DHCP servers started on interfaces: enp1s0f0, enp1s0f1, virbr0.

Apr 26 22:56:45 director maas-log[2288]: maas.rpc.rackcontrollers: [info] Existing rack controller ‘director’ running version 3.6.0-17541-g.561fe1a3e has connected to region ‘director’.

Apr 26 22:56:45 director maas-regiond[1753]: maasserver.ipc: [info] Worker pid:1982 registered RPC connection to (‘4anw43’, ‘192.168.122.1’, 5250).

Apr 26 22:56:45 director maas-rackd[1807]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘4anw43’ registered (via director:pid=1982) with MAAS version 3.6.0-17541-g.561fe1a3e.

Apr 26 22:56:45 director maas-regiond[1753]: maasserver.ipc: [info] Worker pid:1982 registered RPC connection to (‘4anw43’, ‘192.168.122.1’, 5250).

Apr 26 22:56:45 director maas-rackd[1807]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘4anw43’ registered (via director:pid=1982) with MAAS version 3.6.0-17541-g.561fe1a3e.

Apr 26 22:56:45 director maas-regiond[1753]: maasserver.ipc: [info] Worker pid:1982 registered RPC connection to (‘4anw43’, ‘192.168.122.1’, 5250).

Apr 26 22:56:45 director maas-rackd[1807]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘4anw43’ registered (via director:pid=1982) with MAAS version 3.6.0-17541-g.561fe1a3e.

Apr 26 22:56:46 director maas-regiond[1753]: maasserver.ipc: [info] Worker pid:1982 registered RPC connection to (‘4anw43’, ‘192.168.122.1’, 5250).

Apr 26 22:56:46 director maas-rackd[1807]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘4anw43’ registered (via director:pid=1982) with MAAS version 3.6.0-17541-g.561fe1a3e.

Apr 26 22:56:46 director maas-rackd[1807]: provisioningserver.utils.services: [info] Beaconing process for virbr0 started.

Apr 26 22:56:46 director maas-rackd[1807]: provisioningserver.utils.services: [info] Beaconing process for enp1s0f1 started.

Apr 26 22:56:46 director maas-rackd[1807]: provisioningserver.utils.services: [info] Beaconing process for enp1s0f0 started.

Apr 26 22:56:47 director kernel: [ 1272.385655] tcpdump[5402]: segfault at 0 ip 00007fa8addf220d sp 00007fff2577f880 error 4 in libc.so.6[7fa8adcb0000+188000]

Apr 26 22:56:47 director kernel: [ 1272.385670] Code: 00 0f 85 a0 00 00 00 48 83 c4 38 89 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 1f 44 00 00 48 8b 05 f1 8b 09 00 8b 4d ac 64 89 08 <41> 0f b6 07 83 e8 2b a8 fd 0f 84 54 ff ff ff 49 8b 36 4c 89 ff e8

Apr 26 22:56:47 director kernel: [ 1272.389369] tcpdump[5403]: segfault at 0 ip 00007f8e75e1620d sp 00007fff481c1ff0 error 4 in libc.so.6[7f8e75cd4000+188000]

Apr 26 22:56:47 director kernel: [ 1272.389380] Code: 00 0f 85 a0 00 00 00 48 83 c4 38 89 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 1f 44 00 00 48 8b 05 f1 8b 09 00 8b 4d ac 64 89 08 <41> 0f b6 07 83 e8 2b a8 fd 0f 84 54 ff ff ff 49 8b 36 4c 89 ff e8

Apr 26 22:56:47 director kernel: [ 1272.401314] tcpdump[5401]: segfault at 0 ip 00007f73de2d020d sp 00007ffe61aeebb0 error 4 in libc.so.6[7f73de18e000+188000]

Apr 26 22:56:47 director kernel: [ 1272.401323] Code: 00 0f 85 a0 00 00 00 48 83 c4 38 89 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 1f 44 00 00 48 8b 05 f1 8b 09 00 8b 4d ac 64 89 08 <41> 0f b6 07 83 e8 2b a8 fd 0f 84 54 ff ff ff 49 8b 36 4c 89 ff e8

Apr 26 22:56:47 director maas-rackd[1807]: provisioningserver.utils.services: [critical] Beaconing process for enp1s0f1 failed.

Apr 26 22:56:47 director maas-rackd[1807]: #011Traceback (most recent call last):

Apr 26 22:56:47 director maas-rackd[1807]: #011Failure: twisted.internet.error.ProcessTerminated: A process has ended with a probable error condition: process ended with exit code 3.

Apr 26 22:56:47 director maas-rackd[1807]: #011

Apr 26 22:56:47 director maas-rackd[1807]: provisioningserver.utils.services: [critical] Beaconing process for virbr0 failed.

Apr 26 22:56:47 director maas-rackd[1807]: #011Traceback (most recent call last):

Apr 26 22:56:47 director maas-rackd[1807]: #011Failure: twisted.internet.error.ProcessTerminated: A process has ended with a probable error condition: process ended with exit code 3.

Apr 26 22:56:47 director maas-rackd[1807]: #011

Apr 26 22:56:47 director maas-rackd[1807]: provisioningserver.utils.services: [critical] Beaconing process for enp1s0f0 failed.

Apr 26 22:56:47 director maas-rackd[1807]: #011Traceback (most recent call last):

Apr 26 22:56:47 director maas-rackd[1807]: #011Failure: twisted.internet.error.ProcessTerminated: A process has ended with a probable error condition: process ended with exit code 3.

Apr 26 22:56:47 director maas-rackd[1807]: #011

usually these logs are harmless and should self-recover. In anycase these errors should not be related to the failed deployment, instead you might be hitting https://bugs.launchpad.net/maas/+bug/2106671 .

In order to better understand why cloud-init failed you have to login to the machine manually, run cloud-init collect-logs and inspect the logs

Thank you for the response, looks like it is due to Unable to deploy Ubuntu 22.04/20.04 via MAAS—cloud‑init bug workaround not working

Deployed with 24.02 and it came up fine

Machine State Address Inst id Base AZ Message
10 started 11.11.11.45 opencontrol ubuntu@24.04 default Deployed
11 started 11.11.11.46 compute1 ubuntu@24.04 default Deployed
12 started 11.11.11.47 compute2 ubuntu@24.04 default Deployed