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.
Related
Below are the commands executed and error stack:
[root#DGTLSITTIBCO2 ~]# rabbitmqctl join_cluster rabbit#DGTLSITTIBCO1
Clustering node rabbit#DGTLSITTIBCO2 with rabbit#DGTLSITTIBCO1 Error:
unable to perform an operation on node 'rabbit#DGTLSITTIBCO1'. Please
see diagnostics information and suggestions below.
Most common reasons for this are:
Target node is unreachable (e.g. due to hostname resolution, TCP connection or firewall issues)
CLI tool fails to authenticate with the server (e.g. due to CLI tool's Erlang cookie not matching that of the server)
Target node is not running
In addition to the diagnostics info below:
See the CLI, clustering and networking guides on rabbitmq documentation to learn more
Consult server logs on node rabbit#DGTLSITTIBCO1
DIAGNOSTICS
attempted to contact: [rabbit#DGTLSITTIBCO1]
rabbit#DGTLSITTIBCO1:
connected to epmd (port 4369) on DGTLSITTIBCO1
epmd reports node 'rabbit' uses port 25672 for inter-node and CLI tool traffic
TCP connection succeeded but Erlang distribution failed
TCP connection to remote host has timed out. Is the Erlang distribution using TLS?
Current node details:
node name: rabbitmqcli57#DGTLSITTIBCO2
effective user's home directory: /var/lib/rabbitmq
Erlang cookie hash: ci1chJoiyrDKCLOj2TDxaA==
Please see my answer in the rabbitmq-users mailing list. In short, your Erlang cookies are most likely not synchronized.
Generally, it's not very helpful to paste an error into your message without any other information. The people helping out on this list like to know what version of RabbitMQ and Erlang you're using and on what operating system, and a description of what you're trying to do.
Anyway, in this case, your issue is one of the most commonly reported on this list. If you search for the string Error: unable to perform an operation on node, you'll see many replies with suggestions on how to fix your issue.
The RabbitMQ team also maintains documentation, including a troubleshooting document: https://www.rabbitmq.com/troubleshooting.html
You should also read the Clustering Guide, specifically this section: https://www.rabbitmq.com/clustering.html#erlang-cookie
I am frequently getting the below mentioned errors, the dll version used in the project is - 1.0.488.0
System.TimeoutException: Timeout performing GET
StackExchange.Redis.RedisConnectionException: No connection is available to service this operation: GET
No connection is available to service this operation: EXISTS
Can anyone help me out in figuring what the issue can be?
Have also created an issue on StackExchange's Github repo for the same
Issue created on Github for the same
It looks like your connection broke. And when it did, any commands already sent to Redis would have timed out on the client application, even though they could have executed on the server. If you upgrade to a later version of the StackExchange.Redis client, you will get richer diagnostics information about what the state of the threadpool, CPU etc was on the client application side.
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.
I start to use tsung to test my server with socket.io.
I downloaded the Github Zip, compiled and installed the latest "dev" including Websockets compatibility.
After browsing a lot of Google results and message in this mailing list, I couldn't find any answer to my issue. My problem is that I can't send/receive a message to my socket.io server. I'm able to connect to my socket with handshaking OK but nothing happens when I send the message. I tried to use bidir=true attribute but nothing change.
In my tsung log, I've got this messages:
=INFO REPORT==== 5-Sep-2013::08:08:00 ===
ts_client:(7:<0.93.0>) connect to port 80
=INFO REPORT==== 5-Sep-2013::08:08:00 ===
ts_client:(3:<0.93.0>) Data receive from socket in state think, stop
In my socket log (server side), I've got this messages:
debug: client authorized for
info: transport end (undefined)
debug: cleared heartbeat interval for client b07GKwmOJPQVDwznBzN1
debug: discarding transport
You can find my tsung.xml file here: http://pastebin.com/A60PpKrL
Please help,
Kind Regards,
Arnaud
try the 1.5.1 version as its "stable" and your using a bleeding edge build.
Also, try and tcpdump and tell me what you see, maybe use pastebin to show me the request.
Glassfish 3.1.2
Ubuntu 12.04
I've created a cluster of two nodes and have a JMS queue.
I'm having issues trying to connect to this JMS queue using a remote standalone client.
The cluster JMS listener is on port 27676 and the queue is deployed to the cluster.
mq://Glassfish2:27676/,mq://Glassfish3:27676
When I connect using the code I'd use to connect to a stand alone instance the message is not received by the cluster.
I believe it is using the default 7676 port. When the IIOP port is changed to use port 23700 which is the one the cluster (DAS) is using I get a connection refused exception as it is trying to connect to localhost:27676. At least it's the right port.
WARNING: [C4003]: Error occurred on connection creation [localhost:27676]. - cause: java.net.ConnectException: Connection refused: connect
I've also updated the following values in node config file (domain.xml) to remove references to localhost. jms-host and node-host values.
I had this issue before with a stand alone instance and it was resolved by adding entries to the /etc/hosts file. However, this does not seem to resolve the issue.
I also have all server instance IPs in the hosts file.
Am I missing something very basic here?
Any help would be greatly appreciated.
Thanks
If you look log files under
${glassfish_home}/glassfish/nodes/cluster-name/instance-name/imq/instances/instance-name/log
folder, you will see that
master brockers does not match
Every your node has different master brockers, probably every node know its own brocker as master brocker..
I had the same error and after a few days find this..