Facebook
Twitter
learning_curve
Golden Pleskian
We've run the CLI 17.5.3 > 17.8.11 upgrade process a couple of times, which went quite well, but we're still on 17.5.3 when posting this thread. There were some issues (shown below) the biggest being that sw-cp-server won't run after the upgrade. We run a cloud server, so if there's impactive upgrade issues, we immediately revert back to the pre-upgrade server snapshot with just a few seconds downtime / almost negligable loss of web service. This means we can go and investigate the upgrade issues (e.g. this thread...) solve them and then run the the CLI 17.5.3 > 17.8.11 upgrade process again, sucessfully, if we're lucky 
1) At the pre-upgrade check stage, we get the same error that's already been posted in other threads, relating to web server templates located in /usr/local/psa/admin/conf/templates/custom/ However, like other users have posted, we have no custom templates located in there anyway... and, if we run a previoulsy posted solution, which was; run # plesk repair db then # plesk repair web before the upgrade and then try running the upgrade again We still get exactly the same error message (warning?) at the pre-upgrade check stage.
2) At the changing shell for mhandlers-user stage, we get warnings about missing files e.g.
3) At the same stage, we also get errors which appear at this (early) stage, to be of no immediate detrimental effect e.g.
4) During the Installing Admin Server stage, we get this failure / warning and it is repeated, at the end of this stage too:
5) Then at the end, we see:
Followed soon after by
But having seen earlier that sw_cp_server service failed to start message, we ran
Which tells us
And if we investigate further, we see
We've looked, but can't see a reference to that particular error anywhere else. There was no file named: /etc/sw-cp-server/conf.d/repair_plesk in the /etc/sw-cp-server/conf.d folder with which, we could try and trace any possible reasons for this error... It appears that it may possibly be related to permissions, but, where, we're not sure at this stage. FWIW the file /etc/sw-cp-server/config itself, plus the contents of /etc/sw-cp-server/ and /etc/sw-cp-server/conf.d all seemed to be unchanged...
We think 2) is a set of standard warnings and isn't an issue for us
We think 3) should be okay when we work further on selinux and therefore isn't an issue for us
We think 4) is fine for us because we don't use or have, any chrooted domains anyway (currently)
We'd like to fix 1) and obviously, we do need to fix 5) because that prevented us from even logging into the 17.8.11 Plesk Panel! Anyone from Plesk, your help would be most welcome
1) At the pre-upgrade check stage, we get the same error that's already been posted in other threads, relating to web server templates located in /usr/local/psa/admin/conf/templates/custom/ However, like other users have posted, we have no custom templates located in there anyway... and, if we run a previoulsy posted solution, which was; run # plesk repair db then # plesk repair web before the upgrade and then try running the upgrade again We still get exactly the same error message (warning?) at the pre-upgrade check stage.
2) At the changing shell for mhandlers-user stage, we get warnings about missing files e.g.
Code:
Cleanup: plesk-roundcube [78/135]
warning: file /var/tmp/plesk-roundcube: remove failed: No such file or directory
Code:
Updating: psa-selinux-17.8.11-cos7.build1708180212.17.noarch [70/135]
Failed to resolve roletype statement at /etc/selinux/tmp/tmp/modules/400/plesk/cil:2
semodule: Failed!
Failed to resolve roletype statement at /etc/selinux/final/tmp/modules/400/plesk/cil:2
semodule: Failed!
Code:
which: no unrar in (/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin)
Trying to install sftp-server binary into chroot environment... cp: cannot stat 'internal-sftp': No such file or directory
done
/var/www/vhosts/chrootinternal-sftp: inode/directory; charset=binary
probably it will not work in chrooted accounts
WARNING!
Some problems are found during register /var/www/vhosts/chrootinternal-sftp in chrooted environment(see log file: /var/log/plesk/install/plesk_17.8.11_installation.log)
Code:
Starting sw_cp_server service... failed
Code:
...
All files were downloaded.
All patches were applied.
Patches were installed successfully.
Launching component and product checkers...
Downloading file PSA_17.8.11/examiners/congratulations.sh: 100% was finished.
Components and product check results:
Upgrade is finished
Congratulations...!
Code:
systemctl status sw-cp-server.service
Code:
● sw-cp-server.service - Startup script for Plesk control panel server
Loaded: loaded (/usr/lib/systemd/system/sw-cp-server.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2018-07-16 03:18:30 BST; 40s ago
Process: 29842 ExecStartPre=/usr/sbin/sw-cp-serverd -q -t (code=exited, status=1/FAILURE)
Main PID: 3665 (code=exited, status=0/SUCCESS)
Code:
* systemd[1]: Starting Startup script for Plesk control panel server...
* sw-cp-serverd[29842]: nginx: [emerg] unknown directive "auth_request" in /etc/sw-cp-server/conf.d/repair_plesk.inc:5
* sw-cp-serverd[29842]: nginx: configuration file /etc/sw-cp-server/config test failed
* systemd[1]: sw-cp-server.service: control process exited, code=exited status=1
* systemd[1]: Failed to start Startup script for Plesk control panel server.
* systemd[1]: Unit sw-cp-server.service entered failed state.
* systemd[1]: sw-cp-server.service failedWe think 2) is a set of standard warnings and isn't an issue for us
We think 3) should be okay when we work further on selinux and therefore isn't an issue for us
We think 4) is fine for us because we don't use or have, any chrooted domains anyway (currently)
We'd like to fix 1) and obviously, we do need to fix 5) because that prevented us from even logging into the 17.8.11 Plesk Panel! Anyone from Plesk, your help would be most welcome
