cooperative_monitoring_locks warning: [mariadbmon] Lost the lock 'maxscale_mariadbmonitor' on server

maxscale01.log
2026-09-30 01:31:23 warning: [mariadbmon] Lost the lock 'maxscale_mariadbmonitor' on server 'prod-dbs01' without releasing it. The lock is now owned by connection 52381.
2026-09-30 01:31:23 warning: [mariadbmon] Lost the lock 'maxscale_mariadbmonitor' on server 'prod-dbs03' without releasing it. The lock is now owned by connection 1185768.
2026-09-30 01:31:23 warning: [mariadbmon] Lost the lock 'maxscale_mariadbmonitor' on server 'prod-dbs04' without releasing it. The lock is now owned by connection 52453.
2026-09-30 01:31:23 warning: [mariadbmon] Lost the lock 'maxscale_mariadbmonitor' on server 'prod-dbs02' without releasing it. The lock is now owned by connection 1146440.
2026-09-30 01:31:23 warning: [mariadbmon] Lost the lock 'maxscale_mariadbmonitor_master' on server 'prod-dbs02' without releasing it. The lock is now owned by connection 1146440.
2026-09-30 01:31:23 warning: [mariadbmon] Lost the lock 'maxscale_mariadbmonitor' on server 'dr-dbs02' without releasing it. The lock is now owned by connection 10.
2026-09-30 01:31:23 warning: [mariadbmon] Lost the lock 'maxscale_mariadbmonitor' on server 'dr-dbs01' without releasing it. The lock is now owned by connection 10.
2026-09-30 01:31:23 warning: [mariadbmon] Lost the lock 'maxscale_mariadbmonitor' on server 'dr-dbs03' without releasing it. The lock is now owned by connection 11.
2026-09-30 01:31:23 warning: [mariadbmon] 'MariaDB-Monitor' lost the exclusive lock on a majority of its servers. Configured automatic cluster manipulation operations (e.g. failover) can not be performed.

maxscale02.log
2026-09-30 01:23:30 notice : [mariadbmon] 'MariaDB-Monitor' acquired the exclusive lock on a majority of its servers. Configured automatic cluster manipulation operations (e.g. failover) can be performed in 5 monitor ticks.