Re: #1036 - Table 'gain' is read only
Posted by: Ronald Wiplinger
Date: November 05, 2016 12:09AM
Date: November 05, 2016 12:09AM
I forced disk check by restart and found this in my log file:
Nov 5 13:48:57 ronald-desktop mysql[1718]: * Starting MariaDB database server mysqld
Nov 5 13:48:57 ronald-desktop mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] /usr/sbin/mysqld (mysqld 10.0.25-MariaDB-0ubuntu0.15.10.1) starting as process 1944 ...
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] InnoDB: Using mutexes to ref count buffer pool pages
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] InnoDB: The InnoDB memory heap is disabled
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] InnoDB: Memory barrier is not used
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] InnoDB: Compressed tables use zlib 1.2.8
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] InnoDB: Using Linux native AIO
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] InnoDB: Using CPU crc32 instructions
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] InnoDB: Initializing buffer pool, size = 128.0M
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] InnoDB: Completed initialization of buffer pool
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] InnoDB: Highest supported file format is Barracuda.
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] InnoDB: Log scan progressed past the checkpoint lsn 8242949749
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] InnoDB: Database was not shutdown normally!
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] InnoDB: Starting crash recovery.
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] InnoDB: Reading tablespace information from the .ibd files...
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ecom/wp_termmeta uses space ID: 3 at filepath: ./ecom/wp_termmeta.ibd. Cannot open tablespace mysql/slave_relay_log_info which uses space ID: 3 at filepath: ./mysql/slave_relay_log_info.ibd
Nov 5 13:48:57 ronald-desktop mysqld: 2016-11-05 13:48:57 7fd14ee21780 InnoDB: Operating system error number 2 in a file operation.
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: The error means the system cannot find the path specified.
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: If you are installing InnoDB, remember that you must create
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: directories yourself, InnoDB does not create them.
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: Error: could not open single-table tablespace file ./mysql/slave_relay_log_info.ibd
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: We do not continue the crash recovery, because the table may become
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: To fix the problem and start mysqld:
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: 1) If there is a permission problem in the file and mysqld cannot
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: open the file, you should modify the permissions.
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: 2) If the table is not needed, or you can restore it from a backup,
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: crash recovery and ignore that table.
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: 3) If the file system or the disk is broken, and you cannot remove
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: and force InnoDB to continue crash recovery here.
Nov 5 13:48:57 ronald-desktop mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended
Nov 5 13:49:28 ronald-desktop /etc/init.d/mysql[2253]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Nov 5 13:49:28 ronald-desktop /etc/init.d/mysql[2253]: #007/usr/bin/mysqladmin: connect to server at 'localhost' failed
Nov 5 13:49:28 ronald-desktop /etc/init.d/mysql[2253]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2 "No such file or directory")'
Nov 5 13:49:28 ronald-desktop /etc/init.d/mysql[2253]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Nov 5 13:49:28 ronald-desktop /etc/init.d/mysql[2253]:
Nov 5 13:49:28 ronald-desktop mysql[1718]: ...fail!
Nov 5 13:49:28 ronald-desktop systemd[1]: mysql.service: Control process exited, code=exited status=1
Nov 5 13:49:28 ronald-desktop systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
Nov 5 13:49:28 ronald-desktop systemd[1]: mysql.service: Unit entered failed state.
Nov 5 13:49:28 ronald-desktop systemd[1]: mysql.service: Failed with result 'exit-code'.
Nov 5 13:51:36 ronald-desktop systemd[1]: Starting LSB: Start and stop the mysql database server daemon...
Nov 5 13:51:36 ronald-desktop mysql[3498]: * Starting MariaDB database server mysqld
Nov 5 13:51:37 ronald-desktop mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] /usr/sbin/mysqld (mysqld 10.0.25-MariaDB-0ubuntu0.15.10.1) starting as process 3688 ...
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] InnoDB: Using mutexes to ref count buffer pool pages
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] InnoDB: The InnoDB memory heap is disabled
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] InnoDB: Memory barrier is not used
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] InnoDB: Compressed tables use zlib 1.2.8
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] InnoDB: Using Linux native AIO
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] InnoDB: Using CPU crc32 instructions
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] InnoDB: Initializing buffer pool, size = 128.0M
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] InnoDB: Completed initialization of buffer pool
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] InnoDB: Highest supported file format is Barracuda.
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] InnoDB: Log scan progressed past the checkpoint lsn 8242949749
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] InnoDB: Database was not shutdown normally!
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] InnoDB: Starting crash recovery.
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] InnoDB: Reading tablespace information from the .ibd files...
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ecom/wp_termmeta uses space ID: 3 at filepath: ./ecom/wp_termmeta.ibd. Cannot open tablespace mysql/slave_relay_log_info which uses space ID: 3 at filepath: ./mysql/slave_relay_log_info.ibd
Nov 5 13:51:37 ronald-desktop mysqld: 2016-11-05 13:51:37 7fe25c17d780 InnoDB: Operating system error number 2 in a file operation.
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: The error means the system cannot find the path specified.
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: If you are installing InnoDB, remember that you must create
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: directories yourself, InnoDB does not create them.
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: Error: could not open single-table tablespace file ./mysql/slave_relay_log_info.ibd
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: We do not continue the crash recovery, because the table may become
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: To fix the problem and start mysqld:
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: 1) If there is a permission problem in the file and mysqld cannot
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: open the file, you should modify the permissions.
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: 2) If the table is not needed, or you can restore it from a backup,
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: crash recovery and ignore that table.
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: 3) If the file system or the disk is broken, and you cannot remove
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: and force InnoDB to continue crash recovery here.
Nov 5 13:51:37 ronald-desktop mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended
Nov 5 13:51:40 ronald-desktop kernel: [ 313.820432] [UFW BLOCK] IN=enp5s0 OUT= MAC=d0:50:99:29:b9:ab:24:65:11:df:48:0e:08:00 SRC=198.23.109.211 DST=192.168.178.20 LEN=59 TOS=0x00 PREC=0x00 TTL=46 ID=56579 DF PROTO=TCP SPT=8060 DPT=51020 WINDOW=12 RES=0x00 ACK PSH URGP=0
Nov 5 13:52:07 ronald-desktop /etc/init.d/mysql[3992]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Nov 5 13:52:07 ronald-desktop /etc/init.d/mysql[3992]: #007/usr/bin/mysqladmin: connect to server at 'localhost' failed
Nov 5 13:52:07 ronald-desktop /etc/init.d/mysql[3992]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2 "No such file or directory")'
Nov 5 13:52:07 ronald-desktop /etc/init.d/mysql[3992]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Nov 5 13:52:07 ronald-desktop /etc/init.d/mysql[3992]:
Nov 5 13:52:07 ronald-desktop mysql[3498]: ...fail!
Nov 5 13:52:07 ronald-desktop systemd[1]: mysql.service: Control process exited, code=exited status=1
Nov 5 13:52:07 ronald-desktop systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
Nov 5 13:52:07 ronald-desktop systemd[1]: mysql.service: Unit entered failed state.
Nov 5 13:52:07 ronald-desktop systemd[1]: mysql.service: Failed with result 'exit-code'.
Nov 5 13:53:01 ronald-desktop systemd[1]: Starting LSB: Start and stop the mysql database server daemon...
Nov 5 13:53:01 ronald-desktop mysql[4046]: * Starting MariaDB database server mysqld
Nov 5 13:53:01 ronald-desktop mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] /usr/sbin/mysqld (mysqld 10.0.25-MariaDB-0ubuntu0.15.10.1) starting as process 4236 ...
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: Using mutexes to ref count buffer pool pages
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: The InnoDB memory heap is disabled
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: Memory barrier is not used
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: Compressed tables use zlib 1.2.8
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: Using Linux native AIO
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: Using CPU crc32 instructions
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: Initializing buffer pool, size = 128.0M
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: Completed initialization of buffer pool
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: Highest supported file format is Barracuda.
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: Log scan progressed past the checkpoint lsn 8242949749
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: Database was not shutdown normally!
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: Starting crash recovery.
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: Reading tablespace information from the .ibd files...
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ecom/wp_termmeta uses space ID: 3 at filepath: ./ecom/wp_termmeta.ibd. Cannot open tablespace mysql/slave_relay_log_info which uses space ID: 3 at filepath: ./mysql/slave_relay_log_info.ibd
Nov 5 13:53:01 ronald-desktop mysqld: 2016-11-05 13:53:01 7f5eaa5ab780 InnoDB: Operating system error number 2 in a file operation.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: The error means the system cannot find the path specified.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: If you are installing InnoDB, remember that you must create
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: directories yourself, InnoDB does not create them.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: Error: could not open single-table tablespace file ./mysql/slave_relay_log_info.ibd
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: We do not continue the crash recovery, because the table may become
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: To fix the problem and start mysqld:
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 1) If there is a permission problem in the file and mysqld cannot
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: open the file, you should modify the permissions.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 2) If the table is not needed, or you can restore it from a backup,
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: crash recovery and ignore that table.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 3) If the file system or the disk is broken, and you cannot remove
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: and force InnoDB to continue crash recovery here.
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: innodb_force_recovery was set to 4. Continuing crash recovery even though we cannot access the .ibd file of this table.
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ecom/wp_terms uses space ID: 4 at filepath: ./ecom/wp_terms.ibd. Cannot open tablespace mysql/slave_master_info which uses space ID: 4 at filepath: ./mysql/slave_master_info.ibd
Nov 5 13:53:01 ronald-desktop mysqld: 2016-11-05 13:53:01 7f5eaa5ab780 InnoDB: Operating system error number 2 in a file operation.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: The error means the system cannot find the path specified.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: If you are installing InnoDB, remember that you must create
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: directories yourself, InnoDB does not create them.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: Error: could not open single-table tablespace file ./mysql/slave_master_info.ibd
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: We do not continue the crash recovery, because the table may become
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: To fix the problem and start mysqld:
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 1) If there is a permission problem in the file and mysqld cannot
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: open the file, you should modify the permissions.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 2) If the table is not needed, or you can restore it from a backup,
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: crash recovery and ignore that table.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 3) If the file system or the disk is broken, and you cannot remove
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: and force InnoDB to continue crash recovery here.
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: innodb_force_recovery was set to 4. Continuing crash recovery even though we cannot access the .ibd file of this table.
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ecom/wp_users uses space ID: 1 at filepath: ./ecom/wp_users.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: ./mysql/innodb_table_stats.ibd
Nov 5 13:53:01 ronald-desktop mysqld: 2016-11-05 13:53:01 7f5eaa5ab780 InnoDB: Operating system error number 2 in a file operation.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: The error means the system cannot find the path specified.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: If you are installing InnoDB, remember that you must create
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: directories yourself, InnoDB does not create them.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: Error: could not open single-table tablespace file ./mysql/innodb_table_stats.ibd
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: We do not continue the crash recovery, because the table may become
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: To fix the problem and start mysqld:
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 1) If there is a permission problem in the file and mysqld cannot
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: open the file, you should modify the permissions.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 2) If the table is not needed, or you can restore it from a backup,
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: crash recovery and ignore that table.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 3) If the file system or the disk is broken, and you cannot remove
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: and force InnoDB to continue crash recovery here.
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: innodb_force_recovery was set to 4. Continuing crash recovery even though we cannot access the .ibd file of this table.
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ecom/wp_usermeta uses space ID: 2 at filepath: ./ecom/wp_usermeta.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: ./mysql/innodb_index_stats.ibd
Nov 5 13:53:01 ronald-desktop mysqld: 2016-11-05 13:53:01 7f5eaa5ab780 InnoDB: Operating system error number 2 in a file operation.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: The error means the system cannot find the path specified.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: If you are installing InnoDB, remember that you must create
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: directories yourself, InnoDB does not create them.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: Error: could not open single-table tablespace file ./mysql/innodb_index_stats.ibd
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: We do not continue the crash recovery, because the table may become
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: To fix the problem and start mysqld:
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 1) If there is a permission problem in the file and mysqld cannot
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: open the file, you should modify the permissions.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 2) If the table is not needed, or you can restore it from a backup,
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: crash recovery and ignore that table.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 3) If the file system or the disk is broken, and you cannot remove
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: and force InnoDB to continue crash recovery here.
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: innodb_force_recovery was set to 4. Continuing crash recovery even though we cannot access the .ibd file of this table.
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ecom/wp_term_taxonomy uses space ID: 5 at filepath: ./ecom/wp_term_taxonomy.ibd. Cannot open tablespace mysql/slave_worker_info which uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd
Nov 5 13:53:01 ronald-desktop mysqld: 2016-11-05 13:53:01 7f5eaa5ab780 InnoDB: Operating system error number 2 in a file operation.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: The error means the system cannot find the path specified.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: If you are installing InnoDB, remember that you must create
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: directories yourself, InnoDB does not create them.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: Error: could not open single-table tablespace file ./mysql/slave_worker_info.ibd
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: We do not continue the crash recovery, because the table may become
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: To fix the problem and start mysqld:
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 1) If there is a permission problem in the file and mysqld cannot
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: open the file, you should modify the permissions.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 2) If the table is not needed, or you can restore it from a backup,
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: crash recovery and ignore that table.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 3) If the file system or the disk is broken, and you cannot remove
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: and force InnoDB to continue crash recovery here.
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: innodb_force_recovery was set to 4. Continuing crash recovery even though we cannot access the .ibd file of this table.
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: Restoring possible half-written data pages
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: from the doublewrite buffer...
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: Doing recovery: scanned up to log sequence number 8242949789
Nov 5 13:53:02 ronald-desktop mysqld: 161105 13:53:02 [Note] InnoDB: 128 rollback segment(s) are active.
Nov 5 13:53:02 ronald-desktop mysqld: 161105 13:53:02 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.29-76.2 started; log sequence number 8242949789
Nov 5 13:53:02 ronald-desktop mysqld: 161105 13:53:02 [Note] InnoDB: !!! innodb_force_recovery is set to 4 !!!
Nov 5 13:53:02 ronald-desktop mysqld: 161105 13:53:02 [Note] Plugin 'FEEDBACK' is disabled.
Nov 5 13:53:02 ronald-desktop mysqld: 161105 13:53:02 [ERROR] Plugin 'innodb' already installed
Nov 5 13:53:02 ronald-desktop mysqld: 161105 13:53:02 [ERROR] Plugin 'federated' already installed
Nov 5 13:53:02 ronald-desktop mysqld: 161105 13:53:02 [ERROR] Plugin 'blackhole' already installed
Nov 5 13:53:02 ronald-desktop mysqld: 161105 13:53:02 [ERROR] Plugin 'archive' already installed
Nov 5 13:53:02 ronald-desktop mysqld: 161105 13:53:02 [Note] Server socket created on IP: '127.0.0.1'.
Nov 5 13:53:02 ronald-desktop mysqld: 161105 13:53:02 [Note] /usr/sbin/mysqld: ready for connections.
Nov 5 13:53:02 ronald-desktop mysqld: Version: '10.0.25-MariaDB-0ubuntu0.15.10.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
Nov 5 13:53:02 ronald-desktop mysql[4046]: ...done.
Nov 5 13:53:02 ronald-desktop systemd[1]: Started LSB: Start and stop the mysql database server daemon.
Nov 5 13:53:02 ronald-desktop /etc/mysql/debian-start[4284]: Upgrading MySQL tables if necessary.
Nov 5 13:53:02 ronald-desktop /etc/mysql/debian-start[4287]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Nov 5 13:53:02 ronald-desktop /etc/mysql/debian-start[4287]: Looking for 'mysql' as: /usr/bin/mysql
Nov 5 13:53:02 ronald-desktop /etc/mysql/debian-start[4287]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Nov 5 13:53:02 ronald-desktop /etc/mysql/debian-start[4287]: Version check failed. Got the following error when calling the 'mysql' command line client
Nov 5 13:53:02 ronald-desktop /etc/mysql/debian-start[4287]: ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO)
Nov 5 13:53:02 ronald-desktop /etc/mysql/debian-start[4287]: FATAL ERROR: Upgrade failed
Nov 5 13:53:02 ronald-desktop /etc/mysql/debian-start[4296]: Checking for insecure root accounts.
Nov 5 13:53:02 ronald-desktop mysql[4046]: ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO)
Nov 5 13:53:18 ronald-desktop systemd[1]: Stopping LSB: Start and stop the mysql database server daemon...
Nov 5 13:53:18 ronald-desktop mysql[4331]: * Stopping MariaDB database server mysqld
Nov 5 13:53:19 ronald-desktop mysql[4331]: ...fail!
Nov 5 13:53:19 ronald-desktop systemd[1]: mysql.service: Control process exited, code=exited status=1
Nov 5 13:53:19 ronald-desktop systemd[1]: Stopped LSB: Start and stop the mysql database server daemon.
Nov 5 13:53:19 ronald-desktop systemd[1]: mysql.service: Unit entered failed state.
Nov 5 13:53:19 ronald-desktop systemd[1]: mysql.service: Failed with result 'exit-code'.
Nov 5 13:48:57 ronald-desktop mysql[1718]: * Starting MariaDB database server mysqld
Nov 5 13:48:57 ronald-desktop mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] /usr/sbin/mysqld (mysqld 10.0.25-MariaDB-0ubuntu0.15.10.1) starting as process 1944 ...
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] InnoDB: Using mutexes to ref count buffer pool pages
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] InnoDB: The InnoDB memory heap is disabled
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] InnoDB: Memory barrier is not used
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] InnoDB: Compressed tables use zlib 1.2.8
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] InnoDB: Using Linux native AIO
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] InnoDB: Using CPU crc32 instructions
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] InnoDB: Initializing buffer pool, size = 128.0M
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] InnoDB: Completed initialization of buffer pool
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] InnoDB: Highest supported file format is Barracuda.
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] InnoDB: Log scan progressed past the checkpoint lsn 8242949749
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] InnoDB: Database was not shutdown normally!
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] InnoDB: Starting crash recovery.
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [Note] InnoDB: Reading tablespace information from the .ibd files...
Nov 5 13:48:57 ronald-desktop mysqld: 161105 13:48:57 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ecom/wp_termmeta uses space ID: 3 at filepath: ./ecom/wp_termmeta.ibd. Cannot open tablespace mysql/slave_relay_log_info which uses space ID: 3 at filepath: ./mysql/slave_relay_log_info.ibd
Nov 5 13:48:57 ronald-desktop mysqld: 2016-11-05 13:48:57 7fd14ee21780 InnoDB: Operating system error number 2 in a file operation.
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: The error means the system cannot find the path specified.
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: If you are installing InnoDB, remember that you must create
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: directories yourself, InnoDB does not create them.
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: Error: could not open single-table tablespace file ./mysql/slave_relay_log_info.ibd
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: We do not continue the crash recovery, because the table may become
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: To fix the problem and start mysqld:
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: 1) If there is a permission problem in the file and mysqld cannot
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: open the file, you should modify the permissions.
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: 2) If the table is not needed, or you can restore it from a backup,
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: crash recovery and ignore that table.
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: 3) If the file system or the disk is broken, and you cannot remove
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
Nov 5 13:48:57 ronald-desktop mysqld: InnoDB: and force InnoDB to continue crash recovery here.
Nov 5 13:48:57 ronald-desktop mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended
Nov 5 13:49:28 ronald-desktop /etc/init.d/mysql[2253]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Nov 5 13:49:28 ronald-desktop /etc/init.d/mysql[2253]: #007/usr/bin/mysqladmin: connect to server at 'localhost' failed
Nov 5 13:49:28 ronald-desktop /etc/init.d/mysql[2253]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2 "No such file or directory")'
Nov 5 13:49:28 ronald-desktop /etc/init.d/mysql[2253]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Nov 5 13:49:28 ronald-desktop /etc/init.d/mysql[2253]:
Nov 5 13:49:28 ronald-desktop mysql[1718]: ...fail!
Nov 5 13:49:28 ronald-desktop systemd[1]: mysql.service: Control process exited, code=exited status=1
Nov 5 13:49:28 ronald-desktop systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
Nov 5 13:49:28 ronald-desktop systemd[1]: mysql.service: Unit entered failed state.
Nov 5 13:49:28 ronald-desktop systemd[1]: mysql.service: Failed with result 'exit-code'.
Nov 5 13:51:36 ronald-desktop systemd[1]: Starting LSB: Start and stop the mysql database server daemon...
Nov 5 13:51:36 ronald-desktop mysql[3498]: * Starting MariaDB database server mysqld
Nov 5 13:51:37 ronald-desktop mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] /usr/sbin/mysqld (mysqld 10.0.25-MariaDB-0ubuntu0.15.10.1) starting as process 3688 ...
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] InnoDB: Using mutexes to ref count buffer pool pages
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] InnoDB: The InnoDB memory heap is disabled
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] InnoDB: Memory barrier is not used
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] InnoDB: Compressed tables use zlib 1.2.8
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] InnoDB: Using Linux native AIO
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] InnoDB: Using CPU crc32 instructions
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] InnoDB: Initializing buffer pool, size = 128.0M
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] InnoDB: Completed initialization of buffer pool
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] InnoDB: Highest supported file format is Barracuda.
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] InnoDB: Log scan progressed past the checkpoint lsn 8242949749
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] InnoDB: Database was not shutdown normally!
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] InnoDB: Starting crash recovery.
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [Note] InnoDB: Reading tablespace information from the .ibd files...
Nov 5 13:51:37 ronald-desktop mysqld: 161105 13:51:37 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ecom/wp_termmeta uses space ID: 3 at filepath: ./ecom/wp_termmeta.ibd. Cannot open tablespace mysql/slave_relay_log_info which uses space ID: 3 at filepath: ./mysql/slave_relay_log_info.ibd
Nov 5 13:51:37 ronald-desktop mysqld: 2016-11-05 13:51:37 7fe25c17d780 InnoDB: Operating system error number 2 in a file operation.
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: The error means the system cannot find the path specified.
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: If you are installing InnoDB, remember that you must create
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: directories yourself, InnoDB does not create them.
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: Error: could not open single-table tablespace file ./mysql/slave_relay_log_info.ibd
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: We do not continue the crash recovery, because the table may become
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: To fix the problem and start mysqld:
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: 1) If there is a permission problem in the file and mysqld cannot
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: open the file, you should modify the permissions.
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: 2) If the table is not needed, or you can restore it from a backup,
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: crash recovery and ignore that table.
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: 3) If the file system or the disk is broken, and you cannot remove
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
Nov 5 13:51:37 ronald-desktop mysqld: InnoDB: and force InnoDB to continue crash recovery here.
Nov 5 13:51:37 ronald-desktop mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended
Nov 5 13:51:40 ronald-desktop kernel: [ 313.820432] [UFW BLOCK] IN=enp5s0 OUT= MAC=d0:50:99:29:b9:ab:24:65:11:df:48:0e:08:00 SRC=198.23.109.211 DST=192.168.178.20 LEN=59 TOS=0x00 PREC=0x00 TTL=46 ID=56579 DF PROTO=TCP SPT=8060 DPT=51020 WINDOW=12 RES=0x00 ACK PSH URGP=0
Nov 5 13:52:07 ronald-desktop /etc/init.d/mysql[3992]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Nov 5 13:52:07 ronald-desktop /etc/init.d/mysql[3992]: #007/usr/bin/mysqladmin: connect to server at 'localhost' failed
Nov 5 13:52:07 ronald-desktop /etc/init.d/mysql[3992]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2 "No such file or directory")'
Nov 5 13:52:07 ronald-desktop /etc/init.d/mysql[3992]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Nov 5 13:52:07 ronald-desktop /etc/init.d/mysql[3992]:
Nov 5 13:52:07 ronald-desktop mysql[3498]: ...fail!
Nov 5 13:52:07 ronald-desktop systemd[1]: mysql.service: Control process exited, code=exited status=1
Nov 5 13:52:07 ronald-desktop systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
Nov 5 13:52:07 ronald-desktop systemd[1]: mysql.service: Unit entered failed state.
Nov 5 13:52:07 ronald-desktop systemd[1]: mysql.service: Failed with result 'exit-code'.
Nov 5 13:53:01 ronald-desktop systemd[1]: Starting LSB: Start and stop the mysql database server daemon...
Nov 5 13:53:01 ronald-desktop mysql[4046]: * Starting MariaDB database server mysqld
Nov 5 13:53:01 ronald-desktop mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] /usr/sbin/mysqld (mysqld 10.0.25-MariaDB-0ubuntu0.15.10.1) starting as process 4236 ...
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: Using mutexes to ref count buffer pool pages
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: The InnoDB memory heap is disabled
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: Memory barrier is not used
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: Compressed tables use zlib 1.2.8
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: Using Linux native AIO
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: Using CPU crc32 instructions
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: Initializing buffer pool, size = 128.0M
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: Completed initialization of buffer pool
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: Highest supported file format is Barracuda.
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: Log scan progressed past the checkpoint lsn 8242949749
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: Database was not shutdown normally!
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: Starting crash recovery.
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: Reading tablespace information from the .ibd files...
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ecom/wp_termmeta uses space ID: 3 at filepath: ./ecom/wp_termmeta.ibd. Cannot open tablespace mysql/slave_relay_log_info which uses space ID: 3 at filepath: ./mysql/slave_relay_log_info.ibd
Nov 5 13:53:01 ronald-desktop mysqld: 2016-11-05 13:53:01 7f5eaa5ab780 InnoDB: Operating system error number 2 in a file operation.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: The error means the system cannot find the path specified.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: If you are installing InnoDB, remember that you must create
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: directories yourself, InnoDB does not create them.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: Error: could not open single-table tablespace file ./mysql/slave_relay_log_info.ibd
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: We do not continue the crash recovery, because the table may become
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: To fix the problem and start mysqld:
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 1) If there is a permission problem in the file and mysqld cannot
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: open the file, you should modify the permissions.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 2) If the table is not needed, or you can restore it from a backup,
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: crash recovery and ignore that table.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 3) If the file system or the disk is broken, and you cannot remove
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: and force InnoDB to continue crash recovery here.
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: innodb_force_recovery was set to 4. Continuing crash recovery even though we cannot access the .ibd file of this table.
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ecom/wp_terms uses space ID: 4 at filepath: ./ecom/wp_terms.ibd. Cannot open tablespace mysql/slave_master_info which uses space ID: 4 at filepath: ./mysql/slave_master_info.ibd
Nov 5 13:53:01 ronald-desktop mysqld: 2016-11-05 13:53:01 7f5eaa5ab780 InnoDB: Operating system error number 2 in a file operation.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: The error means the system cannot find the path specified.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: If you are installing InnoDB, remember that you must create
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: directories yourself, InnoDB does not create them.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: Error: could not open single-table tablespace file ./mysql/slave_master_info.ibd
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: We do not continue the crash recovery, because the table may become
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: To fix the problem and start mysqld:
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 1) If there is a permission problem in the file and mysqld cannot
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: open the file, you should modify the permissions.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 2) If the table is not needed, or you can restore it from a backup,
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: crash recovery and ignore that table.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 3) If the file system or the disk is broken, and you cannot remove
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: and force InnoDB to continue crash recovery here.
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: innodb_force_recovery was set to 4. Continuing crash recovery even though we cannot access the .ibd file of this table.
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ecom/wp_users uses space ID: 1 at filepath: ./ecom/wp_users.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: ./mysql/innodb_table_stats.ibd
Nov 5 13:53:01 ronald-desktop mysqld: 2016-11-05 13:53:01 7f5eaa5ab780 InnoDB: Operating system error number 2 in a file operation.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: The error means the system cannot find the path specified.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: If you are installing InnoDB, remember that you must create
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: directories yourself, InnoDB does not create them.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: Error: could not open single-table tablespace file ./mysql/innodb_table_stats.ibd
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: We do not continue the crash recovery, because the table may become
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: To fix the problem and start mysqld:
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 1) If there is a permission problem in the file and mysqld cannot
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: open the file, you should modify the permissions.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 2) If the table is not needed, or you can restore it from a backup,
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: crash recovery and ignore that table.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 3) If the file system or the disk is broken, and you cannot remove
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: and force InnoDB to continue crash recovery here.
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: innodb_force_recovery was set to 4. Continuing crash recovery even though we cannot access the .ibd file of this table.
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ecom/wp_usermeta uses space ID: 2 at filepath: ./ecom/wp_usermeta.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: ./mysql/innodb_index_stats.ibd
Nov 5 13:53:01 ronald-desktop mysqld: 2016-11-05 13:53:01 7f5eaa5ab780 InnoDB: Operating system error number 2 in a file operation.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: The error means the system cannot find the path specified.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: If you are installing InnoDB, remember that you must create
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: directories yourself, InnoDB does not create them.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: Error: could not open single-table tablespace file ./mysql/innodb_index_stats.ibd
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: We do not continue the crash recovery, because the table may become
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: To fix the problem and start mysqld:
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 1) If there is a permission problem in the file and mysqld cannot
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: open the file, you should modify the permissions.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 2) If the table is not needed, or you can restore it from a backup,
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: crash recovery and ignore that table.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 3) If the file system or the disk is broken, and you cannot remove
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: and force InnoDB to continue crash recovery here.
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: innodb_force_recovery was set to 4. Continuing crash recovery even though we cannot access the .ibd file of this table.
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ecom/wp_term_taxonomy uses space ID: 5 at filepath: ./ecom/wp_term_taxonomy.ibd. Cannot open tablespace mysql/slave_worker_info which uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd
Nov 5 13:53:01 ronald-desktop mysqld: 2016-11-05 13:53:01 7f5eaa5ab780 InnoDB: Operating system error number 2 in a file operation.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: The error means the system cannot find the path specified.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: If you are installing InnoDB, remember that you must create
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: directories yourself, InnoDB does not create them.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: Error: could not open single-table tablespace file ./mysql/slave_worker_info.ibd
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: We do not continue the crash recovery, because the table may become
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: To fix the problem and start mysqld:
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 1) If there is a permission problem in the file and mysqld cannot
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: open the file, you should modify the permissions.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 2) If the table is not needed, or you can restore it from a backup,
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: crash recovery and ignore that table.
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: 3) If the file system or the disk is broken, and you cannot remove
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: and force InnoDB to continue crash recovery here.
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: innodb_force_recovery was set to 4. Continuing crash recovery even though we cannot access the .ibd file of this table.
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: Restoring possible half-written data pages
Nov 5 13:53:01 ronald-desktop mysqld: 161105 13:53:01 [Note] InnoDB: from the doublewrite buffer...
Nov 5 13:53:01 ronald-desktop mysqld: InnoDB: Doing recovery: scanned up to log sequence number 8242949789
Nov 5 13:53:02 ronald-desktop mysqld: 161105 13:53:02 [Note] InnoDB: 128 rollback segment(s) are active.
Nov 5 13:53:02 ronald-desktop mysqld: 161105 13:53:02 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.29-76.2 started; log sequence number 8242949789
Nov 5 13:53:02 ronald-desktop mysqld: 161105 13:53:02 [Note] InnoDB: !!! innodb_force_recovery is set to 4 !!!
Nov 5 13:53:02 ronald-desktop mysqld: 161105 13:53:02 [Note] Plugin 'FEEDBACK' is disabled.
Nov 5 13:53:02 ronald-desktop mysqld: 161105 13:53:02 [ERROR] Plugin 'innodb' already installed
Nov 5 13:53:02 ronald-desktop mysqld: 161105 13:53:02 [ERROR] Plugin 'federated' already installed
Nov 5 13:53:02 ronald-desktop mysqld: 161105 13:53:02 [ERROR] Plugin 'blackhole' already installed
Nov 5 13:53:02 ronald-desktop mysqld: 161105 13:53:02 [ERROR] Plugin 'archive' already installed
Nov 5 13:53:02 ronald-desktop mysqld: 161105 13:53:02 [Note] Server socket created on IP: '127.0.0.1'.
Nov 5 13:53:02 ronald-desktop mysqld: 161105 13:53:02 [Note] /usr/sbin/mysqld: ready for connections.
Nov 5 13:53:02 ronald-desktop mysqld: Version: '10.0.25-MariaDB-0ubuntu0.15.10.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
Nov 5 13:53:02 ronald-desktop mysql[4046]: ...done.
Nov 5 13:53:02 ronald-desktop systemd[1]: Started LSB: Start and stop the mysql database server daemon.
Nov 5 13:53:02 ronald-desktop /etc/mysql/debian-start[4284]: Upgrading MySQL tables if necessary.
Nov 5 13:53:02 ronald-desktop /etc/mysql/debian-start[4287]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Nov 5 13:53:02 ronald-desktop /etc/mysql/debian-start[4287]: Looking for 'mysql' as: /usr/bin/mysql
Nov 5 13:53:02 ronald-desktop /etc/mysql/debian-start[4287]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Nov 5 13:53:02 ronald-desktop /etc/mysql/debian-start[4287]: Version check failed. Got the following error when calling the 'mysql' command line client
Nov 5 13:53:02 ronald-desktop /etc/mysql/debian-start[4287]: ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO)
Nov 5 13:53:02 ronald-desktop /etc/mysql/debian-start[4287]: FATAL ERROR: Upgrade failed
Nov 5 13:53:02 ronald-desktop /etc/mysql/debian-start[4296]: Checking for insecure root accounts.
Nov 5 13:53:02 ronald-desktop mysql[4046]: ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO)
Nov 5 13:53:18 ronald-desktop systemd[1]: Stopping LSB: Start and stop the mysql database server daemon...
Nov 5 13:53:18 ronald-desktop mysql[4331]: * Stopping MariaDB database server mysqld
Nov 5 13:53:19 ronald-desktop mysql[4331]: ...fail!
Nov 5 13:53:19 ronald-desktop systemd[1]: mysql.service: Control process exited, code=exited status=1
Nov 5 13:53:19 ronald-desktop systemd[1]: Stopped LSB: Start and stop the mysql database server daemon.
Nov 5 13:53:19 ronald-desktop systemd[1]: mysql.service: Unit entered failed state.
Nov 5 13:53:19 ronald-desktop systemd[1]: mysql.service: Failed with result 'exit-code'.
Subject
Views
Written By
Posted
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.