V
V
Vyacheslav Grachunov2018-03-03 20:30:24
MySQL
Vyacheslav Grachunov, 2018-03-03 20:30:24

How to find out the exact cause of a MariaDB container crash?

There is a container with a database, there are backups made by xtrabackup. Backups of test databases are easily restored. Backup does not want production. Once the container is stopped, it will no longer run. There is another thing: there are no *.cfg files in the backups of the test databases, but there are in the prod. Maybe because of this and what might be important in these files? Svmy main question - how to look with what error falls?
config:

host=127.0.0.1
user=root
port=3308
password=PaSsWoRd
database_dir=/path/to/db
encryption_key=/path/to/key
dbsake_path=/path/to/dbsake
restart_mysql=docker restart 10.1.23-mariadb

recovery script: https://pastebin.com/cyFRehZs
maybe I didn't take it into account?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
V
Vyacheslav Grachunov, 2018-03-04
@Qwentor

All figured out. The reason turned out to be the order table, the name of which matches the MySQL statement, and the fact that I did not take the table names in slash quotes in the recovery script.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question