From 97096e0a29fca0bc5194a8b5d7950bc244963267 Mon Sep 17 00:00:00 2001 From: Jan Gutter Date: Fri, 26 Jul 2019 17:46:44 +0200 Subject: [PATCH] Fix benign epmd@0.0.0.0.socket failure * The restart loop for rabbitmq-server can trigger socket activation of epmd without rabbitmq-server running. This can lead to 'systemctl status' reporting 'State: degraded' with no simple way to reset to 'State: running'. * It's important to note that this socket activation failure is benign and is not an indicator of system failure. Change-Id: Iede4f5ebeffb59644dee4a17b6331b3cdd04d146 Signed-off-by: Jan Gutter --- lib/rpc_backend | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/lib/rpc_backend b/lib/rpc_backend index 1c7c82fcd3..743b4ae170 100644 --- a/lib/rpc_backend +++ b/lib/rpc_backend @@ -66,7 +66,12 @@ EOF sudo systemctl restart epmd.socket epmd.service fi if is_fedora || is_suse; then - sudo systemctl enable rabbitmq-server + # NOTE(jangutter): If rabbitmq is not running (as in a fresh + # install) then rabbit_setuser triggers epmd@0.0.0.0.socket with + # socket activation. This fails the first time and does not get + # cleared. It is benign, but the workaround is to start rabbitmq a + # bit earlier for RPM based distros. + sudo systemctl --now enable rabbitmq-server fi fi }