![]() |
![]() |
Subject: | RabbitMQ service will not start [SOLVED] |
Author: | [Not Specified] |
Posted: | 2015-08-19 03:30 |
I'm running Zenoss version 4.2.5 on Centos 6. It was running normally until two days ago. The RabbitMQ service will now not start. This is the content of the RabbitMQ startup_log:
What should I do next to troubleshoot this problem
Subject: | Please use http://pastebin |
Author: | Jan Garaj |
Posted: | 2015-08-19 03:42 |
Please use http://pastebin.com for log and provide also error rabbitmq log and df -ha and free output.
Devops Monitoring Expert advice:
Dockerize/automate/monitor all the things.
DevOps stack:
Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform /
Elasticsearch
Subject: | rabbitmq startup_err: http:/ |
Author: | [Not Specified] |
Posted: | 2015-08-19 05:22 |
rabbitmq startup_err: http://pastebin.com/2SUz26EC
rabbitmq startup_log: http://pastebin.com/HWmQ6qRZ
rabbitmq log: http://pastebin.com/ST1yVcfc
df -ha:
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 41G 2.8G 36G 8% /
proc 0 0 0 - /proc
sysfs 0 0 0 - /sys
devpts 0 0 0 - /dev/pts
tmpfs 1.9G 56K 1.9G 1% /dev/shm
/dev/sda1 485M 101M 359M 22% /boot
/dev/sda5 16G 374M 15G 3% /home
/dev/sda3 41G 1.3G 38G 4% /opt/zenoss/perf
none 0 0 0 - /proc/sys/fs/binfmt_misc
Subject: | Is something listening on |
Author: | Jan Garaj |
Posted: | 2015-08-19 05:41 |
Is something listening on port 5672 netstat -tanp 5672
badmatch,{error,ehostunreach} -> did you change hostname
Devops Monitoring Expert advice:
Dockerize/automate/monitor all the things.
DevOps stack:
Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform /
Elasticsearch
Subject: | Solved |
Author: | [Not Specified] |
Posted: | 2015-08-19 14:04 |
I figured out why, when I added an iptables rule to allow all traffic to the loopback interface, that it didn't work. I had typed 'l0' instead of 'lo'. [My day job involves configuring Cisco kit, so I regularly have to type 'l0'.]
< |
Previous Issue after upgrade to 5.0.5 |
Next Need 'device in UP!' event. |
> |