[pve-devel] [RFC pve-cluster] start pmxcfs only after corosync is started

Thomas Lamprecht t.lamprecht at proxmox.com
Tue Sep 29 16:35:55 CEST 2015


This should get rid of some errors when rebooting nodes, especially
when rebooting all nodes at the same time.
Errors like:
'pmxcfs[..]: [dcdb] crit: cpg_initialize failed: 2'
at boot, or endlessly thrown errors like:
'pmxcfs[..]: [status] crit: cpg_send_message failed: 9'
should more or less disappear.

Restarting the pve-cluster.service to get rid off the mentioned
errors and to let the node reconnect to the corosync cluster
shouldn't be necessary anymore.

Signed-off-by: Thomas Lamprecht <t.lamprecht at proxmox.com>
---
 debian/pve-cluster.service | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/pve-cluster.service b/debian/pve-cluster.service
index d3e7b09..bab1c7d 100644
--- a/debian/pve-cluster.service
+++ b/debian/pve-cluster.service
@@ -3,7 +3,7 @@ Description=The Proxmox VE cluster filesystem
 ConditionFileIsExecutable=/usr/bin/pmxcfs
 Wants=corosync.service
 Wants=systemd-timesyncd.service
-Before=corosync.service
+After=corosync.service
 After=network.target
 After=sys-fs-fuse-connections.mount
 After=systemd-timesyncd.service
-- 
2.1.4




More information about the pve-devel mailing list