Hi Simon,<br><br>Thanks for your reply! So I guess we'll have to stick with Erlang R13B03 until we've completely made the transition to Rabbit 2.7.1. <br><br>I just had a look at the logs, you are right, the ssl port is not being listened. What could be wrong here. Is there anything I need to do to enable SSL when building it? <br>
<br>Here is the config file for rabbit 2.7.1. The 1.8.0 config file sits in the same directory with the same content(except the port) but with a different name.<br><br><span style="color:rgb(0,102,0)">[</span><br style="color:rgb(0,102,0)">
<span style="color:rgb(0,102,0)">��� {rabbit, [</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">������� {ssl_listeners, [{"0.0.0.0",4445}]},</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">������� {ssl_options, [</span><br style="color:rgb(0,102,0)">
<span style="color:rgb(0,102,0)">����������� {cacertfile,"/etc/rabbitmq/certs/testca/cacert.pem"},</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">����������� {certfile,"/etc/rabbitmq/certs/server/cert.pem"},</span><br style="color:rgb(0,102,0)">
<span style="color:rgb(0,102,0)">����������� {keyfile,"/etc/rabbitmq/certs/server/key.pem"},</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">����������� {verify, verify_peer},</span><br style="color:rgb(0,102,0)">
<span style="color:rgb(0,102,0)">����������� {fail_if_no_peer_cert, false}</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">������� ]}</span><br style="color:rgb(0,102,0)"><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><br>When I start rabbit 2.7.1, I only see it starts to listen to the non-ssl port as follows:<br><br>
<span style="color:rgb(0,102,0)">=INFO REPORT==== 14-Mar-2012::11:05:06 ===</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">Limiting to approx 924 file handles (829 sockets)</span><br style="color:rgb(0,102,0)">
<br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">=INFO REPORT==== 14-Mar-2012::11:05:06 ===</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">Memory limit set to 1304MB of 3260MB total.</span><br style="color:rgb(0,102,0)">
<br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">=INFO REPORT==== 14-Mar-2012::11:05:06 ===</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">msg_store_transient: using rabbit_msg_store_ets_index to provide index</span><br style="color:rgb(0,102,0)">
<br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">=INFO REPORT==== 14-Mar-2012::11:05:07 ===</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">msg_store_persistent: using rabbit_msg_store_ets_index to provide index</span><br style="color:rgb(0,102,0)">
<br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">=WARNING REPORT==== 14-Mar-2012::11:05:07 ===</span><br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">msg_store_persistent: rebuilding indices from scratch</span><br style="color:rgb(0,102,0)">
<br style="color:rgb(0,102,0)"><span style="color:rgb(0,102,0)">=INFO REPORT==== 14-Mar-2012::11:05:07 ===</span><br style="color:rgb(0,102,0)"><span style="color:rgb(255,0,0)">started TCP Listener on [::]:4446</span><br style="color:rgb(0,102,0)">
<br>Cheers,<br><br>Brian<br><br><div class="gmail_quote">On Tue, Mar 13, 2012 at 10:53 PM, Simon MacMullen <span dir="ltr"><<a href="mailto:simon@rabbitmq.com">simon@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 13/03/12 03:21, Brian Jing wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The problem is that although I have SSL configured for 2.7.1, only<br>
non-SSl connections currently work. For any SSL connections, I get a<br>
"connection refused" on the client side. I triple checked the SSL<br>
certificates and saw no problems. However, when I list the status of the<br>
2.7.1 server , it says the following:<br>
</blockquote>
<br></div>
That looks like Rabbit is not even trying to listen for SSL. Do you see something like<br>
<br>
=INFO REPORT==== 13-Mar-2012::11:49:04 ===<br>
started TCP Listener on [::]:5672<br>
<br>
=INFO REPORT==== 13-Mar-2012::11:49:04 ===<br>
started SSL Listener on [::]:5671<br>
<br>
in the logs? Or is there an error? What does your config file look like?<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I noticed that ServerA doesn't have ssl in the "running_application"<br>
list. Is this why SSL doesn't work? I'm pretty sure erlang R13B03 thats<br>
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<br>
version solve the problem? Would the latest Erlang be incompatible with<br>
rabbitmq 1.8.0? If I were to still use Erlang R13B03, what shall I do to<br>
make 2.7.1 work with SSL?<br>
</blockquote>
<br></div>
The SSL dependencies haven't changed much since 1.8.0. SSL support in newer Erlang is more robust, but if it was working for you with R13B03 and 1.8.0 then it should work with R13B03 and 2.7.1.<br>
<br>
I'm not sure, but I suspect Erlang R15B will not work with 1.8.0. Various bits of deprecated API have been removed, and I imagine 1.8.0 used them.<br>
<br>
Cheers, Simon<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Simon MacMullen<br>
RabbitMQ, VMware<br>
</font></span></blockquote></div><br>