[rabbitmq-discuss] rabbitmq fails on start

Wed Jun 29 16:53:21 BST 2011

[jlh at hydra ~]$ sudo /usr/local/etc/rc.d/rabbitmq start
Starting all nodes...
Starting node rabbit at hydra...
Activating RabbitMQ plugins ...
0 plugins activated:

+---+   +---+
|   |   |   |
|   |   |   |
|   |   |   |
|   +---+   +-------+
|                   |
| RabbitMQ  +---+   |
|           |   |   |
|   v2.3.1  +---+   |
|                   |
+-------------------+
AMQP 0-9-1 / 0-9 / 0-8
Copyright (C) 2007-2011 VMware, Inc.
Licensed under the MPL.  See http://www.rabbitmq.com/

node           : rabbit at hydra
app descriptor :
/usr/local/sbin/../lib/erlang/lib/rabbitmq_server-2.3.1/sbin/../ebin/rabbit.app
home dir       : /var/db/rabbitmq
config file(s) : (none)
cookie hash    : +5sKmojC5RpkPIWY1ICaBQ==
log            : /var/log/rabbitmq/rabbit at hydra.log
sasl log       : /var/log/rabbitmq/rabbit at hydra-sasl.log
database dir   : /var/db/rabbitmq/mnesia/rabbit at hydra
erlang version : 5.8.4

starting file handle cache server
...done
starting worker pool
 ...done
starting database
...done
starting codec correctness check
 ...done
-- external infrastructure ready
starting plugin registry
 ...done
starting auth mechanism cr-demo
...done
starting auth mechanism amqplain
 ...done
starting auth mechanism plain
...done
starting statistics event manager
...done
starting logging server
...done
starting exchange type direct
...done
starting exchange type fanout
...done
starting exchange type headers
 ...done
starting exchange type topic
 ...done
-- kernel ready
starting alarm handler
 ...done
starting node monitor
...done
starting cluster delegate
...done
starting guid generator
...done
starting memory monitor
...done
-- core initialized
starting empty DB check
...done
starting exchange recovery
 ...done
starting queue supervisor and queue recovery
 ...done
-- message delivery logic ready
starting error log relay
 ...done
starting networking
...BOOT ERROR: FAILED
Reason: badarg
Stacktrace: [{inet6_tcp,listen,2},
             {rabbit_networking,ipv6_status,1},
             {rabbit_networking,port_to_listeners,1},
             {rabbit_networking,check_tcp_listener_address_auto,2},
             {rabbit_networking,start_listener,4},
             {rabbit_networking,'-boot_tcp/0-lc$^0/1-0-',1},
             {rabbit_networking,boot_tcp,0},
             {rabbit_networking,boot,0}]
{"Kernel pid
terminated",application_controller,"{application_start_failure,rabbit,{bad_return,{{rabbit,start,[normal,[]]},{'EXIT',{rabbit,failure_during_boot}}}}}"}
Error: {node_start_failed,normal}
Kernel pid terminated (application_controller)
({application_start_failure,rabbit,{bad_return,{{rabbit,start,[normal,[]]},{'EXIT',{rabbit,failure_during_boot}}}}})

versions...
rabbitmq-2.3.1_2
erlang-lite-r14b03,1
FreeBSD 8.1

I tried restarting the rabbitmq service and it failed out with this message.
 (It had been running for some time without problem prior.)  I noticed that
erlang and rabbitmq were both moving along so I updated my ports but no joy.

--rc.con snippet----
# fire up RabbitMQ, la rasion d'etre
rabbitmq_enable="YES"
RABBITMQ_NODE_IP_ADDRESS="172.16.1.104"

#epmd for erlang network processes
epmd_enable="YES"

I don't comprehend the error message and where I should start looking.
Ideas?

Best,
-Jeff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110629/b6f5e93d/attachment.htm>