[rabbitmq-discuss] Rabbitmq server crash and no start more

[Gustavo Aquino]

Hi,

I'm posting about my others environments that I got the same problem, after
one analysis my conclusion is that hostname and network configuration causes
the problem too.

In two cases RHE and Debian RabbitMQ stop to work when my NOC team change
server address and hostname configurations. I delete the schema.DAT and all
come back to work again.

Can I do a suggestion ? Can rabbitmq-server accept -h parameter where user
specify the hostname ?

Regards.


On Mon, Jan 25, 2010 at 7:42 AM, Robert Raschke <rtrlists at googlemail.com>wrote:

>
>
> On Sun, Jan 24, 2010 at 8:07 PM, Gustavo Aquino <aquino.gustavo at gmail.com>wrote:
>
>>
>> ====== Fail process.
>> * ./start-rabbitmq.sh *
>>
>> +---+   +---+
>> |   |   |   |
>> |   |   |   |
>> |   |   |   |
>> |   +---+   +-------+
>> |                   |
>> | RabbitMQ  +---+   |
>> |           |   |   |
>> |   v1.7.0  +---+   |
>> |                   |
>> +-------------------+
>> AMQP 8-0
>> Copyright (C) 2007-2009 LShift Ltd., Cohesive Financial Technologies LLC.,
>> and Rabbit Technologies Ltd.
>> Licensed under the MPL.  See http://www.rabbitmq.com/
>>
>> node          : rabbit at 189-94-130-143
>> app descriptor:
>> /opt/local/lib/rabbitmq/bin/../lib/rabbitmq_server-1.7.0/sbin/../ebin/rabbit.app
>> home dir      : /opt/local/var/lib/rabbitmq
>> cookie hash   : diX16VkN3b6UrKJtDPVb1Q==
>> log           : /opt/local/var/log/rabbitmq/rabbit.log
>> sasl log      : /opt/local/var/log/rabbitmq/rabbit-sasl.log
>> database dir  : /opt/local/var/lib/rabbitmq/mnesia/rabbit
>>
>> starting database             ...done
>> starting core processes       ...done
>> starting recovery             ...done
>> starting persister            ...done
>> starting guid generator       ...done
>> starting builtin applications ...done
>> starting TCP listeners        ...done
>> starting SSL listeners        ...done
>>
>> broker running
>> *^C*
>> *BREAK: (a)bort (c)ontinue (p)roc info (i)nfo (l)oaded*
>> *       (v)ersion (k)ill (D)b-tables (d)istribution*
>> *a*
>>
>> *$~ gustavoaquino$ ./start-rabbitmq.sh *
>> Password:
>>
>> +---+   +---+
>>  |   |   |   |
>> |   |   |   |
>> |   |   |   |
>> |   +---+   +-------+
>> |                   |
>> | RabbitMQ  +---+   |
>> |           |   |   |
>> |   v1.7.0  +---+   |
>> |                   |
>> +-------------------+
>> AMQP 8-0
>> Copyright (C) 2007-2009 LShift Ltd., Cohesive Financial Technologies LLC.,
>> and Rabbit Technologies Ltd.
>> Licensed under the MPL.  See http://www.rabbitmq.com/
>>
>> node          : rabbit at 187-26-170-110
>> app descriptor:
>> /opt/local/lib/rabbitmq/bin/../lib/rabbitmq_server-1.7.0/sbin/../ebin/rabbit.app
>> home dir      : /opt/local/var/lib/rabbitmq
>> cookie hash   : diX16VkN3b6UrKJtDPVb1Q==
>> log           : /opt/local/var/log/rabbitmq/rabbit.log
>> sasl log      : /opt/local/var/log/rabbitmq/rabbit-sasl.log
>> database dir  : /opt/local/var/lib/rabbitmq/mnesia/rabbit
>>
>> *starting database             ...{"init terminating in
>> do_boot",{{nocatch,{error,{cannot_start_application,rabbit,{{timeout_waiting_for_tables,[rabbit_user,rabbit_user_permission,rabbit_vhost,rabbit_config,rabbit_listener,rabbit_durable_route,rabbit_route,rabbit_reverse_route,rabbit_durable_exchange,rabbit_exchange,rabbit_durable_queue,rabbit_queue]},{rabbit,start,[normal,[]]}}}}},[{init,start_it,1},{init,start_em,1}]}}
>> *
>> *
>> *
>> *Crash dump was written to: erl_crash.dump*
>> *init terminating in do_boot ()*
>>
>> === Final fail process
>>
>>
>>
> The first invocation thinks the node is called rabbit at 189-94-130-143,
> whereeas the second one thinks it is rabbit at 187-26-170-110.
>
> I think that may be the root of your issue, since the second one will fail
> to start the internal Mnesia DB components.
>
> Why is Rabbit picking up different node names for you?
>
> Robby
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20100126/efc26521/attachment.htm