Pacemaker kills RabbitMQ
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Fix Released
|
High
|
Alexey Lebedeff | ||
6.0.x |
Won't Fix
|
High
|
MOS Maintenance | ||
6.1.x |
Fix Released
|
High
|
Sergii Rizvan | ||
7.0.x |
Fix Released
|
High
|
Sergii Rizvan | ||
8.0.x |
Fix Released
|
High
|
Alexey Lebedeff |
Bug Description
Fuel 6.1, Ubuntu,
RabbitMQ OCF script updated to the latest from the MU3.
We noticed the instance of RabbitMQ was re-created some time ago, it turned out Pacemaker restarted it.
This is a part of a log from Pacemaker:
Oct 29 20:45:15 [10696] controller3 pacemaker_remoted: notice: operation_finished: p_rabbitmq-
Oct 29 20:45:15 [10696] controller3 pacemaker_remoted: notice: operation_finished: p_rabbitmq-
Oct 29 20:45:15 [10696] controller3 pacemaker_remoted: notice: operation_finished: p_rabbitmq-
Oct 29 20:45:15 [10699] controller3 crmd: notice: process_lrm_event: Operation p_rabbitmq-
Oct 29 20:45:15 [10699] controller3 crmd: notice: process_lrm_event: GGUTTPLDI003.
tags: | added: customer-found support |
tags: | added: on-verification |
tags: | removed: on-verification |
tags: | added: on-verification |
tags: | added: 7.0-mu-2 |
Seems I hit the same bug with erlang cookies once again, but the output is a bit different:
Nov 13 17:10:52 [10699] controller3 crmd: notice: process_lrm_event: controller3- p_rabbitmq- server_ monitor_ 30000:40837 [ \r\nCrash dump was written to: erl_crash. dump\r\ nKernel pid terminated (application_ controller) ({application_ start_failure, kernel, {{shutdown, {failed_ to_start_ child,net_ sup,{shutdown, {failed_ to_start_ child,auth, {{case_ clause, eof},[{ auth,read_ cooki\r\ n ]