Legacy Knowledge Base
Published Jul. 2, 2025

Error with liboneagentloader.so starting Liferay service

Written By

David Tello

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.
Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM).

Issue

    • After updating the Liferay service image used to deploy the service, there are errors in the log and the service doesn't start.
    • The error obtained is:
Info: Using DT_HOME: /opt/liferaycloud/dynatrace/oneagent 
Error occurred during initialization of VM
Could not find agent library /opt/liferaycloud/dynatrace/oneagent/agent/lib64/liboneagentloader.so in absolute path, with error: libc.musl-x86_64.so.1: cannot open shared object file: No such file or directory
[LIFERAY] Executing scripts in /usr/local/liferay/scripts/post-shutdown:
[LIFERAY] Executing 010_shutdown.sh.
[DXP Cloud] shutting down liferay service

Environment

  • Liferay PaaS

Resolution

  • There is an error (LCE-2203) in the Liferay service images in the versions d2.x.x.
  • This error avoids installing the Dynatrace correctly when the container is starting.
  • This error was solve in the release DXP Stack 2021.50.1.
  • To resolve the problem, the image used in the Liferay service LCP.json should be d4.3.1 or newer.

 

 

 

Did this article resolve your issue ?

Legacy Knowledge Base