Hi,
FAILED
Reason: {error,
{timeout_waiting_for_tables, ....
That's usually caused by firewall or networking issues (that error means
the node is having trouble contacting the other nodes).

Is the cluster running on a single machine, or on different
machines? If the latter, could you check that 1) networking works when
RabbitMQ tries to start up at boot and 2) that it can contact the other
nodes?

Cheers,
Alex
On Mon, Dec 19, 2011 at 03:07:55PM +0600, evkdev at gmail.com wrote:
Hi! I have a problem with running RabbitMQ as windows service. I have a cluster with 3 nodes and everything works fine if run rabbit with ?rabbitmq-server start ?detached?. I also able to run it as windows service under Administrator account. But after reboot, RabbitMQ service fails to start.
In Event Log there is an entry: ?RabbitMQ: Erlang machine voluntarily stopped. The service is not restarted as OnFail is set to ignore?.
In rabbit logs I see this:
FAILED
Reason: {error,
{timeout_waiting_for_tables, ....
Whatever I tried ? nothing helps to resolve this issue. If I log in after reboot, and start RabbitMQ service manually ? everything works fine.
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss at lists.rabbitmq.com
https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

Search Discussions

Discussion Posts

Previous

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 2 of 2 | next ›
Discussion Overview
grouprabbitmq-discuss @
categoriesrabbitmq
postedDec 19, '11 at 9:07a
activeDec 21, '11 at 4:50p
posts2
users2
websiterabbitmq.com
irc#rabbitmq

2 users in discussion

Alexandru Scvorţov: 1 post Evkdev: 1 post

People

Translate

site design / logo © 2018 Grokbase