When does RabbitMQ log "RabbitMQ is asked to stop"? #12534
-
Community Support Policy
RabbitMQ version used3.13.7 Erlang version used26.2.x Operating system (distribution) usedUbuntu 24.04.1 LTS How is RabbitMQ deployed?Debian package rabbitmq-diagnostics status outputLogs from node 2 (if applicable, with sensitive values edited out)See https://www.rabbitmq.com/docs/logging to learn how to collect logs Logs from node 3 (if applicable, with sensitive values edited out)See https://www.rabbitmq.com/docs/logging to learn how to collect logs rabbitmq.confSee https://www.rabbitmq.com/docs/configure#config-location to learn how to find rabbitmq.conf file location Steps to deploy RabbitMQ clusterNormally Steps to reproduce the behavior in questionI am checking advanced.configSee https://www.rabbitmq.com/docs/configure#config-location to learn how to find advanced.config file location Application code# PASTE CODE HERE, BETWEEN BACKTICKSKubernetes deployment file# Relevant parts of K8S deployment that demonstrate how RabbitMQ is deployed
# PASTE YAML HERE, BETWEEN BACKTICKSWhat problem are you trying to solve?Due to automatic restart all my client application went down |
Beta Was this translation helpful? Give feedback.
Answered by
gomoripeti
Oct 17, 2024
Replies: 3 comments 1 reply
-
|
Hi the log line "RabbitMQ is asked to stop..." suggests that RabbitMQ did not crash, there was no error but it was instructed to stop externally. You can try to think about what other component or human could have asked RabbitMQ to stop (RabbitMQ does not ask itself to stop, especially in a single node scenario) |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
michaelklishin
-
|
@tousif-hub as @gomoripeti already explained, the error message means that the node was instructed to shut down using Nothing in the provided log suggests that the node "has crashed". Someone or something has told it to stop. RabbitMQ nodes may choose to do an equivalent of |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi all, Thanks for your above input. 2024-10-17 06:28:38.042265+05:30 [error] <0.985692.0> operation none caused a connection exception connection_forced: "broker forc |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
@tousif-hub the message is reasonably specific. A client connection was forcibly closed because the node was told to shut down. RabbitMQ notifies clients via a connection errors instead of silently letting the kernel close the TCP connection. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi
the log line "RabbitMQ is asked to stop..." suggests that RabbitMQ did not crash, there was no error but it was instructed to stop externally. You can try to think about what other component or human could have asked RabbitMQ to stop (RabbitMQ does not ask itself to stop, especially in a single node scenario)