How to find out the exact cause of the fall of the container with MariaDB?

Have a container with a base, there are backups made, xtrabackup. Backups of test databases safely restored. Backup production does not want. After stopping the container, it won't run. There is such a thing: in Baqubah test databases no file type *.cfg and prod there. Maybe because of this, and what's in these files can be important? Sumy the main question - how to look at the 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=10.1.23 restart docker-mariadb


the restore script: https://pastebin.com/cyFRehZs

I have not considered?
June 7th 19 at 14:29
1 answer
June 7th 19 at 14:31
Solution
All figured out. The reason was the order table, the name of which coincides with the MySQL statement and the fact that I wasn't slanting quotation marks the names of the tables in the restore script.

Find more questions by tags MariaDBMySQLBacking upDockerbash