MySQL starting and shutting down without erros after import a snapshot into a new droplet

May 27, 2019 172 views
MySQL Ubuntu 16.04

I have created a new Droplet with an screenshot of another droplet. Same configuration.
All access are ok, Apache ok but MySQL stops working after a reset and I can´t start anymore.
There is no error in the log file. Checked swap files, space, configuration faile, everything seens to be ok.

Here is the log file:
2019-05-27T17:51:39.485619Z 0 [Warning] Changed limits: maxopenfiles: 1024 (requested 5000)
2019-05-27T17:51:39.485886Z 0 [Warning] Changed limits: tableopencache: 431 (requested 2000)
2019-05-27T17:51:39.666083Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use –explicitdefaultsfortimestamp server option (see documentation for more details).
2019-05-27T17:51:39.668243Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.26-0ubuntu0.16.04.1) starting as process 4022 …
2019-05-27T17:51:39.673534Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-05-27T17:51:39.673678Z 0 [Note] InnoDB: Mutexes and rw
locks use GCC atomic builtins
2019-05-27T17:51:39.673744Z 0 [Note] InnoDB: Uses event mutexes
2019-05-27T17:51:39.673830Z 0 [Note] InnoDB: GCC builtin _atomicthreadfence() is used for memory barrier
2019-05-27T17:51:39.673905Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2019-05-27T17:51:39.673987Z 0 [Note] InnoDB: Using Linux native AIO
2019-05-27T17:51:39.674345Z 0 [Note] InnoDB: Number of pools: 1
2019-05-27T17:51:39.674547Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-05-27T17:51:39.676567Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-05-27T17:51:39.686220Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-05-27T17:51:39.688855Z 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-27T17:51:39.700954Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2019-05-27T17:51:39.711658Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-05-27T17:51:39.711903Z 0 [Note] InnoDB: Setting file ’./ibtmp1’ size to 12 MB. Physically writing the file full; Please wait …
2019-05-27T17:51:39.743031Z 0 [Note] InnoDB: File ’./ibtmp1’ size is now 12 MB.
2019-05-27T17:51:39.744153Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2019-05-27T17:51:39.744245Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2019-05-27T17:51:39.744636Z 0 [Note] InnoDB: Waiting for purge to start
2019-05-27T17:51:39.794896Z 0 [Note] InnoDB: 5.7.26 started; log sequence number 12913170
2019-05-27T17:51:39.795432Z 0 [Note] Plugin ‘FEDERATED’ is disabled.
2019-05-27T17:51:39.802073Z 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-27T17:51:39.802286Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib
bufferpool
2019-05-27T17:51:39.809116Z 0 [Note] InnoDB: Buffer pool(s) load completed at 190527 17:51:39
2019-05-27T17:51:39.814404Z 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.7.26-0ubuntu0.16.04.1’ socket: ’/var/run/mysqld/mysqld.sock’ port: 0 (Ubuntu)
2019-05-27T17:51:40.478609Z 0 [Note] Giving 1 client threads a chance to die gracefully
2019-05-27T17:51:40.478755Z 0 [Note] Shutting down slave threads
2019-05-27T17:51:42.478953Z 0 [Note] Forcefully disconnecting 0 remaining clients
2019-05-27T17:51:42.479264Z 0 [Note] Binlog end
2019-05-27T17:51:42.479693Z 0 [Note] Shutting down plugin 'ngram’
2019-05-27T17:51:42.479815Z 0 [Note] Shutting down plugin 'partition’
2019-05-27T17:51:42.479907Z 0 [Note] Shutting down plugin 'ARCHIVE’
2019-05-27T17:51:42.479980Z 0 [Note] Shutting down plugin 'BLACKHOLE’
2019-05-27T17:51:42.480046Z 0 [Note] Shutting down plugin 'MRG
MYISAM’
2019-05-27T17:51:42.480109Z 0 [Note] Shutting down plugin 'MEMORY’
2019-05-27T17:51:42.480179Z 0 [Note] Shutting down plugin 'MyISAM’
2019-05-27T17:51:42.480257Z 0 [Note] Shutting down plugin 'PERFORMANCESCHEMA’
2019-05-27T17:51:42.480357Z 0 [Note] Shutting down plugin 'INNODB
SYSVIRTUAL’
2019-05-27T17:51:42.480420Z 0 [Note] Shutting down plugin 'INNODB
SYSDATAFILES’
2019-05-27T17:51:42.480477Z 0 [Note] Shutting down plugin 'INNODB
SYSTABLESPACES’
2019-05-27T17:51:42.480532Z 0 [Note] Shutting down plugin 'INNODB
SYSFOREIGNCOLS’
2019-05-27T17:51:42.480587Z 0 [Note] Shutting down plugin 'INNODBSYSFOREIGN’
2019-05-27T17:51:42.480642Z 0 [Note] Shutting down plugin 'INNODBSYSFIELDS’
2019-05-27T17:51:42.480698Z 0 [Note] Shutting down plugin 'INNODBSYSCOLUMNS’
2019-05-27T17:51:42.480753Z 0 [Note] Shutting down plugin 'INNODBSYSINDEXES’
2019-05-27T17:51:42.480808Z 0 [Note] Shutting down plugin 'INNODBSYSTABLESTATS’
2019-05-27T17:51:42.480865Z 0 [Note] Shutting down plugin 'INNODBSYSTABLES’
2019-05-27T17:51:42.480928Z 0 [Note] Shutting down plugin 'INNODBFTINDEXTABLE’
2019-05-27T17:51:42.480984Z 0 [Note] Shutting down plugin 'INNODB
FTINDEXCACHE’
2019-05-27T17:51:42.481056Z 0 [Note] Shutting down plugin 'INNODBFTCONFIG’
2019-05-27T17:51:42.481119Z 0 [Note] Shutting down plugin 'INNODBFTBEINGDELETED’
2019-05-27T17:51:42.481176Z 0 [Note] Shutting down plugin 'INNODB
FTDELETED’
2019-05-27T17:51:42.481231Z 0 [Note] Shutting down plugin 'INNODB
FTDEFAULTSTOPWORD’
2019-05-27T17:51:42.481285Z 0 [Note] Shutting down plugin 'INNODBMETRICS’
2019-05-27T17:51:42.481340Z 0 [Note] Shutting down plugin 'INNODB
TEMPTABLEINFO’
2019-05-27T17:51:42.481394Z 0 [Note] Shutting down plugin 'INNODBBUFFERPOOLSTATS’
2019-05-27T17:51:42.481448Z 0 [Note] Shutting down plugin 'INNODB
BUFFERPAGELRU’
2019-05-27T17:51:42.481502Z 0 [Note] Shutting down plugin 'INNODBBUFFERPAGE’
2019-05-27T17:51:42.481555Z 0 [Note] Shutting down plugin 'INNODBCMPPERINDEXRESET’
2019-05-27T17:51:42.481610Z 0 [Note] Shutting down plugin 'INNODBCMPPERINDEX’
2019-05-27T17:51:42.481663Z 0 [Note] Shutting down plugin 'INNODB
CMPMEMRESET’
2019-05-27T17:51:42.481717Z 0 [Note] Shutting down plugin 'INNODB
CMPMEM’
2019-05-27T17:51:42.481772Z 0 [Note] Shutting down plugin 'INNODBCMPRESET’
2019-05-27T17:51:42.481826Z 0 [Note] Shutting down plugin 'INNODBCMP’
2019-05-27T17:51:42.481879Z 0 [Note] Shutting down plugin 'INNODB
LOCKWAITS’
2019-05-27T17:51:42.481933Z 0 [Note] Shutting down plugin 'INNODB
LOCKS’
2019-05-27T17:51:42.481987Z 0 [Note] Shutting down plugin 'INNODBTRX’
2019-05-27T17:51:42.482060Z 0 [Note] Shutting down plugin 'InnoDB’
2019-05-27T17:51:42.482209Z 0 [Note] InnoDB: FTS optimize thread exiting.
2019-05-27T17:51:42.482407Z 0 [Note] InnoDB: Starting shutdown…
2019-05-27T17:51:42.582833Z 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib
bufferpool
2019-05-27T17:51:42.583271Z 0 [Note] InnoDB: Buffer pool(s) dump completed at 190527 17:51:42
2019-05-27T17:51:43.591713Z 0 [Note] InnoDB: Shutdown completed; log sequence number 12913198
2019-05-27T17:51:43.593488Z 0 [Note] InnoDB: Removed temporary tablespace data file: “ibtmp1”
2019-05-27T17:51:43.593603Z 0 [Note] Shutting down plugin 'CSV’
2019-05-27T17:51:43.593662Z 0 [Note] Shutting down plugin 'sha256
password’
2019-05-27T17:51:43.593710Z 0 [Note] Shutting down plugin 'mysqlnativepassword’
2019-05-27T17:51:43.593923Z 0 [Note] Shutting down plugin 'binlog’
2019-05-27T17:51:43.594271Z 0 [Note] /usr/sbin/mysqld: Shutdown complete

Any clues?
Tks for helping
Issler

1 Answer

Hello,

I have a few suggestions to start troubleshooting the issue.

1.Can you let me know if you tried to start MySQL with innodbforcerecovery? If yes, on what state did you managed to start it from 1 to 6? Maybe there is a Database corruption.

2.Try to repair the databases located in the MySQL service?

  1. Try to temporarily move away the databases from MySQL and try to star it. Does it start or does it still shutdowns?

When you have the time, please pop a reply so that we can further troubleshoot.

Have another answer? Share your knowledge.