containers fail to start on overcloud controller due to 'The maximum number of active connections for UID 0 has been reached'
Issue
- After
yum update -y
andreboot
on overcloud controller node, containers fail to start due toThe maximum number of active connections for UID 0 has been reached
:
Dec 20 02:47:14 overcloud-controller-0 dbus-daemon[2561]: [system] The maximum number of active connections for UID 0 has been reached (max_connections_per_user=256)
Dec 20 02:47:14 overcloud-controller-0 dbus-daemon[2561]: [system] The maximum number of active connections for UID 0 has been reached (max_connections_per_user=256)
Dec 20 02:47:14 overcloud-controller-0 dbus-daemon[2561]: [system] The maximum number of active connections for UID 0 has been reached (max_connections_per_user=256)
Dec 20 02:47:14 overcloud-controller-0 dbus-daemon[2561]: [system] The maximum number of active connections for UID 0 has been reached (max_connections_per_user=256)
Dec 20 02:47:14 overcloud-controller-0 dbus-daemon[2561]: [system] The maximum number of active connections for UID 0 has been reached (max_connections_per_user=256)
Dec 20 02:47:14 overcloud-controller-0 dbus-daemon[2561]: [system] The maximum number of active connections for UID 0 has been reached (max_connections_per_user=256)
Dec 20 02:47:14 overcloud-controller-0 dbus-daemon[2561]: [system] The maximum number of active connections for UID 0 has been reached (max_connections_per_user=256)
Dec 20 02:47:14 overcloud-controller-0 dbus-daemon[2561]: [system] The maximum number of active connections for UID 0 has been reached (max_connections_per_user=256)
- When this happens, it's not possible to login into the controller again and podman ps command timed out
Environment
- Red Hat OpenStack Platform 15.0 (RHOSP)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.