NRPE check check_rabbitmq.py does not work when enforcing SSL
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack RabbitMQ Server Charm |
Fix Released
|
Low
|
Felipe Reyes |
Bug Description
# Versions
Juju 2.1.3
MAAS 2.1.5
rabbitmq-server rev. 61
nrpe rev. 13
# Issue
The default rabbitmq check that is supplied by the rabbitmq-server charm does not work when ssl=only.
# Error message when running the check in /usr/local/
ERROR: Could not connect to RabbitMQ server localhost:5672
I guess this is because when setting ssl=only, the rabbitmq.config gets the following entries where it only listens to ssl on 5671:
[
{rabbit, [
]},
]}
]
A suggestion for an initial fix: Add a regular systemd service check to make sure rabbitmq is running like many of the other openstack charms have. Then take a look at a better way to make sure rabbitmq is running and behaving as the current check is 4 years old and there are probably better ways to check it.
Changed in charm-rabbitmq-server: | |
assignee: | nobody → Felipe Reyes (freyes) |
tags: | added: sts |
tags: | added: backport-potential |
Changed in charm-rabbitmq-server: | |
milestone: | none → 18.05 |
Changed in charm-rabbitmq-server: | |
status: | Fix Committed → Fix Released |
+1 on adding a generic service check - I suspect that this check script is one of many in this charm that don't work when SSL is enforced.