Mysql restarts, how to understand why?

Question

linux

Good afternoon. I can't figure out why mysql is restarting / need help.
I turned off the task book in mysqle itself, checked all the crons there, there is nothing connected with mysql.
There is only one database on the server and all tables are in innodb.
Suslog:

Event Scheduler: Purging the queue. 0 events
 [Note] InnoDB: FTS optimize thread exiting.
 [Note] InnoDB: Starting shutdown...
 [Note] InnoDB: Shutdown completed; log sequence number 7548952730
 [Note] /usr/sbin/mysqld: Shutdown complete
 mysqld:
 mysqld from pid file /var/run/mysqld/mysqld.pid ended
 mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql
 [Note] Using unique option prefix 'thread_cache' is error-prone and can break in the future. Please use the full name 'thread_cache_size' instead.
 [Note] /usr/sbin/mysqld (mysqld 10.1.18-MariaDB-1~trusty) starting as process 12448 ...
 [Warning] You need to use --log-bin to make --binlog-format work.
 [Note] Using unique option prefix 'myisam-recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.
 [Note] InnoDB: Using mutexes to ref count buffer pool pages
 [Note] InnoDB: The InnoDB memory heap is disabled
 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
[Note] InnoDB: Compressed tables use zlib 1.2.8
[Note] InnoDB: Using Linux native AIO
[Note] InnoDB: Using SSE crc32 instructions
[Note] InnoDB: Initializing buffer pool, size = 3.0G
[Note] InnoDB: Completed initialization of buffer pool
[Note] InnoDB: Highest supported file format is Barracuda.
[Note] InnoDB: 128 rollback segment(s) are active.
[Note] InnoDB: Waiting for purge to start
[Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.32-78.1 started; log sequence number 7548952730
[Note] InnoDB: Dumping buffer pool(s) not yet started
[Note] Plugin 'FEEDBACK' is disabled.
[Note] Server socket created on IP: '::'.
[Warning] 'user' entry '[email protected]' ignored in --skip-name-resolve mode.
[Warning] 'user' entry '‘mytop’@’localhost’' ignored in --skip-name-resolve mode.
[Warning] 'proxies_priv' entry '@% [email protected]' ignored in --skip-name-resolve mode.
 [Note] /usr/sbin/mysqld: ready for connections.
 socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
 Upgrading MySQL tables if necessary.
 /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
 Looking for 'mysql' as: /usr/bin/mysql
 Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
 This installation of MySQL is already upgraded to 10.1.18-MariaDB, use --force if you still need to run mysql_upgrade
 Checking for insecure root accounts.

I'm thinking of upgrading to 10.1.19.
I would be grateful for any hint.
Thanks

Answer 1

Not very familiar with MySQL/MariaDB, but there you can probably run the server process in debug mode and look at a more detailed log.