[rabbitmq-discuss] Issues with rabbitmq and manual configured hostname

[Martin Wilhelm]

Hi Rabbits,

I had tried rabbitmq-1.7.0 with the following
config:

[root at lnxv-3339:~]$ cat /etc/rabbitmq/rabbitmq.conf
NODENAME=wico at localhost
RABBITMQ_MNESIA_BASE=/data/netapp/config/tmp/rabbitmq-DB/mnesia

localhost is listed in /etc/hosts

If I start rabbitmq, odd things are happen:

========================= >% ===========================

[root at lnxv-3339:~]$ Erlang has closed
/etc/init.d/rabbitmq-server start
Starting rabbitmq-server: Starting all nodes...
Starting node wico at localhost@lnxv-3339...

+---+   +---+
|   |   |   |
|   |   |   |
|   |   |   |
|   +---+   +-------+
|                   |
| 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          : wico at localhost
app descriptor:
/usr/lib64/rabbitmq/lib/rabbitmq_server-1.7.0/sbin/../ebin/rabbit.app
home dir      : /var/lib/rabbitmq
cookie hash   : XVo5QytTWAtzrwBowsFu3A==
log           : /var/log/rabbitmq/wico at localhost.log
sasl log      : /var/log/rabbitmq/wico at localhost-sasl.log
database dir  : /data/netapp/config/tmp/rabbitmq-DB/mnesia/wico at localhost

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

Error: cannot_get_pid
FAILED - check /var/log/rabbitmq/startup_log, _err
rabbitmq-server.


========================= >% ===========================

Again: cannot_get_pid, but the queue is running (we can
connect etc.). We need a "positive result" if rabbitmq
is started. For now we get an exit != 0 (cannot_get_pid).

With Version 1.7.0 rabbitmqctl status gives:

========================= >% ===========================

[root at lnxv-3339:~]$ rabbitmqctl -n wico at localhost status
Status of node wico at localhost ...
[{running_applications,[{rabbit,"RabbitMQ","1.7.0"},
                           {mnesia,"MNESIA  CXC 138 12","4.4.7"},
                           {os_mon,"CPO  CXC 138 46","2.1.8"},
                           {sasl,"SASL  CXC 138 11","2.1.5.4"},
                           {stdlib,"ERTS  CXC 138 10","1.15.5"},
                           {kernel,"ERTS  CXC 138 10","2.12.5"}]},
    {nodes,[wico at localhost]},
    {running_nodes,[wico at localhost]}]
...done.

========================= >% ===========================

This seems to be ok now.

Again - I'm unable to stop rabbitmq correctly:

========================= >% ===========================

[root at lnxv-3339:~]$ /usr/sbin/rabbitmq-multi stop_all
Stopping all nodes...
Error: no_nodes_running

========================= >% ===========================

But there are nodes running as rabbitmqctl shows (and
we can connect to). ;)


Can someone give me a hint?
Sorry for going like a bull at a gate...



Greetings,
Martin


VZnet Netzwerke Ltd. || Saarbrücker Str. 38 || D - 10405 Berlin


MWilhelm at vz.net


VZnet Netzwerke Limited, Registered Office Berlin, Registration Court Charlottenburg, HRB 101454
Executive Directors: Markus Berger-de León, Clemens Riedl
Non-Executive Directors: Dr. Jochen Gutbrod, Martin Weber, Claas van Delden
Headquarters: VZnet Netzwerke Limited, 5 New Street Square, London EC4A 3TW, United Kingdom
Companies House Cardiff No. 5607971, Place of Registration: England and Wales