• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue Login to Plesk failed : Server Error 500 Plesk\Exception\Database

simoncsc

New Pleskian
Hi,

I got below error messages when try to login to Plesk:

Server Error
500 Plesk\Exception\Database
DB query failed: SQLSTATE[HY000] [2002] Connection refused
TypePlesk\Exception\Database
MessageDB query failed: SQLSTATE[HY000] [2002] Connection refused
FileMysql.php
Line60
How to fix this problem.
 
Below is my Mariadb status:

# 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: d isabled)
Drop-In: /usr/lib/systemd/system/mariadb.service.d
└─respawn.conf
Active: activating (auto-restart) (Result: exit-code) since Tue 2020-04-28 12:39:4 3 HKT; 4s ago
Process: 24011 ExecStartPost=/usr/libexec/mariadb-wait-ready $MAINPID (code=exited, status=1/FAILURE)
Process: 24010 ExecStart=/usr/bin/mysqld_safe --basedir=/usr (code=exited, status=0 /SUCCESS)
Process: 23975 ExecStartPre=/usr/libexec/mariadb-prepare-db-dir %n (code=exited, st atus=0/SUCCESS)
Main PID: 24010 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/mariadb.service

Apr 28 12:39:43 main-times.com systemd[1]: Failed to start MariaDB database server.
Apr 28 12:39:43 main-times.com systemd[1]: Unit mariadb.service entered failed state.
Apr 28 12:39:43 main-times.com systemd[1]: mariadb.service failed.
 
Can you find something more informative in mariadb log?
 
Can you find something more informative in mariadb log?

Hi IgorG

Below is the mariadb log:
200428 11:36:56 [Note] /usr/libexec/mysqld: Shutdown complete

Error in my_thread_global_end(): 2 threads didn't exit
200428 11:37:01 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
200428 11:37:07 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
200428 11:37:07 [Note] /usr/libexec/mysqld (mysqld 5.5.64-MariaDB) starting as process 23446 ...
200428 11:37:07 InnoDB: The InnoDB memory heap is disabled
200428 11:37:07 InnoDB: Mutexes and rw_locks use GCC atomic builtins
200428 11:37:07 InnoDB: Compressed tables use zlib 1.2.7
200428 11:37:07 InnoDB: Using Linux native AIO
200428 11:37:07 InnoDB: Initializing buffer pool, size = 128.0M
200428 11:37:07 InnoDB: Completed initialization of buffer pool
200428 11:37:07 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
200428 11:37:07 InnoDB: Error: page 10963 log sequence number 617515890
InnoDB: is in the future! Current system log sequence number 617515719.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: MySQL :: MySQL 8.0 Reference Manual :: 15.21.2 Forcing InnoDB Recovery
InnoDB: for more information.
200428 11:37:07 InnoDB: Waiting for the background threads to start
200428 11:37:08 InnoDB: Error: tablespace size stored in header is 17536 pages, but
200428 11:37:08 InnoDB: the sum of data file sizes is only 17024 pages
200428 11:37:08 InnoDB: Cannot start InnoDB. The tail of the system tablespace is
200428 11:37:08 InnoDB: missing. Have you edited innodb_data_file_path in my.cnf in an
200428 11:37:08 InnoDB: inappropriate way, removing ibdata files from there?
200428 11:37:08 InnoDB: You can set innodb_force_recovery=1 in my.cnf to force
200428 11:37:08 InnoDB: a startup if you are trying to recover a badly corrupt database.
200428 11:37:08 [ERROR] Plugin 'InnoDB' init function returned error.
200428 11:37:08 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
200428 11:37:08 [Note] Plugin 'FEEDBACK' is disabled.
200428 11:37:08 [ERROR] Unknown/unsupported storage engine: InnoDB
200428 11:37:08 [ERROR] Aborting

200428 11:37:08 [Note] /usr/libexec/mysqld: Shutdown complete

Error in my_thread_global_end(): 2 threads didn't exit
200428 11:37:13 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
 
Back
Top