I've set up my Rabbitmq on a host and now when I click on "Federation Status" I get: Error detail:econnrefused.
Log doesn't show much either, how can I narrow it down and figure out what the problem is?
Thanks
'econnrefused' is erlang's tcp module error message, means tcp connection has been refused.
You can adjust the rabbitmq's configure file for printing rabbitmq's connection info message.
It may be related to firewall configuration or plugin problem.
You should spend time for understanding where is rabbitmq's configuration file and how to adjust it and where is log output carefully.
Related
I am new to rabbitmq and would appreciate help in the issue I am facing.
I have deployed rabbitmq using the rabbitmq cluster k8s operator on openshift which is hosted on Azure. (This is the guide I referred to deploy the operator).
The operator and cluster is up and running, also able to access the management UI on localhost:15672.
But when I describe the pod, it shows the warning of readiness probe failed:
dial tcp <IP>:5672 connect: connection refused
Due to this, when I try to run the rabbitmq hello world tutorial, it fails with the error:
connect ETIMEDOUT 172.30.69.51:5672
errno: -4039
code: 'ETIMEDOUT'
syscall:'connect'
address: 172.30.69.51
port:5672
(172.30.69.51 is the clusterIP)
From the management UI, I am able to create new exchange, queue and binding and send & publish msgs.
PS. apologies if the conversation format is incorrect, pls feel free to correct me and I'll take care from next time. Thank you.
I setup rabbit-mq cluster version 3.8.2 .
I enabled Prometheus module in all rabbit to scrape data out of it for monitoring.
my alert system constantly shows that the rabbit is down but its not.
anyone can help me with that.
problem to scrape rabbitmq on rabbitmq1:15692 for more than 10 minutes. Node seems down.
Have you checked port 15692 in the RabbitMQ node? It will probably show you that the connection is refused.
I would recommend monitoring port 5672 to make sure your node is up. But you can also have problems with RabbitMQ, given that the prometheus plugin does not work correctly and the port is not always answered.
I see that my custom Spring cloud stream sink with log sink stream app dependency loses RabbitMQ connectivity during RabbitMQ outage, tries making a connection for 5 times and then stops its consumer. I have to manually restart the app to make it successfully connect once the RabbitMQ is up. When I see the default properties of rabbitMQ binding here, it gives interval time but there is no property for infinite retry(which i assume to be default behaviour). Can someone please let me know what I might be missing here to make it try connecting infinitely ?
Error faced during outage triggering consumer retry :
2017-08-08T10:52:07.586-04:00 [APP/PROC/WEB/0] [OUT] Caused by: com.rabbitmq.client.ShutdownSignalException: channel error; protocol method: #method<channel.close>(reply-code=404, reply-text=NOT_FOUND - home node 'rabbit#229ec9f90e07c75d56a0aa84dc28f602' of durable queue 'datastream.dataingestor.datastream' in vhost '8880756f-8a21-4dc8-9b97-95e5a3248f58' is down or inaccessible, class-id=50, method-id=10)
It appears you have a RabbitMQ cluster and the queue in question is hosted on a down node.
If the queue was HA, you wouldn't have this problem.
The listener container does not (currently) handle that condition. It will retry for ever if it loses connection to RabbitMQ itself.
Please open a JIRA Issue and we'll take a look. The container should treat that error the same as a connection problem.
Folks,
Apache-Camel does not seem to support AMQPs when connecting to Rabbit. Does anyone know if this is somewhere in the pipeline to be built?
When attempting all connections, we get this in Rabbit logs:
error on AMQP connection <0.30060.4>: {ssl_upgrade_error,timeout} (unknown POSIX error)
Thanks!
Current RabbitMQ Camel Component does not support any SSL configuration features. Also, if you take a look to their JIRA it seems there is no ticket open for implementing this (Camel Jira for RabbitMQ Tickets)
You can fill a ticket or, even better, you could modify the existent component to support SSL and donate it to the open source community. If you plan to do this, please read Apache Camel: Contributing
I'm a fairly new user of ActiveMQ and I'm looking for a way to get detailed debug information on the client side of a queue connection. My problem is this: I have a server that is sending a message through a queue to a client. Using the admin web page associated with the broker, I can verify the following: the queue was created, there is a consumer associated with the queue, the message has been enqueued, the message has been dispatched, the dispatched queue size is 1, the message has not been dequeued. This setup was working yesterday but mysteriously stopped working today even though I did a restart of the activemq service. The log file at /var/log/activemq.log does not contain any useful information.
At this point I'm stumped; I'm assuming that there is some sort of problem with the configuration, but it hasn't changed since yesterday. Does anybody have a suggestion about what my next step should be?
Turn on debug (or even trace) logging in the broker first of all in conf/log4j.properties.
log4j.logger.org.apache.activemq=DEBUG
restart the broker and re-run your scenario. The logging will hopefully provide you with some information.
Jconsole is also a useful tool to monitor the running broker.
Does your client use any message filters?
You can also enable remote debugging and then connect with an IDE.
To start remote debugging execute
$ ACTIVEMQ_DEBUG=true bin/activemq
and then start a remote debugger to connect to port 5005