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

Wed Mar 14 00:26:48 GMT 2012

Hi Simon,

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.

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?

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.

[
    {rabbit, [
        {ssl_listeners, [{"0.0.0.0",4445}]},
        {ssl_options, [
            {cacertfile,"/etc/rabbitmq/certs/testca/cacert.pem"},
            {certfile,"/etc/rabbitmq/certs/server/cert.pem"},
            {keyfile,"/etc/rabbitmq/certs/server/key.pem"},
            {verify, verify_peer},
            {fail_if_no_peer_cert, false}
        ]}

    ]}
].

When I start rabbit 2.7.1, I only see it starts to listen to the non-ssl
port as follows:

=INFO REPORT==== 14-Mar-2012::11:05:06 ===
Limiting to approx 924 file handles (829 sockets)

=INFO REPORT==== 14-Mar-2012::11:05:06 ===
Memory limit set to 1304MB of 3260MB total.

=INFO REPORT==== 14-Mar-2012::11:05:06 ===
msg_store_transient: using rabbit_msg_store_ets_index to provide index

=INFO REPORT==== 14-Mar-2012::11:05:07 ===
msg_store_persistent: using rabbit_msg_store_ets_index to provide index

=WARNING REPORT==== 14-Mar-2012::11:05:07 ===
msg_store_persistent: rebuilding indices from scratch

=INFO REPORT==== 14-Mar-2012::11:05:07 ===
started TCP Listener on [::]:4446

Cheers,

Brian

On Tue, Mar 13, 2012 at 10:53 PM, Simon MacMullen <simon at rabbitmq.com>wrote:

> On 13/03/12 03:21, Brian Jing wrote:
>
>> 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:
>>
>
> That looks like Rabbit is not even trying to listen for SSL. Do you see
> something like
>
> =INFO REPORT==== 13-Mar-2012::11:49:04 ===
> started TCP Listener on [::]:5672
>
> =INFO REPORT==== 13-Mar-2012::11:49:04 ===
> started SSL Listener on [::]:5671
>
> in the logs? Or is there an error? What does your config file look like?
>
>
>  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?
>>
>
> 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.
>
> 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.
>
> Cheers, Simon
>
> --
> Simon MacMullen
> RabbitMQ, VMware
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120314/39886277/attachment.htm>