[rabbitmq-discuss] Problems starting RabbitMQ as a windows service.

Richard Hudson richard.hudson at paragon.co.nz
Mon Aug 15 00:26:32 BST 2011


We've recently moved over to using RabbitMQ from MSMQ and have generally had
success in running RabbitMQ as a windows service on a number of different
OSes (XP, Windows2003, Windows 7).

However, we've come across a strange problem when starting up a rabbitMQ
service on Windows 2003 SP2 on a VM, using RabbitMQ 2.51 and Erlang 5.8.4.
Not sure if the VM aspect is relevant.

Using the rabbitmq-service.bat to install the service, the service (running
under the local system account) starts and stops pretty much straight away.
Here's the output from rabbitMQ.debug
-- rabbit boot start
starting file handle cache server
starting worker pool
starting database
starting codec correctness check
-- external infrastructure ready
starting statistics event manager
starting logging server
starting plugin registry
starting auth mechanism amqplain
starting auth mechanism cr-demo
starting auth mechanism plain
starting exchange type direct
starting exchange type fanout
starting exchange type headers
starting exchange type topic
-- kernel ready
starting node monitor
starting cluster delegate
starting guid generator
starting alarm handler
starting memory monitor
-- core initialized
starting empty DB check
starting exchange, queue and binding recovery
-- message delivery logic ready
starting error log relay
starting networking
Reason: {badmatch,


                             "TCP Listener"]},
Stacktrace: [{rabbit_networking,start_listener0,4},
in message_loop
win32sysinfo:Erlang has closed.Eshell V5.8.4  (abort with ^G)
(rabbit at UKFAST-QOB4QITU)1> {"Kernel pid

The port is definitely not in use. Nor is there a firewall enabled.

Having looked though the archives we've tried passing in sname and name
arguments to erl.exe with no luck.

The interesting thing is that we can get RabbitMQ to run as an application
on this box, using the standard rabbitmq-server.bat.

After a bit of messing around we also found that if we set
to point to D:\Program Files\erl5.8.4\bin\erl.exe rather than D:\Program
Files\erl5.8.4\erts-5.8.4\bin\erl.exe then the service also runs. Queues get
created and we can successfully publish/subscribe to queues .

Does anyone have any thoughts on why the standard service install would fail
but the application and modified install seem to work fine.

How safe is it to use erl.exe from erl5.8.4\bin\erl.exe rather than
i.e is this an acceptable workaround.

Thanks in advance for any help.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110815/90cb0e8c/attachment.htm>

More information about the rabbitmq-discuss mailing list