Comments - mariadb server mysteriously seems to be crashing
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
Have you looked at the actual log file? It has more information. You may want to increase the logging level in your systemctl script to see more.
In my experience, a lot of the time this is due to a corrupted database file. (You do have backups, right?) If the log messages convince you of corruption, you can do an escalating series of innodb_force_recovery. Values greater than 0 will open your database read-only with various checks disabled, which may allow you to export your corrupted database files, and then you can start up in normal mode (innodb_force_recovery = 0) and you can DROP the offending table and re-import it.
https://mariadb.com/kb/en/library/innodb-recovery-modes/
hi - i did as you suggested, and also did mysqldump/rebuild to several DB's, but it seems to be happening yet again:
2019-10-11 9:25:57 140163911001856 [Warning] Aborted connection 14 to db: 'ComXX2' user: 'comTrainer' host: 'localhost' (Got an error reading communication packets) 2019-10-11 9:25:57 140163577476864 [Warning] Aborted connection 23 to db: 'ComXX2' user: 'comTrainer' host: 'localhost' (Got an error reading communication packets) 2019-10-11 9:25:57 140163446568704 [Warning] Aborted connection 39 to db: 'ComXX2' user: 'comTrainer' host: 'localhost' (Got an error reading communication packets) 2019-10-11 9:25:57 140163472668416 [Note] InnoDB: Buffer pool(s) load completed at 191011 9:25:57 2019-10-11 9:26:06 140163575326464 [ERROR] mysqld: Table './ComXX12/wp_46_redirection_404' is marked as crashed and should be repaired 2019-10-11 9:26:06 140163575326464 [ERROR] mysqld: Table 'wp_46_redirection_404' is marked as crashed and should be repaired