Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[META 105] Parsing container ID in Cloud Foundry Garden

See original GitHub issue

Describe the bug The health checker for cloud foundry is unable to find guid - apm.agent.impl.payload.SystemInfo - container ID is null

To Reproduce Enable elk-apm and restage app

See error

Expected behavior A clear and concise description of what you expected to happen.

Debug logs SystemInfo - Could not parse container ID from SystemInfo - container ID is null

/** * Name of the system platform the agent is running on. */ private final String platform;

   2019-06-25T13:45:45.82-0400 [APP/PROC/WEB/0] OUT 2019-06-25 17:45:45.825 [main] DEBUG co.elastic.apm.agent.impl.payload.SystemInfo - Could not parse container ID from '/proc/self/cgroup' line: 12:memory:/system.slice/garden.service/garden/70eb4ce5-a065-4401-6990-88ed
   2019-06-25T13:45:45.82-0400 [APP/PROC/WEB/0] OUT 2019-06-25 17:45:45.826 [main] DEBUG co.elastic.apm.agent.impl.payload.SystemInfo - Could not parse container ID from '/proc/self/cgroup' line: 11:hugetlb:/garden/70eb4ce5-a065-4401-6990-88ed
   2019-06-25T13:45:45.82-0400 [APP/PROC/WEB/0] OUT 2019-06-25 17:45:45.826 [main] DEBUG co.elastic.apm.agent.impl.payload.SystemInfo - Could not parse container ID from '/proc/self/cgroup' line: 10:freezer:/garden/70eb4ce5-a065-4401-6990-88ed
   2019-06-25T13:45:45.82-0400 [APP/PROC/WEB/0] OUT 2019-06-25 17:45:45.827 [main] DEBUG co.elastic.apm.agent.impl.payload.SystemInfo - Could not parse container ID from '/proc/self/cgroup' line: 9:net_cls,net_prio:/garden/70eb4ce5-a065-4401-6990-88ed
   2019-06-25T13:45:45.82-0400 [APP/PROC/WEB/0] OUT 2019-06-25 17:45:45.827 [main] DEBUG co.elastic.apm.agent.impl.payload.SystemInfo - Could not parse container ID from '/proc/self/cgroup' line: 8:pids:/system.slice/garden.service/garden/70eb4ce5-a065-4401-6990-88ed
   2019-06-25T13:45:45.82-0400 [APP/PROC/WEB/0] OUT 2019-06-25 17:45:45.828 [main] DEBUG co.elastic.apm.agent.impl.payload.SystemInfo - Could not parse container ID from '/proc/self/cgroup' line: 7:perf_event:/garden/70eb4ce5-a065-4401-6990-88ed
   2019-06-25T13:45:45.82-0400 [APP/PROC/WEB/0] OUT 2019-06-25 17:45:45.828 [main] DEBUG co.elastic.apm.agent.impl.payload.SystemInfo - Could not parse container ID from '/proc/self/cgroup' line: 6:rdma:/
   2019-06-25T13:45:45.82-0400 [APP/PROC/WEB/0] OUT 2019-06-25 17:45:45.829 [main] DEBUG co.elastic.apm.agent.impl.payload.SystemInfo - Could not parse container ID from '/proc/self/cgroup' line: 5:blkio:/system.slice/garden.service/garden/70eb4ce5-a065-4401-6990-88ed
   2019-06-25T13:45:45.83-0400 [APP/PROC/WEB/0] OUT 2019-06-25 17:45:45.829 [main] DEBUG co.elastic.apm.agent.impl.payload.SystemInfo - Could not parse container ID from '/proc/self/cgroup' line: 4:cpuset:/garden/70eb4ce5-a065-4401-6990-88ed
   2019-06-25T13:45:45.83-0400 [APP/PROC/WEB/0] OUT 2019-06-25 17:45:45.830 [main] DEBUG co.elastic.apm.agent.impl.payload.SystemInfo - Could not parse container ID from '/proc/self/cgroup' line: 3:cpu,cpuacct:/system.slice/garden.service/garden/70eb4ce5-a065-4401-6990-88ed
   2019-06-25T13:45:45.83-0400 [APP/PROC/WEB/0] OUT 2019-06-25 17:45:45.830 [main] DEBUG co.elastic.apm.agent.impl.payload.SystemInfo - Could not parse container ID from '/proc/self/cgroup' line: 2:devices:/system.slice/garden.service/garden/70eb4ce5-a065-4401-6990-88ed
   2019-06-25T13:45:45.83-0400 [APP/PROC/WEB/0] OUT 2019-06-25 17:45:45.831 [main] DEBUG co.elastic.apm.agent.impl.payload.SystemInfo - Could not parse container ID from '/proc/self/cgroup' line: 1:name=systemd:/system.slice/garden.service/garden/70eb4ce5-a065-4401-6990-88ed
   2019-06-25T13:45:45.83-0400 [APP/PROC/WEB/0] OUT 2019-06-25 17:45:45.831 [main] DEBUG co.elastic.apm.agent.impl.payload.SystemInfo - container ID is null

Issue Analytics

State:
Created 4 years ago
Comments:10 (8 by maintainers)

Top GitHub Comments

1reaction

eyalkorencommented, Jul 3, 2019

@kmacpher67 any updates?

1reaction

eyalkorencommented, Jun 26, 2019

Thanks for reporting!

The container ID parsing error should not prevents the agent from working. If you get this healthcheck error, it is not related. It is a failure of communication with the APM server. Make sure your APM server is reachable from within the cloud foundry container running this JVM.

Nevertheless, I want to fix this container ID parsing anyway. Just to make sure- 70eb4ce5-a065-4401-6990-88ed in the case above is the valid container ID we should discover, right? If so, please try out this snapshot build and see if it solves the issue.