I've just hit this again overnight. Logs are attached, command output is below.
$ sudo rabbitmqctl list_queues -p /maas_workers name messages_unacknowledged Listing queues ... c1d352af-8060-4bf4-b820-f468b22a97fb 4 celery 0 maas-juju.celeryd.pidbox 0 master 0 ...done. $ sudo service maas-cluster-celery status maas-cluster-celery start/running, process 6499 $ sudo service maas-region-celery status maas-region-celery start/running, process 6555
I've just hit this again overnight. Logs are attached, command output is below.
$ sudo rabbitmqctl list_queues -p /maas_workers name messages_ unacknowledged 8060-4bf4- b820-f468b22a97 fb 4 celeryd. pidbox 0
Listing queues ...
c1d352af-
celery 0
maas-juju.
master 0
...done.
$ sudo service maas-cluster-celery status
maas-cluster-celery start/running, process 6499
$ sudo service maas-region-celery status
maas-region-celery start/running, process 6555