Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

Backup is failed with RangeError

Written By

Balázs Létai

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

  • Backup is failed with RangeError
    ERROR 
    [WARN] RangeError: The offset is lower than the number of bytes written. The server has 1990721536 bytes and while 1990861321 bytes has been uploaded - thus 139785 bytes are missing. Stopping as this could result in data loss. Initiate a new upload to continue. 
        at Upload.startUploading (/lcp/app/backup/node_modules/@google-cloud/storage/build/src/resumable-upload.js:360:32) 
        at Upload.continueUploading (/lcp/app/backup/node_modules/@google-cloud/storage/build/src/resumable-upload.js:347:14) 
        at runMicrotasks (<anonymous>) 
        at processTicksAndRejections (internal/process/task_queues.js:95:5) 
    ERROR 
    [WARN] Storage upload currently unavailable - attempt: 2

Environment

  • Liferay PaaS

Resolution

  • When RangeError observed, it could be due to the document library and/or database being updated mid-upload and causing a syncing issue that cannot be resolved without creating a new backup.
  • Attempt to initiate a new backup manually, and see if this failure could be still observed.

 

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