mein mysql-Server ist in einer Woche schon 2x abgestürzt - immer war ich in WordPress was am tun, gerade war es wieder so. im Status hab ich das gelesen:
Code: Select all
Aug 10 19:44:49 mail.iteagle.de mariadbd[962]: 2023-08-10 19:44:49 28 [Warning] Checking table: './customer3_db1/hesk_attachments'
Aug 10 19:44:49 mail.iteagle.de mariadbd[962]: 2023-08-10 19:44:49 29 [ERROR] mariadbd: Table './customer3_db1/hesk_pipe_loops' is marked as crashed and should be repaired
Aug 10 19:44:49 mail.iteagle.de mariadbd[962]: 2023-08-10 19:44:49 29 [Warning] Checking table: './customer3_db1/hesk_pipe_loops'
Code: Select all
MariaDB [customer3_db1]> REPAIR TABLE hesk_pipe_loops;
+----------------------------------+--------+----------+----------+
| Table | Op | Msg_type | Msg_text |
+----------------------------------+--------+----------+----------+
| customer3.hesk_pipe_loops | repair | status | OK |
+----------------------------------+--------+----------+----------+
1 row in set (0.002 sec)
Komplette "service"-Ausgabe :
Code: Select all
root@mail:/home# sudo service mysql status
● mariadb.service - MariaDB 10.5.19 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Active: failed (Result: oom-kill) since Fri 2023-08-18 16:56:23 CEST; 1min 53s ago
Docs: man:mariadbd(8)
https://mariadb.com/kb/en/library/systemd/
Process: 570 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Process: 621 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 682 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: 962 ExecStart=/usr/sbin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=killed, signal=KILL)
Process: 1131 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 1133 ExecStartPost=/etc/mysql/debian-start (code=exited, status=0/SUCCESS)
Main PID: 962 (code=killed, signal=KILL)
Status: "Taking your SQL requests now..."
CPU: 31min 9.187s
Aug 10 19:44:49 mail.domain.tld mariadbd[962]: 2023-08-10 19:44:49 28 [Warning] Checking table: './customer3_db1/hesk_attachments'
Aug 10 19:44:49 mail.domain.tld mariadbd[962]: 2023-08-10 19:44:49 29 [ERROR] mariadbd: Table './customer3_db1/hesk_pipe_loops' is marked as crashed and should be repaired
Aug 10 19:44:49 mail.domain.tld mariadbd[962]: 2023-08-10 19:44:49 29 [Warning] Checking table: './customer3_db1/hesk_pipe_loops'
Aug 13 08:00:55 mail.domain.tld mariadbd[962]: 2023-08-13 8:00:55 391016 [Warning] Aborted connection 391016 to db: 'keyhelp' user: 'keyhelp' host: 'localhost' (Got timeout reading communication packets)
Aug 13 08:00:57 mail.domain.tld mariadbd[962]: 2023-08-13 8:00:57 387351 [Warning] Aborted connection 387351 to db: 'keyhelp' user: 'keyhelp' host: 'localhost' (Got timeout reading communication packets)
Aug 18 08:02:26 mail.domain.tld mariadbd[962]: 2023-08-18 8:02:26 1849053 [Warning] Aborted connection 1849053 to db: 'keyhelp' user: 'keyhelp' host: 'localhost' (Got timeout reading communication packets)
Aug 18 16:56:23 mail.domain.tld systemd[1]: mariadb.service: A process of this unit has been killed by the OOM killer.
Aug 18 16:56:23 mail.domain.tld systemd[1]: mariadb.service: Main process exited, code=killed, status=9/KILL
Aug 18 16:56:23 mail.domain.tld systemd[1]: mariadb.service: Failed with result 'oom-kill'.
Aug 18 16:56:23 mail.domain.tld systemd[1]: mariadb.service: Consumed 31min 9.187s CPU time.