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 _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
