Hi Miroslav,
Thank you for your helpful suggestions! I followed your advice and used the pcs
command with the -f option to create the cluster CIB configuration, and then
pushed it using pcs cluster cib-push.
I'm happy to report that the configuration time has been significantly reduced!
The res
efore=shutdown.target reboot.target halt.target
```
After making this modification, the issue no longer occurs during reboot.
chenzu...@gmail.com
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home:
not
designed to handle this scenario?
Other：
The configuration of corosync.conf can be found in the attached file
corosync.conf.
Other relevant information is available in the attached file log.txt.
The script used for the up/down testing is attached as ip_up_and_down.sh.
chenzu
efore=shutdown.target reboot.target halt.target
```
After making this modification, the issue no longer occurs during reboot.
chenzu...@gmail.com
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home:
e: 1739893594, last update node:
lustre-oss-node28, last update device: vdy
chenzu...@gmail.com
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
://wiki.lustre.org/LNet_Router_Config_Guide.
chenzu...@gmail.com
From: users-request
Date: 2025-03-14 17:48
To: users
Subject: Users Digest, Vol 122, Issue 3
Send Users mailing list submissions to
users@clusterlabs.org
To subscribe or unsubscribe via the World Wide Web, visit
https
s-node32
nodeid: 4
}
}
quorum {
provider: corosync_votequorum
}
logging {
to_logfile: yes
logfile: /var/log/cluster/corosync.log
to_syslog: yes
timestamp: on
}
chenzu...@gmail.com
___
Manage your subscription:
htt
