Endre
New Pleskian
Hello Pleskians,
I get this error when I try to log in to Plesk control panel:
I have seen many similar error reports here and tried the recomended solutions like this one below:
https://support.plesk.com/hc/en-us/...eption-SQLSTATE-HY000-2002-Connection-refused
Still no good.
Using ssh I got these:
systemctl status mariadb.service
journalctl -xe
I don't know what else can I do.
Please help me as all our websites and applications are down because of this error.
Thank you!
Best regards,
Endre
I get this error when I try to log in to Plesk control panel:
Type | Plesk\Exception\Database |
Message | DB query failed: SQLSTATE[HY000] [2002] No such file or directory |
File | Mysql.php |
Line | 79 |
I have seen many similar error reports here and tried the recomended solutions like this one below:
https://support.plesk.com/hc/en-us/...eption-SQLSTATE-HY000-2002-Connection-refused
Still no good.
Using ssh I got these:
systemctl status mariadb.service
● mariadb.service - MariaDB 10.2.41 database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; disabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf
/usr/lib/systemd/system/mariadb.service.d
└─respawn.conf
Active: activating (auto-restart) (Result: exit-code) since Tue 2021-11-09 08:37:34 CET; 3s ago
Docs: man:mysqld(8)
systemd
Process: 7952 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS --basedir=/usr $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
Process: 7923 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
Process: 7921 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Main PID: 7952 (code=exited, status=1/FAILURE)
Status: "MariaDB server is down"
Tasks: 0
Memory: 0B
CGroup: /system.slice/mariadb.service
Nov 09 08:37:34 bvfpl01.bvfheating.net systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
Nov 09 08:37:34 bvfpl01.bvfheating.net systemd[1]: Failed to start MariaDB 10.2.41 database server.
Nov 09 08:37:34 bvfpl01.bvfheating.net systemd[1]: Unit mariadb.service entered failed state.
Nov 09 08:37:34 bvfpl01.bvfheating.net systemd[1]: mariadb.service failed.
journalctl -xe
My /etc/my.conf file looks like this:Nov 09 08:39:03 bvfpl01.bvfheating.net mysqld[10576]: 2021-11-09 8:39:03 139620843448064 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
Nov 09 08:39:03 bvfpl01.bvfheating.net mysqld[10576]: 2021-11-09 8:39:03 139621408299200 [Note] InnoDB: Highest supported file format is Barracuda.
Nov 09 08:39:03 bvfpl01.bvfheating.net mysqld[10576]: 2021-11-09 8:39:03 139621408299200 [Note] InnoDB: Starting crash recovery from checkpoint LSN=17672690040
Nov 09 08:39:03 bvfpl01.bvfheating.net mysqld[10576]: 2021-11-09 8:39:03 139621408299200 [ERROR] InnoDB: ############### CORRUPT LOG RECORD FOUND ##################
Nov 09 08:39:03 bvfpl01.bvfheating.net mysqld[10576]: 2021-11-09 8:39:03 139621408299200 [Note] InnoDB: Log record type 87, page 17672690176:140723838914912. Log parsing proceeded successfully up to 17672690040. Previous log record type 128, is mult
Nov 09 08:39:03 bvfpl01.bvfheating.net mysqld[10576]: 2021-11-09 8:39:03 139621408299200 [Note] InnoDB: Hex dump starting 0 bytes before and ending 100 bytes after the corrupted record:
Nov 09 08:39:03 bvfpl01.bvfheating.net mysqld[10576]: len 100; hex 5700331c008093000000dd9062d900000f78196a04000000010370756d0b6c617374436865636b656401050a31363336333337353035a90083b0000600038004ffffffff800680077fff02035f00000b5725f90000ddfb7b00ae000
Nov 09 08:39:03 bvfpl01.bvfheating.net mysqld[10576]: 2021-11-09 8:39:03 139621408299200 [Warning] InnoDB: The log file may have been corrupt and it is possible that the log scan did not proceed far enough in recovery! Please run CHECK TABLE on your
Nov 09 08:39:03 bvfpl01.bvfheating.net mysqld[10576]: 2021-11-09 8:39:03 139621408299200 [ERROR] InnoDB: Missing MLOG_CHECKPOINT at 17672690040 between the checkpoint 17672690040 and the end 17672690270.
Nov 09 08:39:03 bvfpl01.bvfheating.net mysqld[10576]: 2021-11-09 8:39:03 139621408299200 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
Nov 09 08:39:04 bvfpl01.bvfheating.net mysqld[10576]: 2021-11-09 8:39:04 139621408299200 [Note] InnoDB: Starting shutdown...
Nov 09 08:39:04 bvfpl01.bvfheating.net mysqld[10576]: 2021-11-09 8:39:04 139621408299200 [ERROR] Plugin 'InnoDB' init function returned error.
Nov 09 08:39:04 bvfpl01.bvfheating.net mysqld[10576]: 2021-11-09 8:39:04 139621408299200 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Nov 09 08:39:04 bvfpl01.bvfheating.net mysqld[10576]: 2021-11-09 8:39:04 139621408299200 [Note] Plugin 'FEEDBACK' is disabled.
Nov 09 08:39:04 bvfpl01.bvfheating.net mysqld[10576]: 2021-11-09 8:39:04 139621408299200 [ERROR] Unknown/unsupported storage engine: InnoDB
Nov 09 08:39:04 bvfpl01.bvfheating.net mysqld[10576]: 2021-11-09 8:39:04 139621408299200 [ERROR] Aborting
Nov 09 08:39:04 bvfpl01.bvfheating.net systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
Nov 09 08:39:04 bvfpl01.bvfheating.net systemd[1]: Failed to start MariaDB 10.2.41 database server.
-- Subject: Unit mariadb.service has failed
-- Defined-By: systemd
-- Support: systemd-devel Info Page
--
-- Unit mariadb.service has failed.
--
-- The result is failed.
Nov 09 08:39:04 bvfpl01.bvfheating.net systemd[1]: Unit mariadb.service entered failed state.
Nov 09 08:39:04 bvfpl01.bvfheating.net systemd[1]: mariadb.service failed.
Nov 09 08:39:04 bvfpl01.bvfheating.net systemd[1]: plesk-web-socket.service holdoff time over, scheduling restart.
Nov 09 08:39:04 bvfpl01.bvfheating.net systemd[1]: Stopped Plesk Web Socket Service.
-- Subject: Unit plesk-web-socket.service has finished shutting down
-- Defined-By: systemd
-- Support: systemd-devel Info Page
--
-- Unit plesk-web-socket.service has finished shutting down.
Nov 09 08:39:04 bvfpl01.bvfheating.net systemd[1]: Starting LSB: start and stop MariaDB...
-- Subject: Unit mysql.service has begun start-up
-- Defined-By: systemd
-- Support: systemd-devel Info Page
--
-- Unit mysql.service has begun starting up.
Nov 09 08:39:05 bvfpl01.bvfheating.net mysql[10593]: Starting MariaDB.211109 08:39:05 mysqld_safe Logging to '/var/log/mariadb/mariadb.log'.
Nov 09 08:39:05 bvfpl01.bvfheating.net mysql[10593]: 211109 08:39:05 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
Nov 09 08:39:06 bvfpl01.bvfheating.net mysql[10593]: /etc/rc.d/init.d/mysql: line 263: kill: (10618) - No such process
Nov 09 08:39:06 bvfpl01.bvfheating.net mysql[10593]: ERROR!
Nov 09 08:39:06 bvfpl01.bvfheating.net systemd[1]: mysql.service: control process exited, code=exited status=1
Nov 09 08:39:06 bvfpl01.bvfheating.net systemd[1]: Failed to start LSB: start and stop MariaDB.
-- Subject: Unit mysql.service has failed
-- Defined-By: systemd
-- Support: systemd-devel Info Page
--
-- Unit mysql.service has failed.
--
-- The result is failed.
Nov 09 08:39:06 bvfpl01.bvfheating.net systemd[1]: Unit mysql.service entered failed state.
Nov 09 08:39:06 bvfpl01.bvfheating.net systemd[1]: mysql.service failed.
Nov 09 08:39:06 bvfpl01.bvfheating.net grafana-server[2227]: t=2021-11-09T08:39:06+0100 lvl=eror msg="Alert Rule Result Error" logger=alerting.evalContext ruleId=3 name="Mail server memory usage" error="tsdb.HandleRequest() error Could not find execu
I am running vps with the below versions:bind-address = ::ffff:127.0.0.1
local-infile=0
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
# Settings user and group are ignored when systemd is used.
# If you need to run mysqld under a different user or group,
# customize your systemd unit file for mariadb according to the
# instructions in Understanding and administering systemd :: Fedora Docs
innodb_force_recovery=1
[mysqld_safe]
log-error=/var/log/mariadb/mariadb.log
pid-file=/var/run/mariadb/mariadb.pid
#
# include all files from the config directory
#
!includedir /etc/my.cnf.d
Everything is up-to-date.Product version: Plesk Obsidian 18.0.39.1
OS version: CentOS 7.9.2009 x86_64
Build date: 2021/10/14 23:00
Revision: abd80734589dbcc9d72ab53622ef5737a658fb43
I don't know what else can I do.
Please help me as all our websites and applications are down because of this error.
Thank you!
Best regards,
Endre