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

[Brian Jing]

Hi Emile & Simon,

Is rabbit 2.7.1 *completely* compatible with client libraries that use AMQP
0-8? If we updated our rabbit 1.8.0 to 2.7.1, would it cause the old
clients to fail by any chance?

Cheers,

Brian

On Thu, Mar 15, 2012 at 11:08 AM, Brian Jing <brian.newsgroup at gmail.com>wrote:

> Hi Emile,
>
> On Wed, Mar 14, 2012 at 9:57 PM, Emile Joubert <emile at rabbitmq.com> wrote:
>
>> Hi Brian,
>>
>> On 14/03/12 00:26, Brian Jing wrote:
>> > =INFO REPORT==== 14-Mar-2012::11:05:07 ===
>> > started TCP Listener on [::]:4446
>>
>> Where does the config for this port number (4446) come from?
>
>
> This comes from the NODE_PORT variable defined in the environment config
> file. since the existing 1.8.0 already uses 5672 as the default port,  I
> need a different port to be able to run this second instance of rabbitmq on
> the same machine. Does this make sense?
>
>
>> Are you
>> sure the correct config file is being read during broker startup?  What
>> does the broker startup banner say?
>>
>> I'm pretty sure that the correct config files are being used. I changed
> the default env config file from /etc/rabbitmq/rabbitmq-env.conf to
> /etc/rabbitmq/rabbitmq_env.conf before I rebuilt the source (only thing I
> changed in the source). I know this env config file is being used because
> rabbitmq 2.7.1 generates separate log files for the SERVICENAME I specified
> and rabbitmq 2.7.1 listens to the port I specified in the env file as well.
>
> The content of my rabbitmq_env.conf is as follows:
>
> # cat /etc/rabbitmq/rabbitmq_env.conf
> SERVICENAME=RabbitMQ-new
> NODENAME=rabbit-new@$HOSTNAME
> NODE_PORT=4446
> CONFIG_FILE=/etc/rabbitmq/rabbitmq-2.7.1.config
>
> Content of my new rabbitmq.conf:
>
> # cat /etc/rabbitmq/rabbitmq-2.7.1.config
>
> [
>     {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}
>         ]}
>
>     ]}
> ].
>
> Here is the rabbitmq startup information:
>
> # /opt/rabbitmq-server-2.7.1/sbin/rabbitmq-server
> Activating RabbitMQ plugins ...
> 0 plugins activated:
>
>
> +---+   +---+
> |   |   |   |
> |   |   |   |
> |   |   |   |
> |   +---+   +-------+
> |                   |
> | RabbitMQ  +---+   |
> |           |   |   |
> |   v2.7.1  +---+   |
> |                   |
> +-------------------+
> AMQP 0-9-1 / 0-9 / 0-8
> Copyright (C) 2007-2011 VMware, Inc.
> Licensed under the MPL.  See http://www.rabbitmq.com/
>
> node           : rabbit-new at ServerA
> app descriptor : /opt/rabbitmq-server-2.7.1/sbin/../ebin/rabbit.app
> home dir       : /root
> config file(s) : (none)
> cookie hash    :
> log            : /var/log/rabbitmq/rabbit-new at ServerA.log
> sasl log       : /var/log/rabbitmq/rabbit-new at ServerA-sasl.log
> database dir   : /var/lib/rabbitmq/mnesia/rabbit-new at ServerA
> erlang version : 5.7.4
>
> -- rabbit boot start
> starting file handle cache server
> ...done
> starting worker pool
> ...done
> starting database
> ...done
> starting codec correctness check
> ...done
> -- external infrastructure ready
> starting plugin registry
> ...done
> starting auth mechanism cr-demo
> ...done
> starting auth mechanism amqplain
> ...done
> starting auth mechanism plain
> ...done
> starting statistics event manager
> ...done
> starting logging server
> ...done
> starting exchange type direct
> ...done
> starting exchange type fanout
> ...done
> starting exchange type headers
> ...done
> starting exchange type topic
> ...done
> -- kernel ready
> starting alarm handler
> ...done
> starting node monitor
> ...done
> starting cluster delegate
> ...done
> starting guid generator
> ...done
> starting memory monitor
> ...done
> -- core initialized
> starting empty DB check
> ...done
> starting exchange, queue and binding recovery
> ...done
> starting mirror queue slave sup
> ...done
> starting adding mirrors to queues
> ...done
> -- message delivery logic ready
> starting error log relay
> ...done
> starting networking
> ...done
> starting direct_client
> ...done
> starting notify cluster nodes
> ...done
>
> broker running
>
> Cheers,
>
> Brian
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120315/5662ea5f/attachment.htm>