diff options
| author | Bogdan Dobrelya <bdobrelia@mirantis.com> | 2016-01-11 14:19:27 +0100 |
|---|---|---|
| committer | Bogdan Dobrelya <bdobrelia@mirantis.com> | 2016-01-11 15:45:15 +0100 |
| commit | 5a3418f2f1b427dcdf2bf5f36e8caad475dc0dce (patch) | |
| tree | a026fa624a5245349f42d8a3fbf5e04620ba4f33 /scripts/rabbitmq-server.ocf | |
| parent | 968623d98da33d686d20b389132946073b1b0adf (diff) | |
| download | rabbitmq-server-git-5a3418f2f1b427dcdf2bf5f36e8caad475dc0dce.tar.gz | |
Fix get_status, action_stop, proc_stop then beam's unresponsive
* Fix get status() to catch beam state and output errors
* Fix action_stop() to force name-based mathcing then no
pidfile and the beam's unresponsive
* Fix proc_stop to use name based matching if no pidfile
found
* Fix proc_stop to retry sending the signal when using the name
based match as well
W/o this patch, the situation is possible when:
- beam's running and cannot process signals, but is reported "not running"
by the get_status(), while in fact it shall be reported as generic error
- which_applications() returned error, while its output is still
being parsed for the "what" match, while it shall not.
- action stop and proc_stop gives up then there is no pidfile and the beam's
running unresponsive.
The solution is to make get_status to return generic error and action
stop to use the rabbit process name matching for killing it.
Related Fuel bug:
https://bugs.launchpad.net/fuel/+bug/1529897
Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>
Diffstat (limited to 'scripts/rabbitmq-server.ocf')
0 files changed, 0 insertions, 0 deletions