"Transport endpoint is not connected (107)" Error in Pacemaker

Solution Verified - Updated -

Issue

In high-availability environments using Pacemaker, users may occasionally encounter an error from the pacemaker-controld process indicating a problem with inter-process communication (IPC). This error typically appears in logs as:

pacemaker-controld[13654]:error: error receiving from setup sock (/dev/shm/qb-...): Transport endpoint is not connected (107)

This error points to a potential issue with the libqb library used by Pacemaker for IPC, which helps coordinate communication across cluster nodes.

Environment

  • Red Hat Enterprise Linux 7, 8, 9
  • Pacemaker cluster

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content