I guess the issue is mostly about how to manage custom updates replacing some standard packages using Debian. Maybe superuser.com (https://stackoverflow.com/questions/tagged/debian) is a place to ask.
Kind regards, Ulrich Windl From: Users <users-boun...@clusterlabs.org> On Behalf Of j...@wheeling-nipponsteel.com Sent: Friday, April 25, 2025 2:45 PM To: users@clusterlabs.org Subject: [EXT] [ClusterLabs] Any node rebooting with 8x module stops all nodes Greeting, Forgive me if this is the wrong spot to ask, because this involve pacemaker and DRBD, I'm not sure which direction to go for help. I have a 3 node cluster for running DRBD and VMs. All are Debian12. Two are "disk" nodes, the third is "diskless" Debian packs the old 8.x version of the DRBD kernel modules, so I compile the 9.2 branch modules from source. Here is my issue, which I'm sure someone else has run into before. If the kernel has been upgraded, and a node is rebooted, it tries coming up with the 8.x driver. This of course doesn't work with a 3 node DRBD cluster. The problem is that it wreaks havoc with the whole cluster and the VMs end up failing and are offline. I would hope that if the rebooted node was a "secondary", that the "primary" would be okay to continue with perhaps some error. However, that is not the case. I have gone so far as write a script that is called by cron on reboot to check for the version of the module and if it's 8.x it builds/installs the new module. But it appears that Pacemaker must come up before this process is done. Any help is appreciated. Jay Fluharty Network Analyst Wheeling-Nippon Steel Inc. PO Box 635 Follansbee, WV 26037 j...@wheeling-nipponsteel.com 1-304-527-4819
_______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
