Mysql goes down

Posted 1 year ago by deansatch

Just noticed mysql went down for a few minutes. This is the log...any ideas what the cause could be?

2018-03-20T16:54:17.865993Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
2018-03-20T16:54:17.866081Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
2018-03-20T16:54:18.030503Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-03-20T16:54:18.032406Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.21-0ubuntu0.16.04.1) starting as process 22733 ...
2018-03-20T16:54:18.038007Z 0 [Note] InnoDB: PUNCH HOLE support available
2018-03-20T16:54:18.038049Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-03-20T16:54:18.038059Z 0 [Note] InnoDB: Uses event mutexes
2018-03-20T16:54:18.038065Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2018-03-20T16:54:18.038072Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2018-03-20T16:54:18.038078Z 0 [Note] InnoDB: Using Linux native AIO
2018-03-20T16:54:18.038379Z 0 [Note] InnoDB: Number of pools: 1
2018-03-20T16:54:18.038522Z 0 [Note] InnoDB: Using CPU crc32 instructions
2018-03-20T16:54:18.040492Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2018-03-20T16:54:18.050071Z 0 [Note] InnoDB: Completed initialization of buffer pool
2018-03-20T16:54:18.052516Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2018-03-20T16:54:18.070163Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2018-03-20T16:54:18.072329Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 39365648
2018-03-20T16:54:18.072360Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 39365657
2018-03-20T16:54:18.072370Z 0 [Note] InnoDB: Database was not shutdown normally!
2018-03-20T16:54:18.072389Z 0 [Note] InnoDB: Starting crash recovery.
2018-03-20T16:54:18.239588Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2018-03-20T16:54:18.239634Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2018-03-20T16:54:18.239698Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2018-03-20T16:54:18.268402Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2018-03-20T16:54:18.269730Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2018-03-20T16:54:18.269753Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2018-03-20T16:54:18.270515Z 0 [Note] InnoDB: Waiting for purge to start
2018-03-20T16:54:18.320775Z 0 [Note] InnoDB: 5.7.21 started; log sequence number 39365657
2018-03-20T16:54:18.321824Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2018-03-20T16:54:18.322183Z 0 [Note] Plugin 'FEDERATED' is disabled.
2018-03-20T16:54:18.329836Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
2018-03-20T16:54:18.329865Z 0 [Note] Server hostname (bind-address): ''; port: 3306
2018-03-20T16:54:18.329879Z 0 [Note]   - '' resolves to '';
2018-03-20T16:54:18.329914Z 0 [Note] Server socket created on IP: ''.
2018-03-20T16:54:18.338620Z 0 [Note] InnoDB: Buffer pool(s) load completed at 180320 16:54:18
2018-03-20T16:54:18.359917Z 0 [Note] Event Scheduler: Loaded 0 events
2018-03-20T16:54:18.360114Z 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.7.21-0ubuntu0.16.04.1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
2018-03-20T16:54:18.870806Z 2 [Note] Access denied for user 'root'@'localhost' (using password: NO)

Please sign in or create an account to participate in this conversation.

Reply to

Use Markdown with GitHub-flavored code blocks.