1. devstack
  2. Commit 97096e0a29fca0bc5194a8b5d7950bc244963267
Browse code

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 <jan.gutter@netronome.com>

Jan Gutter authored on 2019/07/27 00:46:44
Showing 1 changed files
lib/rpc_backend
History View file @ 97096e0
... ... 
@@ -66,7 +66,12 @@ EOF
66 66 
             sudo systemctl restart epmd.socket epmd.service
67 67 
         fi
68 68 
         if is_fedora || is_suse; then
69 
-            sudo systemctl enable rabbitmq-server
69 
+            # NOTE(jangutter): If rabbitmq is not running (as in a fresh
70 
+            # install) then rabbit_setuser triggers epmd@0.0.0.0.socket with
71 
+            # socket activation. This fails the first time and does not get
72 
+            # cleared. It is benign, but the workaround is to start rabbitmq a
73 
+            # bit earlier for RPM based distros.
74 
+            sudo systemctl --now enable rabbitmq-server
70 75 
         fi
71 76 
     fi
72 77 
 }