IBM Support

Recurring messages complain that "Scope libcontainer-nnnnn has no PIDs. Refusing"

Troubleshooting


Problem

Several occurrences of the message "Scope libcontainer-nnnnn has no PIDs. Refusing" are reported in /var/log/messages

Cause

These messages have been introduced with latest kubernetes versions, where now cgroup-driver is set to systemd.
These messages are harmless (there is no functional impact).
In next releases, ICP will provide a better separation between kubelet log and other syslog messages, by providing a custom configuration of rsyslog.

Resolving The Problem

As a work-around, you can configure rsyslog to ignore that.  Please try this procedure:
cd /etc/rsyslog.d
create a new file "ignore-systemd-session-slice.conf" with following contents (3 rows)
if ($programname == "systemd") and ($msg contains "_systemd_test_default.slice" or$msg contains "systemd-test-default-dependencies.scope") then {
  stop
}
and finally...
service rsyslog restart

Document Location

Worldwide

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSBS6K","label":"IBM Cloud Private"},"Component":"","Platform":[{"code":"PF016","label":"Linux"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Product Synonym

ICP; IBM Cloud Private

Document Information

Modified date:
07 May 2019

UID

ibm10883724