On Wed, Aug 3, 2022 at 2:59 PM Lentes, Bernd
wrote:
>
> Hi,
>
> i have the following situation:
> 2-node Cluster, just one node running (ha-idg-1).
> The second node (ha-idg-2) is in standby. DLM monitor on ha-idg-1 times out.
> Cluster tries to restart all services depending on DLM:
> Aug 03
Hi,
i have the following situation:
2-node Cluster, just one node running (ha-idg-1).
The second node (ha-idg-2) is in standby. DLM monitor on ha-idg-1 times out.
Cluster tries to restart all services depending on DLM:
Aug 03 01:07:11 [19367] ha-idg-1pengine: notice: LogAction:*
The "found ... active" messages mean that it was the case at some
point, not necessarily currently. Newer versions log much better
messages like:
info: Probe found rsc1 active on node1 at Aug 1 15:41:34 2022
so you can see it was a historical result. The later "Started" messages
are where the
Hi,
i have a strange behaviour found in the cluster log
(/var/log/cluster/corosync.log).
I KNOW that i put one node (ha-idg-2) in standby mode and stopped the pacemaker
service on that node:
The history of the shell says:
993 2022-08-02 18:28:25 crm node standby ha-idg-2
994 2022-08-02
On Wed, Aug 3, 2022 at 4:02 PM Ulrich Windl
wrote:
>
> >>> Klaus Wenninger schrieb am 03.08.2022 um 15:51 in
> Nachricht
> :
> > On Tue, Aug 2, 2022 at 4:10 PM Ken Gaillot wrote:
> >>
> >> On Tue, 2022-08-02 at 19:13 +0900, 井上和徳 wrote:
> >> > Hi,
> >> >
> >> > Since O_DIRECT is not specified in
>>> Klaus Wenninger schrieb am 03.08.2022 um 15:51 in
Nachricht
:
> On Tue, Aug 2, 2022 at 4:10 PM Ken Gaillot wrote:
>>
>> On Tue, 2022-08-02 at 19:13 +0900, 井上和徳 wrote:
>> > Hi,
>> >
>> > Since O_DIRECT is not specified in open() [1], it reads the buffer
>> > cache and
>> > may result in a
On Tue, Aug 2, 2022 at 4:10 PM Ken Gaillot wrote:
>
> On Tue, 2022-08-02 at 19:13 +0900, 井上和徳 wrote:
> > Hi,
> >
> > Since O_DIRECT is not specified in open() [1], it reads the buffer
> > cache and
> > may result in a false negative. I fear that this possibility
> > increases
> > in environments
Hi!
I wanted to inform you of an unpleasant bug in ldirectord of SLES12 SP5:
We had a short network problem while some redundancy paths reconfigured in the
infrastructure, effectively causing that some network services could not be
reached.
Unfortunately ldirectord controlled by the cluster
>>> Andrei Borzenkov schrieb am 03.08.2022 um 08:58 in
Nachricht :
> On 03.08.2022 09:02, Ulrich Windl wrote:
> Ken Gaillot schrieb am 02.08.2022 um 16:09 in
>> Nachricht
>> <0a2125a43bbfc09d2ca5bad1a693710f00e33731.ca...@redhat.com>:
>>> On Tue, 2022-08-02 at 19:13 +0900, 井上和徳 wrote:
On 03.08.2022 09:02, Ulrich Windl wrote:
Ken Gaillot schrieb am 02.08.2022 um 16:09 in
> Nachricht
> <0a2125a43bbfc09d2ca5bad1a693710f00e33731.ca...@redhat.com>:
>> On Tue, 2022-08-02 at 19:13 +0900, 井上和徳 wrote:
>>> Hi,
>>>
>>> Since O_DIRECT is not specified in open() [1], it reads the
>>> "Ulrich Windl" schrieb am 03.08.2022
um
08:02 in Nachricht <62ea0f6202a10004c...@gwsmtp.uni-regensburg.de>:
Ken Gaillot schrieb am 02.08.2022 um 16:09 in
> Nachricht
> <0a2125a43bbfc09d2ca5bad1a693710f00e33731.ca...@redhat.com>:
>> On Tue, 2022-08-02 at 19:13 +0900, 井上和徳 wrote:
>>>
>>> Ken Gaillot schrieb am 02.08.2022 um 16:09 in
Nachricht
<0a2125a43bbfc09d2ca5bad1a693710f00e33731.ca...@redhat.com>:
> On Tue, 2022-08-02 at 19:13 +0900, 井上和徳 wrote:
>> Hi,
>>
>> Since O_DIRECT is not specified in open() [1], it reads the buffer
>> cache and
>> may result in a false
12 matches
Mail list logo