Hi there,<br><br>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.<br>
<br>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. <br>These are the env variables I specified in rabbitmq_env.conf:<br>
<span style="color:rgb(0,102,0)">SERVICENAME=</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">NODENAME=</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">NODE_PORT=</span><br style="color:rgb(0,102,0)">
<span style="color:rgb(0,102,0)">CONFIG_FILE=</span><br><br>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:<br>
<br><span style="color:rgb(0,102,0)">Status of node 'rabbit-new@ServerA' ...</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">[{pid,23440},</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">�{running_applications,[{rabbit,"RabbitMQ","2.7.1"},</span><br style="color:rgb(0,102,0)">
<span style="color:rgb(0,102,0)">����������������������� {os_mon,"CPO� CXC 138 46","2.2.4"},</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">����������������������� {sasl,"SASL� CXC 138 11","2.1.8"},</span><br style="color:rgb(0,102,0)">
<span style="color:rgb(0,102,0)">����������������������� {mnesia,"MNESIA� CXC 138 12","4.4.12"},</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">����������������������� {stdlib,"ERTS� CXC 138 10","1.16.4"},</span><br style="color:rgb(0,102,0)">
<span style="color:rgb(0,102,0)">����������������������� {kernel,"ERTS� CXC 138 10","2.13.4"}]},</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">�{os,{unix,linux}},</span><br style="color:rgb(0,102,0)">
<span style="color:rgb(0,102,0)">�{erlang_version,"Erlang R13B03 (erts-5.7.4) [source] [64-bit] [smp:4:4] [rq:4] [async-threads:30] [hipe] [kernel-poll:true]\n"},</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">�{memory,..</span><br style="color:rgb(0,102,0)">
<span style="color:rgb(0,102,0)">�...</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">�...</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">...done.</span><br><br>On another machine that only has 2.7.1 on, it produces the following:<br>
<br><span style="color:rgb(0,102,0)">Status of node rabbit@ServerB ...</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">[{pid,30862},</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">�{running_applications,</span><br style="color:rgb(0,102,0)">
<span style="color:rgb(0,102,0)">���� [{rabbitmq_federation,"RabbitMQ Federation","2.7.1"},</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">����� {rabbitmq_management,"RabbitMQ Management Console","2.7.1"},</span><br style="color:rgb(0,102,0)">
<span style="color:rgb(0,102,0)">����� {rabbitmq_management_agent,"RabbitMQ Management Agent","2.7.1"},</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">����� {amqp_client,"RabbitMQ AMQP Client","2.7.1"},</span><br style="color:rgb(0,102,0)">
<span style="color:rgb(0,102,0)">����� {rabbit,"RabbitMQ","2.7.1"},</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">����� {ssl,"Erlang/OTP SSL application","4.1.6"},</span><br style="color:rgb(0,102,0)">
<span style="color:rgb(0,102,0)">����� {public_key,"Public key infrastructure","0.13"},</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">����� {crypto,"CRYPTO version 2","2.0.4"},</span><br style="color:rgb(0,102,0)">
<span style="color:rgb(0,102,0)">����� {os_mon,"CPO� CXC 138 46","2.2.7"},</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">����� {sasl,"SASL� CXC 138 11","2.1.10"},</span><br style="color:rgb(0,102,0)">
<span style="color:rgb(0,102,0)">����� {rabbitmq_mochiweb,"RabbitMQ Mochiweb Embedding","2.7.1"},</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">����� {webmachine,"webmachine","1.7.0-rmq2.7.1-hg"},</span><br style="color:rgb(0,102,0)">
<span style="color:rgb(0,102,0)">����� {mochiweb,"MochiMedia Web Server","1.3-rmq2.7.1-git"},</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">����� {inets,"INETS� CXC 138 49","5.7.1"},</span><br style="color:rgb(0,102,0)">
<span style="color:rgb(0,102,0)">����� {mnesia,"MNESIA� CXC 138 12","4.5"},</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">����� {stdlib,"ERTS� CXC 138 10","1.17.5"},</span><br style="color:rgb(0,102,0)">
<span style="color:rgb(0,102,0)">����� {kernel,"ERTS� CXC 138 10","2.14.5"}]},</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">�{os,{unix,linux}},</span><br style="color:rgb(0,102,0)">
<span style="color:rgb(0,102,0)">�{erlang_version,</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">���� "Erlang R14B04 (erts-5.8.5) [source] [64-bit] [smp:2:2] [rq:2] [async-threads:30] [kernel-poll:true]\n"},</span><br style="color:rgb(0,102,0)">
<span style="color:rgb(0,102,0)">�{memory,</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">� ...</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">� ...</span><br style="color:rgb(0,102,0)">
<span style="color:rgb(0,102,0)">...done.</span><br><br>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.<br>
<br>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?<br>
<br>Thanks,<br><br>Brian<br><br>