Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

A build to update the patching tool is stuck and failed

Written By

Sivakumar Perumal

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How to articles!

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

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability 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

  • A build to install the patching tool in Liferay fails as the default.properties is not getting created and somehow the pod got stuck at the below point.
     
    Oct 26 19:30:51.126 build-10 [liferay-7768cf9c77-sk8nz] [LIFERAY] Updating Patching Tool.
    Oct 26 19:30:56.399 build-10 [liferay-7768cf9c77-sk8nz] Auto discovery looks for portal segments. The selected directory is "/opt/liferay/tomcat".
    Oct 26 19:30:57.114 build-10 [liferay-7768cf9c77-sk8nz] The .liferay-home has not been detected in the given directory tree.
    Oct 26 19:30:57.114 build-10 [liferay-7768cf9c77-sk8nz] 
    Oct 26 19:30:57.114 build-10 [liferay-7768cf9c77-sk8nz] Configuration:
    Oct 26 19:30:57.114 build-10 [liferay-7768cf9c77-sk8nz] patching.mode=binary
    Oct 26 19:30:57.115 build-10 [liferay-7768cf9c77-sk8nz] war.path=../tomcat/webapps/ROOT/
    Oct 26 19:30:57.115 build-10 [liferay-7768cf9c77-sk8nz] global.lib.path=../tomcat/lib/ext/
    Oct 26 19:30:57.115 build-10 [liferay-7768cf9c77-sk8nz] liferay.home=[please enter manually]
    Oct 26 19:30:57.115 build-10 [liferay-7768cf9c77-sk8nz] 
    Oct 26 19:30:57.115 build-10 [liferay-7768cf9c77-sk8nz] The configuration hasn't been saved. Please save this to the default.properties file.
    Oct 26 19:30:57.625 build-10 [liferay-7768cf9c77-sk8nz] 
    Oct 26 19:30:57.625 build-10 [liferay-7768cf9c77-sk8nz] [LIFERAY] Patching Tool updated successfully.
    Oct 26 19:31:01.602 build-10 [liferay-7768cf9c77-sk8nz] There's no configuration available. Running auto-discovery in the parent folder.
    Oct 26 19:31:01.604 build-10 [liferay-7768cf9c77-sk8nz] Directory is not set in command line, using ../
    Oct 26 19:31:01.785 build-10 [liferay-7768cf9c77-sk8nz] Auto discovery looks for portal segments. The selected directory is "/opt/liferay".

Environment

  • Liferay SaaS

Resolution

  • The behavior is due to the script that scans documents under the data folder to detect Liferay home and takes more time. Since this time is exceeding the deployment timeout, the deployment fails.
  • As a workaround, this can be resolved by adding a below default.properties file to the patching tool.zip and permanently can be resolved by using the latest docker image version.
     
    patching.mode=binary
    war.path=../tomcat/webapps/ROOT/
    global.lib.path=../tomcat/lib/ext/
    liferay.home=../

Additional Information

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