When using Dynatrace and Rancher the following error will be show'n in rancher console:
ERROR:ld.so: object'/opt/dynatrace/oneagent/agent/lib64/liboneagentproc.so' from /etc/ld.so.preload cannot be preloaded (cannot load shared object file): ignored HOSTXX
clearing the ld.so.preload file works.
Does anybody recognize this scenario? Is this an error in the creation of the Racher container?
Solved! Go to Solution.
Did you resolved it? I suppose that this may need support ticket for investigation.
We just hit this issue. Has to do with docker not being able to find the liboneagentproc.so file after the 1.189 agent update as the path was changed in that version. This occurred when the host got the new version of the agent but had not yet been restarted. Restarting docker fixed the issue.
oneagent storage path (/opt/dynatrace/oneagent/agent/lib64/liboneagentproc.so), whilst starting from 1.189 said dynamic library is stored in version-specific path (in this case /opt/dyntrace/oneagent/bin/220.127.116.1100407-143018/linux-x86-64/liboneagentproc.so)
Same here. The nodes that were updated last night are missing these files.
please create a support ticket if you've experienced this issue.
We've already identified a bug in the product and are working on a fix.
They are pushing a fix for this for v1.189 of the oneagent.
Anyone has any updates about this?
I had the same issue in my cluster, I was not able to create new pods after this update:
ERROR: ld.so: object '/opt/dynatrace/oneagent/agent/lib64/liboneagentproc.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
Hi All, would like to also ask if this issue was addressed since we also encountered this error on 1.185 version of oneagent even though there's no present docker or rancher. hoping to find some answers from other users that may have encountered this.
I have face this ld_preload_cannot be preloaded. What I have found is while building dynatrace image it is unable to load the liboneagentproc.so libraries. So we have used new dynatrace token for the image build, and the image able to load the libraries after that my error was disappeared