RabbitMQ 3.7.3 start up crash when RABBITMQ_NODENAME is set as fully qualified machine name.

[Aniket Patil]

Hi all,

I have installed latest rabbit MQ 3.7.3 along with Erlang 19.3.  I am unable to start rabbit mq if i set the RABBITMQ_NODENAME  to long name. (rabbit@machinename.domainname.com)

I did also set the RABBITMQ_USE_LONGNAME=true as an environmental variable as per documentation. 

I get the following error when I start rabbitMQ server and an erlang crash dump.(attached)

{"init terminating in do_boot",{undef,[{rabbit_prelaunch,rabbitmqprelaunch1523804,[],[]},{init,start

_em,1,[{file,"init.erl"},{line,1083}]},{init,do_boot,3,[{file,"init.erl"},{line,791}]}]}}

init terminating in do_boot ({undef,[{rabbit_prelaunch,rabbitmqprelaunch1523804,[],[]},{init,start_e

m,1,[{_},{_}]},{init,do_boot,3,[{_},{_}]}]})

Any help on this is highly appreciated. 

Thanks,
Aniket

[Luke Bakken]

Hi Aniket,

I can't seem to reproduce this using the generic-unix package on my workstation and have attached the output below. How did you install RabbitMQ? What operating system and version? How are you setting the RABBITMQ_NODENAME and RABBITMQ_USE_LONGNAME variables?

Thanks -

Luke

$ RABBITMQ_ALLOW_INPUT=true RABBITMQ_NODENAME='rab...@shostakovich.bakken.io' RABBITMQ_USE_LONGNAME=true ./sbin/rabbitmq-server 

Erlang/OTP 19 [erts-8.3] [source] [64-bit] [smp:8:8] [async-threads:128] [hipe] [kernel-poll:true]

Eshell V8.3  (abort with ^G)

(rab...@shostakovich.bakken.io)1> 

  ##  ##

  ##  ##      RabbitMQ 3.7.3. Copyright (C) 2007-2018 Pivotal Software, Inc.

  ##########  Licensed under the MPL.  See http://www.rabbitmq.com/

  ######  ##

  ##########  Logs: /home/lbakken/issues/rmq-generic-unix/rabbitmq_server-3.7.3/var/log/rabbitmq/rab...@shostakovich.bakken.io.log

                    /home/lbakken/issues/rmq-generic-unix/rabbitmq_server-3.7.3/var/log/rabbitmq/rab...@shostakovich.bakken.io_upgrade.log

              Starting broker...

(rab...@shostakovich.bakken.io)1>  completed with 3 plugins.

node().

'rab...@shostakovich.bakken.io'

(rab...@shostakovich.bakken.io)2>

[Michael Klishin]

See https://groups.google.com/d/msg/rabbitmq-users/f2NZimcFBuQ/P6wF6n-5DQAJ.

Something in your environment overrides one of the environment variables RabbitMQ

uses in a way that breaks Erlang VM argument list (e.g. causes it to have missing arguments or

incorrect quoting, or something of that kind).

On Mon, Feb 12, 2018 at 7:54 PM, Aniket Patil <app...@asu.edu> wrote:

Hi all,

I have installed latest rabbit MQ 3.7.3 along with Erlang 19.3.  I am unable to start rabbit mq if i set the RABBITMQ_NODENAME  to long name. (rab...@machinename.domainname.com)

I did also set the RABBITMQ_USE_LONGNAME=true as an environmental variable as per documentation. 

I get the following error when I start rabbitMQ server and an erlang crash dump.(attached)

{"init terminating in do_boot",{undef,[{rabbit_prelaunch,rabbitmqprelaunch1523804,[],[]},{init,start

_em,1,[{file,"init.erl"},{line,1083}]},{init,do_boot,3,[{file,"init.erl"},{line,791}]}]}}

init terminating in do_boot ({undef,[{rabbit_prelaunch,rabbitmqprelaunch1523804,[],[]},{init,start_e

m,1,[{_},{_}]},{init,do_boot,3,[{_},{_}]}]})

Any help on this is highly appreciated. 

Thanks,
Aniket

--
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

[Aniket Patil]

Thanks Luke and Micheal

@Luke I am trying this on a Windows Server 2012 machine.  I have set the RABBITMQ_NODENAME  and RABBITMQ_USE_LONGNAME   as environmental variables under advanced system settings in Control Panel. 

@ Micheal I did look at earlier post but they were reported for https://groups.google.com/d/msg/rabbitmq-users/f2NZimcFBuQ/P6wF6n-5DQAJ. but they were for older versions. I am trying the latest version.

Is there a specific environment variable I am missing, I have the following environmental  variables set currently 

1. RABBITMQ_CONFIG_FILE

2. RABBITMQ_NODENAME

3. RABBITMQ_DIST_PORT

4.  RABBITMQ_USE_LONGNAME

Also it works fine if i remove the RABBITMQ_NODENAME environmental vatriable and set RABBITMQ_NODENAME to rabbit@machineName instead of rab...@machineName.domain.com

Please let me know if I am missing something. 

Thanks,

Aniket

On Monday, February 12, 2018 at 11:54:25 AM UTC-8, Aniket Patil wrote:

[Michael Klishin]

There is nothing version-specific about the general problem.

Please provide the exact values of the environment variables or we won’t be able to help you.

MK

--

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-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.

[Aniket Patil]

Also it works fine if i remove the RABBITMQ_USE_LONGNAMEenvironmental variable and set RABBITMQ_NODENAME to rabbit@machineName instead of rab...@machineName.domain.com

On Monday, February 12, 2018 at 11:54:25 AM UTC-8, Aniket Patil wrote:

[Michael Klishin]

Aniket,

Please understand that we cannot suggest much without seeing the exact values

used for all of the variables in question.

A specific variable tweaked or removed can be a red herring, we’ve seen that before.

The quickest way to get to the bottom of such issues if finding a way to capture what command line arguments are passed to the VM. I’m not sure what’d be the best way to do that on Windows, unfortunately.

--

[Aniket Patil]

Thanks Micheal. Appreciate your help on this. Following are my environmental variables on my windows environment.

1. ERLANG_HOME=C:\Program Files\erl9.0

2. RABBITMQ_DIST_PORT=27273

3. RABBITMQ_NODENAME=rab...@patil.esri.com

4. RABBITMQ_USE_LONGNAME=true

On Monday, February 12, 2018 at 11:54:25 AM UTC-8, Aniket Patil wrote:

[Luke Bakken]

Hi Aniket,

Thanks for providing that information. I've found a couple bugs around how long names are handled by Windows startup scripts and have created an issue here:

https://github.com/rabbitmq/rabbitmq-server/issues/1508

Thanks,

Luke

On Monday, February 12, 2018 at 2:11:55 PM UTC-8, Aniket Patil wrote:

Thanks Micheal. Appreciate your help on this. Following are my environmental variables on my windows environment.

1. ERLANG_HOME=C:\Program Files\erl9.0

2. RABBITMQ_DIST_PORT=27273

3. RABBITMQ_NODENAME=rabbit@patil.esri.com

[Aniket Patil]

Thanks. I did study the raabitmq-env.bat file and i found the following piece of code. 

if "!RABBITMQ_USE_LONGNAME!"=="true" (

    if "!USE_LONGNAME!"=="true" (

        set RABBITMQ_NAME_TYPE="-name"

        set NAMETYPE=longnames

echo RABBITMQ_NAME_TYPE

echo NAMETYPE

    )

)

I did set the USE_LONGNAME  to true and it fixed my issues. 

Thanks for all the help appreciate it.

On Monday, February 12, 2018 at 11:54:25 AM UTC-8, Aniket Patil wrote:

[Luke Bakken]

Thanks for letting me know.

Just so you know, the variables that start with RABBITMQ_ are those that come from the environment, and corresponding variables that don't have the RABBITMQ_ prefix come from the %AppData%\RabbitMQ\rabbitmq-env-conf.bat file (if it's present).