Hello everybody,
I am having a lot of problems with juju after not being able to ssh in my instances with openstack, I had everything up and running until rabbitmq all of the sudden stopped working.
I tried to destroy the controller and recreate it but that ended up causing more problems 
This is what my juju status looks like now…https://imgur.com/a/kmF7Ao3
You’ll need to provide a little more information. What version of Juju? The status shows that machine 0 is down, and that machine is the one to which things like mysql are deployed - it that’s not working, then other workloads will be blocked. So you’ll need to look into the reason why machine 0 is not able to contact the controller. Is that instance shown as deployed in maas, what do the logs say etc.
Hello All
Even i have the same problem ,All of a sudden rabbit mq server stopping working states error , not able to do ssh into any machines using name , ip able to ssh , Dashboard also not able to login
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
hyd-lab-skyos hyd-maas-controller HYD-MAAS-SKYOS 2.6.4 unsupported 14:43:41Z
App Version Status Scale Charm Store Rev OS Notes
ceph-cluster active 3 hacluster jujucharms 51 ubuntu
ceph-mon 12.2.11 active 3 ceph-mon jujucharms 31 ubuntu
ceph-osd 12.2.11 active 6 ceph-osd jujucharms 275 ubuntu
ceph-radosgw 12.2.11 active 3 ceph-radosgw jujucharms 262 ubuntu
cinder 12.0.5 active 3 cinder jujucharms 276 ubuntu
cinder-ceph 12.0.5 active 3 cinder-ceph jujucharms 238 ubuntu
cinder-cluster active 3 hacluster jujucharms 51 ubuntu
dashboard-cluster active 3 hacluster jujucharms 51 ubuntu
glance 16.0.1 active 3 glance jujucharms 273 ubuntu
glance-cluster active 3 hacluster jujucharms 51 ubuntu
heat 6.1.2 active 3 heat jujucharms 259 ubuntu
heat-cluster active 3 hacluster jujucharms 51 ubuntu
keystone 13.0.2 active 3 keystone jujucharms 294 ubuntu
keystone-cluster active 3 hacluster jujucharms 51 ubuntu
keystone-ldap 13.0.2 active 3 keystone-ldap jujucharms 12 ubuntu
mysql 5.6.37-26.21 active 3 percona-cluster jujucharms 272 ubuntu
mysql-cluster active 3 hacluster jujucharms 51 ubuntu
neutron-api 12.0.5 active 3 neutron-api jujucharms 268 ubuntu
neutron-cluster active 3 hacluster jujucharms 51 ubuntu
neutron-openvswitch 12.0.5 active 6 neutron-openvswitch jujucharms 255 ubuntu
nova-cloud-controller 17.0.9 active 3 nova-cloud-controller jujucharms 319 ubuntu
nova-compute 17.0.9 active 6 nova-compute jujucharms 291 ubuntu
novacloud-cluster active 3 hacluster jujucharms 51 ubuntu
ntp 4.2.8p4+dfsg active 6 ntp jujucharms 31 ubuntu
openstack-dashboard 13.0.1 active 3 openstack-dashboard jujucharms 278 ubuntu
rabbitmq-server 3.5.7 error 3 rabbitmq-server jujucharms 84 ubuntu
Unit Workload Agent Machine Public address Ports Message
ceph-mon/0 active idle 0/lxd/0 10.218.5.145 Unit is ready and clustered
ceph-mon/1 active idle 1/lxd/0 10.218.5.182 Unit is ready and clustered
ceph-mon/2 active idle 2/lxd/0 10.218.5.92 Unit is ready and clustered
ceph-osd/0 active idle 0 10.218.5.93 Unit is ready (7 OSD)
ceph-osd/1 active idle 1 10.218.5.112 Unit is ready (7 OSD)
ceph-osd/2 active idle 2 10.218.5.129 Unit is ready (7 OSD)
ceph-osd/3 active idle 3 10.218.5.161 Unit is ready (7 OSD)
ceph-osd/4 active idle 4 10.218.5.137 Unit is ready (7 OSD)
ceph-osd/5 active idle 5 10.218.5.111 Unit is ready (7 OSD)
ceph-radosgw/0 active idle 0/lxd/1 10.218.5.154 80/tcp Unit is ready
ceph-cluster/2 active idle 10.218.5.154 Unit is ready and clustered
ceph-radosgw/1 active idle 1/lxd/1 10.218.5.173 80/tcp Unit is ready
ceph-cluster/0 active idle 10.218.5.173 Unit is ready and clustered
ceph-radosgw/2 active idle 2/lxd/1 10.218.5.128 80/tcp Unit is ready
ceph-cluster/1 active idle 10.218.5.128 Unit is ready and clustered
cinder/0 active idle 0/lxd/2 10.218.5.101 8776/tcp Unit is ready
cinder-ceph/1 active idle 10.218.5.101 Unit is ready
cinder-cluster/1 active idle 10.218.5.101 Unit is ready and clustered
cinder/1 active idle 1/lxd/2 10.218.5.188 8776/tcp Unit is ready
cinder-ceph/0 active idle 10.218.5.188 Unit is ready
cinder-cluster/0 active idle 10.218.5.188 Unit is ready and clustered
cinder/2 active idle 2/lxd/2 10.218.5.183 8776/tcp Unit is ready
cinder-ceph/2 active idle 10.218.5.183 Unit is ready
cinder-cluster/2 active idle 10.218.5.183 Unit is ready and clustered
glance/0 active idle 0/lxd/3 10.218.5.104 9292/tcp Unit is ready
glance-cluster/2 active idle 10.218.5.104 Unit is ready and clustered
glance/1 active idle 1/lxd/3 10.218.5.174 9292/tcp Unit is ready
glance-cluster/0 active idle 10.218.5.174 Unit is ready and clustered
glance/2 active idle 2/lxd/3 10.218.5.181 9292/tcp Unit is ready
glance-cluster/1 active idle 10.218.5.181 Unit is ready and clustered
heat/0 active idle 0/lxd/4 10.218.5.97 8000/tcp,8004/tcp Unit is ready
heat-cluster/1 active idle 10.218.5.97 Unit is ready and clustered
heat/1 active idle 1/lxd/4 10.218.5.180 8000/tcp,8004/tcp Unit is ready
heat-cluster/0 active idle 10.218.5.180 Unit is ready and clustered
heat/2 active idle 2/lxd/4 10.218.5.190 8000/tcp,8004/tcp Unit is ready
heat-cluster/2 active idle 10.218.5.190 Unit is ready and clustered
keystone/0 active idle 0/lxd/5 10.218.5.102 5000/tcp Unit is ready
keystone-cluster/2 active idle 10.218.5.102 Unit is ready and clustered
keystone-ldap/0 active idle 10.218.5.102 Unit is ready
keystone/1 active idle 1/lxd/5 10.218.5.157 5000/tcp Unit is ready
keystone-cluster/0 active idle 10.218.5.157 Unit is ready and clustered
keystone-ldap/2 active idle 10.218.5.157 Unit is ready
keystone/2 active idle 2/lxd/5 10.218.5.144 5000/tcp Unit is ready
keystone-cluster/1 active idle 10.218.5.144 Unit is ready and clustered
keystone-ldap/1 active idle 10.218.5.144 Unit is ready
mysql/0 active idle 0/lxd/6 10.218.5.163 3306/tcp Unit is ready
mysql-cluster/2 active idle 10.218.5.163 Unit is ready and clustered
mysql/1 active idle 1/lxd/6 10.218.5.146 3306/tcp Unit is ready
mysql-cluster/1 active idle 10.218.5.146 Unit is ready and clustered
mysql/2 active idle 2/lxd/6 10.218.5.165 3306/tcp Unit is ready
mysql-cluster/0 active idle 10.218.5.165 Unit is ready and clustered
neutron-api/0 active idle 0/lxd/7 10.218.5.185 9696/tcp Unit is ready
neutron-cluster/2 active idle 10.218.5.185 Unit is ready and clustered
neutron-api/1 active idle 1/lxd/7 10.218.5.140 9696/tcp Unit is ready
neutron-cluster/0 active idle 10.218.5.140 Unit is ready and clustered
neutron-api/2 active idle 2/lxd/7 10.218.5.141 9696/tcp Unit is ready
neutron-cluster/1 active idle 10.218.5.141 Unit is ready and clustered
nova-cloud-controller/0 active idle 0/lxd/8 10.218.5.155 8774/tcp,8778/tcp Unit is ready
novacloud-cluster/2 active idle 10.218.5.155 Unit is ready and clustered
nova-cloud-controller/1 active idle 1/lxd/8 10.218.5.121 8774/tcp,8778/tcp Unit is ready
novacloud-cluster/0 active idle 10.218.5.121 Unit is ready and clustered
nova-cloud-controller/2 active idle 2/lxd/8 10.218.5.159 8774/tcp,8778/tcp Unit is ready
novacloud-cluster/1 active idle 10.218.5.159 Unit is ready and clustered
nova-compute/0 active idle 0 10.218.5.93 Unit is ready
neutron-openvswitch/4 active idle 10.218.5.93 Unit is ready
ntp/4 active idle 10.218.5.93 123/udp ntp: Ready
nova-compute/1 active idle 1 10.218.5.112 Unit is ready
neutron-openvswitch/2 active idle 10.218.5.112 Unit is ready
ntp/2 active idle 10.218.5.112 123/udp ntp: Ready
nova-compute/2 active idle 2 10.218.5.129 Unit is ready
neutron-openvswitch/5 active idle 10.218.5.129 Unit is ready
ntp/5 active idle 10.218.5.129 123/udp ntp: Ready
nova-compute/3 active idle 3 10.218.5.161 Unit is ready
neutron-openvswitch/1 active idle 10.218.5.161 Unit is ready
ntp/1 active idle 10.218.5.161 123/udp ntp: Ready
nova-compute/4 active idle 4 10.218.5.137 Unit is ready
neutron-openvswitch/3 active idle 10.218.5.137 Unit is ready
ntp/3 active idle 10.218.5.137 123/udp ntp: Ready
nova-compute/5 active idle 5 10.218.5.111 Unit is ready
neutron-openvswitch/0 active idle 10.218.5.111 Unit is ready
ntp/0 active idle 10.218.5.111 123/udp ntp: Ready
openstack-dashboard/0 active idle 0/lxd/9 10.218.5.171 80/tcp,443/tcp Unit is ready
dashboard-cluster/1 active idle 10.218.5.171 Unit is ready and clustered
openstack-dashboard/1 active idle 1/lxd/9 10.218.5.162 80/tcp,443/tcp Unit is ready
dashboard-cluster/0 active idle 10.218.5.162 Unit is ready and clustered
openstack-dashboard/2 active idle 2/lxd/9 10.218.5.82 80/tcp,443/tcp Unit is ready
dashboard-cluster/2 active idle 10.218.5.82 Unit is ready and clustered
rabbitmq-server/0 error idle 0/lxd/10 10.218.5.87 5672/tcp hook failed: "update-status"
rabbitmq-server/1 error idle 1/lxd/10 10.218.5.160 5672/tcp hook failed: "update-status"
rabbitmq-server/2 error idle 2/lxd/10 10.218.5.139 5672/tcp hook failed: "update-status"
Machine State DNS Inst id Series AZ Message
0 started 10.218.5.93 hydoscomp03 xenial Rack_B3_B4 Deployed
0/lxd/0 started 10.218.5.145 juju-e6107c-0-lxd-0 xenial Rack_B3_B4 Container started
0/lxd/1 started 10.218.5.154 juju-e6107c-0-lxd-1 xenial Rack_B3_B4 Container started
0/lxd/2 started 10.218.5.101 juju-e6107c-0-lxd-2 xenial Rack_B3_B4 Container started
0/lxd/3 started 10.218.5.104 juju-e6107c-0-lxd-3 xenial Rack_B3_B4 Container started
0/lxd/4 started 10.218.5.97 juju-e6107c-0-lxd-4 xenial Rack_B3_B4 Container started
0/lxd/5 started 10.218.5.102 juju-e6107c-0-lxd-5 xenial Rack_B3_B4 Container started
0/lxd/6 started 10.218.5.163 juju-e6107c-0-lxd-6 xenial Rack_B3_B4 Container started
0/lxd/7 started 10.218.5.185 juju-e6107c-0-lxd-7 xenial Rack_B3_B4 Container started
0/lxd/8 started 10.218.5.155 juju-e6107c-0-lxd-8 xenial Rack_B3_B4 Container started
0/lxd/9 started 10.218.5.171 juju-e6107c-0-lxd-9 xenial Rack_B3_B4 Container started
0/lxd/10 started 10.218.5.87 juju-e6107c-0-lxd-10 xenial Rack_B3_B4 Container started
1 started 10.218.5.112 hydoscomp02 xenial Rack_B3_B4 Deployed
1/lxd/0 started 10.218.5.182 juju-e6107c-1-lxd-0 xenial Rack_B3_B4 Container started
1/lxd/1 started 10.218.5.173 juju-e6107c-1-lxd-1 xenial Rack_B3_B4 Container started
1/lxd/2 started 10.218.5.188 juju-e6107c-1-lxd-2 xenial Rack_B3_B4 Container started
1/lxd/3 started 10.218.5.174 juju-e6107c-1-lxd-3 xenial Rack_B3_B4 Container started
1/lxd/4 started 10.218.5.180 juju-e6107c-1-lxd-4 xenial Rack_B3_B4 Container started
1/lxd/5 started 10.218.5.157 juju-e6107c-1-lxd-5 xenial Rack_B3_B4 Container started
1/lxd/6 started 10.218.5.146 juju-e6107c-1-lxd-6 xenial Rack_B3_B4 Container started
1/lxd/7 started 10.218.5.140 juju-e6107c-1-lxd-7 xenial Rack_B3_B4 Container started
1/lxd/8 started 10.218.5.121 juju-e6107c-1-lxd-8 xenial Rack_B3_B4 Container started
1/lxd/9 started 10.218.5.162 juju-e6107c-1-lxd-9 xenial Rack_B3_B4 Container started
1/lxd/10 started 10.218.5.160 juju-e6107c-1-lxd-10 xenial Rack_B3_B4 Container started
2 started 10.218.5.129 hydoscomp04 xenial Rack_B3_B4 Deployed
2/lxd/0 started 10.218.5.92 juju-e6107c-2-lxd-0 xenial Rack_B3_B4 Container started
2/lxd/1 started 10.218.5.128 juju-e6107c-2-lxd-1 xenial Rack_B3_B4 Container started
2/lxd/2 started 10.218.5.183 juju-e6107c-2-lxd-2 xenial Rack_B3_B4 Container started
2/lxd/3 started 10.218.5.181 juju-e6107c-2-lxd-3 xenial Rack_B3_B4 Container started
2/lxd/4 started 10.218.5.190 juju-e6107c-2-lxd-4 xenial Rack_B3_B4 Container started
2/lxd/5 started 10.218.5.144 juju-e6107c-2-lxd-5 xenial Rack_B3_B4 Container started
2/lxd/6 started 10.218.5.165 juju-e6107c-2-lxd-6 xenial Rack_B3_B4 Container started
2/lxd/7 started 10.218.5.141 juju-e6107c-2-lxd-7 xenial Rack_B3_B4 Container started
2/lxd/8 started 10.218.5.159 juju-e6107c-2-lxd-8 xenial Rack_B3_B4 Container started
2/lxd/9 started 10.218.5.82 juju-e6107c-2-lxd-9 xenial Rack_B3_B4 Container started
2/lxd/10 started 10.218.5.139 juju-e6107c-2-lxd-10 xenial Rack_B3_B4 Container started
3 started 10.218.5.161 hydoscomp06 xenial Rack_B3_B4 Deployed
4 started 10.218.5.137 hydoscomp01 xenial Rack_B3_B4 Deployed
5 started 10.218.5.111 hydoscomp05 xenial Rack_B3_B4 Deployed
$RabbitMQ does not like running out of resources (disk/RAM)… but I don’t know why this would prevent you from being able to SSH into the machine at all.
How much memory do you have available within those containers? Could you please provide the output of the following command?
juju run --application rabbitmq-server -- free -m
You may wish to check your queue lengths and potentially purge them or free up some resources.
Hopefully we’ll be able to assist to diagnose the issue for you.