Start rabbitmq-server a daemon with a custom RabbitMQ Node name

118 views
Skip to first unread message

Giri Chintala

unread,
Aug 24, 2016, 10:57:44 PM8/24/16
to rabbitmq-users

I am using RabbitMQ 3.6.3 in RHEL7. I am trying to override default RabbitMQ node name (setting RABBITMQ_NODENAME env variable) and run rabbitmq-server a daemon by running the following commands, but unfortunately RabbitMQ is ignoring  RABBITMQ_NODENAME environment variable and naming name as "rabbitmq@hotname".

$ export RABBITMQ_NODENAME=rabbit-i-f05ba3c1
$ chkconfig rabbitmq-server on
$ service rabbitmq-server status



Giri Chintala

unread,
Aug 25, 2016, 12:15:30 AM8/25/16
to rabbitmq-users
Update:

I just tried a different way to set RabbitMQ node name. RabbitMQ is setting node name properly if  NODENAME is in /etc/rabbitmq/rabbitmq-env.conf.  I am still not sure why RabbitMQ is ignoring RABBITMQ_NODENAME environment variable.

Now, I am struggling with a new issue.

My RabbitMQ Node is running on AWS EC2 RHEL7 and i executed the below commands to configure and run RabbitMQ-server as demon. 

RabbitMQ-Server is failed to start when ec2-instance reboots,  it logged "su: cannot open session: Permission denied" in /var/log/rabbitmq/startup_err.  

However i am able to start service manually after reboot using $ service rabbitmq-server start



$ yum install -y socat
$ rpm -Uvh rabbitmq.rpm --force --nodeps
$ chkconfig rabbitmq-server on
$ service rabbitmq-server start
Reply all
Reply to author
Forward
0 new messages