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

    • How to upgrade CPM using a patch

      Please note: upgrading using patch does not upgrade Apache 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. When using ...

    • Must Gather information for CPM: how to collect relevant details for support.

      When opening a support ticket, please provide the following information. You can attach the collected files (preferably in a single archive) to the ticket or an email reply (up to 20MB). For larger files, please ask the support team for FTP ...

    • Does CPM Support rolling forward SQL logs after restore?

      CPM doesn't support rolling forward SQL logs, since CPM performs "full backup", not "logs backup". We recommend to use the simple recovery model with CPM backups.