AhMaD AbUIeSa
AhMaD AbUIeSa

Reputation: 815

Rabbitmq service not reachable within k3s pods?

I have the following setup: k3s installation and istio as ingress controller,

problem we face that rabbitmq service is not reachable from within pods internally.

Any idea why this is happening though I have another port from inside that rabbitmq service exposed via 443 and it respond back fine [ that's just to rule out DNS issues ]

Upvotes: 0

Views: 506

Answers (1)

Hemanth Kumar
Hemanth Kumar

Reputation: 3772

The connection error:111 is might be due to below concerns and can you check on this :

  • Check whether the Port 5671 is open or blocked by using nmap or telnet.
  • Check if there are any firewalls blocking this port/host. Try to disable the firewall and have a check
  • Seems to be your istio is having SSL certificate enabled - this blocking the port 5671 to reach the connection. Can you disable the SSL certificate and have a check. If it is connected then SSL certificate is the reason which is blocking this. In this case you need to make sure 5671 Port should accept the SSL certificate. If there is no SSL certificate enabled then the first two points might be the reason.
  • Can you try by using this command echo | openssl s_client -connect <hostname>:<port> | head

Refer to this RabbitMQ troubleshooting doc for more information

Upvotes: 0

Related Questions