• 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

Issue Everything works, just plesk is not responding. Reinstall it?

nardev

New Pleskian
Hello,

I have quite a big mess on my plesk server, i'm looking at logs but i can't determine what is going one since there is nothing going on.

When i try to open plesk, i just get "waiting" in my browser.

When i try to run some command like "/usr/local/psa/bin/pleskbackup server" again, it just stops.

Websites and all other services works just fine. It shows 12.5 current version.

Is there any way for me to run reinstall plesk but not to damage anything else and to "suck in" all current websites in that reinstalled plesk?

p.s. since it seemed to me that plesk tried to "upgrade" to newer version, i tried this, but it just stops at that point and gives no return:


=====

sth@server: /var/lib/psa/dumps# /opt/psa/bootstrapper/pp12.5.30-bootstrapper/bootstrapper.sh repair
Started bootstrapper repair procedure. This may take a while.
Certain actions may be skipped if not applicable.

-- Warning: Skipping the data of table mysql.event. Specify the --events option explicitly.
Finishing up upgrade procedures and rerunning previously failed upgrade actions...
===> Cumulative APS controller database (apsc) upgrade and repair has been started.
===> Cumulative upgrade and repair of APS controller database has been completed.
===> Cumulative APS controller upgrade and repair (final stage) has been started.
===> Cumulative upgrade and repair of APS controller (final stage) has been completed.
===> Cumulative Plesk database upgrade and repair (revertable stage) has been started.
===> Preparing Plesk database upgrade (revertable stage).
===> Cumulative upgrade and repair of Plesk database (revertable stage) has been completed.
===> Plesk database scheme upgrade has been started.
Applying migrations from: /opt/psa/bootstrapper/pp12.5.30-bootstrapper/migrations/
===> Plesk database scheme upgrade has been completed.
---
 
Last edited:
Check that port 8443 is not firewalled. Check sw-cp-server logs - /var/log/sw-cp-server/error_log and /var/log/sw-cp-server/sw-engine.log
Make sure that you have similar output of command:

# lsof -i tcp:8443
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
sw-cp-ser 19038 root 14u IPv4 83064227 0t0 TCP *:pcsync-https (LISTEN)
sw-cp-ser 19038 root 16u IPv6 83064229 0t0 TCP *:pcsync-https (LISTEN)
sw-cp-ser 19039 sw-cp-server 14u IPv4 83064227 0t0 TCP *:pcsync-https (LISTEN)
sw-cp-ser 19039 sw-cp-server 16u IPv6 83064229 0t0 TCP *:pcsync-https (LISTEN)
 
Check that port 8443 is not firewalled. Check sw-cp-server logs - /var/log/sw-cp-server/error_log and /var/log/sw-cp-server/sw-engine.log
Make sure that you have similar output of command:

# lsof -i tcp:8443
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
sw-cp-ser 19038 root 14u IPv4 83064227 0t0 TCP *:pcsync-https (LISTEN)
sw-cp-ser 19038 root 16u IPv6 83064229 0t0 TCP *:pcsync-https (LISTEN)
sw-cp-ser 19039 sw-cp-server 14u IPv4 83064227 0t0 TCP *:pcsync-https (LISTEN)
sw-cp-ser 19039 sw-cp-server 16u IPv6 83064229 0t0 TCP *:pcsync-https (LISTEN)



Yep i get this:


COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
sw-cp-ser 23737 root 8u IPv4 288975 0t0 TCP *:8443 (LISTEN)
sw-cp-ser 23737 root 10u IPv6 288977 0t0 TCP *:8443 (LISTEN)
sw-cp-ser 23738 sw-cp-server 8u IPv4 288975 0t0 TCP *:8443 (LISTEN)
sw-cp-ser 23738 sw-cp-server 10u IPv6 288977 0t0 TCP *:8443 (LISTEN)
 
What about

Check that port 8443 is not firewalled. Check sw-cp-server logs - /var/log/sw-cp-server/error_log and /var/log/sw-cp-server/sw-engine.log

?
 
What about



?


2016/11/29 08:44:48 [crit] 23738#0: *46 connect() to unix:/var/run/sw-engine.sock failed (2: No such file or directory) while connecting to upstream, client: XXX, server: , request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock:", host: "XXX:8443"


I CURRENTLY STARTED
/usr/local/psa/bootstrapper/pp12.5.30-bootstrapper/bootstrapper.sh rerun
so that is why this is terminated, the issue is also that this "rerun" is stuck at

===> Cumulative upgrade and repair of Plesk (final stage) has been completed.
and it just blinks...

tail -f /var/log/sw-cp-server/sw-engine.log
[29-Nov-2016 08:35:54] NOTICE: configuration file /etc/sw-engine/sw-engine-fpm.conf test is successful

[29-Nov-2016 08:35:54] NOTICE: fpm is running, pid 23667
[29-Nov-2016 08:35:54] NOTICE: ready to handle connections
[29-Nov-2016 08:40:47] NOTICE: Terminating ...
[29-Nov-2016 08:40:47] NOTICE: exiting, bye-bye!
[29-Nov-2016 08:40:47] NOTICE: fpm is running, pid 32051
[29-Nov-2016 08:40:47] NOTICE: ready to handle connections
[29-Nov-2016 08:42:59] NOTICE: Terminating ...
[29-Nov-2016 08:42:59] NOTICE: exiting, bye-bye!
 
Since psa was stopped,

i started psa and now i get back to:

Base table or view not found: 1146 Table 'psa.sessions' doesn't exist (Pdo.php:234)


i tried to fix this through: https://kb.plesk.com/en/122876

but it didn't work as i said at
bootstrapper.sh --rerun
 
Try to fix it with

# plesk repair installation


ROW OPERATIONS
--------------
0 queries inside InnoDB, 0 queries in queue
1 read views open inside InnoDB
Main thread process no. 8882, id 140187012024064, state: sleeping
Number of rows inserted 2, updated 24, deleted 1, read 59899
0.02 inserts/s, 0.02 updates/s, 0.00 deletes/s, 341.62 reads/s
----------------------------
END OF INNODB MONITOR OUTPUT
============================

DATABASE ERROR!!!
Database psa found, but version undefined

ERROR while trying to find psa database
Check the error reason(see log file: /var/log/plesk/install/plesk_12.5.30_repair.log), fix and try again

***** problem report *****
ERROR while trying to find psa database
Check the error reason(see log file: /var/log/plesk/install/plesk_12.5.30_repair.log), fix and try again

exit status


====

and of course, i get the same error message in that log
 
Hi nardev,

the mentioned KB - article 6586 defines SEVERAL SYMPTOMS, which all could be solved with the provided resolution. If you don't tryout the given resolution at least, you will never find out, if this fixes your current described issue(s). ;)
 
Back
Top