>>> Jan Pokorný schrieb am 23.07.2019 um 16:49 in
Nachricht
<20190723144951.gd25...@redhat.com>:
> On 23/07/19 09:07 ‑0500, Ken Gaillot wrote:
>> On Tue, 2019‑07‑23 at 08:48 +0200, Ulrich Windl wrote:
>>> It's not that I like all the changes systemd requires, but systemd
>>> complains about not
On 23/07/19 09:07 -0500, Ken Gaillot wrote:
> On Tue, 2019-07-23 at 08:48 +0200, Ulrich Windl wrote:
>> It's not that I like all the changes systemd requires, but systemd
>> complains about not being able to unmount /var while /var/run or
>> /var/lock is being used...
>
> Agreed, it should be a
On Mon, 2019-07-22 at 15:54 +, Jean-Jacques Pons wrote:
> Hello everyone,
>
> I’m having stability issue with a 2 nodes active/passive HA
> infrastructure (Zabbix VMs in this case).
> Daily backup create a latency, slowing Corosync scheduling and
> triggering a token timeout. It frequently
Jean-Jacques,
Hello everyone,
I'm having stability issue with a 2 nodes active/passive HA infrastructure
(Zabbix VMs in this case).
Daily backup create a latency, slowing Corosync scheduling and triggering a
token timeout. It frequently ends up on a split brain issue, where service is
On Tue, 2019-07-23 at 08:48 +0200, Ulrich Windl wrote:
> Hi!
>
> My old RAs include /usr/lib/ocf/resource.d/heartbeat/.ocf-shellfuncs.
> Recently I discovered /usr/lib/ocf/lib/heartbeat/ocf-shellfuncs.
> (I wonder whether the latter shouldn't be /usr/lib/ocf/ocf-shellfuncs
> simply)
>
> So
On Tue, 2019-07-23 at 08:17 +0200, Ulrich Windl wrote:
> Hi!
>
> As suggested I'm considering to replace all "ocf_log err ..."
> preceeding an error exit code with "ocf_exit_reason ..." in my OCF
> RA.
> However I have a question: Is it OK to call ocf_exit_reason more than
> once before actually
On Tue, 2019-07-23 at 07:57 +0200, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 22.07.2019 um
> > > > 18:14 in Nachricht
>
> :
> > On Mon, 2019-07-22 at 15:45 +0200, Ulrich Windl wrote:
> > > Hi!
> > >
> > > My RA actually sends OCF_ERR_ARGS if checking the args detects a
> > > problem.
>
Hi Rohit,
Did you see the two earlier replies?
https://lists.clusterlabs.org/pipermail/users/2019-July/026035.html
On Tue, 2019-07-23 at 11:14 +0530, Rohit Saini wrote:
> Gentle Reminder!!
>
> On Wed, Jul 17, 2019 at 1:14 PM Rohit Saini <
> rohitsaini111.fo...@gmail.com> wrote:
> > Gentle
Hello everyone,
I'm having stability issue with a 2 nodes active/passive HA infrastructure
(Zabbix VMs in this case).
Daily backup create a latency, slowing Corosync scheduling and triggering a
token timeout. It frequently ends up on a split brain issue, where service is
started on both nodes
Hi!
As suggested I'm considering to replace all "ocf_log err ..." preceeding an
error exit code with "ocf_exit_reason ..." in my OCF RA.
However I have a question: Is it OK to call ocf_exit_reason more than once
before actually exiting? I assume the last message being used will be the one
10 matches
Mail list logo