>> On Thursday 28 July 2022 at 22:17:01, john tillman wrote:
>>
>>> I have a two cluster setup with a qdevice. 'pcs quorum status' from a
>>> cluster node shows the qdevice casting a vote. On the qdevice node
>>> 'corosync-qnetd-tool -s' says I have 2 connected clients and 1 cluster.
>>> The vote
On Fri, Jul 29, 2022 at 1:02 PM Reid Wahl wrote:
>
> On Fri, Jul 29, 2022 at 12:52 PM Ross Sponholtz
> wrote:
> >
> > I’m running a RHEL pacemaker cluster on Azure, and I’ve gotten a failure &
> > fencing where I get these messages in the log file:
> >
> >
> > warning: vip_ABC_30_monitor_1
On Fri, Jul 29, 2022 at 12:52 PM Ross Sponholtz wrote:
>
> I’m running a RHEL pacemaker cluster on Azure, and I’ve gotten a failure &
> fencing where I get these messages in the log file:
>
>
> warning: vip_ABC_30_monitor_1 process (PID 1779737) timed out
> crit: vip_ABC_30_monitor_1
On Fri, Jul 29, 2022 at 5:57 AM lejeczek via Users
wrote:
>
> On 28/07/2022 00:33, Reid Wahl wrote:
> > On Wed, Jul 27, 2022 at 2:08 AM lejeczek via Users
> > wrote:
> >>
> >>
> >> On 26/07/2022 20:56, Reid Wahl wrote:
> >>> On Tue, Jul 26, 2022 at 4:21 AM lejeczek via Users
> >>> wrote:
>
I’m running a RHEL pacemaker cluster on Azure, and I’ve gotten a failure &
fencing where I get these messages in the log file:
warning: vip_ABC_30_monitor_1 process (PID 1779737) timed out
crit: vip_ABC_30_monitor_1 process (PID 1779737) will not die!
This resource uses the IPAddr2
On 28/07/2022 00:33, Reid Wahl wrote:
On Wed, Jul 27, 2022 at 2:08 AM lejeczek via Users
wrote:
On 26/07/2022 20:56, Reid Wahl wrote:
On Tue, Jul 26, 2022 at 4:21 AM lejeczek via Users
wrote:
Hi guys
I set up a clone of a new instance of mariadb galera - which otherwise,
outside of pcs
