rabbitmq-env.conf usage results in config file not found at startup

603 views
Skip to first unread message

Steven Blanc

unread,
Apr 25, 2017, 2:03:36 PM4/25/17
to rabbitm...@googlegroups.com

Hello,

I am  testing rabbitmq-server 3.6.5, Erlang 19.2 on CentOS 7.3.  This is an upgrade we are planning to make from our current production environment of rabbitmq-server 3.5.1, Erlang 17.3 and CentOS 6.5

 

Previously we delivered a package separate from rabbitmq-server that delivered a modified /etc/rabbitmq/rabbitmq.config file that contained our unique config.

Up through CentOS 6.5 rpm/yum didn’t complain about two packages installing the same file.  Now with CentOS 7.3 we get a transaction error with the file conflict.

To remedy this I have made a change to deliver /etc/rabbitmq/rabbitmq-avid.config with our changes in it rather than the conflicting /etc/rabbitmq/rabbitmq.config, along with a new /etc/rabbitmq/rabbitmq-env.conf file.

The contents of the rabbitmq-env.conf file are:

 

# This is a /bin/sh script file - use ordinary env var syntax

CONFIG_FILE=/etc/rabbitmq/rabbitmq-avid.config

 

When I restart rabbitmq-server after installing the package is see this in the log:

 

=INFO REPORT==== 25-Apr-2017::13:53:16 ===

node           : rabbit@vm-cent73-steve

home dir       : /var/lib/rabbitmq

config file(s) : /etc/rabbitmq/rabbitmq-avid.config (not found)

 

Yet the file is there:
$0-sblanc@vm-cent73-steve > ll /etc/rabbitmq/rabbitmq-avid.config

-rwxr-xr-x 1 rabbitmq rabbitmq 1041 Dec  1 13:06 /etc/rabbitmq/rabbitmq-avid.config*

 

I even tried using rabbitmq-env.conf to identify the rabbitmq.config file delivered by the rabbitmq-server package and it won’t find that when identified by the env file:

 

=INFO REPORT==== 25-Apr-2017::13:55:58 ===

node           : rabbit@vm-cent73-steve

home dir       : /var/lib/rabbitmq

config file(s) : /etc/rabbitmq/rabbitmq.config (not found)

 

Am I doing something wrong?  It seems to me that if I use the rabbitmq-env.conf file to identify the CONFIG_FILE it fails to find it no matter what.

 

Thanks,

Steve

Michael Klishin

unread,
Apr 25, 2017, 2:43:32 PM4/25/17
to rabbitm...@googlegroups.com
Drop the ".config" file extension:

CONFIG_FILE=/etc/rabbitmq/rabbitmq-avid

(starting with 3.7.0 both options will work).


«RABBITMQ_CONFIG_FILE: The path to the configuration file, without the .config extension…»

I'll make it more prominent in http://www.rabbitmq.com/configure.html.

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
MK

Staff Software Engineer, Pivotal/RabbitMQ

Michael Klishin

unread,
Apr 25, 2017, 2:44:04 PM4/25/17
to rabbitm...@googlegroups.com
By "both options" I mean both when a ".config" extension is present and when it's not.

To post to this group, send email to rabbitm...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.
--
MK

Staff Software Engineer, Pivotal/RabbitMQ

Michael Klishin

unread,
Apr 25, 2017, 2:44:54 PM4/25/17
to rabbitm...@googlegroups.com
Also, only the value of RABBITMQ_CONFIG_FILE (CONFIG_FILE in rabbitmq-env.conf)
should not have the extension. The actual file should.

On Tue, Apr 25, 2017 at 8:43 PM, Michael Klishin <mkli...@pivotal.io> wrote:
To post to this group, send email to rabbitm...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.
--
MK

Staff Software Engineer, Pivotal/RabbitMQ
Reply all
Reply to author
Forward
0 new messages