Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

Deployment timeout when deploying backup service

Written By

Gustavo Vasconcelos

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

  • Under certain circumstances, a new deployment fails with a timeout message around the 30 minute mark:
Deployment timeout in 30m 13s
  • The error always includes the backup service failing to deploy:
Deployment timed out for
backup liferaycloud/backup:4.2.1
  •  Other services may or may not also have a failed deployment state, but backup is always one of them.

Environment

  • Liferay Cloud
  • Liferay PaaS

Resolution

  • The reason for a deployment timeout that includes the backup service may be related to a currently running backup operation (backup creation or backup upload).
  • You can check if there's a backup operation currently running by checking the logs of the backup service:
Jul 12 13:13:00.816 build-1418 [backup-7df55665b7-gxwlf] [INFO] 16.89 GiB uploaded for mnglojjnwbzxslmsxc/volume/dxpcloud-mnglojjnwbzxslmsxc-202207121558.tgz
  • During this operation, the previous backup instance will refuse to termine until the upload is complete. New instances will fail to start up because the old instance is still running, and the deployment will time out.
  • The solution for this is issue is either:
    • Wait for the running backup operation to complete, and then deploy the new services:
Jul 12 13:18:00.817 build-1418 [backup-7df55665b7-gxwlf] [INFO] 24.96 GiB uploaded for mnglojjnwbzxslmsxc/volume/dxpcloud-mnglojjnwbzxslmsxc-202207121558.tgz
Jul 12 13:18:29.324 build-1418 [backup-7df55665b7-gxwlf] [INFO] Volume backup succeeded: mnglojjnwbzxslmsxc/volume/dxpcloud-mnglojjnwbzxslmsxc-202207121558.tgz
Jul 12 13:18:29.324 build-1418 [backup-7df55665b7-gxwlf] [INFO] Backup completed: dxpcloud-mnglojjnwbzxslmsxc-202207121558
<From this point on you can deploy new services>
    • Create and deploy a new build that doesn't include a deployment for the backup service.

Additional Information

 

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