[rabbitmq-discuss] Stopping rabbitmq-server: FAILED

Jain, Punit Punit.Jain at emc.com
Thu Mar 6 13:59:31 GMT 2014

In this case "service rabbitmq-server stop" failed with the exit status 2, but, in actual, rabbitmq-server was stopped fine. I verified it by checking processes and the broker's status. "rabbitmq-server stop" is a part of an RPM scriptlet, which does the configuration for RabbitMQ, and it failed due to this error during an upgrade.

Could you please explain the meaning of the return code '2'? We are planning to put a mitigation to avoid some of these types of errors. Also, is there any other return code we should check? It would be best if we could know all the possible return code and their meaning.


From: rabbitmq-discuss [mailto:rabbitmq-discuss-bounces at lists.rabbitmq.com] On Behalf Of Christian Rohling
Sent: Sunday, February 16, 2014 4:07 AM
To: Discussions about RabbitMQ
Subject: Re: [rabbitmq-discuss] Stopping rabbitmq-server: FAILED

I think the most likely cause of this is not having permissions for the rabbitmq process in the directory it wants to read/write it's PID to.


On Sat, Feb 15, 2014 at 10:27 AM, Jain, Punit <Punit.Jain at emc.com<mailto:Punit.Jain at emc.com>> wrote:
Hi All,
I am using RabbitMQ version 3.1.3 on SuSE. I got following error while trying to stop rabbitmq-server:
Stopping rabbitmq-server: FAILED - check /var/log/rabbitmq/shutdown_log, _err

Error: {'EXIT',{error,{could_not_read_pid,{error,enoent}}}}

What could be the reason for this?


rabbitmq-discuss mailing list
rabbitmq-discuss at lists.rabbitmq.com<mailto:rabbitmq-discuss at lists.rabbitmq.com>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140306/c660c341/attachment.html>

More information about the rabbitmq-discuss mailing list