N2WS-17075 - logs can be unexpectedly truncated

N2WS-17075 - logs can be unexpectedly truncated

Issue:

CPM logs of Server, API and DR might get unexpectedly truncated, resulting in smaller logs that might make it harder to analyze potential issues.

Solution:
Patch for v3.2.1 Available and attached to this KB

Click here to go back to the Release notes: Release notes for the latest v3.2.x CPM release

    • 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 ...

    • 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, ...

    • N2WS-23161 - When server fails to terminate worker, it is failing to add log message

      Issue: When N2WS Server is failing to terminate a worker instance, there is an exception when adding the log Traceback (most recent call last): File "./cpmserver/cpm/backup_copy/proxy_operations.py", line 194, in terminate_proxy File ...

    • N2WS-24114 - N2WS AMI redeploy fails for server upgraded with patch

      Issue: Customers who upgraded their N2WS server from v4.2 to v4.3 with patch downloaded from release notes before 20th June, will not be able to redeploy the server. When trying to redeploy from marketplace and using existing 4.3 cpmdata volume, ...

    • How to upgrade CPM using a patch

      Please note: upgrading using patch does not upgrade Apache/OS Upgrade Diagram General 1. It is recommended to deploy the patch when you have no active backup policies, DR or recovery running. as it will restart Apache and require few min downtime. 2. ...