One of the Pod is going in crash loop back off error when i tried to deploy this template. The other pod is running and is ready.
Error in logs: Connection attempt from disallowed node 'rabbitmqcli-1384-rabbit@rabbitmq-cluster-1.rabbitmq-cluster.rabbitmq-ha.svc.cluster.local'
In events: (combined from similar events): Readiness probe failed: Error: unable to perform an operation on node 'rabbit@rabbitmq-cluster-1.rabbitmq-cluster.rabbitmq-ha.svc.cluster.local'. 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 https://rabbitmq.com/documentation.html to learn more Consult server logs on node rabbit@rabbitmq-cluster-1.rabbitmq-cluster.rabbitmq-ha.svc.cluster.local If target node is configured to use long node names, don't forget to use --longnames with CLI tools DIAGNOSTICS =========== attempted to contact: ['rabbit@rabbitmq-cluster-1.rabbitmq-cluster.rabbitmq-ha.svc.cluster.local'] rabbit@rabbitmq-cluster-1.rabbitmq-cluster.rabbitmq-ha.svc.cluster.local: connected to epmd (port 4369) on rabbitmq-cluster-1.rabbitmq-cluster.rabbitmq-ha.svc.cluster.local epmd reports node 'rabbit' uses port 25672 for inter-node and CLI tool traffic TCP connection succeeded but Erlang distribution failed suggestion: check if the Erlang cookie identical for all server nodes and CLI tools suggestion: check if all server nodes and CLI tools use consistent hostnames when addressing each other suggestion: check if inter-node connections may be configured to use TLS. If so, all nodes and CLI tools must do that suggestion: see the CLI, clustering and networking guides on https://rabbitmq.com/documentation.html to learn more Current node details: node name: 'rabbitmqcli-492-rabbit@rabbitmq-cluster-1.rabbitmq-cluster.rabbitmq-ha.svc.cluster.local' effective user's home directory: /var/lib/rabbitmq Erlang cookie hash: 6ofCpuGcLssmT/U34mLOFg==
One of the Pod is going in crash loop back off error when i tried to deploy this template. The other pod is running and is ready.
Error in logs: Connection attempt from disallowed node 'rabbitmqcli-1384-rabbit@rabbitmq-cluster-1.rabbitmq-cluster.rabbitmq-ha.svc.cluster.local'
In events: (combined from similar events): Readiness probe failed: Error: unable to perform an operation on node 'rabbit@rabbitmq-cluster-1.rabbitmq-cluster.rabbitmq-ha.svc.cluster.local'. 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 https://rabbitmq.com/documentation.html to learn more Consult server logs on node rabbit@rabbitmq-cluster-1.rabbitmq-cluster.rabbitmq-ha.svc.cluster.local If target node is configured to use long node names, don't forget to use --longnames with CLI tools DIAGNOSTICS =========== attempted to contact: ['rabbit@rabbitmq-cluster-1.rabbitmq-cluster.rabbitmq-ha.svc.cluster.local'] rabbit@rabbitmq-cluster-1.rabbitmq-cluster.rabbitmq-ha.svc.cluster.local: connected to epmd (port 4369) on rabbitmq-cluster-1.rabbitmq-cluster.rabbitmq-ha.svc.cluster.local epmd reports node 'rabbit' uses port 25672 for inter-node and CLI tool traffic TCP connection succeeded but Erlang distribution failed suggestion: check if the Erlang cookie identical for all server nodes and CLI tools suggestion: check if all server nodes and CLI tools use consistent hostnames when addressing each other suggestion: check if inter-node connections may be configured to use TLS. If so, all nodes and CLI tools must do that suggestion: see the CLI, clustering and networking guides on https://rabbitmq.com/documentation.html to learn more Current node details: node name: 'rabbitmqcli-492-rabbit@rabbitmq-cluster-1.rabbitmq-cluster.rabbitmq-ha.svc.cluster.local' effective user's home directory: /var/lib/rabbitmq Erlang cookie hash: 6ofCpuGcLssmT/U34mLOFg==