Comment 0 for bug 1446526

Currently, the action stop would fail if there is no pid file exist for some reason, but rabbit beam process might still be running.
stop_server_process() https://github.com/stackforge/fuel-library/blob/master/deployment/puppet/cluster/files/ocf/rabbitmq#L583-593 exits with generic error and not trying to stop the running process.

It should instead invoke 'rabbitmqctl stop' and return generic error only if this operation have failed as well. Note, it should not try to find beam process in ps and kill it as this could affect other rabbitmq instances running around.