• 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 Error 500 Plesk

S

Samuel Desloges

Basic Pleskian
Hello,

I have try to upgrade MariaDB like this:
How to upgrade MySQL 5.5 to 5.6/5.7 or MariaDB 5.5 to 10.0/10.1/10.2 on Linux?

and now I have:
[[controllers.error.error.title]]
500
Plesk\Exception\Database
DB query failed: SQLSTATE[HY000] [1049] Unknown database 'psa'

Type Plesk\Exception\Database
Message DB query failed: SQLSTATE[HY000] [1049] Unknown database 'psa'
File Mysql.php
Line 60


How can I restore the system or correct the problem?

I have find this log:

+ plesk-php72-pear

+ plesk-dovecot-pigeonhole

+ plesk-php72-cli

+ plesk-php72-opcache

+ plesk-mail-pc-driver

+ plesk-php72-fpm

+ plesk-php72-imap

+ wpb-headers

+ plesk-php72-ldap

+ plesk-php72-gd

+ plesk-php72-pdo

+ plesk-php72-dba

+ plesk-service-node-utilities

+ plesk-php72-ioncube-loader

+ plesk-php72-process

+ psa

+ perl-Git

+ plesk-web-hosting

+ plesk-git-http

+ psa-libpam-plesk

+ plesk-php72-xdebug

+ plesk-php72-odbc

+ plesk-php72-mysql

+ plesk-management-node

+ plesk-php72-intl

+ plesk-web-socket

+ psa-updates

+ plesk-php72-soap

+ plesk-php72-enchant

+ plesk-php72-sodium

+ plesk-php72-mbstring

+ plesk-backup-utilities

+ plesk-php72-imagick

+ plesk-dovecot

+ plesk-roundcube

+ psa-logrotate

+ plesk-php72-xmlrpc

+ git

+ plesk-php72-pspell

+ plesk-core-utilities

+ psa-phpmyadmin

+ plesk-resctrl

+ psa-locale-base-en-US

+ plesk-modsecurity-configurator

+ plesk-dovecot-imap-driver

+ psa-mail-driver-common

+ plesk-completion

+ wpb-core

+ plesk-repair-kit

+ plesk-php72-pgsql

+ psa-vhost

+ plesk-php72-bcmath

+ pp-sitebuilder

+ plesk-l10n

+ plesk-php72

+ psa-libxml-proxy

+ plesk-php72-redis

+ plesk-php72-snmp

+ psa-drweb-configurator

+ plesk-php72-xml

+ plesk-php72-tidy

Preparing Your System for Product Installation

===============================================================================



There are 72 packages required for the product to function properly which

were not found in your system.



There are 0 packages that need to be upgraded

in order to install the product.





Available actions:

(F) Go forward

(B) Go back

(Q) Cancel installation

(S) Show the list of packages



Select an action [F/b/q/s]: f

Installing packages

===> Cumulative Plesk database upgrade (revertable stage) has been started.

===> Preparing Plesk database upgrade (revertable stage).



**** Product prep-install started.

Create user 'psaadm' and group 'psaadm'

Group 'psaadm' already exists

Checking for the user 'psaadm'...

User 'psaadm' already exists

Create group swkey-data

Group 'swkey-data' already exists

Trying to add supplementary group 'swkey-data' for user 'psaadm'... already there

Trying to got legacy variables... done

Trying to save legacy variables... done

Trying to resolve hostname 'ns397050.ip-94-23-52.eu' and validate its IP address... done





===> Checking for the necessary system accounts

Checking for the system groups and users necessary for admin server...

Group 'psaadm' already exists

Checking for the user 'psaadm'...

User 'psaadm' already exists

Group 'psaserv' already exists

Trying to add supplementary group 'psaserv' for user 'psaadm'... already there

Group 'psacln' already exists

Checking that /usr/local/psa/bin/chrootsh registered as login shell...

/usr/local/psa/bin/chrootsh already registered as a login shell



===> Performing safe prep-install database actions





===> Upgrading database



Trying to start service mariadb... active

done

Trying to establish test connection... connected

done

Trying to find psa database... not found

ERROR 1049 (42000): Unknown database 'psa'

ERROR 1049 (42000): Unknown database 'psa'

Trying to backup MySQL database... done

MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.18.0.21-18.0.21.20200116-142017.dump.gz

ERROR 1049 (42000): Unknown database 'psa'

ERROR 1049 (42000): Unknown database 'psa'

===> Cumulative Plesk database upgrade (revertable stage) has been started.

ERROR 1049 (42000): Unknown database 'psa'

ERROR 1049 (42000): Unknown database 'psa'

Upgrade or repair for 'core' (stage 'prep') is not required

===> Preparing Plesk database upgrade (revertable stage).

Trying to set psa database version to 018000000... ERROR 1049 (42000): Unknown database 'psa'

ERROR 1049 (42000): Unknown database 'psa'



ERROR while trying to execute SQL query, the query was: replace into misc (param,val) values('version', '018000000')



Check the error reason (see log file: /var/log/plesk/install/plesk_18.0.21_installation.log), fix and try again

***** problem report *****

ERROR while trying to execute SQL query, the query was: replace into misc (param,val) values('version', '018000000')

sh: /usr/local/psa/admin/bin/php: No such file or directory



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.

Visit Plesk Help Center to search for a solution.

[root@ns397050 ~]# ^C

[root@ns397050 ~]# cd /var/log/plesk/install/

[root@ns397050 install]# ^C

[root@ns397050 install]# plesk_18.0.21_installation.log

-bash: plesk_18.0.21_installation.log: command not found

[root@ns397050 install]# vi plesk_18.0.21_installation.log

START Bootstrapper 19.0.21 prep-install for BASE AT Thu Nov 21 10:53:35 CET 2019



**** Product prep-install started.

Create user 'psaadm' and group 'psaadm'

Group 'psaadm' already exists

Checking for the user 'psaadm'...

User 'psaadm' already exists

Create group swkey-data

Group 'swkey-data' already exists

Trying to add supplementary group 'swkey-data' for user 'psaadm'... already there

Trying to got legacy variables... done

Trying to save legacy variables... done

Trying to resolve hostname 'ns397050.ip-94-23-52.eu' and validate its IP address... done





===> Checking for the necessary system accounts

Checking for the system groups and users necessary for admin server...

Group 'psaadm' already exists

Checking for the user 'psaadm'...

User 'psaadm' already exists

Group 'psaserv' already exists

Trying to add supplementary group 'psaserv' for user 'psaadm'... already there

Group 'psacln' already exists

Checking that /usr/local/psa/bin/chrootsh registered as login shell...

/usr/local/psa/bin/chrootsh already registered as a login shell



===> Performing safe prep-install database actions





===> Upgrading database



Trying to start service mariadb... active

done

Trying to establish test connection... connected

done

Trying to find psa database... version is 018000000

Trying to backup MySQL database... done

MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.18.0.20-18.0.21.20191121-105336.dump.gz

===> Cumulative APS controller database (apsc) upgrade 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.18.0.20-18.0.21.20191121-105337.dump.gz

===> Cumulative upgrade of APS controller database has been completed.

===> Cumulative Plesk database upgrade (revertable stage) has been started.

Upgrade or repair for 'core' (stage 'prep') is not required

===> Preparing Plesk database upgrade (revertable stage).

Trying to set psa database version to 018000000... done

===> Cumulative upgrade of Plesk database (revertable stage) has been completed.

===> Plesk database scheme upgrade has been started.

Applying migrations from: /usr/local/psa/bootstrapper/pp18.0.21-bootstrapper/migrations/

Migration 18.0.21/2019-11-12-07-09-27_add_open_in_new_tab_field_to_panel_notification_messages.php applied

===> Plesk database scheme upgrade has been completed.

Trying to start service mariadb... active

done

Trying to establish test connection... connected

done



**** Product prep-install for BASE completed successfully.



STOP Bootstrapper 18.0.21 prep-install for BASE AT Thu Nov 21 10:53:37 CET 2019

START Bootstrapper 18.0.21 prep-install for fail2ban-configurator AT Thu Nov 21 10:53:38 CET 2019



"plesk_18.0.21_installation.log" 10709L, 632831C


Thanks.
 
Is your mysql is working? try to restore psa database in this case (backup should be in /tmp/all-databases.sql )
 
No Mysql doesn't work.
I have the file all-databases.sql and I have all the files of my websites.
If I reinstall the server, can I restore my website with all-databases.sql and all the files of my websites.
If yes, how to restore all-databases.sql on Centos 7 or 8 (If I reinstall, I think to swotch on Centos 8 if it's possible).

Thanks.
 
Samuel Desloges said:
No Mysql doesn't work.
I have the file all-databases.sql and I have all the files of my websites.
If I reinstall the server, can I restore my website with all-databases.sql and all the files of my websites.
If yes, how to restore all-databases.sql on Centos 7 or 8 (If I reinstall, I think to swotch on Centos 8 if it's possible).

Thanks.
Click to expand...
What error do you have in mysql.log? service mysql status?
 
service mariadb status
Redirecting to /bin/systemctl status mariadb.service
● mariadb.service - MariaDB database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor pres et: disabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf
Active: active (running) since Thu 2020-01-16 14:15:33 CET; 3 days ago
Process: 10882 ExecStartPost=/usr/libexec/mariadb-wait-ready $MAINPID (code=ex ited, status=0/SUCCESS)
Process: 10844 ExecStartPre=/usr/libexec/mariadb-prepare-db-dir %n (code=exite d, status=0/SUCCESS)
Main PID: 10880 (mysqld_safe)
CGroup: /system.slice/mariadb.service
├─10880 /bin/sh /usr/bin/mysqld_safe --basedir=/usr
└─11055 /usr/libexec/mysqld --basedir=/usr --datadir=/var/lib/mysq...

Jan 16 14:15:31 ns397050.ip-94-23-52.eu systemd[1]: Starting MariaDB database...
Jan 16 14:15:31 ns397050.ip-94-23-52.eu mariadb-prepare-db-dir[10844]: Databa...
Jan 16 14:15:31 ns397050.ip-94-23-52.eu mariadb-prepare-db-dir[10844]: If thi...
Jan 16 14:15:31 ns397050.ip-94-23-52.eu mysqld_safe[10880]: 200116 14:15:31 m...
Jan 16 14:15:31 ns397050.ip-94-23-52.eu mysqld_safe[10880]: 200116 14:15:31 m...
Jan 16 14:15:33 ns397050.ip-94-23-52.eu systemd[1]: Started MariaDB database ...
Hint: Some lines were ellipsized, use -l to show in full.
 
service mariadb status -l
Redirecting to /bin/systemctl status -l mariadb.service
● mariadb.service - MariaDB database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf
Active: active (running) since Thu 2020-01-16 14:15:33 CET; 3 days ago
Process: 10882 ExecStartPost=/usr/libexec/mariadb-wait-ready $MAINPID (code=exited, status=0/SUCCESS)
Process: 10844 ExecStartPre=/usr/libexec/mariadb-prepare-db-dir %n (code=exited, status=0/SUCCESS)
Main PID: 10880 (mysqld_safe)
CGroup: /system.slice/mariadb.service
├─10880 /bin/sh /usr/bin/mysqld_safe --basedir=/usr
└─11055 /usr/libexec/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysql/plugin --log-error=/var/log/mariadb/mariadb.log --pid-file=/var/run/mariadb/mariadb.pid --socket=/var/lib/mysql/mysql.sock

Jan 16 14:15:31 ns397050.ip-94-23-52.eu systemd[1]: Starting MariaDB database server...
Jan 16 14:15:31 ns397050.ip-94-23-52.eu mariadb-prepare-db-dir[10844]: Database MariaDB is probably initialized in /var/lib/mysql already, nothing is done.
Jan 16 14:15:31 ns397050.ip-94-23-52.eu mariadb-prepare-db-dir[10844]: If this is not the case, make sure the /var/lib/mysql is empty before running mariadb-prepare-db-dir.
Jan 16 14:15:31 ns397050.ip-94-23-52.eu mysqld_safe[10880]: 200116 14:15:31 mysqld_safe Logging to '/var/log/mariadb/mariadb.log'.
Jan 16 14:15:31 ns397050.ip-94-23-52.eu mysqld_safe[10880]: 200116 14:15:31 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
Jan 16 14:15:33 ns397050.ip-94-23-52.eu systemd[1]: Started MariaDB database server.
 
I have the log for Mariadb, but not for Mysql.

vi mariadb.log
200116 12:44:07 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
200116 12:44:07 [Note] /usr/libexec/mysqld (mysqld 5.5.64-MariaDB) starting as process 12072 ...
200116 12:44:07 InnoDB: The InnoDB memory heap is disabled
200116 12:44:07 InnoDB: Mutexes and rw_locks use GCC atomic builtins
200116 12:44:07 InnoDB: Compressed tables use zlib 1.2.7
200116 12:44:07 InnoDB: Using Linux native AIO
200116 12:44:07 InnoDB: Initializing buffer pool, size = 128.0M
200116 12:44:07 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
200116 12:44:07 InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
200116 12:44:07 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
200116 12:44:07 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
200116 12:44:07 InnoDB: Waiting for the background threads to start
200116 12:44:08 Percona XtraDB (Experts in Database Performance Management) 5.5.61-MariaDB-38.13 started; log sequence number 0
200116 12:44:08 [Note] Plugin 'FEEDBACK' is disabled.
200116 12:44:08 [Note] Server socket created on IP: '0.0.0.0'.
200116 12:44:08 [Note] Event Scheduler: Loaded 0 events
200116 12:44:08 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.64-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
200116 12:59:41 [Note] /usr/libexec/mysqld: Normal shutdown
200116 12:59:41 [Note] Event Scheduler: Purging the queue. 0 events
200116 12:59:41 InnoDB: Starting shutdown...
200116 12:59:43 InnoDB: Shutdown completed; log sequence number 1597945
200116 12:59:43 [Note] /usr/libexec/mysqld: Shutdown complete

200116 12:59:43 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
200116 12:59:43 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
200116 12:59:43 [Note] /usr/libexec/mysqld (mysqld 5.5.64-MariaDB) starting as process 22045 ...
200116 12:59:43 InnoDB: The InnoDB memory heap is disabled
200116 12:59:43 InnoDB: Mutexes and rw_locks use GCC atomic builtins
200116 12:59:43 InnoDB: Compressed tables use zlib 1.2.7
200116 12:59:43 InnoDB: Using Linux native AIO
200116 12:59:43 InnoDB: Initializing buffer pool, size = 128.0M
200116 12:59:43 InnoDB: Completed initialization of buffer pool
200116 12:59:43 InnoDB: highest supported file format is Barracuda.
200116 12:59:43 InnoDB: Waiting for the background threads to start
200116 12:59:44 Percona XtraDB (Experts in Database Performance Management) 5.5.61-MariaDB-38.13 started; log sequence number 1597945
200116 12:59:44 [Note] Plugin 'FEEDBACK' is disabled.
200116 12:59:44 [Note] Server socket created on IP: '0.0.0.0'.
200116 12:59:44 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.64-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
200116 13:06:58 [Note] /usr/libexec/mysqld: Normal shutdown
200116 13:06:58 InnoDB: Starting shutdown...
200116 13:06:58 InnoDB: Shutdown completed; log sequence number 1597971
200116 13:06:58 [Note] /usr/libexec/mysqld: Shutdown complete

200116 13:06:59 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
200116 13:06:59 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
200116 13:06:59 [Note] /usr/libexec/mysqld (mysqld 5.5.64-MariaDB) starting as process 27237 ...
200116 13:06:59 InnoDB: The InnoDB memory heap is disabled
200116 13:06:59 InnoDB: Mutexes and rw_locks use GCC atomic builtins
"mariadb.log" 184L, 12694C
 
Samuel Desloges said:
I have the log for Mariadb, but not for Mysql.

vi mariadb.log
200116 12:44:07 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
200116 12:44:07 [Note] /usr/libexec/mysqld (mysqld 5.5.64-MariaDB) starting as process 12072 ...
200116 12:44:07 InnoDB: The InnoDB memory heap is disabled
200116 12:44:07 InnoDB: Mutexes and rw_locks use GCC atomic builtins
200116 12:44:07 InnoDB: Compressed tables use zlib 1.2.7
200116 12:44:07 InnoDB: Using Linux native AIO
200116 12:44:07 InnoDB: Initializing buffer pool, size = 128.0M
200116 12:44:07 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
200116 12:44:07 InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
200116 12:44:07 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
200116 12:44:07 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
200116 12:44:07 InnoDB: Waiting for the background threads to start
200116 12:44:08 Percona XtraDB (Experts in Database Performance Management) 5.5.61-MariaDB-38.13 started; log sequence number 0
200116 12:44:08 [Note] Plugin 'FEEDBACK' is disabled.
200116 12:44:08 [Note] Server socket created on IP: '0.0.0.0'.
200116 12:44:08 [Note] Event Scheduler: Loaded 0 events
200116 12:44:08 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.64-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
200116 12:59:41 [Note] /usr/libexec/mysqld: Normal shutdown
200116 12:59:41 [Note] Event Scheduler: Purging the queue. 0 events
200116 12:59:41 InnoDB: Starting shutdown...
200116 12:59:43 InnoDB: Shutdown completed; log sequence number 1597945
200116 12:59:43 [Note] /usr/libexec/mysqld: Shutdown complete

200116 12:59:43 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
200116 12:59:43 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
200116 12:59:43 [Note] /usr/libexec/mysqld (mysqld 5.5.64-MariaDB) starting as process 22045 ...
200116 12:59:43 InnoDB: The InnoDB memory heap is disabled
200116 12:59:43 InnoDB: Mutexes and rw_locks use GCC atomic builtins
200116 12:59:43 InnoDB: Compressed tables use zlib 1.2.7
200116 12:59:43 InnoDB: Using Linux native AIO
200116 12:59:43 InnoDB: Initializing buffer pool, size = 128.0M
200116 12:59:43 InnoDB: Completed initialization of buffer pool
200116 12:59:43 InnoDB: highest supported file format is Barracuda.
200116 12:59:43 InnoDB: Waiting for the background threads to start
200116 12:59:44 Percona XtraDB (Experts in Database Performance Management) 5.5.61-MariaDB-38.13 started; log sequence number 1597945
200116 12:59:44 [Note] Plugin 'FEEDBACK' is disabled.
200116 12:59:44 [Note] Server socket created on IP: '0.0.0.0'.
200116 12:59:44 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.64-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
200116 13:06:58 [Note] /usr/libexec/mysqld: Normal shutdown
200116 13:06:58 InnoDB: Starting shutdown...
200116 13:06:58 InnoDB: Shutdown completed; log sequence number 1597971
200116 13:06:58 [Note] /usr/libexec/mysqld: Shutdown complete

200116 13:06:59 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
200116 13:06:59 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
200116 13:06:59 [Note] /usr/libexec/mysqld (mysqld 5.5.64-MariaDB) starting as process 27237 ...
200116 13:06:59 InnoDB: The InnoDB memory heap is disabled
200116 13:06:59 InnoDB: Mutexes and rw_locks use GCC atomic builtins
"mariadb.log" 184L, 12694C
Click to expand...
mariadb is similar a mysql (an variant of mysql), so all is right at this point. Do


mysql -uadmin -p`cat /etc/psa/.psa.shadow`

and review if you are able to log.
 
It seems to be ok:

mysql -uadmin -p`cat /etc/psa/.psa.shadow`
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 354832
Server version: 5.5.64-MariaDB MariaDB Server

Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [(none)]>
 
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
MariaDB [psa]>
 
mysql -uadmin -p`cat /etc/psa/.psa.shadow`
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 356102
Server version: 5.5.64-MariaDB MariaDB Server

Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [(none)]> use psa
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
MariaDB [psa]> show tables;
+-----------------------------------+
| Tables_in_psa |
+-----------------------------------+
| APSApplicationItems |
| APSCatalogUpdates |
| APSClientApplicationItems |
| APSLicenseTypes |
| APSLicenses |
| ApiRpcCallsStat |
| ApsTokens |
| BackendCache |
| BackupExcludeFiles |
| BackupsScheduled |
| BackupsSettings |
| BlUpgradeActions |
| BlUpgrades |
| Cards |
| CliCallsStat |
| ClientsTraffic |
| Configurations |
| DatabaseCustomHosts |
| DatabaseServers |
| DatabaseUserRemoteAccessRules |
| DomainOutgoingMessagesPeaks |
| DomainOutgoingMessagesStats |
| DomainServices |
| DomainsTraffic |
| DynamicIpSecurity |
| EmailActivations |
| GL_remote_domains |
| GL_settings |
| IP_Addresses |
| IisAppPoolDomains |
| IisAppPools |
| IisAppPoolsPolicy |
| IpAddressesCollections |
| IpCollections |
| Limits |
| LimitsReservation |
| Logos |
| MailLists |
| MailMessagesStat |
| MailOutgoingMessagesPeaks |
| MailOutgoingMessagesStats |
| ModuleSettings
 
you had to do it after "use psa":

mysql -uadmin -p`cat /etc/psa/.psa.shadow`
MariaDB [(none)]>use psa
MariaDB [psa]>show tables;
 
Ignore
MariaDB [(none)]> show tables;
ERROR 1046 (3D000): No database selected
MariaDB [(none)]>

It's only if I do:
mysql -uadmin -p`cat /etc/psa/.psa.shadow`
show tables;
 
So, you have correctly the psa database working.
You still have message error on your plesk web access? Do you have try an


service sw-cp-server restart

?
 
You must log in or register to reply here.

Similar threads

M
Issue Plesk Update 18.0.34 to 18.0.57 Database 'psa' not found
Replies
10
Views
819
musa.sc
M
S
Resolved ERR_CONNECTION_REFUSED after update
Replies
5
Views
2K
sistemsb
S
M
Issue trying to upgrade plesk almalinux 8.7
Replies
1
Views
1K
Peter Debik
P
P
Resolved Plesk update: ERROR while trying to backup MySQL database
Replies
19
Views
455
Patashoow
P
J
Issue Table 'psa.DomainKeys' doesn't exist
Replies
7
Views
341
Peter Debik
P
Back
Top