• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved Unable to access login page - due to failed update?

Martin Allen

New Pleskian
We are unable to access the Plesk login page for our server (https://77.68.11.162:8443/) running Plesk Onyx on CentOS 7
eventually receiving a 504 Gateway timeout - this was working correctly up to yesterday.

All the Plesk Services are running
#systemctl status sw-engine
#systemctl status sw-cp-server
#systemctl status psa
all return as active (running) or active (exited) for psa

looking in the /usr/local/psa/admin/logs/panel.log
it looks like an automatic update failed?

Code:
[2017-12-05 03:22:14] ERR [panel] Task failed: id=971, pid=53063, type=panel-update, error=Execution failed.
Command: autoinstaller
Arguments: Array
(
    [0] => --select-product-id
    [1] => plesk
    [2] => --select-release-current
    [3] => --upgrade-installed-components
)

Details: Doing restart of Plesk Installer...
Downloading file products.inf3: 0%
.......
Downloading file PHP71_17/php71-cos7-x86_64.plesk17.inf3: 100% was finished.
Downloading file SITEBUILDER_17.0.15/sitebuilder-17.0.15-rhall-all.inf3: 0%
Downloading file SITEBUILDER_17.0.15/sitebuilder-17.0.15-rhall-all.inf3: 100% was finished.
gpg-pubkey-f4a80eb5-53a7ff4b gpg(CentOS-7 Key (CentOS 7 Official Signing Key) <[email protected]>)
gpg-pubkey-914bdf7e-55c05220 gpg(Plesk Team <[email protected]>)
gpg-pubkey-be1229cf-5631588c gpg(Microsoft (Release signing) <[email protected]>)
gpg-pubkey-404d2e7a-55709ddb gpg(DataGrid <[email protected]>)
gpg-pubkey-8508ad86-5787fd00 gpg(DataGrid (No sub-key) <[email protected]>)
gpg-pubkey-2c52609d-55a59f6e gpg(Docker Release Tool (releasedocker) <[email protected]>)
gpg-pubkey-352c64e5-52ae6884 gpg(Fedora EPEL (7) <[email protected]>)
Loaded plugins: fastestmirror, priorities
Repository packages-microsoft-com-prod is listed more than once in the configuration


Detecting installed product components.
gpg-pubkey-f4a80eb5-53a7ff4b gpg(CentOS-7 Key (CentOS 7 Official Signing Key) <[email protected]>)
gpg-pubkey-be1229cf-5631588c gpg(Microsoft (Release signing) <[email protected]>)
gpg-pubkey-404d2e7a-55709ddb gpg(DataGrid <[email protected]>)
gpg-pubkey-8508ad86-5787fd00 gpg(DataGrid (No sub-key) <[email protected]>)
gpg-pubkey-2c52609d-55a59f6e gpg(Docker Release Tool (releasedocker) <[email protected]>)
gpg-pubkey-352c64e5-52ae6884 gpg(Fedora EPEL (7) <[email protected]>)
gpg-pubkey-914bdf7e-55c05220 gpg(Plesk Team <[email protected]>)
Retrieving information about the installed license key...
Launching component and product checkers...
Downloading file PSA_17.0.17/examiners/disk_space_check.sh: 0%
Downloading file PSA_17.0.17/examiners/disk_space_check.sh: 100% was finished.
Downloading file PSA_17.0.17/examiners/panel_preupgrade_checker.php: 0%
Downloading file PSA_17.0.17/examiners/panel_preupgrade_checker.php: 100% was finished.
Downloading file PSA_17.0.17/examiners/php_launcher.sh: 0%
Downloading file PSA_17.0.17/examiners/php_launcher.sh: 100% was finished.
Loaded plugins: fastestmirror, priorities
Repository packages-microsoft-com-prod is listed more than once in the configuration

NGINX-thirdparty                                         | 2.9 kB     00:00     

PHP_5_6-thirdparty                                       | 2.9 kB     00:00     

PHP_7_0-thirdparty                                       | 2.9 kB     00:00     

....

updates/7/x86_64/primary_db                              | 3.6 MB     00:00     
remi-safe/primary_db                             0.0 B/s | 1.1 MB     00:00     

remi-safe/primary_db                                     | 1.1 MB     00:11     
Determining fastest mirrors
 * base: mirrors.coreix.net
 * epel: mirrors.coreix.net
 * epel-debuginfo: mirrors.coreix.net
 * epel-source: mirrors.coreix.net
 * extras: centos.serverspace.co.uk
 * remi-safe: mirror.23media.de
 * updates: centos.serverspace.co.uk
 * webtatic: uk.repo.webtatic.com
131 packages excluded due to repository priority protections
+ plesk-php71-intl
+ plesk-php70-fpm
....
+ plesk-php70-snmp
+ plesk-php70-tidy
+ plesk-php70-soap

Installing packages
Unable to create lock file in /var/lock
Another instance of bootstrapper is already running. Please wait until it finishes.
If you are completely sure there is no other instance running,
just remove /var/lock/parallels-panel-bootstrapper-running.lock file and retry.
Note: running more than one instance at once may badly damage your system.

ERROR: An error occurred during performing of installation PREP actions (see log for details). Installation was rolled back.
Warning! Not all packages were installed.
Please check if your system services are operable.
Please resolve this issue and try to install the packages again.
If you cannot resolve the issue on your own, contact product technical support for assistance.

I've looked in /var/lock and there is indeed a parallels-panel-bootstrapper-running.lock file, but how can I tell if there is no other instance running?

Would this be the cause of the problem, and if it is, how do I fix it?!
 
After some help from 1&1 and Plesk Technical support the issue has now been resolved - their solution is below

The issue is resolved and Plesk is accessible.
The issue is similar to SystemD bug described in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756760 , when SystemD does not clean stale session files, which are in "closing" state.
I have moved /var/run/session files into /123/session, then restarted: systemd-loginctl , systemd-user-sessions services and all plesk managed services via

# service systemd-loginctl restart
# service systemd-user-sessions restart
# service psa stopall
# service psa startall

Afterwards, I was able to get access to Plesk and use plesk command line tools.
I also see that while I was logged on the server, most system packages were updated.

[root@localhost sessions]# yum load-transaction
[...]
114 packages excluded due to repository priority protections
?? | Install | Remove | Filename
* | 43 | 42 | yum_save_tx.2017-12-07.18-48.zKZck9.yumtx
y | 5 | 4 | yum_save_tx.2017-12-07.19-36.QSJ7Oq.yumtx
y | 5 | 4 | yum_save_tx.2017-12-07.19-36.xODx1Y.yumtx

------------------------------------------------------------------------------------------------
 
Back
Top