Offline server, mysql error

May 24, 2019 138 views
MySQL Ubuntu

my server went offline and the following error appears in mysql, can anyone help me solve it and put my blog back online

2019-05-24T18:05:26.269059Z 0 [Warning] Changed limits: maxopenfiles: 1024 (requested 5000)
2019-05-24T18:05:26.269718Z 0 [Warning] Changed limits: tableopencache: 431 (requested 2000)
2019-05-24T18:05:26.573817Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicitdefaultsfortimestamp server option (see documentation for more details).
2019-05-24T18:05:26.578381Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.26-0ubuntu0.16.04.1) starting as process 1431 ...
2019-05-24T18:05:26.622659Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-05-24T18:05:26.622685Z 0 [Note] InnoDB: Mutexes and rw
locks use GCC atomic builtins
2019-05-24T18:05:26.622690Z 0 [Note] InnoDB: Uses event mutexes
2019-05-24T18:05:26.622694Z 0 [Note] InnoDB: GCC builtin _atomicthreadfence() is used for memory barrier
2019-05-24T18:05:26.622698Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2019-05-24T18:05:26.622702Z 0 [Note] InnoDB: Using Linux native AIO
2019-05-24T18:05:26.630436Z 0 [Note] InnoDB: Number of pools: 1
2019-05-24T18:05:26.633992Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-05-24T18:05:26.636553Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-05-24T18:05:26.668054Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-05-24T18:05:26.690310Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-05-24T18:05:26.743229Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2019-05-24T18:05:26.770218Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 38722558620
2019-05-24T18:05:26.770244Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 38722558629
2019-05-24T18:05:26.770250Z 0 [Note] InnoDB: Database was not shutdown normally!
2019-05-24T18:05:26.770254Z 0 [Note] InnoDB: Starting crash recovery.
2019-05-24T18:05:27.021937Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-05-24T18:05:27.021971Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-05-24T18:05:27.022050Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-05-24T18:05:27.057880Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2019-05-24T18:05:27.059157Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2019-05-24T18:05:27.059171Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2019-05-24T18:05:27.059613Z 0 [Note] InnoDB: Waiting for purge to start
2019-05-24T18:05:27.109830Z 0 [Note] InnoDB: 5.7.26 started; log sequence number 38722558629
2019-05-24T18:05:27.110537Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib
2019-05-24T18:05:27.111058Z 0 [Note] Plugin 'FEDERATED' is disabled.
2019-05-24T18:05:27.127531Z 0 [Note] InnoDB: Buffer pool(s) load completed at 190524 18:05:27
2019-05-24T18:05:27.129591Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
2019-05-24T18:05:27.129611Z 0 [Note] Server hostname (bind-address): ''; port: 3306
2019-05-24T18:05:27.129624Z 0 [Note] - '' resolves to '';
2019-05-24T18:05:27.129666Z 0 [Note] Server socket created on IP: ''.
2019-05-24T18:05:27.181405Z 0 [Note] Event Scheduler: Loaded 0 events
2019-05-24T18:05:27.181637Z 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.7.26-0ubuntu0.16.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
2019-05-24T18:05:27.238013Z 2 [Note] Access denied for user 'root'@'localhost' (using password: NO)

1 Answer

Hi there,

From what I can tell, the vast majority of that log is simply letting you know that it has recovered from a crashed state where it shut down unexpectedly.

The last line is the only thing that I can see as an issue, it failed to log in a root locally, which may suggest that the root user has been removed from the SQL server or its permissions/password changed.

Have another answer? Share your knowledge.