[rabbitmq-discuss] First-time rabbitmq install crashed after a week & now node won't restart

Wed Sep 1 05:16:23 BST 2010

Update: Rabbitmq works again after reboot. Problem seems to have coincided
with maxing out of server memory.

Cc'ing:
I did not change the hostname.  You might be on to something - there may be
a problem with how ec2 handles hostnames/dhcp.  But as far as I know, the
hostname as been constant throughout.
Thanks, Ian.
Mark

On Tue, Aug 31, 2010 at 9:27 PM, Ian Ragsdale <ian.ragsdale at gmail.com>wrote:

> Did you happen to change your hostname?  That would cause rabbitmqctl to
> fail to connect to a running server that was started with a different
> hostname, and a running server would cause the second failure (because it
> couldn't listen on the correct port).
>
> - Ian
>
>
> On Aug 31, 2010, at 9:17 PM, Mark Soper <masoper at gmail.com> wrote:
>
> Just getting started with rabbitmq, hoping for advice on how to
> troubleshoot this:
>
> Last week I started using celery with rabbitmq on EC2 Ubuntu server.
> It ran fine for a week, then died.
>
> > sudo rabbitmqctl status
>
> Status of node 'rabbit at domU-12-31-39-05-6E-52' ...
> Error: unable to connect to node 'rabbit at domU-12-31-39-05-6E-52': nodedown
> diagnostics:
> - nodes and their ports on domU-12-31-39-05-6E-52:
> [{rabbitmqctl11365,50319}]
> - current node: 'rabbitmqctl11365 at domU-12-31-39-05-6E-52'
> - current node home dir: /var/lib/rabbitmq
> - current node cookie hash: nF0wVuFwDDUCqBIAugLXcw==
>
>
> > sudo rabbitmq-server
>
> +---+   +---+
> |   |   |   |
> |   |   |   |
> |   |   |   |
> |   +---+   +-------+
> |                   |
> | RabbitMQ  +---+   |
> |           |   |   |
> |   v1.7.2  +---+   |
> |                   |
> +-------------------+
> AMQP 8-0
> Copyright (C) 2007-2010 LShift Ltd., Cohesive Financial Technologies LLC.,
> and Rabbit Technologies Ltd.
> Licensed under the MPL.  See <http://www.rabbitmq.com/>
> http://www.rabbitmq.com/
>
> node          : rabbit at domU-12-31-39-05-6E-52
> app descriptor:
> /usr/lib/rabbitmq/lib/rabbitmq_server-1.7.2/sbin/../ebin/rabbit.app
> home dir      : /var/lib/rabbitmq
> cookie hash   : nF0wVuFwDDUCqBIAugLXcw==
> log           : /var/log/rabbitmq/rabbit.log
> sasl log      : /var/log/rabbitmq/rabbit-sasl.log
> database dir  : /var/lib/rabbitmq/mnesia/rabbit
>
> starting internal event notification system
> ...done
> starting logging server
> ...done
> starting database
> ...done
> -- kernel ready
> starting alarm handler
>  ...done
> starting queue supervisor
> ...done
> starting node monitor
> ...done
> starting cluster router
> ...done
> -- core initialized
> starting empty DB check
> ...done
> starting codec correctness check
>  ...done
> starting exchange recovery
>  ...done
> starting queue recovery
> ...done
> starting persister
>  ...done
> starting guid generator
> ...done
> -- message delivery logic ready
> starting error log relay
>  ...done
> starting networking
> ...BOOT ERROR: FAILED
> Reason: {{badmatch,
>              {error,
>                  {shutdown,
>
> {child,undefined,'rabbit_tcp_listener_sup_0.0.0.0:5672',
>                          {tcp_listener_sup,start_link,
>                              [{0,0,0,0},
>                               5672,
>                               [binary,
>                                {packet,raw},
>                                {reuseaddr,true},
>                                {exit_on_close,false}],
>                               {rabbit_networking,tcp_listener_started,[]},
>                               {rabbit_networking,tcp_listener_stopped,[]},
>                               {rabbit_networking,start_client,[]},
>                               "TCP Listener"]},
>                          transient,infinity,supervisor,
>                          [tcp_listener_sup]}}}},
>          [{rabbit_networking,start_listener,4},
>           {rabbit_networking,'-boot_tcp/0-lc$^0/1-0-',1},
>           {rabbit_networking,boot_tcp,0},
>           {rabbit_networking,boot,0},
>           {rabbit,'-run_boot_step/1-lc$^1/1-1-',1},
>           {rabbit,run_boot_step,1},
>           {rabbit,'-start/2-lc$^0/1-0-',1},
>           {rabbit,start,2}]}
> Erlang has closed
> {"init terminating in
> do_boot",{{nocatch,{error,{cannot_start_application,rabbit,{bad_return,{{rabbit,start,[normal,[]]},{'EXIT',{rabbit,failure_during_boot}}}}}}},[{init,start_it,1},{init,start_em,1}]}}
>
> Crash dump was written to: erl_crash.dump
> init terminating in do_boot ()
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>

-- 
617-999-3047
masoper at gmail.com
http://twitter.com/marksoper
http://facebook.com/masoper
http://linkedin.com/in/marksoper
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20100901/478b4844/attachment-0001.htm>