Ken Gaillot
> I'm glad it's resolved, but for future reference, that does indicate a
> serious problem. It means the fencer is not accepting any requests, so
> any fencing attempts or even attempts to monitor a fencing device from
> that node will fail.
>
That sounds like pacemaker-fenced
On Sun, 2023-03-26 at 10:42 +, S Sathish S via Users wrote:
> Hi Jan,
>
> In Corosync which all scenario it send cpg message and what is impact
> if we are not secure communication.
Pacemaker uses CPG extensively to communicate between nodes. Sensitive
information such as the entire CIB is
On Mon, 2023-03-27 at 14:48 +0800, d tbsky wrote:
> Hi:
>the cluster is running under RHEL 9.0 elements. today I saw log
> report strange errors like below:
>
> Mar 27 13:07:06.287 example.com pacemaker-fenced[2405]
> (qb_sys_mmap_file_open) error: couldn't allocate file
>
On 26/03/2023 12:42, S Sathish S wrote:
Hi Jan,
Hi,
In Corosync which all scenario it send cpg message and what is impact if we are
not secure communication.
It really depends of what services are used, but generally speaking
corosync without cpg is not super useful so I guess cpg is
Christine caulfield
> It sounds like you're running an old version of libqb, upgrading to
> libqb 2.0.6 (in RHEL 9.1) should fix those messages
Thanks a lot for the quick response! I will arrange the upgrade.
Regards,
tbskyd
___
Manage your
On 27/03/2023 07:48, d tbsky wrote:
Hi:
the cluster is running under RHEL 9.0 elements. today I saw log
report strange errors like below:
Mar 27 13:07:06.287 example.com pacemaker-fenced[2405]
(qb_sys_mmap_file_open) error: couldn't allocate file
Hi:
the cluster is running under RHEL 9.0 elements. today I saw log
report strange errors like below:
Mar 27 13:07:06.287 example.com pacemaker-fenced[2405]
(qb_sys_mmap_file_open) error: couldn't allocate file
/dev/shm/qb-2405-2403-12-A9UUaJ/qb-request-stonith-ng-data:
Interrupted