• 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 File Not Found when accessing Control Panel

KalenXI

New Pleskian
It appears over the weekend something changed that broke the Plesk control panel. When I first tried to access the control panel I was getting a 502 error on every page. I found another forum post that suggested rebooting the server would fix the issue so I did that and now I get a "File Not Found" error on every control panel page.

The server is running Ubuntu 14.04.5 LTS and Plesk 12.5.30

This is what I get in /var/log/sw-cp-server/error_log:
Code:
2017/07/26 20:22:39 [error] 5162#0: *14 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 96.244.198.243, server: , request: "GET /smb/ HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock:", host: "vps61071.vps.ovh.ca:8443"
2017/07/26 20:22:41 [error] 5162#0: *14 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 96.244.198.243, server: , request: "GET /smb/ HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock:", host: "vps61071.vps.ovh.ca:8443"
2017/07/26 20:24:54 [error] 5162#0: *24 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 96.244.198.243, server: , request: "GET /admin HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock:", host: "vps61071.vps.ovh.ca:8443"
2017/07/26 20:36:23 [error] 12858#0: *1 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 96.244.198.243, server: , request: "GET /smb HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock:", host: "vps61071.vps.ovh.ca:8443"
2017/07/26 20:36:28 [error] 12858#0: *1 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 96.244.198.243, server: , request: "GET /smb HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock:", host: "vps61071.vps.ovh.ca:8443"
2017/07/27 00:11:17 [error] 2168#0: *1 directory index of "/opt/psa/admin/htdocs/" is forbidden, client: 196.52.43.53, server: , request: "GET / HTTP/1.1", host: "lastedit.com"
2017/07/29 01:04:46 [error] 2168#0: *4 directory index of "/opt/psa/admin/htdocs/" is forbidden, client: 209.126.136.4, server: , request: "GET / HTTP/1.1", host: "158.69.216.51:8443"
2017/07/29 06:24:24 [error] 2168#0: *6 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 96.244.198.243, server: , request: "GET /smb/ HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock:", host: "vps61071.vps.ovh.ca:8443"
2017/07/29 06:24:24 [error] 2168#0: *6 open() "/opt/psa/admin/htdocs/favicon.ico" failed (2: No such file or directory), client: 96.244.198.243, server: , request: "GET /favicon.ico HTTP/1.1", host: "vps61071.vps.ovh.ca:8443", referrer: "https://vps61071.vps.ovh.ca:8443/smb/"
2017/07/29 06:28:28 [error] 2168#0: *8 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 96.244.198.243, server: , request: "GET /smb/ HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock:", host: "vps61071.vps.ovh.ca:8443"

I've also tried running the bootstrapper repair which results in:
Code:
# ./bootstrapper.sh repair                                                                                                             1 ↵
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.

**** Product repair started.

===> Checking for previous installation ... not found.
Started bootstrapper repair procedure. This may take a while.
Certain actions may be skipped if not applicable.

 Trying to start service mysql... /usr/sbin/mysqld (pid 1112) is running...
done
 Trying to establish test connection... connected
done
 Trying to find psa database... version is 012005030
Version is OK, no need to create psa database.
 Trying to backup MySQL database... done
 MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.-12.5.30.20170729-064509.dump.gz
 Finishing up upgrade procedures and rerunning previously failed upgrade actions...
./bootstrapper.sh: line 839: /usr/lib/plesk-9.0/vps_optimized_aspects/mysql-innodb: No such file or directory
===> Cumulative APS controller database (apsc) upgrade and repair has been started.
Upgrade or repair for 'apsc' (stage 'prep') is not required
 Trying to backup MySQL database... done
 MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.apsc.-12.5.30.20170729-064510.dump.gz
===> Cumulative upgrade and repair of APS controller database has been completed.
Could not open input file: /opt/psa/admin/plib/scripts/check_apsc_connection.php
 Trying to reset database user password for 'apsc@'... done

ERROR while trying to can not find "register_apsc_database.php"
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 can not find "register_apsc_database.php"
Check the error reason(see log file: /var/log/plesk/install/plesk_12.5.30_repair.log), fix and try again

Checking the repair log shows the same error:
Code:
# tail /var/log/plesk/install/plesk_12.5.30_repair.log                                                                                 1 ↵

===> Restoring database from backup /var/lib/psa/dumps/mysql.preupgrade.-12.5.30.20170729-064509.dump.gz


**** Product repair failed.

*****  problem report *****
ERROR while trying to can not find "register_apsc_database.php"
Check the error reason(see log file: /var/log/plesk/install/plesk_12.5.30_repair.log), fix and try again
STOP Bootstrapper 12.5.30 repair AT Sat Jul 29 06:45:50 EDT 2017

I've also tried running plesk repair, but the plesk command is apparently not installed:
Code:
# plesk repair                                                                                                                         1 ↵
zsh: command not found: plesk
 
Try to run

# plesk installer --select-release-current --reinstall-patch --upgrade-installed-components

and then

# plesk repair installation
 
Like I said, the plesk CLI utility doesn't appear to be installed or isn't in my path:

Code:
# plesk installer --select-release-current --reinstall-patch --upgrade-installed-compnents
zsh: command not found: plesk

Where would that utility typically be installed? Perhaps I just need to include it in my terminal path. Or alternatively is there a way to run that command without the CLI utility?
 
Back
Top