[rabbitmq-discuss] Issue with running two RabbitMQ servers on one machine

[Brian Jing]

Hi there,

We need to upgrade our messaging server from 1.8.0 to 2.7.1. To ensure a
smooth transition, we are trying to make the two rabbit server versions
coexist on the same machine, so we can have our existing messaging system
running while having our new messaging system being tested in the same
environment, This also ensures minimal interruption for the transition in
the production environment as well.

I grabbed the rabbit 2.7.1 source and changed the location of
rabbitmq_env.conf, so that I can specify a different environment for the
new rabbit server.
These are the env variables I specified in rabbitmq_env.conf:
SERVICENAME=
NODENAME=
NODE_PORT=
CONFIG_FILE=

Now I've got 2.7.1 running alongside 1.8.0. The problem is that although I
have SSL configured for 2.7.1, only non-SSl connections currently work. For
any SSL connections, I get a "connection refused" on the client side. I
triple checked the SSL certificates and saw no problems. However, when I
list the status of the 2.7.1 server , it says the following:

Status of node 'rabbit-new at ServerA' ...
[{pid,23440},
 {running_applications,[{rabbit,"RabbitMQ","2.7.1"},
                        {os_mon,"CPO  CXC 138 46","2.2.4"},
                        {sasl,"SASL  CXC 138 11","2.1.8"},
                        {mnesia,"MNESIA  CXC 138 12","4.4.12"},
                        {stdlib,"ERTS  CXC 138 10","1.16.4"},
                        {kernel,"ERTS  CXC 138 10","2.13.4"}]},
 {os,{unix,linux}},
 {erlang_version,"Erlang R13B03 (erts-5.7.4) [source] [64-bit] [smp:4:4]
[rq:4] [async-threads:30] [hipe] [kernel-poll:true]\n"},
 {memory,..
 ...
 ...
...done.

On another machine that only has 2.7.1 on, it produces the following:

Status of node rabbit at ServerB ...
[{pid,30862},
 {running_applications,
     [{rabbitmq_federation,"RabbitMQ Federation","2.7.1"},
      {rabbitmq_management,"RabbitMQ Management Console","2.7.1"},
      {rabbitmq_management_agent,"RabbitMQ Management Agent","2.7.1"},
      {amqp_client,"RabbitMQ AMQP Client","2.7.1"},
      {rabbit,"RabbitMQ","2.7.1"},
      {ssl,"Erlang/OTP SSL application","4.1.6"},
      {public_key,"Public key infrastructure","0.13"},
      {crypto,"CRYPTO version 2","2.0.4"},
      {os_mon,"CPO  CXC 138 46","2.2.7"},
      {sasl,"SASL  CXC 138 11","2.1.10"},
      {rabbitmq_mochiweb,"RabbitMQ Mochiweb Embedding","2.7.1"},
      {webmachine,"webmachine","1.7.0-rmq2.7.1-hg"},
      {mochiweb,"MochiMedia Web Server","1.3-rmq2.7.1-git"},
      {inets,"INETS  CXC 138 49","5.7.1"},
      {mnesia,"MNESIA  CXC 138 12","4.5"},
      {stdlib,"ERTS  CXC 138 10","1.17.5"},
      {kernel,"ERTS  CXC 138 10","2.14.5"}]},
 {os,{unix,linux}},
 {erlang_version,
     "Erlang R14B04 (erts-5.8.5) [source] [64-bit] [smp:2:2] [rq:2]
[async-threads:30] [kernel-poll:true]\n"},
 {memory,
  ...
  ...
...done.

I noticed that ServerA doesn't have ssl in the "running_application" list.
Is this why SSL doesn't work? I'm pretty sure erlang R13B03 thats currently
running on ServerA supports SSL because rabbit 1.8.0 is using it.

What are my options here? Would updating Erlang on ServerA to the latest
version solve the problem? Would the latest Erlang be incompatible with
rabbitmq 1.8.0? If I were to still use Erlang R13B03, what shall I do to
make 2.7.1 work with SSL?

Thanks,

Brian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120313/d9a2779c/attachment.htm>