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

Brian Jing brian.newsgroup at gmail.com
Thu Mar 15 00:08:09 GMT 2012

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

Content of my new rabbitmq.conf:

# cat /etc/rabbitmq/rabbitmq-2.7.1.config
    {rabbit, [
        {ssl_listeners, [{"",4445}]},
        {ssl_options, [
            {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
starting worker pool
starting database
starting codec correctness check
-- external infrastructure ready
starting plugin registry
starting auth mechanism cr-demo
starting auth mechanism amqplain
starting auth mechanism plain
starting statistics event manager
starting logging server
starting exchange type direct
starting exchange type fanout
starting exchange type headers
starting exchange type topic
-- kernel ready
starting alarm handler
starting node monitor
starting cluster delegate
starting guid generator
starting memory monitor
-- core initialized
starting empty DB check
starting exchange, queue and binding recovery
starting mirror queue slave sup
starting adding mirrors to queues
-- message delivery logic ready
starting error log relay
starting networking
starting direct_client
starting notify cluster nodes

broker running


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120315/3e4d7b74/attachment.htm>

More information about the rabbitmq-discuss mailing list