[ClusterLabs] [EXT] [EXT] pacemaker - Response 4 (part 1) to pid xyz failed

[Windl, Ulrich]

Hi!

Maybe provide some more details about the cluster status and resources.

Kind regards,
Ulrich Windl

From: Users <users-bounces at clusterlabs.org> On Behalf Of lejeczek via Users
Sent: Thursday, March 5, 2026 12:50 PM
To: Cluster Labs - All topics related to open-source clustering welcomed <users at clusterlabs.org>
Cc: lejeczek <peljasz at yahoo.co.uk>
Subject: [EXT] [EXT] [ClusterLabs] pacemaker - Response 4 (part 1) to pid xyz failed


Sie auf Links klicken, Anhänge öffnen oder weitere Aktionen ausführen, bevor Sie die Echtheit überprüft haben.
HI guys.

After an upgrade from pacemaker-2.1.10-2.el9 to pacemaker-3.0.1-5.el10 all pacemakers logs:
...
 notice: Response 2 (final part 2) to pid 204474 failed: Resource temporarily unavailable
 notice: Response 2 (final part 2) to pid 204474 failed: Resource temporarily unavailable
 notice: Response 2 (part 1) to pid 204481 failed: Resource temporarily unavailable
 notice: Response 2 (part 1) to pid 204481 failed: Resource temporarily unavailable
 notice: Response 2 (final part 2) to pid 204481 failed: Resource temporarily unavailable
 notice: Response 2 (final part 2) to pid 204481 failed: Resource temporarily unavailable
...

constantly.
Cluster does not signal - certainly not in any obvious way - there are any issues.
Does anybody know what those above are symptom of? How to troubleshoot it?
What resource it that which _pacemakers_ is complaining about?

many thanks, L.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20260310/5bd1fe12/attachment.htm>