• 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 500 Plesk\Exception\Database

hostidex

New Pleskian
Server operating system version
CentOS 7.9.2009 x86_64
Plesk version and microupdate number
Plesk Obsidian 18.0.47.5
Hello everyone,

First of all, I should mention that I have examined many similar topics in the forum and tried the methods written in the topics. But in no way could I run mysql service and mariadb service properly.

First of all, I want to talk about what caused the situation.After the hard reset of the physical machine, the database crashed and I got this error after various operations. I have 16 websites in the server and I want to recover their databases.


I went through the link above and tried the steps. But I would like to state that I got the error "Unit not found" in mysql and mysqld services in the 5th stage. I tried the solution in many similar topics, but I can't find any results.

My /etc/my.cnf file ( I also tried changing the bind address to 127.0.0.1. Problem not solved)
-------------------------------------------
[mysqld]
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

[client]

socket=/var/lib/mysql/mysql.sock

[mysqld_safe]
log-error=/var/log/mariadb/mariadb.log
pid-file=/var/run/mariadb/mariadb.pid

Until this stage, I thought that the problem was caused by a wrong configuration in the InnoDB engine and was damaged, but I could not come up with a solution. I would greatly appreciate it if you could help me build the build here from scratch and recover the databases.
 
What's the output of systemctl status mariadb or systemctl status mysql ?
What's in the logfile /var/log/mariadb/mariadb.log ?
 
systemctl status mariadb

# systemctl status mariadb
● mariadb.service - MariaDB 10.3.38 database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; disabled; vendor pre set: 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: active (running) since Prş 2023-02-09 11:58:08 +03; 33s ago
Docs: man:mysqld(8)
systemd
Process: 1527 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_STAR T_POSITION (code=exited, status=0/SUCCESS)
Process: 1141 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR = || VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ] && systemc tl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/S UCCESS)
Process: 1094 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START _POSITION (code=exited, status=0/SUCCESS)
Main PID: 1315 (mysqld)
Status: "Taking your SQL requests now..."
CGroup: /system.slice/mariadb.service
└─1315 /usr/sbin/mysqld

Şub 09 11:58:39 vegas.sobemedya.com mysqld[1315]: 2023-02-09 11:58:39 60 [Wa...
Şub 09 11:58:39 vegas.sobemedya.com mysqld[1315]: 2023-02-09 11:58:39 61 [Wa...
Şub 09 11:58:39 vegas.sobemedya.com mysqld[1315]: 2023-02-09 11:58:39 62 [Wa...
Şub 09 11:58:39 vegas.sobemedya.com mysqld[1315]: 2023-02-09 11:58:39 63 [Wa...
Şub 09 11:58:39 vegas.sobemedya.com mysqld[1315]: 2023-02-09 11:58:39 64 [Wa...
Şub 09 11:58:39 vegas.sobemedya.com mysqld[1315]: 2023-02-09 11:58:39 65 [Wa...
Şub 09 11:58:39 vegas.sobemedya.com mysqld[1315]: 2023-02-09 11:58:39 66 [Wa...
Şub 09 11:58:39 vegas.sobemedya.com mysqld[1315]: 2023-02-09 11:58:39 67 [Wa...
Şub 09 11:58:39 vegas.sobemedya.com mysqld[1315]: 2023-02-09 11:58:39 68 [Wa...
Şub 09 11:58:39 vegas.sobemedya.com mysqld[1315]: 2023-02-09 11:58:39 69 [Wa...
Hint: Some lines were ellipsized, use -l to show in full.

systemctl status mysql
Unit mysql.service could not be found.

mariadb.log
I attached the log file
 

Attachments

  • mariadb.zip
    3.1 KB · Views: 1
OK, your data is corrupt and MariaDB is unable to start, relevant part in the log file:
Code:
2023-02-08 11:36:20 0 [Note] InnoDB: Waiting for purge to start
2023-02-08 11:36:20 0x7f2306ffd700  InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.3.38/storage/innobase/trx/trx0purge.cc line 118
InnoDB: Failing assertion: purge_sys.tail.trx_no <= purge_sys.rseg->last_trx_no()

You can try to recover your database by following the recommendations here:
InnoDB Recovery Modes

If nothing helps then you should restore your databases from a backup.
 
All backups I have are incremental backup. Therefore I cannot recover databases from there. I will try InnoD Recovery Modes. Thanks @Monty
 
Back
Top