Early systemd bugs caused dbus issues and session files not being cleaned
up properly. At least EL 7.4 or older were affected.
What is your OS and version?
P.S.: I know your pain. I am still fighting to explain that without planned
downtime, the end users will definitely get
On 7/29/20 10:39 AM, Reid Wahl wrote:
> Hi,
>
> It looks like this is a bug that was fixed in later releases. The
> `path` variable was a null pointer when it was passed to
> `systemd_unit_exec_with_unit` as the `unit` argument. Commit 62a0d26a
>
Hi Reid Wahl,
There are more log informations below. The reason seems to be that
communication with DBUS timed out. Any suggestions?
1672712 Jul 24 21:20:17 [3945305] B0610011 lrmd: info:
pcmk_dbus_timeout_dispatch:Timeout 0x147bbd0 expired
1672713 Jul 24 21:20:17 [3945305]
Hi,
It looks like this is a bug that was fixed in later releases. The `path`
variable was a null pointer when it was passed to
`systemd_unit_exec_with_unit` as the `unit` argument. Commit 62a0d26a
RPM Version Information:
corosync-2.3.4-7.el7_2.1.x86_64
pacemaker-1.1.12-22.el7.x86_64
Coredump file backtrace:
```
warning: .dynamic section for "/lib64/libk5crypto.so.3" is not at the expected
address (wrong library or version mismatch?)
Missing separate debuginfo for
Try: yum
