• 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 Can't restart Maria since upgrade to 18.0.41

F

fab4_33

New Pleskian
Hello all !

I upgrade to 18.0.41, all seems goods until yesterday, in plesk admin i clean some old database, but after a while il can't connect anymore :

from admin panel
DB query failed: SQLSTATE[HY000] [2002] No such file or directory

if i do : plesk repair installation i got
Warning: restart service mariadb failed

systemctl status mariadb.service

Code: 
mariadb.service - MariaDB 10.2.41 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: activating (auto-restart) (Result: signal) since mer. 2022-02-02 10:12:49 CET; 3s ago
     Docs: man:mysqld(8)
           https://mariadb.com/kb/en/library/systemd/
  Process: 28137 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
  Process: 2023 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS --basedir=/usr $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=killed, signal=ABRT)
  Process: 1974 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: 1971 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
 Main PID: 2023 (code=killed, signal=ABRT)

févr. 02 10:12:49 myserver.net systemd[1]: Failed to start MariaDB 10.2.41 database server.
févr. 02 10:12:49 myserver.net systemd[1]: Unit mariadb.service entered failed state.
févr. 02 10:12:49 myserver.net systemd[1]: mariadb.service failed.



I really don't known what to do
Thanks for help
 
i try of df -H

Code: 
/dev/root           21G     15G  4,7G  77% /
devtmpfs            17G       0   17G   0% /dev
tmpfs               17G       0   17G   0% /dev/shm
tmpfs               17G    984M   16G   6% /run
tmpfs               17G       0   17G   0% /sys/fs/cgroup
/dev/sda1          535M    3,8M  532M   1% /boot/efi
/dev/md3           2,0T    788G  1,1T  43% /var
tmpfs              3,4G       0  3,4G   0% /run/user/1001
tmpfs              3,4G       0  3,4G   0% /run/user/0
/dev/dm-1           11G    156M   11G   2% /var/lib/docker/devicemapper/mnt/8449edd70cef9da73737f50c65d4d70bb0cb67cf5aaa2cf9a3f43fdbda004a9d
tmpfs              3,4G       0  3,4G   0% /run/user/10000

so not space issue
 
from grep maria /var/log/messages output :

Code: 
ttps://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
Feb  2 10:29:38 mywebsite mysqld: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Feb  2 10:29:38 mywebsite mysqld: The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
Feb  2 10:29:38 mywebsite systemd: mariadb.service: main process exited, code=killed, status=6/ABRT
Feb  2 10:29:38 mywebsite systemd: Unit mariadb.service entered failed state.
Feb  2 10:29:38 mywebsite systemd: mariadb.service failed.
Feb  2 10:29:43 mywebsite systemd: mariadb.service holdoff time over, scheduling restart.
Feb  2 10:29:44 mywebsite mysqld: 2022-02-02 10:29:44 140476650678464 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
 
from grep mysql
/var/log/messages output :

Code: 
https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
Feb  2 10:37:36 mywebsite mysqld: 2022-02-02 10:37:36 140505097390272 [ERROR] [FATAL] InnoDB: Trying to read page number 4294967295 in space 0, space name innodb_system, which is outside the tablespace bounds. Byte offset 0, len 16384Please check that the configuration matches the InnoDB system tablespace location (ibdata files)
Feb  2 10:37:36 mywebsite mysqld: 220202 10:37:36 [ERROR] mysqld got signal 6 ;
Feb  2 10:37:36 mywebsite mysqld: This could be because you hit a bug. It is also possible that this binary
Feb  2 10:37:36 mywebsite mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Feb  2 10:37:36 mywebsite mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Feb  2 10:37:36 mywebsite mysqld: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Feb  2 10:37:36 mywebsite mysqld: We will try our best to scrape up some info that will hopefully help
Feb  2 10:37:36 mywebsite mysqld: diagnose the problem, but since we have already crashed,
Feb  2 10:37:36 mywebsite mysqld: something is definitely wrong and this may fail.
Feb  2 10:37:36 mywebsite mysqld: Server version: 10.2.41-MariaDB
Feb  2 10:37:36 mywebsite mysqld: key_buffer_size=134217728
Feb  2 10:37:36 mywebsite mysqld: read_buffer_size=131072
Feb  2 10:37:36 mywebsite mysqld: max_used_connections=0
Feb  2 10:37:36 mywebsite mysqld: max_threads=102
Feb  2 10:37:36 mywebsite mysqld: thread_count=0
Feb  2 10:37:36 mywebsite mysqld: It is possible that mysqld could use up to
Feb  2 10:37:36 mywebsite mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 355180 K  bytes of memory
Feb  2 10:37:36 mywebsite mysqld: Hope that's ok; if not, decrease some variables in the equation.
Feb  2 10:37:36 mywebsite mysqld: Thread pointer: 0x0
Feb  2 10:37:36 mywebsite mysqld: Attempting backtrace. You can use the following information to find out
Feb  2 10:37:36 mywebsite mysqld: where mysqld died. If you see no messages after this, something went
Feb  2 10:37:36 mywebsite mysqld: terribly wrong...
Feb  2 10:37:36 mywebsite mysqld: stack_bottom = 0x0 thread_stack 0x49000
Feb  2 10:37:36 mywebsite mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x563427605e8e]
Feb  2 10:37:36 mywebsite mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x30d)[0x56342709df3d]
Feb  2 10:37:36 mywebsite mysqld: sigaction.c:0(__restore_rt)[0x7fc9e42a2630]
Feb  2 10:37:36 mywebsite mysqld: :0(__GI_raise)[0x7fc9e2572387]
Feb  2 10:37:36 mywebsite mysqld: :0(__GI_abort)[0x7fc9e2573a78]
Feb  2 10:37:36 mywebsite mysqld: /usr/sbin/mysqld(+0x9a3323)[0x563427395323]
Feb  2 10:37:36 mywebsite mysqld: /usr/sbin/mysqld(+0xa53063)[0x563427445063]
Feb  2 10:37:36 mywebsite mysqld: /usr/sbin/mysqld(+0xa07110)[0x5634273f9110]
Feb  2 10:37:36 mywebsite mysqld: /usr/sbin/mysqld(+0x9e6cf8)[0x5634273d8cf8]
Feb  2 10:37:36 mywebsite mysqld: /usr/sbin/mysqld(+0x986fd8)[0x563427378fd8]
Feb  2 10:37:36 mywebsite mysqld: /usr/sbin/mysqld(+0x9880b4)[0x56342737a0b4]
Feb  2 10:37:36 mywebsite mysqld: /usr/sbin/mysqld(+0x995be0)[0x563427387be0]
Feb  2 10:37:36 mywebsite mysqld: /usr/sbin/mysqld(+0x98c7a1)[0x56342737e7a1]
Feb  2 10:37:36 mywebsite mysqld: /usr/sbin/mysqld(+0x95c246)[0x56342734e246]
Feb  2 10:37:36 mywebsite mysqld: /usr/sbin/mysqld(+0x84408d)[0x56342723608d]
Feb  2 10:37:36 mywebsite mysqld: /usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x64)[0x5634270a0444]
Feb  2 10:37:36 mywebsite mysqld: /usr/sbin/mysqld(+0x526dd0)[0x563426f18dd0]
Feb  2 10:37:36 mywebsite mysqld: /usr/sbin/mysqld(_Z11plugin_initPiPPci+0x9a2)[0x563426f1a692]
Feb  2 10:37:36 mywebsite mysqld: /usr/sbin/mysqld(+0x4714e1)[0x563426e634e1]
Feb  2 10:37:36 mywebsite mysqld: /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x4be)[0x563426e69d6e]
Feb  2 10:37:36 mywebsite mysqld: /lib64/libc.so.6(__libc_start_main+0xf5)[0x7fc9e255e555]
Feb  2 10:37:36 mywebsite mysqld: /usr/sbin/mysqld(+0x46b2bd)[0x563426e5d2bd]
Feb  2 10:37:36 mywebsite mysqld: The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
Feb  2 10:37:36 mywebsite mysqld: information that should help you find out what is causing the crash.
Feb  2 10:37:36 mywebsite mysqld: Writing a core file...
Feb  2 10:37:36 mywebsite mysqld: Working directory at /var/lib/mysql
Feb  2 10:37:36 mywebsite mysqld: Resource Limits:
Feb  2 10:37:36 mywebsite mysqld: Limit                     Soft Limit           Hard Limit           Units
Feb  2 10:37:36 mywebsite mysqld: Max cpu time              unlimited            unlimited            seconds
Feb  2 10:37:36 mywebsite mysqld: Max file size             unlimited            unlimited            bytes
Feb  2 10:37:36 mywebsite mysqld: Max data size             unlimited            unlimited            bytes
Feb  2 10:37:36 mywebsite mysqld: Max stack size            8388608              unlimited            bytes
Feb  2 10:37:36 mywebsite mysqld: Max core file size        0                    unlimited            bytes
Feb  2 10:37:36 mywebsite mysqld: Max resident set          unlimited            unlimited            bytes
Feb  2 10:37:36 mywebsite mysqld: Max processes             127002               127002               processes
Feb  2 10:37:36 mywebsite mysqld: Max open files            32768                32768                files
Feb  2 10:37:36 mywebsite mysqld: Max locked memory         65536                65536                bytes
Feb  2 10:37:36 mywebsite mysqld: Max address space         unlimited            unlimited            bytes
Feb  2 10:37:36 mywebsite mysqld: Max file locks            unlimited            unlimited            locks
Feb  2 10:37:36 mywebsite mysqld: Max pending signals       127002               127002               signals
Feb  2 10:37:36 mywebsite mysqld: Max msgqueue size         819200               819200               bytes
Feb  2 10:37:36 mywebsite mysqld: Max nice priority         0                    0
Feb  2 10:37:36 mywebsite mysqld: Max realtime priority     0                    0
Feb  2 10:37:36 mywebsite mysqld: Max realtime timeout      unlimited            unlimited            us
Feb  2 10:37:36 mywebsite mysqld: Core pattern: core
Feb  2 10:37:41 mywebsite mysqld: 2022-02-02 10:37:41 140638484228288 [Note] /usr/sbin/mysqld (mysqld 10.2.41-MariaDB) starting as process 7325 ...
Feb  2 10:37:41 mywebsite mysqld: 2022-02-02 10:37:41 140638484228288 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Feb  2 10:37:41 mywebsite mysqld: 2022-02-02 10:37:41 140638484228288 [Note] InnoDB: Uses event mutexes
Feb  2 10:37:41 mywebsite mysqld: 2022-02-02 10:37:41 140638484228288 [Note] InnoDB: Compressed tables use zlib 1.2.7
Feb  2 10:37:41 mywebsite mysqld: 2022-02-02 10:37:41 140638484228288 [Note] InnoDB: Using Linux native AIO
Feb  2 10:37:41 mywebsite mysqld: 2022-02-02 10:37:41 140638484228288 [Note] InnoDB: Number of pools: 1
Feb  2 10:37:41 mywebsite mysqld: 2022-02-02 10:37:41 140638484228288 [Note] InnoDB: Using SSE2 crc32 instructions
Feb  2 10:37:42 mywebsite mysqld: 2022-02-02 10:37:42 140638484228288 [Note] InnoDB: Initializing buffer pool, total size = 100M, instances = 1, chunk size = 100M
Feb  2 10:37:42 mywebsite mysqld: 2022-02-02 10:37:42 140638484228288 [Note] InnoDB: Completed initialization of buffer pool
Feb  2 10:37:42 mywebsite mysqld: 2022-02-02 10:37:42 140637957551872 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
Feb  2 10:37:42 mywebsite mysqld: 2022-02-02 10:37:42 140638484228288 [Note] InnoDB: Highest supported file format is Barracuda.
Feb  2 10:37:42 mywebsite mysqld: 2022-02-02 10:37:42 140638484228288 [Note] InnoDB: Starting crash recovery from checkpoint LSN=405049244137
Feb  2 10:37:42 mywebsite mysqld: 2022-02-02 10:37:42 140638484228288 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=278] with future log sequence number 405049689196
Feb  2 10:37:42 mywebsite mysqld: 2022-02-02 10:37:42 140638484228288 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
Feb  2 10:37:42 mywebsite mysqld: 2022-02-02 10:37:42 140638484228288 [ERROR] InnoDB: Page [page id: space=0, page number=8127] log sequence number 405049337534 is in the future! Current system log sequence number 405049244198.
Feb  2 10:37:42 mywebsite mysqld: 2022-02-02 10:37:42 140638484228288 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
 
hi @IgorG
thanks for info

Code: 
MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql -Ns -uadmin psa -Ne"show databases" | grep -v information_schema | grep -v performance_schema > /root/db_list.txt
mkdir /root/db_backup/
cat /root/db_list.txt | while read i; do MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysqldump -uadmin "$i" --routines --databases > /root/db_backup/"$i".sql; echo $i; sleep 5; done

show

Code: 
mysqldump: Couldn't execute 'SHOW FUNCTION STATUS WHERE Db = '184sNIp3UW'': Table 'mysql.proc' doesn't exist (1146)
184sNIp3UW
mysqldump: Couldn't execute 'SHOW FUNCTION STATUS WHERE Db = 'Ab860P1Hki'': Table 'mysql.proc' doesn't exist (1146)
Ab860P1Hki
mysqldump: Couldn't execute 'SHOW FUNCTION STATUS WHERE Db = 'a7GWu4z1E6Ty'': Table 'mysql.proc' doesn't exist (1146)
a7GWu4z1E6Ty
mysqldump: Couldn't execute 'SHOW FUNCTION STATUS WHERE Db = 'academy_6nF1K4edD'': Table 'mysql.proc' doesn't exist (1146)
academy_6nF1K4edD
mysqldump: Couldn't execute 'SHOW FUNCTION STATUS WHERE Db = 'apsc'': Table 'mysql.proc' doesn't exist (1146)
apsc
mysqldump: Couldn't execute 'SHOW FUNCTION STATUS WHERE Db = 'backup_wp_rev_k1ji7'': Table 'mysql.proc' doesn't exist (1146)
backup_wp_rev_k1ji7
mysqldump: Got error: 2013: "Lost connection to MySQL server during query" when using LOCK TABLES
base_photo_ovh_m19
mysqldump: Got error: 2002: "Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111)" when trying to connect

so seems no working
 
fab4_33 said:
Hello all !

I upgrade to 18.0.41, all seems goods until yesterday, in plesk admin i clean some old database, but after a while il can't connect anymore :

from admin panel
DB query failed: SQLSTATE[HY000] [2002] No such file or directory

if i do : plesk repair installation i got
Warning: restart service mariadb failed

systemctl status mariadb.service

Code: 
mariadb.service - MariaDB 10.2.41 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: activating (auto-restart) (Result: signal) since mer. 2022-02-02 10:12:49 CET; 3s ago
     Docs: man:mysqld(8)
           https://mariadb.com/kb/en/library/systemd/
  Process: 28137 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
  Process: 2023 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS --basedir=/usr $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=killed, signal=ABRT)
  Process: 1974 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: 1971 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
 Main PID: 2023 (code=killed, signal=ABRT)

févr. 02 10:12:49 myserver.net systemd[1]: Failed to start MariaDB 10.2.41 database server.
févr. 02 10:12:49 myserver.net systemd[1]: Unit mariadb.service entered failed state.
févr. 02 10:12:49 myserver.net systemd[1]: mariadb.service failed.



I really don't known what to do
Thanks for help
Click to expand...
i have the same exact problem and i am stuck.

i updated, then ran the on terminal the auto clean and auto remove sudo commands now i get the error the OP is getting. when i try to manually start it with the sql commands it fails to connect through the plesk socket and when i try to restart that service it throws the sql db error again. stuck 100% :(
 
You must log in or register to reply here.

Similar threads

F
Question Mariadb down after update Plesk /var 100% full
Replies
8
Views
327
flieg4bei
F
S
Resolved Error 500 Plesk\Exception\Database DB query failed: SQLSTATE[HY000] [2002] No such file or directory
Replies
10
Views
409
Shasam
S
I
Resolved Mariadb does not start when upgrading plesk to 18.0.58 Update 1
Replies
2
Views
599
ivanes82
I
E
Resolved DB query failed: SQLSTATE[HY000] [2002] No such file or directory mariadb cant start
Replies
1
Views
659
emreboy
E
P
Resolved Failed to start MariaDB database server.
Replies
2
Views
8K
pattolentno
P
Back
Top