Some metrics not being reported for Openshift project from osemetainfo container
Article ID: 127228
Updated On:
Products
CA Application Performance Management Agent (APM / Wily / Introscope)
INTROSCOPE
Issue/Introduction
We are not seeing all of the 'deployment config' metrics for a particular Openshift project. Other projects appear to be OK. On one of the PODs that the project is running in, I can see the following errors in the IA logs but don't know if this relates to the issue or not.
2/07/19 02:24:07 PM UTC [WARN] [IntroscopeAgent.DockerStats] No stats collected for 179b6652a51f43337160cd31288e115f99e5077ed7560d61cfae2ee2de3caf70
2/07/19 02:25:37 PM UTC [WARN] [IntroscopeAgent.DockerStats] No stats collected for 179b6652a51f43337160cd31288e115f99e5077ed7560d61cfae2ee2de3caf70
nsenter: cannot open /proc/96093/ns/net: No such file or directory
nsenter: cannot open /proc/96093/ns/net: No such file or directory
nsenter: cannot open /proc/96093/ns/net: No such file or directory
2/07/19 02:24:07 PM UTC [WARN] [IntroscopeAgent.DockerStats] No stats collected for 179b6652a51f43337160cd31288e115f99e5077ed7560d61cfae2ee2de3caf70
2/07/19 02:25:37 PM UTC [WARN] [IntroscopeAgent.DockerStats] No stats collected for 179b6652a51f43337160cd31288e115f99e5077ed7560d61cfae2ee2de3caf70
nsenter: cannot open /proc/96093/ns/net: No such file or directory
nsenter: cannot open /proc/96093/ns/net: No such file or directory
nsenter: cannot open /proc/96093/ns/net: No such file or directory
Environment
Release:
Component: APMAGT
Component: APMAGT
Resolution
The probable reason that pod was not getting any data is a pod initialisation problem and not an issue with the Agent. The following link describes the situation
https://bugzilla.redhat.com/show_bug.cgi?id=1434950
It is likely that the /proc/96093/ns folder is present but there is no net file within it If you check the docker node logs you should see a message like the following
Mar 22 13:01:12 ip-172-31-43-89 atomic-openshift-node: E0322 13:01:12.443538 34645 docker_manager.go:378] NetworkPlugin cni failed on the status hook for pod 'pod1' - Unexpected command output Device "eth0" does not exist.
In this case the Openshift pod restart resolved the problem
https://bugzilla.redhat.com/show_bug.cgi?id=1434950
It is likely that the /proc/96093/ns folder is present but there is no net file within it If you check the docker node logs you should see a message like the following
Mar 22 13:01:12 ip-172-31-43-89 atomic-openshift-node: E0322 13:01:12.443538 34645 docker_manager.go:378] NetworkPlugin cni failed on the status hook for pod 'pod1' - Unexpected command output Device "eth0" does not exist.
In this case the Openshift pod restart resolved the problem
Feedback
Yes
No
Powered by
