Cleanup process may abort due to timeout

Cleanup process may abort due to timeout

If Cleanup process doesn't end successfully, download the cpm logs and search for the following consecutive messages:

ERROR: get_cleanup_data_request(.\common\agentapi_requests.py:146) failed calling url https://127.0.0.1:443/agentapi/cleanup/. Exception: The read operation timed out

ERROR: cleanup_function(.\n2wsoftware\cpmagent\agent.py:2614) get_cleanup_data_request failed, aborting cleanup

If you found the below message printed approximately 2 minutes before the above messages, please upgrade to latest 2.X.X Version

INFO: cleanup_function(.\n2wsoftware\cpmagent\agent.py:2609) Scheduled cleanup started

 

Reference defect number - d7f45e2233, fixed in v2.2.0


    • Related Articles

    • Cleanup Log

      This feature was added to allow CPM users to better understand whether Cleanup process ran successfully. It can be found in the “General Settings” tab. The Cleanup Interval may be set to run every 1 to 24 hours. Last cleanup timestamp will show the ...
    • Cleanup process may end abruptly with UnboundLocalError after upgrade to v2.3.x

      If Cleanup process doesn't complete successfully in v2.3.0/a/b, please download the logs and look for the below print: ERROR: _run_job…"cleanup_function (trigger: interval…, next run at: …" raised an exception Traceback (most recent call last): … ...
    • Cleanup may not delete snapshots older than the defined retention for the policy

      CPM removes the snapshots in accordance with defined retention policies. However, only successful backups are counted towards the retention. It is crucial to understand what a "successful backup" is. A "successful backup" is a backup that has both ...
    • DR process may time out due to exceeding the snapshot limit per region

      In case Backup finished successfully but DR failed after 24 hours due to timeout as seen in the “Backup Log” example below: Error - DR process failed: Timed out after 24 hours Please download logs and search the CPM logs for: RDS DR We reached the ...
    • CPM v3.0.x may launch unnecessarily large Cleanup workers, resulting in extra costs

      CPM v3.0.x may launch unnecessarily large Cleanup workers, resulting in extra costs. In order to reduce the costs, please use the following procedure: Connect (via ssh) to the machine running cpm (you will need to execute "sudo -i" to gain the root ...