zMcuBwKm

12016-09-27 11:51:19 3789 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
22016-09-27 11:51:19 140736262751168 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
32016-09-27 11:51:19 140736262751168 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 3935 ...
42016-09-27 11:51:19 140736262751168 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
52016-09-27 11:51:19 140736262751168 [Note] InnoDB: Using mutexes to ref count buffer pool pages
62016-09-27 11:51:19 140736262751168 [Note] InnoDB: The InnoDB memory heap is disabled
72016-09-27 11:51:19 140736262751168 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
82016-09-27 11:51:19 140736262751168 [Note] InnoDB: Memory barrier is not used
92016-09-27 11:51:19 140736262751168 [Note] InnoDB: Compressed tables use zlib 1.2.8
102016-09-27 11:51:19 140736262751168 [Note] InnoDB: Using CPU crc32 instructions
112016-09-27 11:51:19 140736262751168 [Note] InnoDB: Initializing buffer pool, size = 16.0M
122016-09-27 11:51:19 140736262751168 [Note] InnoDB: Completed initialization of buffer pool
132016-09-27 11:51:19 140736262751168 [Note] InnoDB: Highest supported file format is Barracuda.
142016-09-27 11:51:19 140736262751168 [Note] InnoDB: The log sequence numbers 1823724 and 1823724 in ibdata files do not match the log sequence number 1867605 in the ib_logfiles!
152016-09-27 11:51:19 140736262751168 [Note] InnoDB: Database was not shutdown normally!
162016-09-27 11:51:19 140736262751168 [Note] InnoDB: Starting crash recovery.
172016-09-27 11:51:19 140736262751168 [Note] InnoDB: Reading tablespace information from the .ibd files...
182016-09-27 11:51:19 140736262751168 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace andreadb/andreadbtable uses space ID: 25 at filepath: ./andreadb/andreadbtable.ibd. Cannot open tablespace bitnami_wordpress/wp_termmeta which uses space ID: 25 at filepath: ./bitnami_wordpress/wp_termmeta.ibd
192016-09-27 11:51:19 7fffb6f2c3c0  InnoDB: Operating system error number 2 in a file operation.
20InnoDB: The error means the system cannot find the path specified.
21InnoDB: If you are installing InnoDB, remember that you must create
22InnoDB: directories yourself, InnoDB does not create them.
23InnoDB: Error: could not open single-table tablespace file ./bitnami_wordpress/wp_termmeta.ibd
24InnoDB: We do not continue the crash recovery, because the table may become
25InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
26InnoDB: To fix the problem and start mysqld:
27InnoDB: 1) If there is a permission problem in the file and mysqld cannot
28InnoDB: open the file, you should modify the permissions.
29InnoDB: 2) If the table is not needed, or you can restore it from a backup,
30InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
31InnoDB: crash recovery and ignore that table.
32InnoDB: 3) If the file system or the disk is broken, and you cannot remove
33InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
34InnoDB: and force InnoDB to continue crash recovery here.
352016-09-27 11:51:19 3789 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended
362016-09-27 11:54:48 4232 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
372016-09-27 11:54:49 140736262751168 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
382016-09-27 11:54:49 140736262751168 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 4376 ...
392016-09-27 11:54:49 140736262751168 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
402016-09-27 11:54:49 140736262751168 [Note] InnoDB: Using mutexes to ref count buffer pool pages
412016-09-27 11:54:49 140736262751168 [Note] InnoDB: The InnoDB memory heap is disabled
422016-09-27 11:54:49 140736262751168 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
432016-09-27 11:54:49 140736262751168 [Note] InnoDB: Memory barrier is not used
442016-09-27 11:54:49 140736262751168 [Note] InnoDB: Compressed tables use zlib 1.2.8
452016-09-27 11:54:49 140736262751168 [Note] InnoDB: Using CPU crc32 instructions
462016-09-27 11:54:49 140736262751168 [Note] InnoDB: Initializing buffer pool, size = 16.0M
472016-09-27 11:54:49 140736262751168 [Note] InnoDB: Completed initialization of buffer pool
482016-09-27 11:54:49 140736262751168 [Note] InnoDB: Highest supported file format is Barracuda.
492016-09-27 11:54:49 140736262751168 [Note] InnoDB: The log sequence numbers 1823724 and 1823724 in ibdata files do not match the log sequence number 1867605 in the ib_logfiles!
502016-09-27 11:54:49 140736262751168 [Note] InnoDB: Database was not shutdown normally!
512016-09-27 11:54:49 140736262751168 [Note] InnoDB: Starting crash recovery.
522016-09-27 11:54:49 140736262751168 [Note] InnoDB: Reading tablespace information from the .ibd files...
532016-09-27 11:54:49 140736262751168 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace andreadb/andreadbtable uses space ID: 25 at filepath: ./andreadb/andreadbtable.ibd. Cannot open tablespace bitnami_wordpress/wp_termmeta which uses space ID: 25 at filepath: ./bitnami_wordpress/wp_termmeta.ibd
542016-09-27 11:54:49 7fffb6f2c3c0  InnoDB: Operating system error number 2 in a file operation.
55InnoDB: The error means the system cannot find the path specified.
56InnoDB: If you are installing InnoDB, remember that you must create
57InnoDB: directories yourself, InnoDB does not create them.
58InnoDB: Error: could not open single-table tablespace file ./bitnami_wordpress/wp_termmeta.ibd
59InnoDB: We do not continue the crash recovery, because the table may become
60InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
61InnoDB: To fix the problem and start mysqld:
62InnoDB: 1) If there is a permission problem in the file and mysqld cannot
63InnoDB: open the file, you should modify the permissions.
64InnoDB: 2) If the table is not needed, or you can restore it from a backup,
65InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
66InnoDB: crash recovery and ignore that table.
67InnoDB: 3) If the file system or the disk is broken, and you cannot remove
68InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
69InnoDB: and force InnoDB to continue crash recovery here.
702016-09-27 11:54:49 4232 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended
712016-09-27 12:00:16 4859 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
722016-09-27 12:00:16 140736262751168 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
732016-09-27 12:00:16 140736262751168 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 5005 ...
742016-09-27 12:00:16 140736262751168 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
752016-09-27 12:00:17 140736262751168 [Note] InnoDB: Using mutexes to ref count buffer pool pages
762016-09-27 12:00:17 140736262751168 [Note] InnoDB: The InnoDB memory heap is disabled
772016-09-27 12:00:17 140736262751168 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
782016-09-27 12:00:17 140736262751168 [Note] InnoDB: Memory barrier is not used
792016-09-27 12:00:17 140736262751168 [Note] InnoDB: Compressed tables use zlib 1.2.8
802016-09-27 12:00:17 140736262751168 [Note] InnoDB: Using CPU crc32 instructions
812016-09-27 12:00:17 140736262751168 [Note] InnoDB: Initializing buffer pool, size = 16.0M
822016-09-27 12:00:17 140736262751168 [Note] InnoDB: Completed initialization of buffer pool
832016-09-27 12:00:17 140736262751168 [Note] InnoDB: Highest supported file format is Barracuda.
842016-09-27 12:00:17 140736262751168 [Note] InnoDB: The log sequence numbers 1823724 and 1823724 in ibdata files do not match the log sequence number 1867605 in the ib_logfiles!
852016-09-27 12:00:17 140736262751168 [Note] InnoDB: Database was not shutdown normally!
862016-09-27 12:00:17 140736262751168 [Note] InnoDB: Starting crash recovery.
872016-09-27 12:00:17 140736262751168 [Note] InnoDB: Reading tablespace information from the .ibd files...
882016-09-27 12:00:17 140736262751168 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace andreadb/andreadbtable uses space ID: 25 at filepath: ./andreadb/andreadbtable.ibd. Cannot open tablespace bitnami_wordpress/wp_termmeta which uses space ID: 25 at filepath: ./bitnami_wordpress/wp_termmeta.ibd
892016-09-27 12:00:17 7fffb6f2c3c0  InnoDB: Operating system error number 2 in a file operation.
90InnoDB: The error means the system cannot find the path specified.
91InnoDB: If you are installing InnoDB, remember that you must create
92InnoDB: directories yourself, InnoDB does not create them.
93InnoDB: Error: could not open single-table tablespace file ./bitnami_wordpress/wp_termmeta.ibd
94InnoDB: We do not continue the crash recovery, because the table may become
95InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
96InnoDB: To fix the problem and start mysqld:
97InnoDB: 1) If there is a permission problem in the file and mysqld cannot
98InnoDB: open the file, you should modify the permissions.
99InnoDB: 2) If the table is not needed, or you can restore it from a backup,
100InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
101InnoDB: crash recovery and ignore that table.
102InnoDB: 3) If the file system or the disk is broken, and you cannot remove
103InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
104InnoDB: and force InnoDB to continue crash recovery here.
1052016-09-27 12:00:17 4859 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended
1062016-09-27 12:07:58 18904 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
1072016-09-27 12:07:58 140736262751168 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
1082016-09-27 12:07:58 140736262751168 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 19048 ...
1092016-09-27 12:07:58 140736262751168 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
1102016-09-27 12:07:58 140736262751168 [Note] InnoDB: Using mutexes to ref count buffer pool pages
1112016-09-27 12:07:58 140736262751168 [Note] InnoDB: The InnoDB memory heap is disabled
1122016-09-27 12:07:58 140736262751168 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
1132016-09-27 12:07:58 140736262751168 [Note] InnoDB: Memory barrier is not used
1142016-09-27 12:07:58 140736262751168 [Note] InnoDB: Compressed tables use zlib 1.2.8
1152016-09-27 12:07:58 140736262751168 [Note] InnoDB: Using CPU crc32 instructions
1162016-09-27 12:07:58 140736262751168 [Note] InnoDB: Initializing buffer pool, size = 16.0M
1172016-09-27 12:07:58 140736262751168 [Note] InnoDB: Completed initialization of buffer pool
1182016-09-27 12:07:58 140736262751168 [Note] InnoDB: Highest supported file format is Barracuda.
1192016-09-27 12:07:58 140736262751168 [Note] InnoDB: The log sequence numbers 1823724 and 1823724 in ibdata files do not match the log sequence number 1867605 in the ib_logfiles!
1202016-09-27 12:07:58 140736262751168 [Note] InnoDB: Database was not shutdown normally!
1212016-09-27 12:07:58 140736262751168 [Note] InnoDB: Starting crash recovery.
1222016-09-27 12:07:58 140736262751168 [Note] InnoDB: Reading tablespace information from the .ibd files...
1232016-09-27 12:07:58 140736262751168 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace andreadb/andreadbtable uses space ID: 25 at filepath: ./andreadb/andreadbtable.ibd. Cannot open tablespace bitnami_wordpress/wp_termmeta which uses space ID: 25 at filepath: ./bitnami_wordpress/wp_termmeta.ibd
1242016-09-27 12:07:58 7fffb6f2c3c0  InnoDB: Operating system error number 2 in a file operation.
125InnoDB: The error means the system cannot find the path specified.
126InnoDB: If you are installing InnoDB, remember that you must create
127InnoDB: directories yourself, InnoDB does not create them.
128InnoDB: Error: could not open single-table tablespace file ./bitnami_wordpress/wp_termmeta.ibd
129InnoDB: We do not continue the crash recovery, because the table may become
130InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
131InnoDB: To fix the problem and start mysqld:
132InnoDB: 1) If there is a permission problem in the file and mysqld cannot
133InnoDB: open the file, you should modify the permissions.
134InnoDB: 2) If the table is not needed, or you can restore it from a backup,
135InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
136InnoDB: crash recovery and ignore that table.
137InnoDB: 3) If the file system or the disk is broken, and you cannot remove
138InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
139InnoDB: and force InnoDB to continue crash recovery here.
1402016-09-27 12:07:58 18904 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended
1412016-09-27 12:08:53 19207 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
1422016-09-27 12:08:53 140736262751168 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
1432016-09-27 12:08:53 140736262751168 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 19351 ...
1442016-09-27 12:08:53 140736262751168 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
1452016-09-27 12:08:53 140736262751168 [Note] InnoDB: Using mutexes to ref count buffer pool pages
1462016-09-27 12:08:53 140736262751168 [Note] InnoDB: The InnoDB memory heap is disabled
1472016-09-27 12:08:53 140736262751168 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
1482016-09-27 12:08:53 140736262751168 [Note] InnoDB: Memory barrier is not used
1492016-09-27 12:08:53 140736262751168 [Note] InnoDB: Compressed tables use zlib 1.2.8
1502016-09-27 12:08:53 140736262751168 [Note] InnoDB: Using CPU crc32 instructions
1512016-09-27 12:08:53 140736262751168 [Note] InnoDB: Initializing buffer pool, size = 16.0M
1522016-09-27 12:08:53 140736262751168 [Note] InnoDB: Completed initialization of buffer pool
1532016-09-27 12:08:53 140736262751168 [Note] InnoDB: Highest supported file format is Barracuda.
1542016-09-27 12:08:53 140736262751168 [Note] InnoDB: The log sequence numbers 1823724 and 1823724 in ibdata files do not match the log sequence number 1867605 in the ib_logfiles!
1552016-09-27 12:08:53 140736262751168 [Note] InnoDB: Database was not shutdown normally!
1562016-09-27 12:08:53 140736262751168 [Note] InnoDB: Starting crash recovery.
1572016-09-27 12:08:53 140736262751168 [Note] InnoDB: Reading tablespace information from the .ibd files...
1582016-09-27 12:08:53 140736262751168 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace andreadb/andreadbtable uses space ID: 25 at filepath: ./andreadb/andreadbtable.ibd. Cannot open tablespace bitnami_wordpress/wp_termmeta which uses space ID: 25 at filepath: ./bitnami_wordpress/wp_termmeta.ibd
1592016-09-27 12:08:53 7fffb6f2c3c0  InnoDB: Operating system error number 2 in a file operation.
160InnoDB: The error means the system cannot find the path specified.
161InnoDB: If you are installing InnoDB, remember that you must create
162InnoDB: directories yourself, InnoDB does not create them.
163InnoDB: Error: could not open single-table tablespace file ./bitnami_wordpress/wp_termmeta.ibd
164InnoDB: We do not continue the crash recovery, because the table may become
165InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
166InnoDB: To fix the problem and start mysqld:
167InnoDB: 1) If there is a permission problem in the file and mysqld cannot
168InnoDB: open the file, you should modify the permissions.
169InnoDB: 2) If the table is not needed, or you can restore it from a backup,
170InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
171InnoDB: crash recovery and ignore that table.
172InnoDB: 3) If the file system or the disk is broken, and you cannot remove
173InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
174InnoDB: and force InnoDB to continue crash recovery here.
1752016-09-27 12:08:53 19207 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended
1762016-09-27 12:10:49 563 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
1772016-09-27 12:10:49 140736843703232 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
1782016-09-27 12:10:49 140736843703232 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 707 ...
1792016-09-27 12:10:49 140736843703232 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
1802016-09-27 12:10:50 140736843703232 [Note] InnoDB: Using mutexes to ref count buffer pool pages
1812016-09-27 12:10:50 140736843703232 [Note] InnoDB: The InnoDB memory heap is disabled
1822016-09-27 12:10:50 140736843703232 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
1832016-09-27 12:10:50 140736843703232 [Note] InnoDB: Memory barrier is not used
1842016-09-27 12:10:50 140736843703232 [Note] InnoDB: Compressed tables use zlib 1.2.8
1852016-09-27 12:10:50 140736843703232 [Note] InnoDB: Using CPU crc32 instructions
1862016-09-27 12:10:50 140736843703232 [Note] InnoDB: Initializing buffer pool, size = 16.0M
1872016-09-27 12:10:50 140736843703232 [Note] InnoDB: Completed initialization of buffer pool
1882016-09-27 12:10:50 140736843703232 [Note] InnoDB: Highest supported file format is Barracuda.
1892016-09-27 12:10:50 140736843703232 [Note] InnoDB: The log sequence numbers 1823724 and 1823724 in ibdata files do not match the log sequence number 1867605 in the ib_logfiles!
1902016-09-27 12:10:50 140736843703232 [Note] InnoDB: Database was not shutdown normally!
1912016-09-27 12:10:50 140736843703232 [Note] InnoDB: Starting crash recovery.
1922016-09-27 12:10:50 140736843703232 [Note] InnoDB: Reading tablespace information from the .ibd files...
1932016-09-27 12:10:50 140736843703232 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace andreadb/andreadbtable uses space ID: 25 at filepath: ./andreadb/andreadbtable.ibd. Cannot open tablespace bitnami_wordpress/wp_termmeta which uses space ID: 25 at filepath: ./bitnami_wordpress/wp_termmeta.ibd
1942016-09-27 12:10:50 7fffd99363c0  InnoDB: Operating system error number 2 in a file operation.
195InnoDB: The error means the system cannot find the path specified.
196InnoDB: If you are installing InnoDB, remember that you must create
197InnoDB: directories yourself, InnoDB does not create them.
198InnoDB: Error: could not open single-table tablespace file ./bitnami_wordpress/wp_termmeta.ibd
199InnoDB: We do not continue the crash recovery, because the table may become
200InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
201InnoDB: To fix the problem and start mysqld:
202InnoDB: 1) If there is a permission problem in the file and mysqld cannot
203InnoDB: open the file, you should modify the permissions.
204InnoDB: 2) If the table is not needed, or you can restore it from a backup,
205InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
206InnoDB: crash recovery and ignore that table.
207InnoDB: 3) If the file system or the disk is broken, and you cannot remove
208InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
209InnoDB: and force InnoDB to continue crash recovery here.
2102016-09-27 12:10:50 563 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended
2112016-09-27 12:22:02 5016 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
2122016-09-27 12:22:02 140736843703232 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
2132016-09-27 12:22:02 140736843703232 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 5160 ...
2142016-09-27 12:22:02 140736843703232 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
2152016-09-27 12:22:02 140736843703232 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2162016-09-27 12:22:02 140736843703232 [Note] InnoDB: The InnoDB memory heap is disabled
2172016-09-27 12:22:02 140736843703232 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2182016-09-27 12:22:02 140736843703232 [Note] InnoDB: Memory barrier is not used
2192016-09-27 12:22:02 140736843703232 [Note] InnoDB: Compressed tables use zlib 1.2.8
2202016-09-27 12:22:02 140736843703232 [Note] InnoDB: Using CPU crc32 instructions
2212016-09-27 12:22:02 140736843703232 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2222016-09-27 12:22:02 140736843703232 [Note] InnoDB: Completed initialization of buffer pool
2232016-09-27 12:22:02 140736843703232 [Note] InnoDB: Highest supported file format is Barracuda.
2242016-09-27 12:22:02 140736843703232 [Note] InnoDB: 128 rollback segment(s) are active.
2252016-09-27 12:22:02 140736843703232 [Note] InnoDB: Waiting for purge to start
2262016-09-27 12:22:02 140736843703232 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 1762733
2272016-09-27 12:22:02 123145333121024 [Note] InnoDB: Dumping buffer pool(s) not yet started
2282016-09-27 12:22:02 140736843703232 [Note] Plugin 'FEEDBACK' is disabled.
2292016-09-27 12:22:02 140736843703232 [Note] Recovering after a crash using tc.log
2302016-09-27 12:22:02 140736843703232 [Note] Starting crash recovery...
2312016-09-27 12:22:02 140736843703232 [Note] Crash recovery finished.
2322016-09-27 12:22:02 140736843703232 [Note] Server socket created on IP: '::'.
2332016-09-27 12:22:02 140736843703232 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld: ready for connections.
234Version: '10.1.9-MariaDB'  socket: '/Applications/XAMPP/xamppfiles/var/mysql/mysql.sock'  port: 3306  Source distribution
2352016-09-27 12:39:33 123145335664640 [Warning] InnoDB: Cannot open table loginapp/users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2362016-09-27 12:39:33 123145335664640 [Warning] InnoDB: Cannot open table loginapp/users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2372016-09-27 12:39:33 123145335664640 [Warning] InnoDB: Cannot open table loginapp/users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2382016-09-27 12:39:35 123145335664640 [Warning] InnoDB: Cannot open table loginapp/users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2392016-09-27 13:07:40 123145335664640 [Warning] InnoDB: Cannot open table loginapp/users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2402016-09-27 13:07:40 123145335664640 [Warning] InnoDB: Cannot open table loginapp/users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2412016-09-27 13:07:40 123145335664640 [Warning] InnoDB: Cannot open table loginapp/users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2422016-09-27 13:07:42 123145335664640 [Warning] InnoDB: Cannot open table loginapp/users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2432016-09-27 15:30:43 123145335664640 [Note] InnoDB: Online DDL : Start
2442016-09-27 15:30:43 123145335664640 [Note] InnoDB: Online DDL : Start reading clustered index of the table and create temporary files
2452016-09-27 15:30:43 123145335664640 [Note] InnoDB: Online DDL : End of reading clustered index of the table and create temporary files
2462016-09-27 15:30:43 123145335664640 [Note] InnoDB: Online DDL : Completed
2472016-09-27 17:24:26 123145335353344 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld: Normal shutdown
248
2492016-09-27 17:24:26 123145335353344 [Note] Event Scheduler: Purging the queue. 0 events
2502016-09-27 17:24:26 123145334194176 [Note] InnoDB: FTS optimize thread exiting.
2512016-09-27 17:24:26 123145335353344 [Note] InnoDB: Starting shutdown...
2522016-09-27 17:24:27 123145335353344 [Note] InnoDB: Shutdown completed; log sequence number 1862198
2532016-09-27 17:24:27 123145335353344 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld: Shutdown complete
254
2552016-09-27 17:24:27 5016 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended
2562016-09-29 15:00:50 1123 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
2572016-09-29 15:00:50 140736850977728 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
2582016-09-29 15:00:50 140736850977728 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 1267 ...
2592016-09-29 15:00:50 140736850977728 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
2602016-09-29 15:00:50 140736850977728 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2612016-09-29 15:00:50 140736850977728 [Note] InnoDB: The InnoDB memory heap is disabled
2622016-09-29 15:00:50 140736850977728 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2632016-09-29 15:00:50 140736850977728 [Note] InnoDB: Memory barrier is not used
2642016-09-29 15:00:50 140736850977728 [Note] InnoDB: Compressed tables use zlib 1.2.8
2652016-09-29 15:00:50 140736850977728 [Note] InnoDB: Using CPU crc32 instructions
2662016-09-29 15:00:50 140736850977728 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2672016-09-29 15:00:50 140736850977728 [Note] InnoDB: Completed initialization of buffer pool
2682016-09-29 15:00:50 140736850977728 [Note] InnoDB: Highest supported file format is Barracuda.
2692016-09-29 15:00:50 140736850977728 [Note] InnoDB: 128 rollback segment(s) are active.
2702016-09-29 15:00:50 140736850977728 [Note] InnoDB: Waiting for purge to start
2712016-09-29 15:00:50 140736850977728 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 1862198
2722016-09-29 15:00:50 123145350209536 [Note] InnoDB: Dumping buffer pool(s) not yet started
2732016-09-29 15:00:50 140736850977728 [Note] Plugin 'FEEDBACK' is disabled.
2742016-09-29 15:00:50 140736850977728 [Note] Server socket created on IP: '::'.
2752016-09-29 15:00:50 140736850977728 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld: ready for connections.
276Version: '10.1.9-MariaDB'  socket: '/Applications/XAMPP/xamppfiles/var/mysql/mysql.sock'  port: 3306  Source distribution
2772016-09-29 17:22:20 123145352753152 [Warning] InnoDB: Cannot open table loginapp/users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2782016-09-29 17:22:38 123145352753152 [Warning] InnoDB: Cannot open table loginapp/users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2792016-09-29 17:22:42 123145352753152 [Warning] InnoDB: Cannot open table loginapp/users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2802016-09-29 17:22:49 123145352753152 [Warning] InnoDB: Cannot open table loginapp/users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2812016-09-29 17:23:03 123145352753152 [Warning] InnoDB: Cannot open table loginapp/users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2822016-09-29 17:23:07 123145352753152 [Warning] InnoDB: Cannot open table loginapp/users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2832016-10-01  2:00:15 123145352441856 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld: Normal shutdown
284
2852016-10-01  2:00:15 123145352441856 [Note] Event Scheduler: Purging the queue. 0 events
2862016-10-01  2:00:15 123145351282688 [Note] InnoDB: FTS optimize thread exiting.
2872016-10-01  2:00:15 123145352441856 [Note] InnoDB: Starting shutdown...
2882016-10-01  2:00:17 123145352441856 [Note] InnoDB: Shutdown completed; log sequence number 1927913
2892016-10-01  2:00:17 123145352441856 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld: Shutdown complete
290
2912016-10-01 11:12:39 1091 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
2922016-10-01 11:12:39 140736308630464 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
2932016-10-01 11:12:39 140736308630464 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 1235 ...
2942016-10-01 11:12:39 140736308630464 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
2952016-10-01 11:12:39 140736308630464 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2962016-10-01 11:12:39 140736308630464 [Note] InnoDB: The InnoDB memory heap is disabled
2972016-10-01 11:12:39 140736308630464 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2982016-10-01 11:12:39 140736308630464 [Note] InnoDB: Memory barrier is not used
2992016-10-01 11:12:39 140736308630464 [Note] InnoDB: Compressed tables use zlib 1.2.8
3002016-10-01 11:12:39 140736308630464 [Note] InnoDB: Using CPU crc32 instructions
3012016-10-01 11:12:39 140736308630464 [Note] InnoDB: Initializing buffer pool, size = 16.0M
3022016-10-01 11:12:39 140736308630464 [Note] InnoDB: Completed initialization of buffer pool
3032016-10-01 11:12:39 140736308630464 [Note] InnoDB: Highest supported file format is Barracuda.
3042016-10-01 11:12:39 140736308630464 [Note] InnoDB: 128 rollback segment(s) are active.
3052016-10-01 11:12:39 140736308630464 [Note] InnoDB: Waiting for purge to start
3062016-10-01 11:12:39 140736308630464 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 1927913
3072016-10-01 11:12:39 123145336332288 [Note] InnoDB: Dumping buffer pool(s) not yet started
3082016-10-01 11:12:39 140736308630464 [Note] Plugin 'FEEDBACK' is disabled.
3092016-10-01 11:12:39 140736308630464 [Note] Server socket created on IP: '::'.
3102016-10-01 11:12:39 140736308630464 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld: ready for connections.
311Version: '10.1.9-MariaDB'  socket: '/Applications/XAMPP/xamppfiles/var/mysql/mysql.sock'  port: 3306  Source distribution
3122016-10-01 17:26:50 123145338564608 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld: Normal shutdown
313
3142016-10-03 17:23:36 1158 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
3152016-10-03 17:23:36 140736620217280 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
3162016-10-03 17:23:36 140736620217280 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 1303 ...
3172016-10-03 17:23:36 140736620217280 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
3182016-10-03 17:23:36 140736620217280 [Note] InnoDB: Using mutexes to ref count buffer pool pages
3192016-10-03 17:23:36 140736620217280 [Note] InnoDB: The InnoDB memory heap is disabled
3202016-10-03 17:23:36 140736620217280 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
3212016-10-03 17:23:36 140736620217280 [Note] InnoDB: Memory barrier is not used
3222016-10-03 17:23:36 140736620217280 [Note] InnoDB: Compressed tables use zlib 1.2.8
3232016-10-03 17:23:36 140736620217280 [Note] InnoDB: Using CPU crc32 instructions
3242016-10-03 17:23:36 140736620217280 [Note] InnoDB: Initializing buffer pool, size = 16.0M
3252016-10-03 17:23:36 140736620217280 [Note] InnoDB: Completed initialization of buffer pool
3262016-10-03 17:23:36 140736620217280 [Note] InnoDB: Highest supported file format is Barracuda.
3272016-10-03 17:23:36 140736620217280 [Note] InnoDB: The log sequence numbers 1927913 and 1927913 in ibdata files do not match the log sequence number 1960205 in the ib_logfiles!
3282016-10-03 17:23:36 140736620217280 [Note] InnoDB: Database was not shutdown normally!
3292016-10-03 17:23:36 140736620217280 [Note] InnoDB: Starting crash recovery.
3302016-10-03 17:23:36 140736620217280 [Note] InnoDB: Reading tablespace information from the .ibd files...
3312016-10-03 17:23:36 140736620217280 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace andreadb/andreadbtable uses space ID: 25 at filepath: ./andreadb/andreadbtable.ibd. Cannot open tablespace bitnami_wordpress/wp_termmeta which uses space ID: 25 at filepath: ./bitnami_wordpress/wp_termmeta.ibd
3322016-10-03 17:23:36 7fffcc4143c0  InnoDB: Operating system error number 2 in a file operation.
333InnoDB: The error means the system cannot find the path specified.
334InnoDB: If you are installing InnoDB, remember that you must create
335InnoDB: directories yourself, InnoDB does not create them.
336InnoDB: Error: could not open single-table tablespace file ./bitnami_wordpress/wp_termmeta.ibd
337InnoDB: We do not continue the crash recovery, because the table may become
338InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
339InnoDB: To fix the problem and start mysqld:
340InnoDB: 1) If there is a permission problem in the file and mysqld cannot
341InnoDB: open the file, you should modify the permissions.
342InnoDB: 2) If the table is not needed, or you can restore it from a backup,
343InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
344InnoDB: crash recovery and ignore that table.
345InnoDB: 3) If the file system or the disk is broken, and you cannot remove
346InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
347InnoDB: and force InnoDB to continue crash recovery here.
3482016-10-03 17:23:36 1158 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended
3492016-10-03 17:25:02 1598 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
3502016-10-03 17:25:02 140736620217280 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
3512016-10-03 17:25:02 140736620217280 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 1742 ...
3522016-10-03 17:25:02 140736620217280 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
3532016-10-03 17:25:02 140736620217280 [Note] InnoDB: Using mutexes to ref count buffer pool pages
3542016-10-03 17:25:02 140736620217280 [Note] InnoDB: The InnoDB memory heap is disabled
3552016-10-03 17:25:02 140736620217280 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
3562016-10-03 17:25:02 140736620217280 [Note] InnoDB: Memory barrier is not used
3572016-10-03 17:25:02 140736620217280 [Note] InnoDB: Compressed tables use zlib 1.2.8
3582016-10-03 17:25:02 140736620217280 [Note] InnoDB: Using CPU crc32 instructions
3592016-10-03 17:25:02 140736620217280 [Note] InnoDB: Initializing buffer pool, size = 16.0M
3602016-10-03 17:25:02 140736620217280 [Note] InnoDB: Completed initialization of buffer pool
3612016-10-03 17:25:02 140736620217280 [Note] InnoDB: Highest supported file format is Barracuda.
3622016-10-03 17:25:02 140736620217280 [Note] InnoDB: The log sequence numbers 1927913 and 1927913 in ibdata files do not match the log sequence number 1960205 in the ib_logfiles!
3632016-10-03 17:25:02 140736620217280 [Note] InnoDB: Database was not shutdown normally!
3642016-10-03 17:25:02 140736620217280 [Note] InnoDB: Starting crash recovery.
3652016-10-03 17:25:02 140736620217280 [Note] InnoDB: Reading tablespace information from the .ibd files...
3662016-10-03 17:25:02 140736620217280 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace andreadb/andreadbtable uses space ID: 25 at filepath: ./andreadb/andreadbtable.ibd. Cannot open tablespace bitnami_wordpress/wp_termmeta which uses space ID: 25 at filepath: ./bitnami_wordpress/wp_termmeta.ibd
3672016-10-03 17:25:02 7fffcc4143c0  InnoDB: Operating system error number 2 in a file operation.
368InnoDB: The error means the system cannot find the path specified.
369InnoDB: If you are installing InnoDB, remember that you must create
370InnoDB: directories yourself, InnoDB does not create them.
371InnoDB: Error: could not open single-table tablespace file ./bitnami_wordpress/wp_termmeta.ibd
372InnoDB: We do not continue the crash recovery, because the table may become
373InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
374InnoDB: To fix the problem and start mysqld:
375InnoDB: 1) If there is a permission problem in the file and mysqld cannot
376InnoDB: open the file, you should modify the permissions.
377InnoDB: 2) If the table is not needed, or you can restore it from a backup,
378InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
379InnoDB: crash recovery and ignore that table.
380InnoDB: 3) If the file system or the disk is broken, and you cannot remove
381InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
382InnoDB: and force InnoDB to continue crash recovery here.
3832016-10-03 17:25:02 1598 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended
3842016-10-03 17:28:42 2073 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
3852016-10-03 17:28:42 140736620217280 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
3862016-10-03 17:28:42 140736620217280 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 2217 ...
3872016-10-03 17:28:42 140736620217280 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
3882016-10-03 17:28:42 140736620217280 [Note] InnoDB: Using mutexes to ref count buffer pool pages
3892016-10-03 17:28:42 140736620217280 [Note] InnoDB: The InnoDB memory heap is disabled
3902016-10-03 17:28:42 140736620217280 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
3912016-10-03 17:28:42 140736620217280 [Note] InnoDB: Memory barrier is not used
3922016-10-03 17:28:42 140736620217280 [Note] InnoDB: Compressed tables use zlib 1.2.8
3932016-10-03 17:28:42 140736620217280 [Note] InnoDB: Using CPU crc32 instructions
3942016-10-03 17:28:42 140736620217280 [Note] InnoDB: Initializing buffer pool, size = 16.0M
3952016-10-03 17:28:42 140736620217280 [Note] InnoDB: Completed initialization of buffer pool
3962016-10-03 17:28:42 140736620217280 [Note] InnoDB: Highest supported file format is Barracuda.
3972016-10-03 17:28:42 140736620217280 [Note] InnoDB: The log sequence numbers 1927913 and 1927913 in ibdata files do not match the log sequence number 1960205 in the ib_logfiles!
3982016-10-03 17:28:42 140736620217280 [Note] InnoDB: Database was not shutdown normally!
3992016-10-03 17:28:42 140736620217280 [Note] InnoDB: Starting crash recovery.
4002016-10-03 17:28:42 140736620217280 [Note] InnoDB: Reading tablespace information from the .ibd files...
4012016-10-03 17:28:42 140736620217280 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace andreadb/andreadbtable uses space ID: 25 at filepath: ./andreadb/andreadbtable.ibd. Cannot open tablespace bitnami_wordpress/wp_termmeta which uses space ID: 25 at filepath: ./bitnami_wordpress/wp_termmeta.ibd
4022016-10-03 17:28:42 7fffcc4143c0  InnoDB: Operating system error number 2 in a file operation.
403InnoDB: The error means the system cannot find the path specified.
404InnoDB: If you are installing InnoDB, remember that you must create
405InnoDB: directories yourself, InnoDB does not create them.
406InnoDB: Error: could not open single-table tablespace file ./bitnami_wordpress/wp_termmeta.ibd
407InnoDB: We do not continue the crash recovery, because the table may become
408InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
409InnoDB: To fix the problem and start mysqld:
410InnoDB: 1) If there is a permission problem in the file and mysqld cannot
411InnoDB: open the file, you should modify the permissions.
412InnoDB: 2) If the table is not needed, or you can restore it from a backup,
413InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
414InnoDB: crash recovery and ignore that table.
415InnoDB: 3) If the file system or the disk is broken, and you cannot remove
416InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
417InnoDB: and force InnoDB to continue crash recovery here.
4182016-10-03 17:28:42 2073 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended
4192016-10-03 17:29:20 2311 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
4202016-10-03 17:29:20 140736620217280 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
4212016-10-03 17:29:20 140736620217280 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 2452 ...
4222016-10-03 17:29:20 140736620217280 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
4232016-10-03 17:29:20 140736620217280 [Note] InnoDB: Using mutexes to ref count buffer pool pages
4242016-10-03 17:29:20 140736620217280 [Note] InnoDB: The InnoDB memory heap is disabled
4252016-10-03 17:29:20 140736620217280 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
4262016-10-03 17:29:20 140736620217280 [Note] InnoDB: Memory barrier is not used
4272016-10-03 17:29:20 140736620217280 [Note] InnoDB: Compressed tables use zlib 1.2.8
4282016-10-03 17:29:20 140736620217280 [Note] InnoDB: Using CPU crc32 instructions
4292016-10-03 17:29:20 140736620217280 [Note] InnoDB: Initializing buffer pool, size = 16.0M
4302016-10-03 17:29:20 140736620217280 [Note] InnoDB: Completed initialization of buffer pool
4312016-10-03 17:29:20 140736620217280 [Note] InnoDB: Highest supported file format is Barracuda.
4322016-10-03 17:29:20 140736620217280 [Note] InnoDB: The log sequence numbers 1927913 and 1927913 in ibdata files do not match the log sequence number 1960205 in the ib_logfiles!
4332016-10-03 17:29:20 140736620217280 [Note] InnoDB: Database was not shutdown normally!
4342016-10-03 17:29:20 140736620217280 [Note] InnoDB: Starting crash recovery.
4352016-10-03 17:29:20 140736620217280 [Note] InnoDB: Reading tablespace information from the .ibd files...
4362016-10-03 17:29:20 140736620217280 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace andreadb/andreadbtable uses space ID: 25 at filepath: ./andreadb/andreadbtable.ibd. Cannot open tablespace bitnami_wordpress/wp_termmeta which uses space ID: 25 at filepath: ./bitnami_wordpress/wp_termmeta.ibd
4372016-10-03 17:29:20 7fffcc4143c0  InnoDB: Operating system error number 2 in a file operation.
438InnoDB: The error means the system cannot find the path specified.
439InnoDB: If you are installing InnoDB, remember that you must create
440InnoDB: directories yourself, InnoDB does not create them.
441InnoDB: Error: could not open single-table tablespace file ./bitnami_wordpress/wp_termmeta.ibd
442InnoDB: We do not continue the crash recovery, because the table may become
443InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
444InnoDB: To fix the problem and start mysqld:
445InnoDB: 1) If there is a permission problem in the file and mysqld cannot
446InnoDB: open the file, you should modify the permissions.
447InnoDB: 2) If the table is not needed, or you can restore it from a backup,
448InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
449InnoDB: crash recovery and ignore that table.
450InnoDB: 3) If the file system or the disk is broken, and you cannot remove
451InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
452InnoDB: and force InnoDB to continue crash recovery here.
4532016-10-03 17:29:20 2311 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended
4542016-10-03 17:30:17 2616 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
4552016-10-03 17:30:18 140736620217280 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
4562016-10-03 17:30:18 140736620217280 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 2757 ...
4572016-10-03 17:30:18 140736620217280 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
4582016-10-03 17:30:18 140736620217280 [Note] InnoDB: Using mutexes to ref count buffer pool pages
4592016-10-03 17:30:18 140736620217280 [Note] InnoDB: The InnoDB memory heap is disabled
4602016-10-03 17:30:18 140736620217280 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
4612016-10-03 17:30:18 140736620217280 [Note] InnoDB: Memory barrier is not used
4622016-10-03 17:30:18 140736620217280 [Note] InnoDB: Compressed tables use zlib 1.2.8
4632016-10-03 17:30:18 140736620217280 [Note] InnoDB: Using CPU crc32 instructions
4642016-10-03 17:30:18 140736620217280 [Note] InnoDB: Initializing buffer pool, size = 16.0M
4652016-10-03 17:30:18 140736620217280 [Note] InnoDB: Completed initialization of buffer pool
4662016-10-03 17:30:18 140736620217280 [Note] InnoDB: Highest supported file format is Barracuda.
4672016-10-03 17:30:18 140736620217280 [Note] InnoDB: The log sequence numbers 1927913 and 1927913 in ibdata files do not match the log sequence number 1960205 in the ib_logfiles!
4682016-10-03 17:30:18 140736620217280 [Note] InnoDB: Database was not shutdown normally!
4692016-10-03 17:30:18 140736620217280 [Note] InnoDB: Starting crash recovery.
4702016-10-03 17:30:18 140736620217280 [Note] InnoDB: Reading tablespace information from the .ibd files...
4712016-10-03 17:30:18 140736620217280 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace andreadb/andreadbtable uses space ID: 25 at filepath: ./andreadb/andreadbtable.ibd. Cannot open tablespace bitnami_wordpress/wp_termmeta which uses space ID: 25 at filepath: ./bitnami_wordpress/wp_termmeta.ibd
4722016-10-03 17:30:18 7fffcc4143c0  InnoDB: Operating system error number 2 in a file operation.
473InnoDB: The error means the system cannot find the path specified.
474InnoDB: If you are installing InnoDB, remember that you must create
475InnoDB: directories yourself, InnoDB does not create them.
476InnoDB: Error: could not open single-table tablespace file ./bitnami_wordpress/wp_termmeta.ibd
477InnoDB: We do not continue the crash recovery, because the table may become
478InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
479InnoDB: To fix the problem and start mysqld:
480InnoDB: 1) If there is a permission problem in the file and mysqld cannot
481InnoDB: open the file, you should modify the permissions.
482InnoDB: 2) If the table is not needed, or you can restore it from a backup,
483InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
484InnoDB: crash recovery and ignore that table.
485InnoDB: 3) If the file system or the disk is broken, and you cannot remove
486InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
487InnoDB: and force InnoDB to continue crash recovery here.
4882016-10-03 17:30:18 2616 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended
4892016-10-03 17:30:52 2890 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
4902016-10-03 17:30:52 140736620217280 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
4912016-10-03 17:30:52 140736620217280 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 3031 ...
4922016-10-03 17:30:52 140736620217280 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
4932016-10-03 17:30:52 140736620217280 [Note] InnoDB: Using mutexes to ref count buffer pool pages
4942016-10-03 17:30:52 140736620217280 [Note] InnoDB: The InnoDB memory heap is disabled
4952016-10-03 17:30:52 140736620217280 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
4962016-10-03 17:30:52 140736620217280 [Note] InnoDB: Memory barrier is not used
4972016-10-03 17:30:52 140736620217280 [Note] InnoDB: Compressed tables use zlib 1.2.8
4982016-10-03 17:30:52 140736620217280 [Note] InnoDB: Using CPU crc32 instructions
4992016-10-03 17:30:52 140736620217280 [Note] InnoDB: Initializing buffer pool, size = 16.0M
5002016-10-03 17:30:52 140736620217280 [Note] InnoDB: Completed initialization of buffer pool
5012016-10-03 17:30:52 140736620217280 [Note] InnoDB: Highest supported file format is Barracuda.
5022016-10-03 17:30:52 140736620217280 [Note] InnoDB: The log sequence numbers 1927913 and 1927913 in ibdata files do not match the log sequence number 1960205 in the ib_logfiles!
5032016-10-03 17:30:52 140736620217280 [Note] InnoDB: Database was not shutdown normally!
5042016-10-03 17:30:52 140736620217280 [Note] InnoDB: Starting crash recovery.
5052016-10-03 17:30:52 140736620217280 [Note] InnoDB: Reading tablespace information from the .ibd files...
5062016-10-03 17:30:52 140736620217280 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace andreadb/andreadbtable uses space ID: 25 at filepath: ./andreadb/andreadbtable.ibd. Cannot open tablespace bitnami_wordpress/wp_termmeta which uses space ID: 25 at filepath: ./bitnami_wordpress/wp_termmeta.ibd
5072016-10-03 17:30:52 7fffcc4143c0  InnoDB: Operating system error number 2 in a file operation.
508InnoDB: The error means the system cannot find the path specified.
509InnoDB: If you are installing InnoDB, remember that you must create
510InnoDB: directories yourself, InnoDB does not create them.
511InnoDB: Error: could not open single-table tablespace file ./bitnami_wordpress/wp_termmeta.ibd
512InnoDB: We do not continue the crash recovery, because the table may become
513InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
514InnoDB: To fix the problem and start mysqld:
515InnoDB: 1) If there is a permission problem in the file and mysqld cannot
516InnoDB: open the file, you should modify the permissions.
517InnoDB: 2) If the table is not needed, or you can restore it from a backup,
518InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
519InnoDB: crash recovery and ignore that table.
520InnoDB: 3) If the file system or the disk is broken, and you cannot remove
521InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
522InnoDB: and force InnoDB to continue crash recovery here.
5232016-10-03 17:30:52 2890 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended
5242016-10-03 17:35:10 3424 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
5252016-10-03 17:35:10 140736620217280 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
5262016-10-03 17:35:10 140736620217280 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 3565 ...
5272016-10-03 17:35:10 140736620217280 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
5282016-10-03 17:35:10 140736620217280 [Note] InnoDB: Using mutexes to ref count buffer pool pages
5292016-10-03 17:35:10 140736620217280 [Note] InnoDB: The InnoDB memory heap is disabled
5302016-10-03 17:35:10 140736620217280 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
5312016-10-03 17:35:10 140736620217280 [Note] InnoDB: Memory barrier is not used
5322016-10-03 17:35:10 140736620217280 [Note] InnoDB: Compressed tables use zlib 1.2.8
5332016-10-03 17:35:10 140736620217280 [Note] InnoDB: Using CPU crc32 instructions
5342016-10-03 17:35:10 140736620217280 [Note] InnoDB: Initializing buffer pool, size = 16.0M
5352016-10-03 17:35:10 140736620217280 [Note] InnoDB: Completed initialization of buffer pool
5362016-10-03 17:35:10 140736620217280 [Note] InnoDB: Highest supported file format is Barracuda.
5372016-10-03 17:35:10 140736620217280 [Note] InnoDB: The log sequence numbers 1927913 and 1927913 in ibdata files do not match the log sequence number 1960205 in the ib_logfiles!
5382016-10-03 17:35:10 140736620217280 [Note] InnoDB: Database was not shutdown normally!
5392016-10-03 17:35:10 140736620217280 [Note] InnoDB: Starting crash recovery.
5402016-10-03 17:35:10 140736620217280 [Note] InnoDB: Reading tablespace information from the .ibd files...
5412016-10-03 17:35:10 140736620217280 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace andreadb/andreadbtable uses space ID: 25 at filepath: ./andreadb/andreadbtable.ibd. Cannot open tablespace bitnami_wordpress/wp_termmeta which uses space ID: 25 at filepath: ./bitnami_wordpress/wp_termmeta.ibd
5422016-10-03 17:35:10 7fffcc4143c0  InnoDB: Operating system error number 2 in a file operation.
543InnoDB: The error means the system cannot find the path specified.
544InnoDB: If you are installing InnoDB, remember that you must create
545InnoDB: directories yourself, InnoDB does not create them.
546InnoDB: Error: could not open single-table tablespace file ./bitnami_wordpress/wp_termmeta.ibd
547InnoDB: We do not continue the crash recovery, because the table may become
548InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
549InnoDB: To fix the problem and start mysqld:
550InnoDB: 1) If there is a permission problem in the file and mysqld cannot
551InnoDB: open the file, you should modify the permissions.
552InnoDB: 2) If the table is not needed, or you can restore it from a backup,
553InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
554InnoDB: crash recovery and ignore that table.
555InnoDB: 3) If the file system or the disk is broken, and you cannot remove
556InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
557InnoDB: and force InnoDB to continue crash recovery here.
5582016-10-03 17:35:10 3424 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended
5592016-10-03 17:40:15 3949 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
5602016-10-03 17:40:15 140736620217280 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
5612016-10-03 17:40:15 140736620217280 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 4090 ...
5622016-10-03 17:40:15 140736620217280 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
5632016-10-03 17:40:15 140736620217280 [Note] InnoDB: Using mutexes to ref count buffer pool pages
5642016-10-03 17:40:15 140736620217280 [Note] InnoDB: The InnoDB memory heap is disabled
5652016-10-03 17:40:15 140736620217280 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
5662016-10-03 17:40:15 140736620217280 [Note] InnoDB: Memory barrier is not used
5672016-10-03 17:40:15 140736620217280 [Note] InnoDB: Compressed tables use zlib 1.2.8
5682016-10-03 17:40:15 140736620217280 [Note] InnoDB: Using CPU crc32 instructions
5692016-10-03 17:40:15 140736620217280 [Note] InnoDB: Initializing buffer pool, size = 16.0M
5702016-10-03 17:40:15 140736620217280 [Note] InnoDB: Completed initialization of buffer pool
5712016-10-03 17:40:15 140736620217280 [Note] InnoDB: Highest supported file format is Barracuda.
5722016-10-03 17:40:15 140736620217280 [Note] InnoDB: The log sequence numbers 1927913 and 1927913 in ibdata files do not match the log sequence number 1960205 in the ib_logfiles!
5732016-10-03 17:40:15 140736620217280 [Note] InnoDB: Database was not shutdown normally!
5742016-10-03 17:40:15 140736620217280 [Note] InnoDB: Starting crash recovery.
5752016-10-03 17:40:15 140736620217280 [Note] InnoDB: Reading tablespace information from the .ibd files...
5762016-10-03 17:40:15 140736620217280 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace andreadb/andreadbtable uses space ID: 25 at filepath: ./andreadb/andreadbtable.ibd. Cannot open tablespace bitnami_wordpress/wp_termmeta which uses space ID: 25 at filepath: ./bitnami_wordpress/wp_termmeta.ibd
5772016-10-03 17:40:15 7fffcc4143c0  InnoDB: Operating system error number 2 in a file operation.
578InnoDB: The error means the system cannot find the path specified.
579InnoDB: If you are installing InnoDB, remember that you must create
580InnoDB: directories yourself, InnoDB does not create them.
581InnoDB: Error: could not open single-table tablespace file ./bitnami_wordpress/wp_termmeta.ibd
582InnoDB: We do not continue the crash recovery, because the table may become
583InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
584InnoDB: To fix the problem and start mysqld:
585InnoDB: 1) If there is a permission problem in the file and mysqld cannot
586InnoDB: open the file, you should modify the permissions.
587InnoDB: 2) If the table is not needed, or you can restore it from a backup,
588InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
589InnoDB: crash recovery and ignore that table.
590InnoDB: 3) If the file system or the disk is broken, and you cannot remove
591InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
592InnoDB: and force InnoDB to continue crash recovery here.
5932016-10-03 17:40:15 3949 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended
5942016-10-03 17:42:54 4397 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
5952016-10-03 17:42:54 140736620217280 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
5962016-10-03 17:42:54 140736620217280 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 4538 ...
5972016-10-03 17:42:54 140736620217280 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
5982016-10-03 17:42:55 140736620217280 [Note] InnoDB: Using mutexes to ref count buffer pool pages
5992016-10-03 17:42:55 140736620217280 [Note] InnoDB: The InnoDB memory heap is disabled
6002016-10-03 17:42:55 140736620217280 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
6012016-10-03 17:42:55 140736620217280 [Note] InnoDB: Memory barrier is not used
6022016-10-03 17:42:55 140736620217280 [Note] InnoDB: Compressed tables use zlib 1.2.8
6032016-10-03 17:42:55 140736620217280 [Note] InnoDB: Using CPU crc32 instructions
6042016-10-03 17:42:55 140736620217280 [Note] InnoDB: Initializing buffer pool, size = 16.0M
6052016-10-03 17:42:55 140736620217280 [Note] InnoDB: Completed initialization of buffer pool
6062016-10-03 17:42:55 140736620217280 [Note] InnoDB: Highest supported file format is Barracuda.
6072016-10-03 17:42:55 140736620217280 [Note] InnoDB: The log sequence numbers 1927913 and 1927913 in ibdata files do not match the log sequence number 1960205 in the ib_logfiles!
6082016-10-03 17:42:55 140736620217280 [Note] InnoDB: Database was not shutdown normally!
6092016-10-03 17:42:55 140736620217280 [Note] InnoDB: Starting crash recovery.
6102016-10-03 17:42:55 140736620217280 [Note] InnoDB: Reading tablespace information from the .ibd files...
6112016-10-03 17:42:55 140736620217280 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace andreadb/andreadbtable uses space ID: 25 at filepath: ./andreadb/andreadbtable.ibd. Cannot open tablespace bitnami_wordpress/wp_termmeta which uses space ID: 25 at filepath: ./bitnami_wordpress/wp_termmeta.ibd
6122016-10-03 17:42:55 7fffcc4143c0  InnoDB: Operating system error number 2 in a file operation.
613InnoDB: The error means the system cannot find the path specified.
614InnoDB: If you are installing InnoDB, remember that you must create
615InnoDB: directories yourself, InnoDB does not create them.
616InnoDB: Error: could not open single-table tablespace file ./bitnami_wordpress/wp_termmeta.ibd
617InnoDB: We do not continue the crash recovery, because the table may become
618InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
619InnoDB: To fix the problem and start mysqld:
620InnoDB: 1) If there is a permission problem in the file and mysqld cannot
621InnoDB: open the file, you should modify the permissions.
622InnoDB: 2) If the table is not needed, or you can restore it from a backup,
623InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
624InnoDB: crash recovery and ignore that table.
625InnoDB: 3) If the file system or the disk is broken, and you cannot remove
626InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
627InnoDB: and force InnoDB to continue crash recovery here.
6282016-10-03 17:42:55 4397 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended
6292016-10-03 17:46:37 4914 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
6302016-10-03 17:46:37 140736620217280 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
6312016-10-03 17:46:37 140736620217280 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 5055 ...
6322016-10-03 17:46:37 140736620217280 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
6332016-10-03 17:46:37 140736620217280 [Note] InnoDB: Using mutexes to ref count buffer pool pages
6342016-10-03 17:46:37 140736620217280 [Note] InnoDB: The InnoDB memory heap is disabled
6352016-10-03 17:46:37 140736620217280 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
6362016-10-03 17:46:37 140736620217280 [Note] InnoDB: Memory barrier is not used
6372016-10-03 17:46:37 140736620217280 [Note] InnoDB: Compressed tables use zlib 1.2.8
6382016-10-03 17:46:37 140736620217280 [Note] InnoDB: Using CPU crc32 instructions
6392016-10-03 17:46:37 140736620217280 [Note] InnoDB: Initializing buffer pool, size = 16.0M
6402016-10-03 17:46:37 140736620217280 [Note] InnoDB: Completed initialization of buffer pool
6412016-10-03 17:46:37 140736620217280 [Note] InnoDB: Highest supported file format is Barracuda.
6422016-10-03 17:46:37 140736620217280 [Note] InnoDB: The log sequence numbers 1927913 and 1927913 in ibdata files do not match the log sequence number 1960205 in the ib_logfiles!
6432016-10-03 17:46:37 140736620217280 [Note] InnoDB: Database was not shutdown normally!
6442016-10-03 17:46:37 140736620217280 [Note] InnoDB: Starting crash recovery.
6452016-10-03 17:46:37 140736620217280 [Note] InnoDB: Reading tablespace information from the .ibd files...
6462016-10-03 17:46:37 140736620217280 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace andreadb/andreadbtable uses space ID: 25 at filepath: ./andreadb/andreadbtable.ibd. Cannot open tablespace bitnami_wordpress/wp_termmeta which uses space ID: 25 at filepath: ./bitnami_wordpress/wp_termmeta.ibd
6472016-10-03 17:46:37 7fffcc4143c0  InnoDB: Operating system error number 2 in a file operation.
648InnoDB: The error means the system cannot find the path specified.
649InnoDB: If you are installing InnoDB, remember that you must create
650InnoDB: directories yourself, InnoDB does not create them.
651InnoDB: Error: could not open single-table tablespace file ./bitnami_wordpress/wp_termmeta.ibd
652InnoDB: We do not continue the crash recovery, because the table may become
653InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
654InnoDB: To fix the problem and start mysqld:
655InnoDB: 1) If there is a permission problem in the file and mysqld cannot
656InnoDB: open the file, you should modify the permissions.
657InnoDB: 2) If the table is not needed, or you can restore it from a backup,
658InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
659InnoDB: crash recovery and ignore that table.
660InnoDB: 3) If the file system or the disk is broken, and you cannot remove
661InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
662InnoDB: and force InnoDB to continue crash recovery here.
6632016-10-03 17:46:37 4914 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended
6642016-10-03 17:51:25 5409 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
6652016-10-03 17:51:25 140736620217280 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
6662016-10-03 17:51:25 140736620217280 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 5550 ...
6672016-10-03 17:51:25 140736620217280 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
6682016-10-03 17:51:25 140736620217280 [Note] InnoDB: Using mutexes to ref count buffer pool pages
6692016-10-03 17:51:25 140736620217280 [Note] InnoDB: The InnoDB memory heap is disabled
6702016-10-03 17:51:25 140736620217280 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
6712016-10-03 17:51:25 140736620217280 [Note] InnoDB: Memory barrier is not used
6722016-10-03 17:51:25 140736620217280 [Note] InnoDB: Compressed tables use zlib 1.2.8
6732016-10-03 17:51:25 140736620217280 [Note] InnoDB: Using CPU crc32 instructions
6742016-10-03 17:51:25 140736620217280 [Note] InnoDB: Initializing buffer pool, size = 16.0M
6752016-10-03 17:51:25 140736620217280 [Note] InnoDB: Completed initialization of buffer pool
6762016-10-03 17:51:25 140736620217280 [Note] InnoDB: Highest supported file format is Barracuda.
6772016-10-03 17:51:25 140736620217280 [Note] InnoDB: The log sequence numbers 1927913 and 1927913 in ibdata files do not match the log sequence number 1960205 in the ib_logfiles!
6782016-10-03 17:51:25 140736620217280 [Note] InnoDB: Database was not shutdown normally!
6792016-10-03 17:51:25 140736620217280 [Note] InnoDB: Starting crash recovery.
6802016-10-03 17:51:25 140736620217280 [Note] InnoDB: Reading tablespace information from the .ibd files...
6812016-10-03 17:51:25 140736620217280 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace andreadb/andreadbtable uses space ID: 25 at filepath: ./andreadb/andreadbtable.ibd. Cannot open tablespace bitnami_wordpress/wp_termmeta which uses space ID: 25 at filepath: ./bitnami_wordpress/wp_termmeta.ibd
6822016-10-03 17:51:25 7fffcc4143c0  InnoDB: Operating system error number 2 in a file operation.
683InnoDB: The error means the system cannot find the path specified.
684InnoDB: If you are installing InnoDB, remember that you must create
685InnoDB: directories yourself, InnoDB does not create them.
686InnoDB: Error: could not open single-table tablespace file ./bitnami_wordpress/wp_termmeta.ibd
687InnoDB: We do not continue the crash recovery, because the table may become
688InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
689InnoDB: To fix the problem and start mysqld:
690InnoDB: 1) If there is a permission problem in the file and mysqld cannot
691InnoDB: open the file, you should modify the permissions.
692InnoDB: 2) If the table is not needed, or you can restore it from a backup,
693InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
694InnoDB: crash recovery and ignore that table.
695InnoDB: 3) If the file system or the disk is broken, and you cannot remove
696InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
697InnoDB: and force InnoDB to continue crash recovery here.
6982016-10-03 17:51:25 5409 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended
6992016-10-03 18:01:23 6538 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
7002016-10-03 18:01:23 140736620217280 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
7012016-10-03 18:01:23 140736620217280 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 6679 ...
7022016-10-03 18:01:23 140736620217280 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
7032016-10-03 18:01:23 140736620217280 [Note] InnoDB: Using mutexes to ref count buffer pool pages
7042016-10-03 18:01:23 140736620217280 [Note] InnoDB: The InnoDB memory heap is disabled
7052016-10-03 18:01:23 140736620217280 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
7062016-10-03 18:01:23 140736620217280 [Note] InnoDB: Memory barrier is not used
7072016-10-03 18:01:23 140736620217280 [Note] InnoDB: Compressed tables use zlib 1.2.8
7082016-10-03 18:01:23 140736620217280 [Note] InnoDB: Using CPU crc32 instructions
7092016-10-03 18:01:23 140736620217280 [Note] InnoDB: Initializing buffer pool, size = 16.0M
7102016-10-03 18:01:23 140736620217280 [Note] InnoDB: Completed initialization of buffer pool
7112016-10-03 18:01:23 140736620217280 [Note] InnoDB: Highest supported file format is Barracuda.
7122016-10-03 18:01:23 140736620217280 [Note] InnoDB: The log sequence numbers 1927913 and 1927913 in ibdata files do not match the log sequence number 1960205 in the ib_logfiles!
7132016-10-03 18:01:23 140736620217280 [Note] InnoDB: Database was not shutdown normally!
7142016-10-03 18:01:23 140736620217280 [Note] InnoDB: Starting crash recovery.
7152016-10-03 18:01:23 140736620217280 [Note] InnoDB: Reading tablespace information from the .ibd files...
7162016-10-03 18:01:23 140736620217280 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace andreadb/andreadbtable uses space ID: 25 at filepath: ./andreadb/andreadbtable.ibd. Cannot open tablespace bitnami_wordpress/wp_termmeta which uses space ID: 25 at filepath: ./bitnami_wordpress/wp_termmeta.ibd
7172016-10-03 18:01:23 7fffcc4143c0  InnoDB: Operating system error number 2 in a file operation.
718InnoDB: The error means the system cannot find the path specified.
719InnoDB: If you are installing InnoDB, remember that you must create
720InnoDB: directories yourself, InnoDB does not create them.
721InnoDB: Error: could not open single-table tablespace file ./bitnami_wordpress/wp_termmeta.ibd
722InnoDB: We do not continue the crash recovery, because the table may become
723InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
724InnoDB: To fix the problem and start mysqld:
725InnoDB: 1) If there is a permission problem in the file and mysqld cannot
726InnoDB: open the file, you should modify the permissions.
727InnoDB: 2) If the table is not needed, or you can restore it from a backup,
728InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
729InnoDB: crash recovery and ignore that table.
730InnoDB: 3) If the file system or the disk is broken, and you cannot remove
731InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
732InnoDB: and force InnoDB to continue crash recovery here.
7332016-10-03 18:01:23 6538 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended
7342016-10-03 18:05:47 7097 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
7352016-10-03 18:05:47 140736620217280 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
7362016-10-03 18:05:47 140736620217280 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 7238 ...
7372016-10-03 18:05:47 140736620217280 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
7382016-10-03 18:05:47 140736620217280 [Note] InnoDB: Using mutexes to ref count buffer pool pages
7392016-10-03 18:05:47 140736620217280 [Note] InnoDB: The InnoDB memory heap is disabled
7402016-10-03 18:05:47 140736620217280 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
7412016-10-03 18:05:47 140736620217280 [Note] InnoDB: Memory barrier is not used
7422016-10-03 18:05:47 140736620217280 [Note] InnoDB: Compressed tables use zlib 1.2.8
7432016-10-03 18:05:47 140736620217280 [Note] InnoDB: Using CPU crc32 instructions
7442016-10-03 18:05:47 140736620217280 [Note] InnoDB: Initializing buffer pool, size = 16.0M
7452016-10-03 18:05:47 140736620217280 [Note] InnoDB: Completed initialization of buffer pool
7462016-10-03 18:05:47 140736620217280 [Note] InnoDB: Highest supported file format is Barracuda.
7472016-10-03 18:05:47 140736620217280 [Note] InnoDB: The log sequence numbers 1927913 and 1927913 in ibdata files do not match the log sequence number 1960205 in the ib_logfiles!
7482016-10-03 18:05:47 140736620217280 [Note] InnoDB: Database was not shutdown normally!
7492016-10-03 18:05:47 140736620217280 [Note] InnoDB: Starting crash recovery.
7502016-10-03 18:05:47 140736620217280 [Note] InnoDB: Reading tablespace information from the .ibd files...
7512016-10-03 18:05:47 140736620217280 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace andreadb/andreadbtable uses space ID: 25 at filepath: ./andreadb/andreadbtable.ibd. Cannot open tablespace bitnami_wordpress/wp_termmeta which uses space ID: 25 at filepath: ./bitnami_wordpress/wp_termmeta.ibd
7522016-10-03 18:05:47 7fffcc4143c0  InnoDB: Operating system error number 2 in a file operation.
753InnoDB: The error means the system cannot find the path specified.
754InnoDB: If you are installing InnoDB, remember that you must create
755InnoDB: directories yourself, InnoDB does not create them.
756InnoDB: Error: could not open single-table tablespace file ./bitnami_wordpress/wp_termmeta.ibd
757InnoDB: We do not continue the crash recovery, because the table may become
758InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
759InnoDB: To fix the problem and start mysqld:
760InnoDB: 1) If there is a permission problem in the file and mysqld cannot
761InnoDB: open the file, you should modify the permissions.
762InnoDB: 2) If the table is not needed, or you can restore it from a backup,
763InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
764InnoDB: crash recovery and ignore that table.
765InnoDB: 3) If the file system or the disk is broken, and you cannot remove
766InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
767InnoDB: and force InnoDB to continue crash recovery here.
7682016-10-03 18:05:47 7097 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended
7692016-10-03 18:07:06 871 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
7702016-10-03 18:07:06 140735746061248 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
7712016-10-03 18:07:06 140735746061248 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 1012 ...
7722016-10-03 18:07:06 140735746061248 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
7732016-10-03 18:07:06 140735746061248 [Note] InnoDB: Using mutexes to ref count buffer pool pages
7742016-10-03 18:07:06 140735746061248 [Note] InnoDB: The InnoDB memory heap is disabled
7752016-10-03 18:07:06 140735746061248 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
7762016-10-03 18:07:06 140735746061248 [Note] InnoDB: Memory barrier is not used
7772016-10-03 18:07:06 140735746061248 [Note] InnoDB: Compressed tables use zlib 1.2.8
7782016-10-03 18:07:06 140735746061248 [Note] InnoDB: Using CPU crc32 instructions
7792016-10-03 18:07:06 140735746061248 [Note] InnoDB: Initializing buffer pool, size = 16.0M
7802016-10-03 18:07:06 140735746061248 [Note] InnoDB: Completed initialization of buffer pool
7812016-10-03 18:07:06 140735746061248 [Note] InnoDB: Highest supported file format is Barracuda.
7822016-10-03 18:07:06 140735746061248 [Note] InnoDB: The log sequence numbers 1927913 and 1927913 in ibdata files do not match the log sequence number 1960205 in the ib_logfiles!
7832016-10-03 18:07:06 140735746061248 [Note] InnoDB: Database was not shutdown normally!
7842016-10-03 18:07:06 140735746061248 [Note] InnoDB: Starting crash recovery.
7852016-10-03 18:07:06 140735746061248 [Note] InnoDB: Reading tablespace information from the .ibd files...
7862016-10-03 18:07:06 140735746061248 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace andreadb/andreadbtable uses space ID: 25 at filepath: ./andreadb/andreadbtable.ibd. Cannot open tablespace bitnami_wordpress/wp_termmeta which uses space ID: 25 at filepath: ./bitnami_wordpress/wp_termmeta.ibd
7872016-10-03 18:07:06 7fff9826b3c0  InnoDB: Operating system error number 2 in a file operation.
788InnoDB: The error means the system cannot find the path specified.
789InnoDB: If you are installing InnoDB, remember that you must create
790InnoDB: directories yourself, InnoDB does not create them.
791InnoDB: Error: could not open single-table tablespace file ./bitnami_wordpress/wp_termmeta.ibd
792InnoDB: We do not continue the crash recovery, because the table may become
793InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
794InnoDB: To fix the problem and start mysqld:
795InnoDB: 1) If there is a permission problem in the file and mysqld cannot
796InnoDB: open the file, you should modify the permissions.
797InnoDB: 2) If the table is not needed, or you can restore it from a backup,
798InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
799InnoDB: crash recovery and ignore that table.
800InnoDB: 3) If the file system or the disk is broken, and you cannot remove
801InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
802InnoDB: and force InnoDB to continue crash recovery here.
8032016-10-03 18:07:06 871 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended
8042016-10-03 18:15:53 2150 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
8052016-10-03 18:15:53 140735746061248 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
8062016-10-03 18:15:53 140735746061248 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 2291 ...
8072016-10-03 18:15:53 140735746061248 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
8082016-10-03 18:15:53 140735746061248 [Note] InnoDB: Using mutexes to ref count buffer pool pages
8092016-10-03 18:15:53 140735746061248 [Note] InnoDB: The InnoDB memory heap is disabled
8102016-10-03 18:15:53 140735746061248 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
8112016-10-03 18:15:53 140735746061248 [Note] InnoDB: Memory barrier is not used
8122016-10-03 18:15:53 140735746061248 [Note] InnoDB: Compressed tables use zlib 1.2.8
8132016-10-03 18:15:53 140735746061248 [Note] InnoDB: Using CPU crc32 instructions
8142016-10-03 18:15:53 140735746061248 [Note] InnoDB: Initializing buffer pool, size = 16.0M
8152016-10-03 18:15:53 140735746061248 [Note] InnoDB: Completed initialization of buffer pool
8162016-10-03 18:15:53 140735746061248 [Note] InnoDB: Highest supported file format is Barracuda.
8172016-10-03 18:15:53 140735746061248 [Note] InnoDB: The log sequence numbers 1927913 and 1927913 in ibdata files do not match the log sequence number 1960205 in the ib_logfiles!
8182016-10-03 18:15:53 140735746061248 [Note] InnoDB: Database was not shutdown normally!
8192016-10-03 18:15:53 140735746061248 [Note] InnoDB: Starting crash recovery.
8202016-10-03 18:15:53 140735746061248 [Note] InnoDB: Reading tablespace information from the .ibd files...
8212016-10-03 18:15:53 140735746061248 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace andreadb/andreadbtable uses space ID: 25 at filepath: ./andreadb/andreadbtable.ibd. Cannot open tablespace bitnami_wordpress/wp_termmeta which uses space ID: 25 at filepath: ./bitnami_wordpress/wp_termmeta.ibd
8222016-10-03 18:15:53 7fff9826b3c0  InnoDB: Operating system error number 2 in a file operation.
823InnoDB: The error means the system cannot find the path specified.
824InnoDB: If you are installing InnoDB, remember that you must create
825InnoDB: directories yourself, InnoDB does not create them.
826InnoDB: Error: could not open single-table tablespace file ./bitnami_wordpress/wp_termmeta.ibd
827InnoDB: We do not continue the crash recovery, because the table may become
828InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
829InnoDB: To fix the problem and start mysqld:
830InnoDB: 1) If there is a permission problem in the file and mysqld cannot
831InnoDB: open the file, you should modify the permissions.
832InnoDB: 2) If the table is not needed, or you can restore it from a backup,
833InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
834InnoDB: crash recovery and ignore that table.
835InnoDB: 3) If the file system or the disk is broken, and you cannot remove
836InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
837InnoDB: and force InnoDB to continue crash recovery here.
8382016-10-03 18:15:53 2150 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended
8392016-10-03 18:17:14 2551 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
8402016-10-03 18:17:14 140735746061248 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
8412016-10-03 18:17:14 140735746061248 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 2692 ...
8422016-10-03 18:17:14 140735746061248 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
8432016-10-03 18:17:14 140735746061248 [Note] InnoDB: Using mutexes to ref count buffer pool pages
8442016-10-03 18:17:14 140735746061248 [Note] InnoDB: The InnoDB memory heap is disabled
8452016-10-03 18:17:14 140735746061248 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
8462016-10-03 18:17:14 140735746061248 [Note] InnoDB: Memory barrier is not used
8472016-10-03 18:17:14 140735746061248 [Note] InnoDB: Compressed tables use zlib 1.2.8
8482016-10-03 18:17:14 140735746061248 [Note] InnoDB: Using CPU crc32 instructions
8492016-10-03 18:17:14 140735746061248 [Note] InnoDB: Initializing buffer pool, size = 16.0M
8502016-10-03 18:17:14 140735746061248 [Note] InnoDB: Completed initialization of buffer pool
8512016-10-03 18:17:14 140735746061248 [Note] InnoDB: Highest supported file format is Barracuda.
8522016-10-03 18:17:14 140735746061248 [Note] InnoDB: The log sequence numbers 1927913 and 1927913 in ibdata files do not match the log sequence number 1960205 in the ib_logfiles!
8532016-10-03 18:17:14 140735746061248 [Note] InnoDB: Database was not shutdown normally!
8542016-10-03 18:17:14 140735746061248 [Note] InnoDB: Starting crash recovery.
8552016-10-03 18:17:14 140735746061248 [Note] InnoDB: Reading tablespace information from the .ibd files...
8562016-10-03 18:17:14 140735746061248 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace andreadb/andreadbtable uses space ID: 25 at filepath: ./andreadb/andreadbtable.ibd. Cannot open tablespace bitnami_wordpress/wp_termmeta which uses space ID: 25 at filepath: ./bitnami_wordpress/wp_termmeta.ibd
8572016-10-03 18:17:14 7fff9826b3c0  InnoDB: Operating system error number 2 in a file operation.
858InnoDB: The error means the system cannot find the path specified.
859InnoDB: If you are installing InnoDB, remember that you must create
860InnoDB: directories yourself, InnoDB does not create them.
861InnoDB: Error: could not open single-table tablespace file ./bitnami_wordpress/wp_termmeta.ibd
862InnoDB: We do not continue the crash recovery, because the table may become
863InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
864InnoDB: To fix the problem and start mysqld:
865InnoDB: 1) If there is a permission problem in the file and mysqld cannot
866InnoDB: open the file, you should modify the permissions.
867InnoDB: 2) If the table is not needed, or you can restore it from a backup,
868InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
869InnoDB: crash recovery and ignore that table.
870InnoDB: 3) If the file system or the disk is broken, and you cannot remove
871InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
872InnoDB: and force InnoDB to continue crash recovery here.
8732016-10-03 18:17:14 2551 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended
8742016-10-03 18:19:46 3014 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
8752016-10-03 18:19:46 140735746061248 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
8762016-10-03 18:19:46 140735746061248 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 3155 ...
8772016-10-03 18:19:46 140735746061248 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
8782016-10-03 18:19:46 140735746061248 [Note] InnoDB: Using mutexes to ref count buffer pool pages
8792016-10-03 18:19:46 140735746061248 [Note] InnoDB: The InnoDB memory heap is disabled
8802016-10-03 18:19:46 140735746061248 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
8812016-10-03 18:19:46 140735746061248 [Note] InnoDB: Memory barrier is not used
8822016-10-03 18:19:46 140735746061248 [Note] InnoDB: Compressed tables use zlib 1.2.8
8832016-10-03 18:19:46 140735746061248 [Note] InnoDB: Using CPU crc32 instructions
8842016-10-03 18:19:46 140735746061248 [Note] InnoDB: Initializing buffer pool, size = 16.0M
8852016-10-03 18:19:46 140735746061248 [Note] InnoDB: Completed initialization of buffer pool
8862016-10-03 18:19:46 140735746061248 [Note] InnoDB: Highest supported file format is Barracuda.
8872016-10-03 18:19:46 140735746061248 [Note] InnoDB: The log sequence numbers 1927913 and 1927913 in ibdata files do not match the log sequence number 1960205 in the ib_logfiles!
8882016-10-03 18:19:46 140735746061248 [Note] InnoDB: Database was not shutdown normally!
8892016-10-03 18:19:46 140735746061248 [Note] InnoDB: Starting crash recovery.
8902016-10-03 18:19:46 140735746061248 [Note] InnoDB: Reading tablespace information from the .ibd files...
8912016-10-03 18:19:46 140735746061248 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace andreadb/andreadbtable uses space ID: 25 at filepath: ./andreadb/andreadbtable.ibd. Cannot open tablespace bitnami_wordpress/wp_termmeta which uses space ID: 25 at filepath: ./bitnami_wordpress/wp_termmeta.ibd
8922016-10-03 18:19:46 7fff9826b3c0  InnoDB: Operating system error number 2 in a file operation.
893InnoDB: The error means the system cannot find the path specified.
894InnoDB: If you are installing InnoDB, remember that you must create
895InnoDB: directories yourself, InnoDB does not create them.
896InnoDB: Error: could not open single-table tablespace file ./bitnami_wordpress/wp_termmeta.ibd
897InnoDB: We do not continue the crash recovery, because the table may become
898InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
899InnoDB: To fix the problem and start mysqld:
900InnoDB: 1) If there is a permission problem in the file and mysqld cannot
901InnoDB: open the file, you should modify the permissions.
902InnoDB: 2) If the table is not needed, or you can restore it from a backup,
903InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
904InnoDB: crash recovery and ignore that table.
905InnoDB: 3) If the file system or the disk is broken, and you cannot remove
906InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
907InnoDB: and force InnoDB to continue crash recovery here.
9082016-10-03 18:19:46 3014 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended
9092016-10-03 18:22:00 3389 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
9102016-10-03 18:22:00 140735746061248 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
9112016-10-03 18:22:00 140735746061248 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 3530 ...
9122016-10-03 18:22:00 140735746061248 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
9132016-10-03 18:22:00 140735746061248 [Note] InnoDB: Using mutexes to ref count buffer pool pages
9142016-10-03 18:22:00 140735746061248 [Note] InnoDB: The InnoDB memory heap is disabled
9152016-10-03 18:22:00 140735746061248 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
9162016-10-03 18:22:00 140735746061248 [Note] InnoDB: Memory barrier is not used
9172016-10-03 18:22:00 140735746061248 [Note] InnoDB: Compressed tables use zlib 1.2.8
9182016-10-03 18:22:00 140735746061248 [Note] InnoDB: Using CPU crc32 instructions
9192016-10-03 18:22:00 140735746061248 [Note] InnoDB: Initializing buffer pool, size = 16.0M
9202016-10-03 18:22:00 140735746061248 [Note] InnoDB: Completed initialization of buffer pool
9212016-10-03 18:22:00 140735746061248 [Note] InnoDB: Highest supported file format is Barracuda.
9222016-10-03 18:22:00 140735746061248 [Note] InnoDB: The log sequence numbers 1927913 and 1927913 in ibdata files do not match the log sequence number 1960205 in the ib_logfiles!
9232016-10-03 18:22:00 140735746061248 [Note] InnoDB: Database was not shutdown normally!
9242016-10-03 18:22:00 140735746061248 [Note] InnoDB: Starting crash recovery.
9252016-10-03 18:22:00 140735746061248 [Note] InnoDB: Reading tablespace information from the .ibd files...
9262016-10-03 18:22:00 140735746061248 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace andreadb/andreadbtable uses space ID: 25 at filepath: ./andreadb/andreadbtable.ibd. Cannot open tablespace bitnami_wordpress/wp_termmeta which uses space ID: 25 at filepath: ./bitnami_wordpress/wp_termmeta.ibd
9272016-10-03 18:22:00 7fff9826b3c0  InnoDB: Operating system error number 2 in a file operation.
928InnoDB: The error means the system cannot find the path specified.
929InnoDB: If you are installing InnoDB, remember that you must create
930InnoDB: directories yourself, InnoDB does not create them.
931InnoDB: Error: could not open single-table tablespace file ./bitnami_wordpress/wp_termmeta.ibd
932InnoDB: We do not continue the crash recovery, because the table may become
933InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
934InnoDB: To fix the problem and start mysqld:
935InnoDB: 1) If there is a permission problem in the file and mysqld cannot
936InnoDB: open the file, you should modify the permissions.
937InnoDB: 2) If the table is not needed, or you can restore it from a backup,
938InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
939InnoDB: crash recovery and ignore that table.
940InnoDB: 3) If the file system or the disk is broken, and you cannot remove
941InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
942InnoDB: and force InnoDB to continue crash recovery here.
9432016-10-03 18:22:00 3389 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended
9442016-10-03 18:25:03 3804 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
9452016-10-03 18:25:03 140735746061248 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
9462016-10-03 18:25:03 140735746061248 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 3945 ...
9472016-10-03 18:25:03 140735746061248 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
9482016-10-03 18:25:03 140735746061248 [Note] InnoDB: Using mutexes to ref count buffer pool pages
9492016-10-03 18:25:03 140735746061248 [Note] InnoDB: The InnoDB memory heap is disabled
9502016-10-03 18:25:03 140735746061248 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
9512016-10-03 18:25:03 140735746061248 [Note] InnoDB: Memory barrier is not used
9522016-10-03 18:25:03 140735746061248 [Note] InnoDB: Compressed tables use zlib 1.2.8
9532016-10-03 18:25:03 140735746061248 [Note] InnoDB: Using CPU crc32 instructions
9542016-10-03 18:25:03 140735746061248 [Note] InnoDB: Initializing buffer pool, size = 16.0M
9552016-10-03 18:25:03 140735746061248 [Note] InnoDB: Completed initialization of buffer pool
9562016-10-03 18:25:03 140735746061248 [Note] InnoDB: Highest supported file format is Barracuda.
9572016-10-03 18:25:03 140735746061248 [Note] InnoDB: The log sequence numbers 1927913 and 1927913 in ibdata files do not match the log sequence number 1960205 in the ib_logfiles!
9582016-10-03 18:25:03 140735746061248 [Note] InnoDB: Database was not shutdown normally!
9592016-10-03 18:25:03 140735746061248 [Note] InnoDB: Starting crash recovery.
9602016-10-03 18:25:03 140735746061248 [Note] InnoDB: Reading tablespace information from the .ibd files...
9612016-10-03 18:25:03 140735746061248 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace andreadb/andreadbtable uses space ID: 25 at filepath: ./andreadb/andreadbtable.ibd. Cannot open tablespace bitnami_wordpress/wp_termmeta which uses space ID: 25 at filepath: ./bitnami_wordpress/wp_termmeta.ibd
9622016-10-03 18:25:03 7fff9826b3c0  InnoDB: Operating system error number 2 in a file operation.
963InnoDB: The error means the system cannot find the path specified.
964InnoDB: If you are installing InnoDB, remember that you must create
965InnoDB: directories yourself, InnoDB does not create them.
966InnoDB: Error: could not open single-table tablespace file ./bitnami_wordpress/wp_termmeta.ibd
967InnoDB: We do not continue the crash recovery, because the table may become
968InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
969InnoDB: To fix the problem and start mysqld:
970InnoDB: 1) If there is a permission problem in the file and mysqld cannot
971InnoDB: open the file, you should modify the permissions.
972InnoDB: 2) If the table is not needed, or you can restore it from a backup,
973InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
974InnoDB: crash recovery and ignore that table.
975InnoDB: 3) If the file system or the disk is broken, and you cannot remove
976InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
977InnoDB: and force InnoDB to continue crash recovery here.
9782016-10-03 18:25:03 3804 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended
9792016-10-03 18:30:32 4976 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
9802016-10-03 18:30:32 140735746061248 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
9812016-10-03 18:30:32 140735746061248 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 5117 ...
9822016-10-03 18:30:32 140735746061248 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
9832016-10-03 18:30:32 140735746061248 [Note] InnoDB: Using mutexes to ref count buffer pool pages
9842016-10-03 18:30:32 140735746061248 [Note] InnoDB: The InnoDB memory heap is disabled
9852016-10-03 18:30:32 140735746061248 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
9862016-10-03 18:30:32 140735746061248 [Note] InnoDB: Memory barrier is not used
9872016-10-03 18:30:32 140735746061248 [Note] InnoDB: Compressed tables use zlib 1.2.8
9882016-10-03 18:30:32 140735746061248 [Note] InnoDB: Using CPU crc32 instructions
9892016-10-03 18:30:32 140735746061248 [Note] InnoDB: Initializing buffer pool, size = 16.0M
9902016-10-03 18:30:32 140735746061248 [Note] InnoDB: Completed initialization of buffer pool
9912016-10-03 18:30:32 140735746061248 [Note] InnoDB: Highest supported file format is Barracuda.
9922016-10-03 18:30:32 140735746061248 [Note] InnoDB: The log sequence numbers 1927913 and 1927913 in ibdata files do not match the log sequence number 1960205 in the ib_logfiles!
9932016-10-03 18:30:32 140735746061248 [Note] InnoDB: Database was not shutdown normally!
9942016-10-03 18:30:32 140735746061248 [Note] InnoDB: Starting crash recovery.
9952016-10-03 18:30:32 140735746061248 [Note] InnoDB: Reading tablespace information from the .ibd files...
9962016-10-03 18:30:32 140735746061248 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace andreadb/andreadbtable uses space ID: 25 at filepath: ./andreadb/andreadbtable.ibd. Cannot open tablespace bitnami_wordpress/wp_termmeta which uses space ID: 25 at filepath: ./bitnami_wordpress/wp_termmeta.ibd
9972016-10-03 18:30:32 7fff9826b3c0  InnoDB: Operating system error number 2 in a file operation.
998InnoDB: The error means the system cannot find the path specified.
999InnoDB: If you are installing InnoDB, remember that you must create
1000InnoDB: directories yourself, InnoDB does not create them.
1001InnoDB: Error: could not open single-table tablespace file ./bitnami_wordpress/wp_termmeta.ibd
1002InnoDB: We do not continue the crash recovery, because the table may become
1003InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
1004InnoDB: To fix the problem and start mysqld:
1005InnoDB: 1) If there is a permission problem in the file and mysqld cannot
1006InnoDB: open the file, you should modify the permissions.
1007InnoDB: 2) If the table is not needed, or you can restore it from a backup,
1008InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
1009InnoDB: crash recovery and ignore that table.
1010InnoDB: 3) If the file system or the disk is broken, and you cannot remove
1011InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
1012InnoDB: and force InnoDB to continue crash recovery here.
10132016-10-03 18:30:32 4976 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended
10142016-10-04 10:11:28 5197 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
10152016-10-04 10:11:28 140737227924416 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
10162016-10-04 10:11:28 140737227924416 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 5341 ...
10172016-10-04 10:11:28 140737227924416 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
10182016-10-04 10:11:28 140737227924416 [ERROR] mysqld: File '/Applications/XAMPP/xamppfiles/var/mysql/aria_log_control' not found (Errcode: 13 "Permission denied")
10192016-10-04 10:11:28 140737227924416 [ERROR] mysqld: Got error 'Can't open file' when trying to use aria control file '/Applications/XAMPP/xamppfiles/var/mysql/aria_log_control'
10202016-10-04 10:11:28 140737227924416 [ERROR] Plugin 'Aria' init function returned error.
10212016-10-04 10:11:28 140737227924416 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
10222016-10-04 10:11:28 140737227924416 [Note] InnoDB: Using mutexes to ref count buffer pool pages
10232016-10-04 10:11:28 140737227924416 [Note] InnoDB: The InnoDB memory heap is disabled
10242016-10-04 10:11:28 140737227924416 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
10252016-10-04 10:11:28 140737227924416 [Note] InnoDB: Memory barrier is not used
10262016-10-04 10:11:28 140737227924416 [Note] InnoDB: Compressed tables use zlib 1.2.8
10272016-10-04 10:11:28 140737227924416 [Note] InnoDB: Using CPU crc32 instructions
10282016-10-04 10:11:28 140737227924416 [Note] InnoDB: Initializing buffer pool, size = 16.0M
10292016-10-04 10:11:28 140737227924416 [Note] InnoDB: Completed initialization of buffer pool
10302016-10-04 10:11:28 140737227924416 [ERROR] InnoDB: /Applications/XAMPP/xamppfiles/var/mysql/ibdata1 can't be opened in read-write mode
10312016-10-04 10:11:28 140737227924416 [ERROR] InnoDB: The system tablespace must be writable!
10322016-10-04 10:11:28 140737227924416 [ERROR] Plugin 'InnoDB' init function returned error.
10332016-10-04 10:11:28 140737227924416 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
10342016-10-04 10:11:28 140737227924416 [Note] Plugin 'FEEDBACK' is disabled.
10352016-10-04 10:11:28 140737227924416 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
10362016-10-04 10:11:28 140737227924416 [ERROR] Unknown/unsupported storage engine: InnoDB
10372016-10-04 10:11:28 140737227924416 [ERROR] Aborting
1038
10392016-10-04 10:11:28 5197 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended
10402016-10-04 10:19:41 5926 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
10412016-10-04 10:19:41 140737227924416 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
10422016-10-04 10:19:41 140737227924416 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.9-MariaDB) starting as process 6070 ...
10432016-10-04 10:19:41 140737227924416 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
10442016-10-04 10:19:41 140737227924416 [ERROR] mysqld: File '/Applications/XAMPP/xamppfiles/var/mysql/aria_log_control' not found (Errcode: 13 "Permission denied")
10452016-10-04 10:19:41 140737227924416 [ERROR] mysqld: Got error 'Can't open file' when trying to use aria control file '/Applications/XAMPP/xamppfiles/var/mysql/aria_log_control'
10462016-10-04 10:19:41 140737227924416 [ERROR] Plugin 'Aria' init function returned error.
10472016-10-04 10:19:41 140737227924416 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
10482016-10-04 10:19:42 140737227924416 [Note] InnoDB: Using mutexes to ref count buffer pool pages
10492016-10-04 10:19:42 140737227924416 [Note] InnoDB: The InnoDB memory heap is disabled
10502016-10-04 10:19:42 140737227924416 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
10512016-10-04 10:19:42 140737227924416 [Note] InnoDB: Memory barrier is not used
10522016-10-04 10:19:42 140737227924416 [Note] InnoDB: Compressed tables use zlib 1.2.8
10532016-10-04 10:19:42 140737227924416 [Note] InnoDB: Using CPU crc32 instructions
10542016-10-04 10:19:42 140737227924416 [Note] InnoDB: Initializing buffer pool, size = 16.0M
10552016-10-04 10:19:42 140737227924416 [Note] InnoDB: Completed initialization of buffer pool
10562016-10-04 10:19:42 140737227924416 [ERROR] InnoDB: /Applications/XAMPP/xamppfiles/var/mysql/ibdata1 can't be opened in read-write mode
10572016-10-04 10:19:42 140737227924416 [ERROR] InnoDB: The system tablespace must be writable!
10582016-10-04 10:19:42 140737227924416 [ERROR] Plugin 'InnoDB' init function returned error.
10592016-10-04 10:19:42 140737227924416 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
10602016-10-04 10:19:42 140737227924416 [Note] Plugin 'FEEDBACK' is disabled.
10612016-10-04 10:19:42 140737227924416 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
10622016-10-04 10:19:42 140737227924416 [ERROR] Unknown/unsupported storage engine: InnoDB
10632016-10-04 10:19:42 140737227924416 [ERROR] Aborting
1064
10652016-10-04 10:19:42 5926 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/MBP-di-Andrea.pid ended