Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

Continuous Dynatrace error: ERROR: ld.so: object '/opt/dynatrace/oneagent/agent/lib64/liboneagentproc.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored

Written By

Marcos da Silva Xavier

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

While we make every effort to ensure this Knowledge Base is accurate, itmay not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with anyfeedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

Before using any information from this article, independently verify itssuitability for your situation and project.

Issue

  • A Dynatrace One Agent error is thrown continuously: ERROR: ld.so: object '/opt/dynatrace/oneagent/agent/lib64/liboneagentproc.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.

Environment

  • Liferay PaaS
  • Liferay DXP 7.4+

Resolution

  • Verify Dynatrace Configuration and Credentials: The error message indicates a problem loading the Dynatrace OneAgent library, specifically liboneagentproc.so. In Liferay Cloud DXP 7.4, Dynatrace integration is managed through environment variables. Verify that the LCP_PROJECT_MONITOR_DYNATRACE_TENANT and LCP_PROJECT_MONITOR_DYNATRACE_TOKEN environment variables are correctly configured in the LCP.json file for the Liferay service. Confirm that the Dynatrace subscription is active and the provided credentials are valid. If the credentials are incorrect or the subscription has expired, either update the environment variables with the correct values or renew the subscription. If Dynatrace monitoring is not required, consider temporarily removing these environment variables and redeploying the service.

  • Make sure to check that the Secret for the Dynatrace token is not missing. In case it is, please add it and the issue should be resolved. 

Additional Information

 

 

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?