Question
Mysql Crashes when server is reboot
log 1
2020-06-17T15:55:14.199344Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-06-17T15:55:14.201848Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.30-0ubuntu0.18.04.1) starting as process 1284 ...
2020-06-17T15:55:14.209228Z 0 [Note] InnoDB: PUNCH HOLE support available
2020-06-17T15:55:14.209273Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-06-17T15:55:14.209280Z 0 [Note] InnoDB: Uses event mutexes
2020-06-17T15:55:14.209286Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2020-06-17T15:55:14.209292Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-06-17T15:55:14.209298Z 0 [Note] InnoDB: Using Linux native AIO
2020-06-17T15:55:14.210487Z 0 [Note] InnoDB: Number of pools: 1
2020-06-17T15:55:14.212518Z 0 [Note] InnoDB: Using CPU crc32 instructions
2020-06-17T15:55:14.215334Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2020-06-17T15:55:14.230260Z 0 [Note] InnoDB: Completed initialization of buffer pool
2020-06-17T15:55:14.234012Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-06-17T15:55:14.263438Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2020-06-17T15:57:25.238353Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 3980399339
2020-06-17T15:57:25.238488Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 3980410601
2020-06-17T15:59:36.316075Z 0 [Note] InnoDB: Database was not shutdown normally!
2020-06-17T15:59:36.316134Z 0 [Note] InnoDB: Starting crash recovery.
log 2
mysql.service - MySQL Community Server
Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2020-06-17 16:26:07 UTC; 7min ago
Process: 1618 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=1/FAILURE)
Jun 17 16:26:06 ubuntu-s-2vcpu-2gb-nyc1-01 systemd[1]: mysql.service: Control process exited, code=exited status=1
Jun 17 16:26:06 ubuntu-s-2vcpu-2gb-nyc1-01 systemd[1]: mysql.service: Failed with result 'exit-code'.
Jun 17 16:26:06 ubuntu-s-2vcpu-2gb-nyc1-01 systemd[1]: Failed to start MySQL Community Server.
Jun 17 16:26:07 ubuntu-s-2vcpu-2gb-nyc1-01 systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Jun 17 16:26:07 ubuntu-s-2vcpu-2gb-nyc1-01 systemd[1]: mysql.service: Scheduled restart job, restart counter is at 5.
Jun 17 16:26:07 ubuntu-s-2vcpu-2gb-nyc1-01 systemd[1]: Stopped MySQL Community Server.
Jun 17 16:26:07 ubuntu-s-2vcpu-2gb-nyc1-01 systemd[1]: mysql.service: Start request repeated too quickly.
Jun 17 16:26:07 ubuntu-s-2vcpu-2gb-nyc1-01 systemd[1]: mysql.service: Failed with result 'exit-code'.
Jun 17 16:26:07 ubuntu-s-2vcpu-2gb-nyc1-01 systemd[1]: Failed to start MySQL Community Server.
what is the problem ?
note:
mysql is in blockstrage /mnt/volumexxx but I uses over than 2 mounth
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
×