NOLIBOS Christophe schrieb am Do., 18.
Apr. 2024, 19:01:
> Classified as: {OPEN}
>
>
>
> Hummm… my RHEL 8.8 OS has been hardened.
>
> I am wondering if the problem does not come from that.
>
>
>
> On another side, I get the same issue (i.e. corosync not restarted by
> system) with Pacemaker
Classified as: {OPEN}
Hummm… my RHEL 8.8 OS has been hardened.
I am wondering if the problem does not come from that.
On another side, I get the same issue (i.e. corosync not restarted by system)
with Pacemaker 2.1.5-8 deployed on RHEL 8.4 (not hardened).
I’m checking.
{OPEN}
Classified as: {OPEN}
So, the issue is on systemd?
If I run the same test on RHEL 7 (3.10.0-693.11.1.el7) with pacemaker
1.1.13-10, corosync is correctly restarted by systemd.
[RHEL7 ~]# journalctl -f
-- Logs begin at Wed 2024-01-03 13:15:41 UTC. --
Apr 18 16:26:55 - systemd[1]:
On Thu, Apr 18, 2024 at 6:09 PM Klaus Wenninger wrote:
>
>
> On Thu, Apr 18, 2024 at 6:06 PM NOLIBOS Christophe <
> christophe.noli...@thalesgroup.com> wrote:
>
>> Classified as: {OPEN}
>>
>>
>>
>> Well… why do you say that « Well if corosync isn't there that this is
>> to be expected and
Classified as: {OPEN}
Well… why do you say that « Well if corosync isn't there that this is to be
expected and pacemaker won't recover corosync.”?
In my mind, Corosync is managed by Pacemaker as any other cluster resource and
the "pacemakerd: recover properly from > Corosync crash" fix
Classified as: {OPEN}
[~]$ systemctl status corosync
● corosync.service - Corosync Cluster Engine
Loaded: loaded (/usr/lib/systemd/system/corosync.service; enabled; vendor
preset: disabled)
Active: failed (Result: signal) since Thu 2024-04-18 14:58:42 UTC; 53min ago
Docs:
On Thu, Apr 18, 2024 at 5:07 PM NOLIBOS Christophe via Users <
users@clusterlabs.org> wrote:
> Classified as: {OPEN}
>
> I'm using RedHat 8.8 (4.18.0-477.21.1.el8_8.x86_64).
> When I kill Corosync, no new corosync process is created and pacemaker is
> in failure.
> The only solution is to restart
Classified as: {OPEN}
I'm using RedHat 8.8 (4.18.0-477.21.1.el8_8.x86_64).
When I kill Corosync, no new corosync process is created and pacemaker is in
failure.
The only solution is to restart the pacemaker service.
[~]$ pcs status
Error: unable to get cib
[~]$
[~]$systemctl status pacemaker
●
What OS are you using? Does it use systemd?
What does happen when you kill Corosync?
On Thu, 2024-04-18 at 13:13 +, NOLIBOS Christophe via Users wrote:
> Classified as: {OPEN}
>
> Dear All,
>
> I have a question about the "pacemakerd: recover properly from
> Corosync crash" fix
Classified as: {OPEN}
Dear All,
I have a question about the "pacemakerd: recover properly from Corosync
crash" fix implemented in version 2.1.2.
I have observed the issue when testing pacemaker version 2.0.5, just by
killing the corosync process: Corosync was not recovered.
I am using
On Thu, Apr 18, 2024 at 3:02 AM Nicholas Yang via Users <
users@clusterlabs.org> wrote:
> > NVM, I found them in /usr/local/libexec/pacemaker/
> >
> > I'm guessing a lot of my troubles have been related to the fact this is
> not added to the path by the port pkg!
>
> This is not a problem. crmsh
11 matches
Mail list logo
