---

Subject:	Try to recreate all Zenoss
Author:	Jan Garaj
Posted:	2014-12-26 17:12

Try to recreate all Zenoss exchanges and queues - http://wiki.zenoss.org/Working_with_Queues

Devops Monitoring Expert advice: Dockerize/automate/monitor all the things.

DevOps stack: Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform / Elasticsearch

---

Subject:	Thanks for your advice.
Author:	[Not Specified]
Posted:	2014-12-28 19:57

Thanks for your advice.
1. Any risk to run these steps to recreate all Zenoss exchanges and queues
$ zenoss stop
$ sudo su - # become root
# export VHOST="/zenoss"
# export USER="zenoss"
# export PASS="zenoss" # replace it with $amqppassword from $ZENHOME/etc/global.conf, if needed
# rabbitmqctl stop_app
# rabbitmqctl reset
# rabbitmqctl start_app
# rabbitmqctl add_vhost $VHOST
# rabbitmqctl add_user "$USER" "$PASS"
# rabbitmqctl set_permissions -p "$VHOST" "$USER" '.*' '.*' '.*'
# rabbitmqctl -p $VHOST list_queues # check if all queues exist
# exit # back to zenoss user
$ zenoss start

2. If I don't run it and leave the queued events alone, any potential problem

recently, I found my zenhub failure event cannot auto cleared within short time everyday when Zenoss optimize the db and lock the db. Is it possible caused by these queued events

3. Can I just remove/delete the rabbitmq queue file on harddisk

Thanks

---

Subject:	1.) It's question for your
Author:	Jan Garaj
Posted:	2014-12-29 04:01

1.) It's question for your change management. I'm not official Zenoss support so it can be high risk. Or Jan has some Zenoss experience, so risk is low. Anyway, follow standard procedure: BACKUP (+ROLLBACK) and you are safe.

2.) I don't know. Probably no. 4 events are missing potentially, but you looks happy without them.
Yes RabbitMQ is key part of zenhub, but I can't say, that RabbitMQ is the reason of your zenhub problems without deep knowledge of your Zenoss gears.

3.) This question is for RabbitMQ community/manual. I don't have idea, how RabbitMQ handle missing queue file.

IMHO some events stuck in the queue with some weird status. So BACKUP and shot sick RabbitMQ and start fresh new RabbitMQ. If it doesn't help or you have any new problem, then ROLLBACK and investigate sick RabbitMQ with nonzenoss rabbitmq tools: eg. RabbitMQ management plugin, https://github.com/dubek/rabbitmq-dump-queue, ....

Devops Monitoring Expert advice: Dockerize/automate/monitor all the things.

DevOps stack: Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform / Elasticsearch

---

Subject:	Thanks for help~
Author:	[Not Specified]
Posted:	2014-12-29 20:08

Thanks for help~