[rabbitmq-discuss] AMQP connections closing very frequently

Matthias Radestock matthias at rabbitmq.com
Sun Jun 30 08:32:35 BST 2013

On 30/06/13 06:11, ankitag2010 wrote:
> But couldn't resolve the issue by hard coding the RABBITMQ_CONFIG_ARG.
> Another look at the erlang process:-
> rabbitmq 21883 21880  0 09:34 ?        00:00:04
> /usr/lib64/erlang/erts-5.8.5/bin/beam.smp -W w -K true -A30 -P 1048576 --
> -root /usr/lib64/erlang -progname erl -- -home /var/lib/rabbitmq -- -pa
> /usr/lib/rabbitmq/lib/rabbitmq_server-3.1.1/sbin/../ebin -noshell -noinput
> -s rabbit boot -sname rabbit at test04 -boot start_sasl *-config
> /etc/rabbitmq/rabbitmq* -kernel inet_default_connect_options
> [{nodelay,true}] -sasl errlog_type error -sasl sasl_error_logger false
> -rabbit error_logger {file,"/var/log/rabbitmq/rabbit at test.log"} -rabbit
> sasl_error_logger {file,"/var/log/rabbitmq/rabbit at test04-sasl.log"} -rabbit
> enabled_plugins_file "/etc/rabbitmq/enabled_plugins" -rabbit plugins_dir
> "/usr/lib/rabbitmq/lib/rabbitmq_server-3.1.1/sbin/../plugins" -rabbit
> plugins_expand_dir "/var/lib/rabbitmq/mnesia/rabbit at test-plugins-expand"
> -os_mon start_cpu_sup false -os_mon start_disksup false -os_mon start_memsup
> false -mnesia dir "/var/lib/rabbitmq/mnesia/rabbit at test"

Those '*' are just highlights you inserted when posting, rather than 
what's actually on the command line, right?

If so, that all looks ok.

The only oddness I can see is that the error log and sasl log file names 
refer to different node names - rabbit at test vs rabbit at test04. How does 
that difference arise? And are you sure that you are looking at the 
correct log file when checking that the config file has been read?

And what happens if you hard code the RABBITMQ_CONFIG_ARG to something 
invalid, e.g. "-config /etc/rabbitmq/invalid"?


More information about the rabbitmq-discuss mailing list