Download logs fails with error 500 and apache does not start or Watchdog killed DR process
Issue:
Trying to download logs from the UI fails with error 500 or error Critical Error Watchdog Killed DR process after not responding for more than 1800 seconds
And apache logs showing permission error in /var/log/apache2/error.log (you will need to run sudo su command to access folder/file)
[Sun
Jan 08 06:25:58.075748 2023] [wsgi:error] [pid 27795:tid 140300522448640]
[client 127.0.0.1:33668] PermissionError: [Errno 13] Permission denied: '/var/log/cpm/cpm_server.log'
In addition, During server restart apache might not start.
This could also cause the error message Critical Error - Watchdog Killed DR process after not responding for more than 1800 seconds
Note: This KB is relevant for 4.1 and below, as this was handled in latest 4.2.2 version
Solution:
1. connect to cpm over SSH using cpmuser and your key.
2. run the following command:
- sudo chown -R www-data:www-data /var/log/cpm
After this log download should work and the apache server will start correctly.
Related Articles
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, ...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 ...Permission checks fails with Error: “User not Found”
Permission checks fails with Error: “User not Found” You may receive the following error when checking permissions on an account within CPM. Also, the policy check .CSV file will show only “User not Found” when opened. In the cpm_server logs you ...DR may fail with "DR encountered an internal problem and failed" instead of printing the actual permissions issue
DR may fail with "DR encountered an internal problem and failed" instead of printing the actual permissions issue with CPM role. You may find the error message below in backup log. This message is not informative. Error - DR encountered an internal ...Error on CPM thin agent install: Service failed to start due to insufficient privilege error
If you try to install a new CPM Agent (thin agent) used for VSS backups onto a Windows system that has an old version of the client installed, you will get the following error during the installation process when Windows attempts to start the ...