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

Chris Lumens clumens at redhat.com
Thu Mar 5 14:26:05 UTC 2026


> 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

This message indicates that an EAGAIN was received when pacemaker
daemons were trying to communicate with each other.  "Resource
temporarily unavailable" is simply the result of calling strerror on
that errno.  It doesn't indicate a problem with any particular resource.

By itself, an EAGAIN is not a problem as pacemaker will simply try again
later.  However if you are getting a *lot* of them, it could indicate a
problem.  But we would need more context to tell.  Is your cluster
setup especially large?  Are the cluster nodes running at a very high
load average?  Anything else unusual going on?

- Chris



More information about the Users mailing list