<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Dec 21, 2022 at 11:26 AM Reid Wahl <<a href="mailto:nwahl@redhat.com">nwahl@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Wed, Dec 21, 2022 at 2:15 AM Ulrich Windl<br>
<<a href="mailto:Ulrich.Windl@rz.uni-regensburg.de" target="_blank">Ulrich.Windl@rz.uni-regensburg.de</a>> wrote:<br>
><br>
> Hi!<br>
><br>
> I wonder: Could the error message be triggered by adding an exclusive manatory<br>
> lock in the ip binary?<br>
> If that triggers the bug, I'm rather sure that the error message is bad.<br>
> Shouldn't that be EWOULDBLOCK then?<br>
<br>
I did some cursory reading earlier today, and it seems that ETXTBSY is<br>
becoming less common: <a href="https://lwn.net/Articles/866493/" rel="noreferrer" target="_blank">https://lwn.net/Articles/866493/</a><br>
<br>
Either way, that would be a question for kernel maintainers.<br></blockquote><div><br></div><div>Maybe network-stack-guys there or sbdy with deeper insight of how the ip-tool</div><div>is currently interfering with the kernel.</div><div>Without knowing any details certain things might be handled calling bpf-binaries</div><div>and ip being the userspace application this might still be shown if it was</div><div>actually rather about a bpf-binary to be executed. Thinking of race-conditions</div><div>at that front ...</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
> (I have no idea how Sophos AV works, though. If they open the files to check<br>
> in write-mode, it's really stupid then IMHO)<br>
><br>
> Regards,<br>
> Ulrich<br>
><br>
><br>
> >>> Reid Wahl <<a href="mailto:nwahl@redhat.com" target="_blank">nwahl@redhat.com</a>> schrieb am 21.12.2022 um 10:19 in Nachricht<br>
> <<a href="mailto:CAPiuu9-FiSqXAPf123ErsRWMWraKe2nnK6Pgwwfq4FmfSNxeYQ@mail.gmail.com" target="_blank">CAPiuu9-FiSqXAPf123ErsRWMWraKe2nnK6Pgwwfq4FmfSNxeYQ@mail.gmail.com</a>>:<br>
> > On Wed, Dec 21, 2022 at 12:24 AM Thomas CAS <<a href="mailto:tcas@ikoula.com" target="_blank">tcas@ikoula.com</a>> wrote:<br>
> >><br>
> >> Ken,<br>
> >><br>
> >> Antivirus (sophos-av) is running but not in "real time access scanning",<br>
> the<br>
> > scheduled scan is however at 9pm every day.<br>
> >> 7 minutes later, we got these alerts.<br>
> >> The anti virus may indeed be the cause.<br>
> ><br>
> > I see. That does seem fairly likely. At least, there's no other<br>
> > obvious candidate for the cause.<br>
> ><br>
> > I used to work on a customer-facing support team for the ClusterLabs<br>
> > suite, and we received a fair number of cases where bizarre issues<br>
> > (such as hangs and access errors) were apparently caused by an<br>
> > antivirus. In those cases, all other usual lines of investigation were<br>
> > exhausted, and when we asked the customer to disable their AV, the<br>
> > issue disappeared. This happened with several different AV products.<br>
> ><br>
> > I can't say with any certainty that the AV is causing your issue, and<br>
> > I know it's frustrating that you won't know whether any given<br>
> > intervention worked, since this only happens once every few months.<br>
> ><br>
> > You may want to either exclude certain files from the scan, or write a<br>
> > short script to place the cluster in maintenance mode before the scan<br>
> > and take it out of maintenance after the scan is complete.<br>
> ><br>
> >><br>
> >> I had the case on December 13 (with systemctl here):<br>
> >><br>
> >> pacemaker.log-20221217.gz:Dec 13 21:07:53 wd-websqlng01 pacemaker-controld<br>
><br>
> > [5082] (process_lrm_event) notice: wd-websqlng01-NGINX_monitor_15000:454 [<br>
><br>
> > /etc/init.d/nginx: 33: /lib/lsb/init-functions.d/40-systemd: systemctl: Text<br>
><br>
> > file busy\n/etc/init.d/nginx: 82: /lib/lsb/init-functions.d/40-systemd:<br>
> > /bin/systemctl: Text file busy\n ]<br>
> >> pacemaker.log-20221217.gz:Dec 13 21:07:53 wd-websqlng01 pacemaker-controld<br>
><br>
> > [5082] (process_lrm_event) notice: wd-websqlng01-NGINX_monitor_15000:454 [<br>
><br>
> > /etc/init.d/nginx: 33: /lib/lsb/init-functions.d/40-systemd: systemctl: Text<br>
><br>
> > file busy\n/etc/init.d/nginx: 82: /lib/lsb/init-functions.d/40-systemd:<br>
> > /bin/systemctl: Text file busy\n ]<br>
> >><br>
> >> After, this happens rarely, we had the case in August:<br>
> >><br>
> >> pacemaker.log-20220826.gz:Aug 25 21:06:31 wd-websqlng01 pacemaker-controld<br>
><br>
> > [3718] (process_lrm_event) notice:<br>
> > wd-websqlng01-NGINX-VIP-232_monitor_10000:2877 [<br>
> > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 1:<br>
> > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: uname: Text file<br>
> > busy\nocf-exit-reason:IPaddr2 only supported Linux.\n ]<br>
> >> pacemaker.log-20220826.gz:Aug 25 21:06:31 wd-websqlng01 pacemaker-controld<br>
><br>
> > [3718] (process_lrm_event) notice:<br>
> > wd-websqlng01-NGINX-VIP-231_monitor_10000:2880 [<br>
> > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 1:<br>
> > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: uname: Text file<br>
> > busy\nocf-exit-reason:IPaddr2 only supported Linux.\n ]<br>
> >><br>
> >> It's always around 9:00-9:07 pm,<br>
> >> I'll move the virus scan to 10pm and see.<br>
> ><br>
> > That also sounds like a good plan to confirm the cause :) It might<br>
> > take a while to find out though.<br>
> ><br>
> >><br>
> >> Thanks,<br>
> >> Best regards,<br>
> >><br>
> >> Thomas Cas | Technicien du support infogérance<br>
> >> PHONE : +33 3 51 25 23 26 WEB : <a href="http://www.ikoula.com/en" rel="noreferrer" target="_blank">www.ikoula.com/en</a><br>
> >> IKOULA Data Center 34 rue Pont Assy - 51100 Reims - FRANCE<br>
> >> Before printing this letter, think about the impact on the environment!<br>
> >><br>
> >> -----Message d'origine-----<br>
> >> De : Reid Wahl <<a href="mailto:nwahl@redhat.com" target="_blank">nwahl@redhat.com</a>><br>
> >> Envoyé : mardi 20 décembre 2022 20:34<br>
> >> À : Cluster Labs - All topics related to open-source clustering welcomed<br>
> > <<a href="mailto:users@clusterlabs.org" target="_blank">users@clusterlabs.org</a>><br>
> >> Cc : Ken Gaillot <<a href="mailto:kgaillot@redhat.com" target="_blank">kgaillot@redhat.com</a>>; Service Infogérance<br>
> > <<a href="mailto:infogerance@ikoula.com" target="_blank">infogerance@ikoula.com</a>><br>
> >> Objet : Re: [ClusterLabs] Bug pacemaker with multiple IP<br>
> >><br>
> >> [Vous ne recevez pas souvent de courriers de <a href="mailto:nwahl@redhat.com" target="_blank">nwahl@redhat.com</a>. Découvrez<br>
> > pourquoi ceci est important à <a href="https://aka.ms/LearnAboutSenderIdentification" rel="noreferrer" target="_blank">https://aka.ms/LearnAboutSenderIdentification</a><br>
> ]<br>
> >><br>
> >> On Tue, Dec 20, 2022 at 6:25 AM Thomas CAS <<a href="mailto:tcas@ikoula.com" target="_blank">tcas@ikoula.com</a>> wrote:<br>
> >> ><br>
> >> > Hello Ken,<br>
> >> ><br>
> >> > Thanks for your answer.<br>
> >> > There was no update running at the time of the bug, which is why I<br>
> thought<br>
> > that having too many IPs caused this type of error.<br>
> >> > The /usr/sbin/ip executable was not being modified either.<br>
> >> ><br>
> >> > We have many clusters, and only this one has so many IPs and this<br>
> problem.<br>
> >><br>
> >> How often does this happen, and is it reliably reproducible under any<br>
> > circumstances? Any antivirus software running? It'd be nice to check<br>
> > something like lsof or strace while it's happening, but that may not be<br>
> > feasible if it's sporadic; running those at every monitor would generate<br>
> lots<br>
> > of logs.<br>
> >><br>
> >> AFAICT, having multiple processes execute (or read) the `ip` binary<br>
> > simultaneously *shouldn't* cause problems, as long as nothing opens it for<br>
> > write.<br>
> >><br>
> >> ><br>
> >> > Best regards,<br>
> >> ><br>
> >> > Thomas Cas | Technicien du support infogérance<br>
> >> > PHONE : +33 3 51 25 23 26 WEB :<br>
> ><br>
> <a href="https://fra01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ikoula.c" rel="noreferrer" target="_blank">https://fra01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ikoula.c</a><br>
><br>
> ><br>
> om%2Fen&data=05%7C01%7Ctcas%<a href="http://40ikoula.com" rel="noreferrer" target="_blank">40ikoula.com</a>%7C9aab91944bd6454a773808dae2c13ae4%7C<br>
> ><br>
> cb7a4a4ea7f747cc931f80db4a66f1c7%7C0%7C0%7C638071616800939086%7CUnknown%7CTWF<br>
> ><br>
> pbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7<br>
> ><br>
> C3000%7C%7C%7C&sdata=oYe7ws2%2BPx3sMblOFBgkuXuSHTdguzB%2Flk83O5W2MjE%3D&reserve<br>
> > d=0<br>
> >> > IKOULA Data Center 34 rue Pont Assy - 51100 Reims - FRANCE Before<br>
> >> > printing this letter, think about the impact on the environment!<br>
> >> ><br>
> >> > -----Message d'origine-----<br>
> >> > De : Ken Gaillot <<a href="mailto:kgaillot@redhat.com" target="_blank">kgaillot@redhat.com</a>> Envoyé : lundi 19 décembre 2022<br>
> >> > 22:08 À : Cluster Labs - All topics related to open-source clustering<br>
> >> > welcomed <<a href="mailto:users@clusterlabs.org" target="_blank">users@clusterlabs.org</a>> Cc : Service Infogérance<br>
> >> > <<a href="mailto:infogerance@ikoula.com" target="_blank">infogerance@ikoula.com</a>> Objet : Re: [ClusterLabs] Bug pacemaker with<br>
> >> > multiple IP<br>
> >> ><br>
> >> > [Vous ne recevez pas souvent de courriers de <a href="mailto:kgaillot@redhat.com" target="_blank">kgaillot@redhat.com</a>.<br>
> >> > Découvrez pourquoi ceci est important à<br>
> >> > <a href="https://aka.ms/LearnAboutSenderIdentification" rel="noreferrer" target="_blank">https://aka.ms/LearnAboutSenderIdentification</a> ]<br>
> >> ><br>
> >> > On Mon, 2022-12-19 at 09:48 +0000, Thomas CAS wrote:<br>
> >> > > Hello Clusterlabs,<br>
> >> > ><br>
> >> > > I would like to report a bug on Pacemaker with the "IPaddr2"<br>
> >> > > resource:<br>
> >> > ><br>
> >> > > OS: Debian 10<br>
> >> > > Kernel: Linux wd-websqlng01 4.19.0-18-amd64 #1 SMP Debian 4.19.208-1<br>
> >> > > (2021-09-29) x86_64 GNU/Linux<br>
> >> > > Pacemaker version: 2.0.1-5+deb10u2<br>
> >> > ><br>
> >> > > You will find the configuration of our cluster with 2 nodes attached.<br>
> >> > ><br>
> >> > > Bug :<br>
> >> > ><br>
> >> > > We have several IP configured in the cluster configuration (12)<br>
> >> > > Sometimes the cluster is unstable with the following errors in the<br>
> >> > > pacemaker logs:<br>
> >> > ><br>
> >> > > Dec 18 21:07:51 **SENSITIVEDATA** pacemaker-execd [5079]<br>
> >> > > (operation_finished) notice: NGINX-VIP-<br>
> >> > > 232_monitor_10000:28835:stderr [<br>
> >> > > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 1:<br>
> >> > > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: ip: Text file busy ]<br>
> >> ><br>
> >> > This doesn't sound like a bug in the agent; "Text file busy" suggests<br>
> that<br>
> > the system "ip" command is being modified while the command is running. Is a<br>
><br>
> > software update happening when the problem occurs?<br>
> >> ><br>
> >> > I'm not sure whether there's some other situation that could cause that<br>
> > error, but simply executing the command a bunch of times simultaneously<br>
> > shouldn't cause it as far as I know.<br>
> >> ><br>
> >> > If simultaneous monitors is somehow causing the problem, you should be<br>
> able<br>
> > to work around it by using different intervals for different monitors.<br>
> >> ><br>
> >> > > Dec 18 21:07:51 **SENSITIVEDATA** pacemaker-execd [5079]<br>
> >> > > (operation_finished) notice: NGINX-VIP-<br>
> >> > > 239_monitor_10000:28877:stderr [<br>
> >> > > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 709:<br>
> >> > > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: ip: Text file busy ]<br>
> >> > > Dec 18 21:07:51 **SENSITIVEDATA** pacemaker-execd [5079]<br>
> >> > > (operation_finished) notice: NGINX-VIP-<br>
> >> > > 239_monitor_10000:28877:stderr [<br>
> >> > > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 1:<br>
> >> > > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: ip: Text file busy ]<br>
> >> > > Dec 18 21:07:51 **SENSITIVEDATA** pacemaker-execd [5079]<br>
> >> > > (operation_finished) notice: NGINX-VIP-<br>
> >> > > 234_monitor_10000:28830:stderr [<br>
> >> > > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 1:<br>
> >> > > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: ip: Text file busy ]<br>
> >> > > Dec 18 21:07:51 **SENSITIVEDATA** pacemaker-execd [5079]<br>
> >> > > (operation_finished) notice: NGINX-VIP-<br>
> >> > > 231_monitor_10000:28900:stderr [<br>
> >> > > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 709:<br>
> >> > > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: ip: Text file busy ]<br>
> >> > > Dec 18 21:07:51 **SENSITIVEDATA** pacemaker-execd [5079]<br>
> >> > > (operation_finished) notice: NGINX-VIP-<br>
> >> > > 231_monitor_10000:28900:stderr [<br>
> >> > > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 1:<br>
> >> > > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: ip: Text file busy ]<br>
> >> > > Dec 18 21:07:51 **SENSITIVEDATA** pacemaker-execd [5079]<br>
> >> > > (operation_finished) notice: NGINX-VIP-<br>
> >> > > 235_monitor_10000:28905:stderr [<br>
> >> > > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 709:<br>
> >> > > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: ip: Text file busy ]<br>
> >> > > Dec 18 21:07:51 **SENSITIVEDATA** pacemaker-execd [5079]<br>
> >> > > (operation_finished) notice: NGINX-VIP-<br>
> >> > > 235_monitor_10000:28905:stderr [<br>
> >> > > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 1:<br>
> >> > > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: ip: Text file busy ]<br>
> >> > > Dec 18 21:07:51 **SENSITIVEDATA** pacemaker-execd [5079]<br>
> >> > > (operation_finished) notice: NGINX-VIP-<br>
> >> > > 237_monitor_10000:28890:stderr [<br>
> >> > > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 709:<br>
> >> > > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: ip: Text file busy ]<br>
> >> > > Dec 18 21:07:51 **SENSITIVEDATA** pacemaker-execd [5079]<br>
> >> > > (operation_finished) notice: NGINX-VIP-<br>
> >> > > 237_monitor_10000:28890:stderr [<br>
> >> > > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 1:<br>
> >> > > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: ip: Text file busy ]<br>
> >> > > Dec 18 21:07:51 **SENSITIVEDATA** pacemaker-execd [5079]<br>
> >> > > (operation_finished) notice: NGINX-VIP-<br>
> >> > > 238_monitor_10000:28876:stderr [<br>
> >> > > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 709:<br>
> >> > > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: ip: Text file busy ]<br>
> >> > > Dec 18 21:07:51 **SENSITIVEDATA** pacemaker-execd [5079]<br>
> >> > > (operation_finished) notice: NGINX-VIP-<br>
> >> > > 238_monitor_10000:28876:stderr [<br>
> >> > > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 1:<br>
> >> > > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: ip: Text file busy ]<br>
> >> > > Dec 18 21:07:51 **SENSITIVEDATA** pacemaker-execd [5079]<br>
> >> > > (operation_finished) notice: NGINX-VIP_monitor_10000:28880:stderr [<br>
> >> > > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 709:<br>
> >> > > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: ip: Text file busy ]<br>
> >> > > Dec 18 21:07:51 **SENSITIVEDATA** pacemaker-execd [5079]<br>
> >> > > (operation_finished) notice: NGINX-VIP_monitor_10000:28880:stderr [<br>
> >> > > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 1:<br>
> >> > > /usr/lib/ocf/resource.d/heartbeat/IPaddr2: ip: Text file busy ]<br>
> >> > ><br>
> >> > > The reason is that there are a lot of IPs configured and if the<br>
> >> > > monitors take place at the same time it causes this type of error.<br>
> >> > ><br>
> >> > > Best regards,<br>
> >> > ><br>
> >> > > Thomas Cas | Technicien du support infogérance<br>
> >> > > PHONE : +33 3 51 25 23 26 WEB :<br>
> ><br>
> <a href="https://fra01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ikoula.c" rel="noreferrer" target="_blank">https://fra01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ikoula.c</a><br>
><br>
> ><br>
> om%2Fen&data=05%7C01%7Ctcas%<a href="http://40ikoula.com" rel="noreferrer" target="_blank">40ikoula.com</a>%7C9aab91944bd6454a773808dae2c13ae4%7C<br>
> ><br>
> cb7a4a4ea7f747cc931f80db4a66f1c7%7C0%7C0%7C638071616800939086%7CUnknown%7CTWF<br>
> ><br>
> pbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7<br>
> ><br>
> C3000%7C%7C%7C&sdata=oYe7ws2%2BPx3sMblOFBgkuXuSHTdguzB%2Flk83O5W2MjE%3D&reserve<br>
> > d=0<br>
> >> > > IKOULA Data Center 34 rue Pont Assy - 51100 Reims - FRANCE Before<br>
> >> > > printing this letter, think about the impact on the environment!<br>
> >> > ><br>
> >> > ><br>
> >> > ><br>
> >> > ><br>
> >> > > _______________________________________________<br>
> >> > > Manage your subscription:<br>
> >> > > <a href="https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fli" rel="noreferrer" target="_blank">https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fli</a><br>
> >> > > st<br>
> >> > > <a href="http://s.clusterlabs.org" rel="noreferrer" target="_blank">s.clusterlabs.org</a>%2Fmailman%2Flistinfo%2Fusers&data=05%7C01%7Ctcas%4<br>
> >> > > 0i<br>
> >> > > <a href="http://koula.com" rel="noreferrer" target="_blank">koula.com</a>%7C541f4960600340f90a2c08dae20511fc%7Ccb7a4a4ea7f747cc931f8<br>
> >> > > 0d<br>
> >> > > b4a66f1c7%7C0%7C0%7C638070808660951911%7CUnknown%7CTWFpbGZsb3d8eyJWI<br>
> >> > > jo<br>
> >> > > iMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7<br>
> >> > > C%<br>
> >> > > 7C%7C&sdata=U9osKXkKgjcqp6PN0%2F%2FB%2BzZyX0JMe6WMqRPVDTEGyWg%3D&res<br>
> >> > > er<br>
> >> > > ved=0<br>
> >> > ><br>
> >> > > ClusterLabs home:<br>
> >> > > <a href="https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww" rel="noreferrer" target="_blank">https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww</a>.<br>
> >> > > <a href="http://clusterlabs.org" rel="noreferrer" target="_blank">clusterlabs.org</a>%2F&data=05%7C01%7Ctcas%<a href="http://40ikoula.com" rel="noreferrer" target="_blank">40ikoula.com</a>%7C541f4960600340<br>
> >> > > f9<br>
> >> > > 0a2c08dae20511fc%7Ccb7a4a4ea7f747cc931f80db4a66f1c7%7C0%7C0%7C638070<br>
> >> > > 80<br>
> >> > > 8660951911%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luM<br>
> >> > > zI<br>
> >> > > iLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2FfODTlNES3on<br>
> >> > > Dk<br>
> >> > > %2FfLgs6bWR2iikLdfqx7ePxzZfR%2BIU%3D&reserved=0<br>
> >> > --<br>
> >> > Ken Gaillot <<a href="mailto:kgaillot@redhat.com" target="_blank">kgaillot@redhat.com</a>><br>
> >> ><br>
> >> > _______________________________________________<br>
> >> > Manage your subscription:<br>
> >> > <a href="https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist" rel="noreferrer" target="_blank">https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist</a><br>
> >> > <a href="http://s.clusterlabs.org" rel="noreferrer" target="_blank">s.clusterlabs.org</a>%2Fmailman%2Flistinfo%2Fusers&data=05%7C01%7Ctcas%40i<br>
> >> > <a href="http://koula.com" rel="noreferrer" target="_blank">koula.com</a>%7C9aab91944bd6454a773808dae2c13ae4%7Ccb7a4a4ea7f747cc931f80d<br>
> >> > b4a66f1c7%7C0%7C0%7C638071616800939086%7CUnknown%7CTWFpbGZsb3d8eyJWIjo<br>
> >> > iMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%<br>
> >> > 7C%7C&sdata=3jtVFwvmy127OwWr9ZNbr6B%2FefuvNeZl9YsM31QxHJM%3D&reserved=<br>
> >> > 0<br>
> >> ><br>
> >> > ClusterLabs home:<br>
> >> > <a href="https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww" rel="noreferrer" target="_blank">https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww</a>.<br>
> >> > <a href="http://clusterlabs.org" rel="noreferrer" target="_blank">clusterlabs.org</a>%2F&data=05%7C01%7Ctcas%<a href="http://40ikoula.com" rel="noreferrer" target="_blank">40ikoula.com</a>%7C9aab91944bd6454a<br>
> >> > 773808dae2c13ae4%7Ccb7a4a4ea7f747cc931f80db4a66f1c7%7C0%7C0%7C63807161<br>
> >> > 6800939086%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzI<br>
> >> > iLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=2E8uF0uNDw4djwcy<br>
> >> > %2FjVJ%2FDdJu5E77LQZfU9yrf0dVBI%3D&reserved=0<br>
> >> ><br>
> >><br>
> >><br>
> >> --<br>
> >> Regards,<br>
> >><br>
> >> Reid Wahl (He/Him)<br>
> >> Senior Software Engineer, Red Hat<br>
> >> RHEL High Availability - Pacemaker<br>
> >><br>
> ><br>
> ><br>
> > --<br>
> > Regards,<br>
> ><br>
> > Reid Wahl (He/Him)<br>
> > Senior Software Engineer, Red Hat<br>
> > RHEL High Availability - Pacemaker<br>
> ><br>
> > _______________________________________________<br>
> > Manage your subscription:<br>
> > <a href="https://lists.clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">https://lists.clusterlabs.org/mailman/listinfo/users</a><br>
> ><br>
> > ClusterLabs home: <a href="https://www.clusterlabs.org/" rel="noreferrer" target="_blank">https://www.clusterlabs.org/</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Manage your subscription:<br>
> <a href="https://lists.clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">https://lists.clusterlabs.org/mailman/listinfo/users</a><br>
><br>
> ClusterLabs home: <a href="https://www.clusterlabs.org/" rel="noreferrer" target="_blank">https://www.clusterlabs.org/</a><br>
<br>
<br>
<br>
-- <br>
Regards,<br>
<br>
Reid Wahl (He/Him)<br>
Senior Software Engineer, Red Hat<br>
RHEL High Availability - Pacemaker<br>
<br>
_______________________________________________<br>
Manage your subscription:<br>
<a href="https://lists.clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">https://lists.clusterlabs.org/mailman/listinfo/users</a><br>
<br>
ClusterLabs home: <a href="https://www.clusterlabs.org/" rel="noreferrer" target="_blank">https://www.clusterlabs.org/</a><br>
</blockquote></div></div>