Pacemaker Managed Systemd Resource Operations Time Out and Become Unresponsive
Issue
- Each node in an N-node pacemaker cluster has seen the following error in
pacemaker.log:
lrmd: info: pcmk_dbus_find_error: GetUnit error 'org.freedesktop.DBus.Error.NoReply': Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
- After some of these events it seems that the pacemaker log indicates that the clustered services may have been cycled off and then turned back on.
Environment
- RHEL 7
- systemd
- pacemaker version < pacemaker-1.1.10-32.el7_0.1
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.