How to test the worker configuration from UI
Background:
This document explains the steps to test a CPM Worker configuration. This can help reduce errors during S3 copy and File-Level restores by being able to confirm the settings used for these jobs are successfully able to connect.
Worker configuration are used for EC2/EBS copy to S3, File level recovery and cleanup.
Steps:
1. To test a worker configuration, select in the left-hand pane the Worker Configuration option.
2. Select the worker in the list and select Test
3. You will get several options for the test
(1) - This is always selected, this test if the EC2 worker can communicate with the N2WS server over HTTPS(port 443)
(2) - This is used for File Level recovery(FLR/Explore), it test connection over SSH (port 22) from the temporary ec2 worker to the N2WS server.
(3) - This is used by Copy to S3 and FLR, it test the connection from the worker to the EBS API endpoint
($) - This is used by Copy to S3 and FLR from S3 and cleanup, it test the connection from the worker to the S3 service
4. Check the
results in the Test Status column:
Successful or Failed.
5. This shows a successful test status.
6. Clicking on ‘Test Status’ during or after the failure should expose the root cause of a worker test failure.After a worker test has failed, it will provide a Failure Reason – as shown below.
All Worker test results are logged to the cpm-server logs and will have a message showing why it failed. in this example, it's a timeout.
2020-03-04 19:52:42,236:[139931287242496][gOLjzcrkQs] ERROR: check_test_worker_operation(worker_utils.py:588) Worker configuration for Account - demo-account-1, Region Asia Pacific (Hong Kong), test failed. No communication after 0:10:00 minutes
Related Articles
Troubleshooting File Level Recovery (FLR) communication issue
CPM Configuration File-level recovery requires N2WS to recover volumes in the background and attach them to a temporary EC2 ‘worker’ launched for the operation, The worker will be launched in the same account and region as the snapshots being ...Troubleshooting File Level Recovery (FLR) 3.2
Background: File-level recovery requires N2WS to launch temporary worker instance in the target region. The worker will read the snapshot directly or recover volumes in the background and attach them to a ‘worker’ instance launched for the operation. ...How to retrieve logs from a CPM AWS Worker instance
Linux & AWS knowledge is required Please read the entire KB before starting. N2WS uses temporary EC2 worker instances for several operations (copy to S3, FLR, etc), In cases where a worker is failing before it could communicate with the main server, ..."Worker did not establish connection" and " worker did not complete initializing" errors during S3 and FLR
During S3 operations, you may encounter the message "Worker i-... did not establish connection" in the log of an S3 copy or S3 restore operation. Error - Worker i-1234567890abcdef did not establish connection - terminating operation During File Level ...How To Test Connectivity from a CPM Worker to AWS endpoints
The Following Steps will help you Test the outgoing connection from the CPM Worker to AWS endpoints OR the CPM Server if you need to test to ensure that the Worker can reach the CPM server once it launches. Launch Worker First, ensure the CPM Worker ...