RabbitMQ Shovel plugin stuck on "starting" status -


The rabbit MQ starts just fine, but the shovel plugin status is listed as "Start".

I am using the following rabbitmq.config:

Each broker is running on a different AWS example. Remote server is Windows 2008 server, the local server is Amazon Linux. <{rabbitmq_shovel, [{shovels, [{scrape_request_shovel, [{source, [broker, "amqp: // test_user: test_password @ localhost"}]}, {destinations , [{Broker, "amqp: // test_user: test_password @ ec2 - ### - ## - ### - ### pub1-1 Amazonaws.com"}]}, {qi, & lt; & Lt; "scp_request"> gt; & Gt;}, {ack_mode, on_confirm}, {publish_properties, [{delivery_mode, 2})}, {publish_fields, [{exchange, and lieutenant; & Lt; "" & Gt; & Gt;}, {routing_key, & lt; & Lt; "Scp_request" & gt; Returns:

According to [{scrape_request_shovel, start, {{2012,7,11}, {23,38,47}}}

, the result may be that the user is correct on two brokers Have not been installed in the manner. However, I have checked twice that I have installed the user correctly on both machines through rubbitmusic user- it has also tried with a different set of users to make sure.

I also ran a NMAP scan of port 5672 on the remote host to host port and is running on that port.

UPDATE The problem has not been solved but it seems to be a result of connection problems with the remote server. I have 0 in my config file " Reconnect_delay ", so do not reuse the connection from the shovel endlessly. Highly recommend this problem to other people as well, because it allows you to receive error messages from rabbit_shovel_status. In my case, I got the following error:

  [{scrape_request_shovel, {abort, {{badmatch, {error, access_refused}}, [{rabbit_shovel_worker, make_conn_and_chan, 1}, {{ {20127,12}, {0,4,37}}}]   By answering your question here, if others have to face this issue then this error (and this too) There is a timeout error that you receive it, {{badmatch, {error, etimedout}}), there is almost certainly a communication problem between two machines, which means that port access / firewall settings The reason is most likely.  

What was the silent things I was doing here:

1) My remote EC2 was using the wrong DNS for example (D. Oh! Really dumb - what not I can tell you that for a long time I spent my head against the wall on this one ...). Remember that pausing and starting your instance creates a new DNS, if you do not have an elastic IP with an example.

2) My remote example is a Windows server, and I realized that you have to open up port 5672 both in Windows Firewall and EC2 security groups - There are overlapping levels, and opening the port in EC2 Management Console is not enough if your machine windows are on server EC2, as you have to configure the Windows Server firewall.

Comments

Popular posts from this blog

Python SQLAlchemy:AttributeError: Neither 'Column' object nor 'Comparator' object has an attribute 'schema' -

java - How not to audit a join table and related entities using Hibernate Envers? -

mongodb - CakePHP paginator ignoring order, but only for certain values -