<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.E-MailFormatvorlage19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="DE" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">Kind regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US">Ulrich Windl<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>From:</b> Users <users-bounces@clusterlabs.org> <b>On Behalf Of
</b>jayf@wheeling-nipponsteel.com<br>
<b>Sent:</b> Friday, April 25, 2025 2:45 PM<br>
<b>To:</b> users@clusterlabs.org<br>
<b>Subject:</b> [EXT] [ClusterLabs] Any node rebooting with 8x module stops all nodes<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Greeting,</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">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.</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I have a 3 node cluster for running DRBD and VMs. All are Debian12. Two are "disk" nodes, the third is "diskless"</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Debian packs the old 8.x version of the DRBD kernel modules, so I compile the 9.2 branch modules from source.</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">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.</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">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.</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">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.</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">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.</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">But it appears that Pacemaker must come up before this process is done.</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Any help is appreciated.</span><br>
<br>
<b><span style="font-size:12.0pt;font-family:"Arial",sans-serif">Jay Fluharty</span></b><br>
<i><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Network Analyst</span></i><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Wheeling-Nippon Steel Inc.</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">PO Box 635</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Follansbee, WV 26037</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">jayf@wheeling-nipponsteel.com</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">1-304-527-4819</span><o:p></o:p></p>
</div>
</div>
</body>
</html>