the init script failed to bring down a wedged rabbit server
Bug #1687905 reported by
Tejeev Patel
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack RabbitMQ Server Charm |
Invalid
|
Undecided
|
Unassigned | ||
| rabbitmq-server (Ubuntu) |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
We had to resort to a kill -9 to bring down 2 wedged rabbit servers.
| tags: | added: canonical-bootstack |
Revision history for this message
| James Page (james-page) wrote | #1 |
Revision history for this message
| James Page (james-page) wrote | #2 |
| Changed in charm-rabbitmq-server: | |
| status: | New → Invalid |
| Changed in rabbitmq-server (Ubuntu): | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
Revision history for this message
| James Page (james-page) wrote | #3 |
| Changed in rabbitmq-server (Ubuntu): | |
| status: | Confirmed → Triaged |
To post a comment you must log in.
Wedged erlang processes are a nightmare for this - we actually had a script called the rabbit hammer that did what you describe above to resolve a wedged, clustered rmq deployment.