Just Published! Threat Report: Exposing Malware in Linux-Based Multi-Cloud Environments | Download Now

CBContainers: NodeAgent cannot get the network namespace of PID <PID>: readlink /proc/<PID>ns/net: no such file or directory

CBContainers: NodeAgent cannot get the network namespace of PID <PID>: readlink /proc/<PID>ns/net: no such file or directory

Environment

  • CBContainers: 2.3.0 and lower

Symptoms

Excessive logging coming from CBContainers NodeAgent:
cannot get the network namespace of PID 886638: readlink /proc/886638/ns/net: no such file or directory
cannot get the network namespace of PID 886320: readlink /proc/886320/ns/net: no such file or directory
cannot get the network namespace of PID 822198: readlink /proc/822198/ns/net: no such file or directory
cannot get the network namespace of PID 778779: readlink /proc/778779/ns/net: no such file or directory
cannot get the network namespace of PID 626021: readlink /proc/626021/ns/net: no such file or directory
cannot get the network namespace of PID 411274: readlink /proc/411274/ns/net: no such file or directory
cannot get the network namespace of PID 411183: readlink /proc/411183/ns/net: no such file or directory

 

Cause

  • This condition isn't harmful but a byproduct of logging verbosity.

Resolution

  • Upgrade the CBContainers Node Agent to 2.3.1+.

Labels (2)
Was this article helpful? Yes No
No ratings
Article Information
Author:
Creation Date:
‎03-28-2022
Views:
190
Contributors