N2WS-21357 - Patch installation fails with Internal Server Error

N2WS-21357 - 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 PrivateTmp is set to true, change it to false, you can do it with this command:

sudo sed -i 's|PrivateTmp=true|PrivateTmp=false|g' /lib/systemd/system/apache2.service


Then restart apache2 service:

sudo systemctl daemon-reload

sudo systemctl restart apache2



    • Related Articles

    • N2WS-22811 - Backup fails with error "internal agent error"

      Issue: Backup fails with internal agent error in UI, because it fails to auto-remove terminated instances There is this error in UI Error - Backup is aborted due to an internal agent error and this error in server logs WARNING: ...

    • N2WS-22811 - Backup fails with error "internal agent error"

      Issue: Backup fails with internal agent error in UI, because it fails to auto-remove terminated instances There is this error in UI Error - Backup is aborted due to an internal agent error and this error in server logs WARNING: ...

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

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