Now, by setting RABBITMQ_LOGS=-, regular log messages are written to
stdout. Likewise, RABBITMQ_SASL_LOGS=- sends sasl log messages to
stdout.
This is useful for Docker images.
Fixes#128.
The user shouldn't override the init script's RABBITMQ_PID_FILE value,
otherwise the init script erroneously reports failures to start or stop
the service.
Now, rabbitmq-env logs a warning if RABBITMQ_PID_FILE is already defined
in the environment (ie. by the init script) and in rabbitmq-env.conf.
Fixes#127.
This fixes at least one problem with $RABBITMQ_PID_FILE which, by
default, is set to:
RABBITMQ_PID_FILE=${RABBITMQ_MNESIA_DIR}.pid
In this case, if $RABBITMQ_MNESIA_DIR ends with a trailing slash, the
PID file is a hidden file placed in the Mnesia directory. This prevents
auto-clustering from working and this is tricky to understand why.
Fixes#118.
If this is the case, log a warning to stderr.
Here is an example with the plugins expansion directory:
WARNING: RABBITMQ_PLUGINS_EXPAND_DIR is located inside RABBITMQ_MNESIA_DIR
=> Auto-clustering will not work ('cluster_nodes' in rabbitmq.config)
And with the log directory:
WARNING: RABBITMQ_LOG_BASE is equal to RABBITMQ_MNESIA_DIR
RABBITMQ_LOGS is located inside RABBITMQ_MNESIA_DIR
RABBITMQ_SASL_LOGS is located inside RABBITMQ_MNESIA_DIR
=> Auto-clustering will not work ('cluster_nodes' in rabbitmq.config)
Fixes#120.
Before this change, they were written to /var/log/rabbitmq, no matter
the value of RABBITMQ_LOG_BASE.
In rabbitmq-env, allow the caller to set RABBITMQ_SCRIPTS_DIR to the
directory where rabbitmq-env and rabbitmq-default are located.
In both Fedora and Debian rabbitmq-server.init and
rabbitmq-script-wrapper, load rabbitmq-env and use RABBITMQ_LOG_BASE.
The default value is /var/log/rabbitmq, so the default behaviour remains
the same.
In Debian's rabbitmq-script-wrapper version, use RABBITMQ_LOG_BASE
instead of the hard-coded /var/log/rabbitmq.
Fixes#88.
Jakauppila
Jean-Sébastien Pédron
Michael Klishin
Michael Klishin
Simon MacMullen
Alvaro Videla
Tim Watson