[ClusterLabs] Antw: [EXT] Bug pacemaker with multiple IP

[Ulrich Windl]

>>> Thomas CAS <tcas at ikoula.com> schrieb am 19.12.2022 um 10:48 in Nachricht
<PR3P193MB0829DAE83AC0B53CC8EE11AEA5E59 at PR3P193MB0829.EURP193.PROD.OUTLOOK.COM>:

> Hello Clusterlabs,
> 
> I would like to report a bug on Pacemaker with the "IPaddr2" resource:
> 
> OS: Debian 10
> Kernel: Linux wd‑websqlng01 4.19.0‑18‑amd64 #1 SMP Debian 4.19.208‑1
(2021‑09‑29) 
> x86_64 GNU/Linux
> Pacemaker version: 2.0.1‑5+deb10u2
> 
> You will find the configuration of our cluster with 2 nodes attached.
> 
> Bug :
> 
> We have several IP configured in the cluster configuration (12)
> Sometimes the cluster is unstable with the following errors in the pacemaker

> logs:
> 
> Dec 18 21:07:51 **SENSITIVEDATA** pacemaker‑execd     [5079] 
> (operation_finished)   notice: NGINX‑VIP‑232_monitor_10000:28835:stderr [ 
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 1: 
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2: ip: Text file busy ]

As Ken pointed out already,

"text file busy" in Linux means that some process tried to write to the binary
while it is being executed (at least once). However you can update a running
binary by "removing" (i.e. unlinking) it and then place a new binary. Running
processes will continue to use the old binary while new invocations will use
the new binary.

I suggest to tracxe what's going on. It does not sound good.
Still, I'm not claiming there is no bug in the RA ;-)

Regards,
Ulrich


> Dec 18 21:07:51 **SENSITIVEDATA** pacemaker‑execd     [5079] 
> (operation_finished)   notice: NGINX‑VIP‑239_monitor_10000:28877:stderr [ 
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 709: 
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2: ip: Text file busy ]
> Dec 18 21:07:51 **SENSITIVEDATA** pacemaker‑execd     [5079] 
> (operation_finished)   notice: NGINX‑VIP‑239_monitor_10000:28877:stderr [ 
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 1: 
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2: ip: Text file busy ]
> Dec 18 21:07:51 **SENSITIVEDATA** pacemaker‑execd     [5079] 
> (operation_finished)   notice: NGINX‑VIP‑234_monitor_10000:28830:stderr [ 
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 1: 
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2: ip: Text file busy ]
> Dec 18 21:07:51 **SENSITIVEDATA** pacemaker‑execd     [5079] 
> (operation_finished)   notice: NGINX‑VIP‑231_monitor_10000:28900:stderr [ 
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 709: 
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2: ip: Text file busy ]
> Dec 18 21:07:51 **SENSITIVEDATA** pacemaker‑execd     [5079] 
> (operation_finished)   notice: NGINX‑VIP‑231_monitor_10000:28900:stderr [ 
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 1: 
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2: ip: Text file busy ]
> Dec 18 21:07:51 **SENSITIVEDATA** pacemaker‑execd     [5079] 
> (operation_finished)   notice: NGINX‑VIP‑235_monitor_10000:28905:stderr [ 
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 709: 
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2: ip: Text file busy ]
> Dec 18 21:07:51 **SENSITIVEDATA** pacemaker‑execd     [5079] 
> (operation_finished)   notice: NGINX‑VIP‑235_monitor_10000:28905:stderr [ 
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 1: 
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2: ip: Text file busy ]
> Dec 18 21:07:51 **SENSITIVEDATA** pacemaker‑execd     [5079] 
> (operation_finished)   notice: NGINX‑VIP‑237_monitor_10000:28890:stderr [ 
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 709: 
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2: ip: Text file busy ]
> Dec 18 21:07:51 **SENSITIVEDATA** pacemaker‑execd     [5079] 
> (operation_finished)   notice: NGINX‑VIP‑237_monitor_10000:28890:stderr [ 
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 1: 
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2: ip: Text file busy ]
> Dec 18 21:07:51 **SENSITIVEDATA** pacemaker‑execd     [5079] 
> (operation_finished)   notice: NGINX‑VIP‑238_monitor_10000:28876:stderr [ 
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 709: 
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2: ip: Text file busy ]
> Dec 18 21:07:51 **SENSITIVEDATA** pacemaker‑execd     [5079] 
> (operation_finished)   notice: NGINX‑VIP‑238_monitor_10000:28876:stderr [ 
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 1: 
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2: ip: Text file busy ]
> Dec 18 21:07:51 **SENSITIVEDATA** pacemaker‑execd     [5079] 
> (operation_finished)   notice: NGINX‑VIP_monitor_10000:28880:stderr [ 
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 709: 
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2: ip: Text file busy ]
> Dec 18 21:07:51 **SENSITIVEDATA** pacemaker‑execd     [5079] 
> (operation_finished)   notice: NGINX‑VIP_monitor_10000:28880:stderr [ 
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2: 1: 
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2: ip: Text file busy ]
> 
> The reason is that there are a lot of IPs configured and if the monitors 
> take place at the same time it causes this type of error.
> 
> Best regards,
> 
> Thomas Cas  |  Technicien du support infogérance
> PHONE : +33 3 51 25 23 26       WEB : 
> www.ikoula.com/en<https://www.ikoula.com/en>
> IKOULA Data Center 34 rue Pont Assy ‑ 51100 Reims ‑ FRANCE
> Before printing this letter, think about the impact on the environment!
> 
> [Ikoula]<https://www.ikoula.com/en>
> [Twitter]<https://twitter.com/ikoula_en> [Linkedin] 
> <https://www.linkedin.com/company/ikoula>  [Youtube] 
> <http://www.youtube.fr/ikoulanet>  [Pressroom]
<https://pressroom.ikoula.com/>  
> [Blog] <https://blog.ikoula.com/en>