191122 14:16:26 mysqld_safe Logging to '/var/db/mysql/pm2-64.err'.
191122 14:16:26 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2019-11-22 14:16:26 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-11-22 14:16:26 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.45) starting as process 14637 ...
2019-11-22 14:16:26 14637 [Note] Plugin 'FEDERATED' is disabled.
2019-11-22 14:16:26 14637 [Note] InnoDB: Using atomics to ref count buffer pool pages
2019-11-22 14:16:26 14637 [Note] InnoDB: The InnoDB memory heap is disabled
2019-11-22 14:16:26 14637 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-11-22 14:16:26 14637 [Note] InnoDB: Memory barrier is not used
2019-11-22 14:16:26 14637 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-11-22 14:16:26 14637 [Note] InnoDB: Using CPU crc32 instructions
2019-11-22 14:16:26 14637 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-11-22 14:16:26 14637 [Note] InnoDB: Completed initialization of buffer pool
2019-11-22 14:16:26 14637 [Note] InnoDB: Highest supported file format is Barracuda.
2019-11-22 14:16:26 14637 [Note] InnoDB: The log sequence numbers 1607571 and 1607571 in ibdata files do not match the log sequence number 1607581 in the ib_logfiles!
2019-11-22 14:16:26 14637 [Note] InnoDB: Database was not shutdown normally!
2019-11-22 14:16:26 14637 [Note] InnoDB: Starting crash recovery.
2019-11-22 14:16:26 14637 [Note] InnoDB: Reading tablespace information from the .ibd files...
2019-11-22 14:16:26 14637 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace account/server_settings uses space ID: 5 at filepath: ./account/server_settings.ibd. Cannot open tablespace mysql/slave_worker_info which uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd
2019-11-22 14:16:26 803616000  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./mysql/slave_worker_info.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
191122 14:16:26 mysqld_safe mysqld from pid file /var/db/mysql/pm2-64.pid ended