[rabbitmq-discuss] After upgrade to 3.3.3 rabbitmq-server failing to start

[Karl Jackson]

It did not produce any output. It looks like RABBITMQ_SERVER_ERL_ARGS is
not set. Here is what I did


[root at habu1 tmp]# su - rabbitmq

Last password change : Aug 22, 2013

Password expires : never

Password inactive : never

Account expires : never

Minimum number of days between password change : -1

Maximum number of days between password change : -1

Number of days of warning before password expires : -1

-bash-4.1$ printenv RABBITMQ_SERVER_ERL_ARGS

-bash-4.1$

Thank you,

Karl Jackson


On Thu, Jun 19, 2014 at 2:18 PM, Michael Klishin <mklishin at gopivotal.com>
wrote:

>
>
> On 20 June 2014 at 00:05:49, Karl Jackson (isskjj at gmail.com) wrote:
> > > The output is comparable to what is in the startup-log and startup-err:
> >
> > {"init terminating in do_boot",badarg}
> >
> > Crash dump was written to: erl_crash.dump
> > init terminating in do_boot (badarg)
>
> the crash dump suggests the VM is running with odd startup flags:
>
> [async-threads:0] [kernel-poll:false]
>
> 0 I/O threads sounds problematic. Can something be overriding
> RABBITMQ_SERVER_ERL_ARGS? Did you mean to append flags to it?
>
> Please run printenv RABBITMQ_SERVER_ERL_ARGS as effective RabbitMQ
> user and post the output.
> --
> MK
>
> Software Engineer, Pivotal/RabbitMQ
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140619/8a0296c2/attachment.html>