>>> Reid Wahl <nw...@redhat.com> schrieb am 27.01.2023 um 09:32 in Nachricht <CAPiuu9-ubw=10YRy=RQb94+P1p1a-2VbG_jd6R6eo3Epf=w...@mail.gmail.com>: > On Fri, Jan 27, 2023 at 12:23 AM Thomas CAS <t...@ikoula.com> wrote: > >> Hello Reid, >> >> >> >> Thank you so much for your answer and bug report. >> >> If it is a bug, I do not understand why the problem is present in >> production but not on my lab which is identical? >> > > That's a good question. I'm not sure, and I haven't worked much with this > resource agent. Does the lab show interesting logs at all from the resource
Well, it's not an incredibly clever proposal (just obvious), but anyway: Did you compare the RA files for each node? Did you compare the configs for each node? > agent during startup? I wonder if it's hitting the same "No MySQL master > present" issue but *not* the error that follows. That error is coming from > mysql itself, not from the resource agent. > > After the agent hits the "No MySQL master present" issue, it calls the > unset_master() function. You can take a look at the agent script (in > /usr/lib/ocf/resource.d/heartbeat/mysql by default) to see all the things > that unset_master() is doing, and try to determine what's behaving > differently in production vs. lab. > [...] Regards, Ulrich _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
