© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
From the logs, it also look like the problem with RabbitMQ starts at around 09/18/2018 06:10:45 PM, which occurs before the config_api was rebooted at around 09/19/2018 01:09:13 PM.
To recover, the rabbitMQ cluster will need to be brought back to healthy state on all three controller nodes.