On Tue, 2023-03-28 at 13:11 +0800, d tbsky wrote:
> 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
> >
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 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
>
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
