-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
CentOS Stream 10
-
None
-
None
-
None
-
rhel-arr-emerging
-
None
-
False
-
False
-
-
None
-
CentOS Stream
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
x86_64
-
None
What were you trying to do that didn't work?
HI guys,
These below pacemaker journal logs as notice but logs are flooded with it:
// code placeholder notice: Response 2 (final part 2) to pid 3055550 failed: Resource temporarily unavailable notice: Response 2 (final part 2) to pid 3055550 failed: Resource temporarily unavailable notice: Response 2 (part 1) to pid 3055556 failed: Resource temporarily unavailable notice: Response 2 (part 1) to pid 3055556 failed: Resource temporarily unavailable notice: Response 2 (part 1) to pid 3055556 failed: Resource temporarily unavailable notice: Response 2 (part 1) to pid 3055556 failed: Resource temporarily unavailable notice: Response 2 (part 1) to pid 3055556 failed: Resource temporarily unavailable notice: Response 2 (part 1) to pid 3055556 failed: Resource temporarily unavailable notice: Response 2 (part 1) to pid 3055556 failed: Resource temporarily unavailable notice: Response 2 (part 1) to pid 3055556 failed: Resource temporarily unavailable notice: Response 2 (part 1) to pid 3055556 failed: Resource temporarily unavailable notice: Response 2 (part 1) to pid 3055556 failed: Resource temporarily unavailable notice: Response 2 (part 1) to pid 3055556 failed: Resource temporarily unavailable notice: Response 2 (part 1) to pid 3055556 failed: Resource temporarily unavailable notice: Response 2 (final part 2) to pid 3055556 failed: Resource temporarily unavailable notice: Response 2 (final part 2) to pid 3055556 failed: Resource temporarily unavailable notice: Response 2 (final part 2) to pid 3055556 failed: Resource temporarily unavailable notice: Response 2 (final part 2) to pid 3055556 failed: Resource temporarily unavailable
pacemaker.log
pid 3089965 failed: Resource temporarily unavailable | bytes=11601 rc=-11 ipcs=0x55be84907250 11:24:00.093 swir.mine.priv pacemaker-based [3337] (pcmk__ipc_send_iov) notice: Response 2 (final part 2) to pid 3089965 failed: Resource temporarily unavailable | bytes=11601 rc=-11 ipcs=0x55be84907250 11:24:00.093 swir.mine.priv pacemaker-based [3337] (pcmk__ipc_send_iov) notice: Response 2 (final part 2) to pid 3089965 failed: Resource temporarily unavailable | bytes=11601 rc=-11 ipcs=0x55be84907250 11:24:00.093 swir.mine.priv pacemaker-based [3337] (pcmk__ipc_send_iov) notice: Response 2 (final part 2) to pid 3089965 failed: Resource temporarily unavailable | bytes=11601 rc=-11 ipcs=0x55be84907250 11:24:00.093 swir.mine.priv pacemaker-based [3337] (pcmk__ipc_send_iov) notice: Response 2 (final part 2) to pid 3089965 failed: Resource temporarily unavailable | bytes=11601 rc=-11 ipcs=0x55be84907250 11:24:00.093 swir.mine.priv pacemaker-based [3337] (pcmk__ipc_send_iov) notice: Response 2 (final part 2) to pid 3089965 failed: Resource temporarily unavailable | bytes=11601 rc=-11 ipcs=0x55be84907250
Cluster otherwise does not report any issues. I thought I should report it in case there might some underlying problems.
thanks, L.
What is the impact of this issue to you?
Please provide the package NVR for which the bug is seen:
pacemaker-3.0.1-5.el10 pcs-0.12.2-3.el10 corosync-3.1.10-1.el10
