N2WS-21963 - Copy to S3 fails with Failed to stop processor(s)

• Related Articles

• Patch installation fails with Internal Server Error

  Issue: Patch installation fails with this error in the UI Solution: 1. Connect to the N2WS server via SSH, username is cpmuser and your selected keyPair 2. Run the following command sudo grep PrivateTmp /lib/systemd/system/apache2.service 3. If ...

• N2WS-20766 - RDS export fails due to error "RestoreDBInstanceFromDBSnapshot operation: No default subnet detected"

  Issue: When trying to export RDS instance to S3 bucket, it fails with the following error: Error Process reported error: Failed to create DB instance from snapshot cpm-policy-1-db1-2011-1-11-1-11: An error occurred (InvalidSubnet) when calling the ...

• DR may fail due to the "snap-0123456789abcdef failed, has status error" error

  If Cross-Region DR fails with the following error in the Backup Log: Error - Volume DR copy snapshot failed for region <Region Name>, snapshot snap-<snapshot_ID>e (status: error).” Please download the logs from CPM GUI and search for the following: ...

• Copy backup to S3 may fail with the error message "Workers could not be launched"

  During backup copy to S3 a worker creation may fail with the error (backup.log): - Error - Workers could not be launched The worker usually fails right after it was started. There are several possible issues that gives you this error. 1) The was an ...

• N2WS-22420 - Copy to S3 failing with local device /dev//dev/xvdf (/dev/xvdf) does not exist

  Issue: Copy To S3 is failing with the following error: Solution: Patch for v4.1.1a is available and attached to this KB. Click here to go back to the Release notes: Release notes for the latest v4.1.x CPM release