H6LeF00x

1161213 10:47:27 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql56
22016-12-13 10:47:27 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
32016-12-13 10:47:27 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.28) starting as process 1771 ...
42016-12-13 10:47:27 1771 [Warning] Setting lower_case_table_names=2 because file system for /Applications/MAMP/db/mysql56/ is case insensitive
52016-12-13 10:47:27 1771 [Note] Plugin 'FEDERATED' is disabled.
62016-12-13 10:47:27 1771 [Note] InnoDB: Using atomics to ref count buffer pool pages
72016-12-13 10:47:27 1771 [Note] InnoDB: The InnoDB memory heap is disabled
82016-12-13 10:47:27 1771 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
92016-12-13 10:47:27 1771 [Note] InnoDB: Memory barrier is not used
102016-12-13 10:47:27 1771 [Note] InnoDB: Compressed tables use zlib 1.2.8
112016-12-13 10:47:27 1771 [Note] InnoDB: Using CPU crc32 instructions
122016-12-13 10:47:27 1771 [Note] InnoDB: Initializing buffer pool, size = 128.0M
132016-12-13 10:47:27 1771 [Note] InnoDB: Completed initialization of buffer pool
142016-12-13 10:47:27 1771 [Note] InnoDB: Highest supported file format is Barracuda.
152016-12-13 10:47:27 1771 [Note] InnoDB: 128 rollback segment(s) are active.
162016-12-13 10:47:27 1771 [Note] InnoDB: Waiting for purge to start
172016-12-13 10:47:28 1771 [Note] InnoDB: 5.6.28 started; log sequence number 20287572
182016-12-13 10:47:28 1771 [Note] RSA private key file not found: /Applications/MAMP/db/mysql56//private_key.pem. Some authentication plugins will not work.
192016-12-13 10:47:28 1771 [Note] RSA public key file not found: /Applications/MAMP/db/mysql56//public_key.pem. Some authentication plugins will not work.
202016-12-13 10:47:28 1771 [Note] Server hostname (bind-address): '*'; port: 8889
212016-12-13 10:47:28 1771 [Note] IPv6 is available.
222016-12-13 10:47:28 1771 [Note]   - '::' resolves to '::';
232016-12-13 10:47:28 1771 [Note] Server socket created on IP: '::'.
242016-12-13 10:47:28 1771 [Note] Event Scheduler: Loaded 0 events
252016-12-13 10:47:28 1771 [Note] /Applications/MAMP/Library/bin/mysqld: ready for connections.
26Version: '5.6.28'  socket: '/Applications/MAMP/tmp/mysql/mysql.sock'  port: 8889  MySQL Community Server (GPL)
272016-12-13 10:47:33 1771 [Warning] InnoDB: Cannot open table mysql/innodb_index_stats 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.
282016-12-13 10:47:33 1771 [Warning] InnoDB: Cannot open table mysql/innodb_table_stats 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.
292016-12-13 10:47:33 1771 [Warning] InnoDB: Cannot open table mysql/slave_master_info 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.
302016-12-13 10:47:33 1771 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info 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.
312016-12-13 10:47:33 1771 [Warning] InnoDB: Cannot open table mysql/slave_worker_info 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.
322016-12-13 10:47:46 1336b7000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
332016-12-13 10:47:46 1336b7000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_options" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
342016-12-13 10:47:46 133767000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
352016-12-13 10:47:46 133767000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_posts" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
362016-12-13 10:47:46 133767000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
372016-12-13 10:47:46 133767000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_usermeta" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
382016-12-13 10:47:48 1336b7000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
392016-12-13 10:47:48 1336b7000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_postmeta" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
402016-12-13 10:47:49 133767000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
412016-12-13 10:47:49 133767000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_commentmeta" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
422016-12-13 10:47:51 1336b7000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
432016-12-13 10:47:51 1336b7000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_users" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
442016-12-13 10:47:52 133767000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
452016-12-13 10:47:52 133767000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_comments" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
462016-12-13 10:47:57 133767000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
472016-12-13 10:47:57 133767000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_terms" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
482016-12-13 10:47:57 133767000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
492016-12-13 10:47:57 133767000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_term_taxonomy" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
502016-12-13 10:47:57 133767000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
512016-12-13 10:47:57 133767000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_term_relationships" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
522016-12-13 10:48:06 1322ac000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
532016-12-13 10:48:06 1322ac000 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_options" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
542016-12-13 10:55:08 133767000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
552016-12-13 10:55:08 133767000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_termmeta" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
562016-12-13 10:55:08 133767000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
572016-12-13 10:55:08 133767000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_layerslider" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
582016-12-14 12:05:52 1322ac000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
592016-12-14 12:05:52 1322ac000 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_options" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
602016-12-14 21:36:38 1322ac000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
612016-12-14 21:36:38 1322ac000 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_options" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
622016-12-14 23:14:32 1322ac000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
632016-12-14 23:14:32 1322ac000 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_posts" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
642016-12-14 23:14:42 1322ac000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
652016-12-14 23:14:42 1322ac000 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_postmeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
662016-12-14 23:22:21 1322ac000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
672016-12-14 23:22:21 1322ac000 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_options" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
682016-12-14 23:22:32 1322ac000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
692016-12-14 23:22:32 1322ac000 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_options" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
702016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
712016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
722016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
732016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
742016-12-14 23:37:19 133a20000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_params" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
752016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
762016-12-14 23:37:19 133a20000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
772016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
782016-12-14 23:37:19 133a20000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_sliders" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
792016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
802016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
812016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
822016-12-14 23:37:19 133a20000 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
832016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
842016-12-14 23:37:19 133a20000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
852016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
862016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
872016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
882016-12-14 23:37:19 133a20000 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
892016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
902016-12-14 23:37:19 133a20000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
912016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
922016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
932016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
942016-12-14 23:37:19 133a20000 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_huge_itslider_sliders" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
952016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
962016-12-14 23:37:19 133a20000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_sliders" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
972016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
982016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
992016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1002016-12-14 23:37:19 133a20000 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_huge_itslider_sliders" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
1012016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1022016-12-14 23:37:19 133a20000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_sliders" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1032016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1042016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1052016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1062016-12-14 23:37:19 133a20000 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
1072016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1082016-12-14 23:37:19 133a20000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1092016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1102016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1112016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1122016-12-14 23:37:19 133a20000 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
1132016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1142016-12-14 23:37:19 133a20000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1152016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1162016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1172016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1182016-12-14 23:37:19 133a20000 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
1192016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1202016-12-14 23:37:19 133a20000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1212016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1222016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1232016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1242016-12-14 23:37:19 133a20000 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_huge_itslider_sliders" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
1252016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1262016-12-14 23:37:19 133a20000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_sliders" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1272016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1282016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1292016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1302016-12-14 23:37:19 133a20000 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_huge_itslider_sliders" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
1312016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1322016-12-14 23:37:19 133a20000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_sliders" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1332016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1342016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1352016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1362016-12-14 23:37:19 133a20000 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_huge_itslider_sliders" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
1372016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1382016-12-14 23:37:19 133a20000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_sliders" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1392016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1402016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1412016-12-14 23:37:19 133a20000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."#sql-6eb_294" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1422016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1432016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1442016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1452016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1462016-12-14 23:37:19 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1472016-12-14 23:37:19 1336b7000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1482016-12-14 23:37:19 1336b7000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1492016-12-14 23:37:19 1336b7000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1502016-12-14 23:37:19 1336b7000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1512016-12-14 23:37:23 133767000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1522016-12-14 23:37:23 133767000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1532016-12-14 23:37:39 1322ac000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1542016-12-14 23:37:39 1322ac000 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_huge_itslider_params" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
1552016-12-14 23:37:41 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1562016-12-14 23:37:41 133a20000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1572016-12-14 23:37:42 1336b7000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1582016-12-14 23:37:42 1336b7000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1592016-12-14 23:37:59 1322ac000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1602016-12-14 23:37:59 1322ac000 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
1612016-12-14 23:38:04 133767000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1622016-12-14 23:38:04 133767000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1632016-12-14 23:38:04 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1642016-12-14 23:38:04 133a20000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1652016-12-14 23:38:31 1336b7000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1662016-12-14 23:38:31 1336b7000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1672016-12-14 23:38:42 1322ac000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1682016-12-14 23:38:42 1322ac000 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
1692016-12-14 23:39:03 133767000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1702016-12-14 23:39:03 133767000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1712016-12-14 23:39:21 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1722016-12-14 23:39:21 133a20000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1732016-12-14 23:39:22 1336b7000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1742016-12-14 23:39:22 1336b7000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1752016-12-14 23:39:27 133767000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1762016-12-14 23:39:27 133767000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1772016-12-14 23:39:29 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1782016-12-14 23:39:29 133a20000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1792016-12-14 23:39:32 1336b7000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1802016-12-14 23:39:32 1336b7000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1812016-12-14 23:39:42 133767000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1822016-12-14 23:39:42 133767000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1832016-12-14 23:39:43 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1842016-12-14 23:39:43 133a20000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1852016-12-14 23:39:48 1336b7000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1862016-12-14 23:39:48 1336b7000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1872016-12-14 23:39:49 133767000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1882016-12-14 23:39:49 133767000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1892016-12-14 23:39:50 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1902016-12-14 23:39:50 133a20000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1912016-12-14 23:39:50 1336b7000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1922016-12-14 23:39:50 1336b7000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1932016-12-14 23:39:54 133767000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1942016-12-14 23:39:54 133767000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1952016-12-14 23:40:22 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1962016-12-14 23:40:22 133a20000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1972016-12-14 23:40:23 1336b7000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
1982016-12-14 23:40:23 1336b7000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
1992016-12-14 23:40:26 133767000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2002016-12-14 23:40:26 133767000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2012016-12-14 23:40:43 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2022016-12-14 23:40:43 133a20000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2032016-12-14 23:40:57 1336b7000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2042016-12-14 23:40:57 1336b7000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2052016-12-14 23:41:14 133767000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2062016-12-14 23:41:14 133767000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2072016-12-14 23:41:31 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2082016-12-14 23:41:31 133a20000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2092016-12-14 23:41:38 1336b7000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2102016-12-14 23:41:38 1336b7000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2112016-12-14 23:42:32 133767000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2122016-12-14 23:42:32 133767000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2132016-12-14 23:44:32 133a20000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2142016-12-14 23:44:32 133a20000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2152016-12-14 23:44:52 1336b7000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2162016-12-14 23:44:52 1336b7000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2172016-12-14 23:44:57 133767000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2182016-12-14 23:44:57 133767000 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_huge_itslider_images" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2192016-12-14 23:49:37 1322ac000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2202016-12-14 23:49:37 1322ac000 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_posts" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2212016-12-15 00:02:01 1322ac000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2222016-12-15 00:02:01 1322ac000 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_options" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2232016-12-15 00:11:56 1322ac000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2242016-12-15 00:11:56 1322ac000 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_term_relationships" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2252016-12-15 00:12:07 1322ac000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2262016-12-15 00:12:07 1322ac000 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_term_relationships" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2272016-12-15 00:12:49 1322ac000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2282016-12-15 00:12:49 1322ac000 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_postmeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2292016-12-15 00:30:52 1322ac000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2302016-12-15 00:30:52 1322ac000 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_usermeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2312016-12-15 01:31:46 1322ac000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2322016-12-15 01:31:46 1322ac000 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_posts" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2332016-12-15 01:48:11 1322ac000 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2342016-12-15 01:48:11 1322ac000 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_postmeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
235161215 02:46:46 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql56
2362016-12-15 02:46:46 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2372016-12-15 02:46:46 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.28) starting as process 437 ...
2382016-12-15 02:46:46 437 [Warning] Setting lower_case_table_names=2 because file system for /Applications/MAMP/db/mysql56/ is case insensitive
2392016-12-15 02:46:46 437 [Note] Plugin 'FEDERATED' is disabled.
2402016-12-15 02:46:46 437 [Note] InnoDB: Using atomics to ref count buffer pool pages
2412016-12-15 02:46:46 437 [Note] InnoDB: The InnoDB memory heap is disabled
2422016-12-15 02:46:46 437 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2432016-12-15 02:46:46 437 [Note] InnoDB: Memory barrier is not used
2442016-12-15 02:46:46 437 [Note] InnoDB: Compressed tables use zlib 1.2.8
2452016-12-15 02:46:46 437 [Note] InnoDB: Using CPU crc32 instructions
2462016-12-15 02:46:46 437 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2472016-12-15 02:46:46 437 [Note] InnoDB: Completed initialization of buffer pool
2482016-12-15 02:46:46 437 [Note] InnoDB: Highest supported file format is Barracuda.
2492016-12-15 02:46:46 437 [Note] InnoDB: The log sequence numbers 20287572 and 20287572 in ibdata files do not match the log sequence number 41938886 in the ib_logfiles!
2502016-12-15 02:46:46 437 [Note] InnoDB: Database was not shutdown normally!
2512016-12-15 02:46:46 437 [Note] InnoDB: Starting crash recovery.
2522016-12-15 02:46:46 437 [Note] InnoDB: Reading tablespace information from the .ibd files...
2532016-12-15 02:46:46 437 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_worker_info uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd. Cannot open tablespace wordpress/wp_term_taxonomy which uses space ID: 5 at filepath: ./wordpress/wp_term_taxonomy.ibd
2542016-12-15 02:46:46 7fff7a4bb300  InnoDB: Operating system error number 2 in a file operation.
255InnoDB: The error means the system cannot find the path specified.
256InnoDB: If you are installing InnoDB, remember that you must create
257InnoDB: directories yourself, InnoDB does not create them.
258InnoDB: Error: could not open single-table tablespace file ./wordpress/wp_term_taxonomy.ibd
259InnoDB: We do not continue the crash recovery, because the table may become
260InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
261InnoDB: To fix the problem and start mysqld:
262InnoDB: 1) If there is a permission problem in the file and mysqld cannot
263InnoDB: open the file, you should modify the permissions.
264InnoDB: 2) If the table is not needed, or you can restore it from a backup,
265InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
266InnoDB: crash recovery and ignore that table.
267InnoDB: 3) If the file system or the disk is broken, and you cannot remove
268InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
269InnoDB: and force InnoDB to continue crash recovery here.
270161215 02:46:46 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
271161215 02:47:17 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql56
2722016-12-15 02:47:17 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2732016-12-15 02:47:17 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.28) starting as process 728 ...
2742016-12-15 02:47:17 728 [Warning] Setting lower_case_table_names=2 because file system for /Applications/MAMP/db/mysql56/ is case insensitive
2752016-12-15 02:47:17 728 [Note] Plugin 'FEDERATED' is disabled.
2762016-12-15 02:47:18 728 [Note] InnoDB: Using atomics to ref count buffer pool pages
2772016-12-15 02:47:18 728 [Note] InnoDB: The InnoDB memory heap is disabled
2782016-12-15 02:47:18 728 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2792016-12-15 02:47:18 728 [Note] InnoDB: Memory barrier is not used
2802016-12-15 02:47:18 728 [Note] InnoDB: Compressed tables use zlib 1.2.8
2812016-12-15 02:47:18 728 [Note] InnoDB: Using CPU crc32 instructions
2822016-12-15 02:47:18 728 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2832016-12-15 02:47:18 728 [Note] InnoDB: Completed initialization of buffer pool
2842016-12-15 02:47:18 728 [Note] InnoDB: Highest supported file format is Barracuda.
2852016-12-15 02:47:18 728 [Note] InnoDB: The log sequence numbers 20287572 and 20287572 in ibdata files do not match the log sequence number 41938886 in the ib_logfiles!
2862016-12-15 02:47:18 728 [Note] InnoDB: Database was not shutdown normally!
2872016-12-15 02:47:18 728 [Note] InnoDB: Starting crash recovery.
2882016-12-15 02:47:18 728 [Note] InnoDB: Reading tablespace information from the .ibd files...
2892016-12-15 02:47:18 728 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_worker_info uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd. Cannot open tablespace wordpress/wp_term_taxonomy which uses space ID: 5 at filepath: ./wordpress/wp_term_taxonomy.ibd
2902016-12-15 02:47:18 7fff7a4bb300  InnoDB: Operating system error number 2 in a file operation.
291InnoDB: The error means the system cannot find the path specified.
292InnoDB: If you are installing InnoDB, remember that you must create
293InnoDB: directories yourself, InnoDB does not create them.
294InnoDB: Error: could not open single-table tablespace file ./wordpress/wp_term_taxonomy.ibd
295InnoDB: We do not continue the crash recovery, because the table may become
296InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
297InnoDB: To fix the problem and start mysqld:
298InnoDB: 1) If there is a permission problem in the file and mysqld cannot
299InnoDB: open the file, you should modify the permissions.
300InnoDB: 2) If the table is not needed, or you can restore it from a backup,
301InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
302InnoDB: crash recovery and ignore that table.
303InnoDB: 3) If the file system or the disk is broken, and you cannot remove
304InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
305InnoDB: and force InnoDB to continue crash recovery here.
306161215 02:47:18 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
307161215 02:55:42 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql56
3082016-12-15 02:55:42 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
3092016-12-15 02:55:42 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.28) starting as process 1851 ...
3102016-12-15 02:55:42 1851 [Warning] Setting lower_case_table_names=2 because file system for /Applications/MAMP/db/mysql56/ is case insensitive
3112016-12-15 02:55:42 1851 [Note] Plugin 'FEDERATED' is disabled.
3122016-12-15 02:55:42 1851 [Note] InnoDB: Using atomics to ref count buffer pool pages
3132016-12-15 02:55:42 1851 [Note] InnoDB: The InnoDB memory heap is disabled
3142016-12-15 02:55:42 1851 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
3152016-12-15 02:55:42 1851 [Note] InnoDB: Memory barrier is not used
3162016-12-15 02:55:42 1851 [Note] InnoDB: Compressed tables use zlib 1.2.8
3172016-12-15 02:55:42 1851 [Note] InnoDB: Using CPU crc32 instructions
3182016-12-15 02:55:42 1851 [Note] InnoDB: Initializing buffer pool, size = 128.0M
3192016-12-15 02:55:42 1851 [Note] InnoDB: Completed initialization of buffer pool
3202016-12-15 02:55:42 1851 [Note] InnoDB: Highest supported file format is Barracuda.
3212016-12-15 02:55:42 1851 [Note] InnoDB: The log sequence numbers 20287572 and 20287572 in ibdata files do not match the log sequence number 41938886 in the ib_logfiles!
3222016-12-15 02:55:42 1851 [Note] InnoDB: Database was not shutdown normally!
3232016-12-15 02:55:42 1851 [Note] InnoDB: Starting crash recovery.
3242016-12-15 02:55:42 1851 [Note] InnoDB: Reading tablespace information from the .ibd files...
3252016-12-15 02:55:42 1851 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_worker_info uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd. Cannot open tablespace wordpress/wp_term_taxonomy which uses space ID: 5 at filepath: ./wordpress/wp_term_taxonomy.ibd
3262016-12-15 02:55:42 7fff7a4bb300  InnoDB: Operating system error number 2 in a file operation.
327InnoDB: The error means the system cannot find the path specified.
328InnoDB: If you are installing InnoDB, remember that you must create
329InnoDB: directories yourself, InnoDB does not create them.
330InnoDB: Error: could not open single-table tablespace file ./wordpress/wp_term_taxonomy.ibd
331InnoDB: We do not continue the crash recovery, because the table may become
332InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
333InnoDB: To fix the problem and start mysqld:
334InnoDB: 1) If there is a permission problem in the file and mysqld cannot
335InnoDB: open the file, you should modify the permissions.
336InnoDB: 2) If the table is not needed, or you can restore it from a backup,
337InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
338InnoDB: crash recovery and ignore that table.
339InnoDB: 3) If the file system or the disk is broken, and you cannot remove
340InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
341InnoDB: and force InnoDB to continue crash recovery here.
342161215 02:55:42 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
343161215 02:55:54 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql56
3442016-12-15 02:55:54 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
3452016-12-15 02:55:54 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.28) starting as process 2043 ...
3462016-12-15 02:55:54 2043 [Warning] Setting lower_case_table_names=2 because file system for /Applications/MAMP/db/mysql56/ is case insensitive
3472016-12-15 02:55:54 2043 [Note] Plugin 'FEDERATED' is disabled.
3482016-12-15 02:55:54 2043 [Note] InnoDB: Using atomics to ref count buffer pool pages
3492016-12-15 02:55:54 2043 [Note] InnoDB: The InnoDB memory heap is disabled
3502016-12-15 02:55:54 2043 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
3512016-12-15 02:55:54 2043 [Note] InnoDB: Memory barrier is not used
3522016-12-15 02:55:54 2043 [Note] InnoDB: Compressed tables use zlib 1.2.8
3532016-12-15 02:55:54 2043 [Note] InnoDB: Using CPU crc32 instructions
3542016-12-15 02:55:54 2043 [Note] InnoDB: Initializing buffer pool, size = 128.0M
3552016-12-15 02:55:54 2043 [Note] InnoDB: Completed initialization of buffer pool
3562016-12-15 02:55:54 2043 [Note] InnoDB: Highest supported file format is Barracuda.
3572016-12-15 02:55:54 2043 [Note] InnoDB: The log sequence numbers 20287572 and 20287572 in ibdata files do not match the log sequence number 41938886 in the ib_logfiles!
3582016-12-15 02:55:54 2043 [Note] InnoDB: Database was not shutdown normally!
3592016-12-15 02:55:54 2043 [Note] InnoDB: Starting crash recovery.
3602016-12-15 02:55:54 2043 [Note] InnoDB: Reading tablespace information from the .ibd files...
3612016-12-15 02:55:54 2043 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_worker_info uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd. Cannot open tablespace wordpress/wp_term_taxonomy which uses space ID: 5 at filepath: ./wordpress/wp_term_taxonomy.ibd
3622016-12-15 02:55:54 7fff7a4bb300  InnoDB: Operating system error number 2 in a file operation.
363InnoDB: The error means the system cannot find the path specified.
364InnoDB: If you are installing InnoDB, remember that you must create
365InnoDB: directories yourself, InnoDB does not create them.
366InnoDB: Error: could not open single-table tablespace file ./wordpress/wp_term_taxonomy.ibd
367InnoDB: We do not continue the crash recovery, because the table may become
368InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
369InnoDB: To fix the problem and start mysqld:
370InnoDB: 1) If there is a permission problem in the file and mysqld cannot
371InnoDB: open the file, you should modify the permissions.
372InnoDB: 2) If the table is not needed, or you can restore it from a backup,
373InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
374InnoDB: crash recovery and ignore that table.
375InnoDB: 3) If the file system or the disk is broken, and you cannot remove
376InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
377InnoDB: and force InnoDB to continue crash recovery here.
378161215 02:55:54 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
379161215 02:56:16 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql56
3802016-12-15 02:56:17 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
3812016-12-15 02:56:17 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.28) starting as process 2211 ...
3822016-12-15 02:56:17 2211 [Warning] Setting lower_case_table_names=2 because file system for /Applications/MAMP/db/mysql56/ is case insensitive
3832016-12-15 02:56:17 2211 [Note] Plugin 'FEDERATED' is disabled.
3842016-12-15 02:56:17 2211 [Note] InnoDB: Using atomics to ref count buffer pool pages
3852016-12-15 02:56:17 2211 [Note] InnoDB: The InnoDB memory heap is disabled
3862016-12-15 02:56:17 2211 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
3872016-12-15 02:56:17 2211 [Note] InnoDB: Memory barrier is not used
3882016-12-15 02:56:17 2211 [Note] InnoDB: Compressed tables use zlib 1.2.8
3892016-12-15 02:56:17 2211 [Note] InnoDB: Using CPU crc32 instructions
3902016-12-15 02:56:17 2211 [Note] InnoDB: Initializing buffer pool, size = 128.0M
3912016-12-15 02:56:17 2211 [Note] InnoDB: Completed initialization of buffer pool
3922016-12-15 02:56:17 2211 [Note] InnoDB: Highest supported file format is Barracuda.
3932016-12-15 02:56:17 2211 [Note] InnoDB: The log sequence numbers 20287572 and 20287572 in ibdata files do not match the log sequence number 41938886 in the ib_logfiles!
3942016-12-15 02:56:17 2211 [Note] InnoDB: Database was not shutdown normally!
3952016-12-15 02:56:17 2211 [Note] InnoDB: Starting crash recovery.
3962016-12-15 02:56:17 2211 [Note] InnoDB: Reading tablespace information from the .ibd files...
3972016-12-15 02:56:17 2211 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_worker_info uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd. Cannot open tablespace wordpress/wp_term_taxonomy which uses space ID: 5 at filepath: ./wordpress/wp_term_taxonomy.ibd
3982016-12-15 02:56:17 7fff7a4bb300  InnoDB: Operating system error number 2 in a file operation.
399InnoDB: The error means the system cannot find the path specified.
400InnoDB: If you are installing InnoDB, remember that you must create
401InnoDB: directories yourself, InnoDB does not create them.
402InnoDB: Error: could not open single-table tablespace file ./wordpress/wp_term_taxonomy.ibd
403InnoDB: We do not continue the crash recovery, because the table may become
404InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
405InnoDB: To fix the problem and start mysqld:
406InnoDB: 1) If there is a permission problem in the file and mysqld cannot
407InnoDB: open the file, you should modify the permissions.
408InnoDB: 2) If the table is not needed, or you can restore it from a backup,
409InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
410InnoDB: crash recovery and ignore that table.
411InnoDB: 3) If the file system or the disk is broken, and you cannot remove
412InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
413InnoDB: and force InnoDB to continue crash recovery here.
414161215 02:56:17 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
415161215 02:56:43 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql56
4162016-12-15 02:56:43 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
4172016-12-15 02:56:43 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.28) starting as process 2489 ...
4182016-12-15 02:56:43 2489 [Warning] Setting lower_case_table_names=2 because file system for /Applications/MAMP/db/mysql56/ is case insensitive
4192016-12-15 02:56:43 2489 [Note] Plugin 'FEDERATED' is disabled.
4202016-12-15 02:56:43 2489 [Note] InnoDB: Using atomics to ref count buffer pool pages
4212016-12-15 02:56:43 2489 [Note] InnoDB: The InnoDB memory heap is disabled
4222016-12-15 02:56:43 2489 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
4232016-12-15 02:56:43 2489 [Note] InnoDB: Memory barrier is not used
4242016-12-15 02:56:43 2489 [Note] InnoDB: Compressed tables use zlib 1.2.8
4252016-12-15 02:56:43 2489 [Note] InnoDB: Using CPU crc32 instructions
4262016-12-15 02:56:43 2489 [Note] InnoDB: Initializing buffer pool, size = 128.0M
4272016-12-15 02:56:43 2489 [Note] InnoDB: Completed initialization of buffer pool
4282016-12-15 02:56:43 2489 [Note] InnoDB: Highest supported file format is Barracuda.
4292016-12-15 02:56:43 2489 [Note] InnoDB: The log sequence numbers 20287572 and 20287572 in ibdata files do not match the log sequence number 41938886 in the ib_logfiles!
4302016-12-15 02:56:43 2489 [Note] InnoDB: Database was not shutdown normally!
4312016-12-15 02:56:43 2489 [Note] InnoDB: Starting crash recovery.
4322016-12-15 02:56:43 2489 [Note] InnoDB: Reading tablespace information from the .ibd files...
4332016-12-15 02:56:43 2489 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_worker_info uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd. Cannot open tablespace wordpress/wp_term_taxonomy which uses space ID: 5 at filepath: ./wordpress/wp_term_taxonomy.ibd
4342016-12-15 02:56:43 7fff7a4bb300  InnoDB: Operating system error number 2 in a file operation.
435InnoDB: The error means the system cannot find the path specified.
436InnoDB: If you are installing InnoDB, remember that you must create
437InnoDB: directories yourself, InnoDB does not create them.
438InnoDB: Error: could not open single-table tablespace file ./wordpress/wp_term_taxonomy.ibd
439InnoDB: We do not continue the crash recovery, because the table may become
440InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
441InnoDB: To fix the problem and start mysqld:
442InnoDB: 1) If there is a permission problem in the file and mysqld cannot
443InnoDB: open the file, you should modify the permissions.
444InnoDB: 2) If the table is not needed, or you can restore it from a backup,
445InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
446InnoDB: crash recovery and ignore that table.
447InnoDB: 3) If the file system or the disk is broken, and you cannot remove
448InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
449InnoDB: and force InnoDB to continue crash recovery here.
450161215 02:56:43 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
451161215 03:03:16 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql56
4522016-12-15 03:03:16 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
4532016-12-15 03:03:16 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.28) starting as process 2761 ...
4542016-12-15 03:03:16 2761 [Warning] Setting lower_case_table_names=2 because file system for /Applications/MAMP/db/mysql56/ is case insensitive
4552016-12-15 03:03:16 2761 [Note] Plugin 'FEDERATED' is disabled.
4562016-12-15 03:03:16 2761 [Note] InnoDB: Using atomics to ref count buffer pool pages
4572016-12-15 03:03:16 2761 [Note] InnoDB: The InnoDB memory heap is disabled
4582016-12-15 03:03:16 2761 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
4592016-12-15 03:03:16 2761 [Note] InnoDB: Memory barrier is not used
4602016-12-15 03:03:16 2761 [Note] InnoDB: Compressed tables use zlib 1.2.8
4612016-12-15 03:03:16 2761 [Note] InnoDB: Using CPU crc32 instructions
4622016-12-15 03:03:16 2761 [Note] InnoDB: Initializing buffer pool, size = 128.0M
4632016-12-15 03:03:16 2761 [Note] InnoDB: Completed initialization of buffer pool
4642016-12-15 03:03:16 2761 [Note] InnoDB: Highest supported file format is Barracuda.
4652016-12-15 03:03:16 2761 [Note] InnoDB: The log sequence numbers 20287572 and 20287572 in ibdata files do not match the log sequence number 41938886 in the ib_logfiles!
4662016-12-15 03:03:16 2761 [Note] InnoDB: Database was not shutdown normally!
4672016-12-15 03:03:16 2761 [Note] InnoDB: Starting crash recovery.
4682016-12-15 03:03:16 2761 [Note] InnoDB: Reading tablespace information from the .ibd files...
4692016-12-15 03:03:16 2761 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_worker_info uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd. Cannot open tablespace wordpress/wp_term_taxonomy which uses space ID: 5 at filepath: ./wordpress/wp_term_taxonomy.ibd
4702016-12-15 03:03:16 7fff7a4bb300  InnoDB: Operating system error number 2 in a file operation.
471InnoDB: The error means the system cannot find the path specified.
472InnoDB: If you are installing InnoDB, remember that you must create
473InnoDB: directories yourself, InnoDB does not create them.
474InnoDB: Error: could not open single-table tablespace file ./wordpress/wp_term_taxonomy.ibd
475InnoDB: We do not continue the crash recovery, because the table may become
476InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
477InnoDB: To fix the problem and start mysqld:
478InnoDB: 1) If there is a permission problem in the file and mysqld cannot
479InnoDB: open the file, you should modify the permissions.
480InnoDB: 2) If the table is not needed, or you can restore it from a backup,
481InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
482InnoDB: crash recovery and ignore that table.
483InnoDB: 3) If the file system or the disk is broken, and you cannot remove
484InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
485InnoDB: and force InnoDB to continue crash recovery here.
486161215 03:03:16 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
487161215 03:03:24 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql56
4882016-12-15 03:03:25 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
4892016-12-15 03:03:25 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.28) starting as process 2916 ...
4902016-12-15 03:03:25 2916 [Warning] Setting lower_case_table_names=2 because file system for /Applications/MAMP/db/mysql56/ is case insensitive
4912016-12-15 03:03:25 2916 [Note] Plugin 'FEDERATED' is disabled.
4922016-12-15 03:03:25 2916 [Note] InnoDB: Using atomics to ref count buffer pool pages
4932016-12-15 03:03:25 2916 [Note] InnoDB: The InnoDB memory heap is disabled
4942016-12-15 03:03:25 2916 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
4952016-12-15 03:03:25 2916 [Note] InnoDB: Memory barrier is not used
4962016-12-15 03:03:25 2916 [Note] InnoDB: Compressed tables use zlib 1.2.8
4972016-12-15 03:03:25 2916 [Note] InnoDB: Using CPU crc32 instructions
4982016-12-15 03:03:25 2916 [Note] InnoDB: Initializing buffer pool, size = 128.0M
4992016-12-15 03:03:25 2916 [Note] InnoDB: Completed initialization of buffer pool
5002016-12-15 03:03:25 2916 [Note] InnoDB: Highest supported file format is Barracuda.
5012016-12-15 03:03:25 2916 [Note] InnoDB: The log sequence numbers 20287572 and 20287572 in ibdata files do not match the log sequence number 41938886 in the ib_logfiles!
5022016-12-15 03:03:25 2916 [Note] InnoDB: Database was not shutdown normally!
5032016-12-15 03:03:25 2916 [Note] InnoDB: Starting crash recovery.
5042016-12-15 03:03:25 2916 [Note] InnoDB: Reading tablespace information from the .ibd files...
5052016-12-15 03:03:25 2916 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_worker_info uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd. Cannot open tablespace wordpress/wp_term_taxonomy which uses space ID: 5 at filepath: ./wordpress/wp_term_taxonomy.ibd
5062016-12-15 03:03:25 7fff7a4bb300  InnoDB: Operating system error number 2 in a file operation.
507InnoDB: The error means the system cannot find the path specified.
508InnoDB: If you are installing InnoDB, remember that you must create
509InnoDB: directories yourself, InnoDB does not create them.
510InnoDB: Error: could not open single-table tablespace file ./wordpress/wp_term_taxonomy.ibd
511InnoDB: We do not continue the crash recovery, because the table may become
512InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
513InnoDB: To fix the problem and start mysqld:
514InnoDB: 1) If there is a permission problem in the file and mysqld cannot
515InnoDB: open the file, you should modify the permissions.
516InnoDB: 2) If the table is not needed, or you can restore it from a backup,
517InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
518InnoDB: crash recovery and ignore that table.
519InnoDB: 3) If the file system or the disk is broken, and you cannot remove
520InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
521InnoDB: and force InnoDB to continue crash recovery here.
522161215 03:03:25 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
523161215 03:06:43 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql56
5242016-12-15 03:06:43 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
5252016-12-15 03:06:43 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.28) starting as process 522 ...
5262016-12-15 03:06:44 522 [Warning] Setting lower_case_table_names=2 because file system for /Applications/MAMP/db/mysql56/ is case insensitive
5272016-12-15 03:06:44 522 [Note] Plugin 'FEDERATED' is disabled.
5282016-12-15 03:06:44 522 [Note] InnoDB: Using atomics to ref count buffer pool pages
5292016-12-15 03:06:44 522 [Note] InnoDB: The InnoDB memory heap is disabled
5302016-12-15 03:06:44 522 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
5312016-12-15 03:06:44 522 [Note] InnoDB: Memory barrier is not used
5322016-12-15 03:06:44 522 [Note] InnoDB: Compressed tables use zlib 1.2.8
5332016-12-15 03:06:44 522 [Note] InnoDB: Using CPU crc32 instructions
5342016-12-15 03:06:44 522 [Note] InnoDB: Initializing buffer pool, size = 128.0M
5352016-12-15 03:06:44 522 [Note] InnoDB: Completed initialization of buffer pool
5362016-12-15 03:06:44 522 [Note] InnoDB: Highest supported file format is Barracuda.
5372016-12-15 03:06:44 522 [Note] InnoDB: The log sequence numbers 20287572 and 20287572 in ibdata files do not match the log sequence number 41938886 in the ib_logfiles!
5382016-12-15 03:06:44 522 [Note] InnoDB: Database was not shutdown normally!
5392016-12-15 03:06:44 522 [Note] InnoDB: Starting crash recovery.
5402016-12-15 03:06:44 522 [Note] InnoDB: Reading tablespace information from the .ibd files...
5412016-12-15 03:06:44 522 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_worker_info uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd. Cannot open tablespace wordpress/wp_term_taxonomy which uses space ID: 5 at filepath: ./wordpress/wp_term_taxonomy.ibd
5422016-12-15 03:06:44 7fff78ad7300  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 ./wordpress/wp_term_taxonomy.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.
558161215 03:06:44 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
559161215 03:11:11 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql56
5602016-12-15 03:11:11 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
5612016-12-15 03:11:11 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.28) starting as process 756 ...
5622016-12-15 03:11:11 756 [Warning] Setting lower_case_table_names=2 because file system for /Applications/MAMP/db/mysql56/ is case insensitive
5632016-12-15 03:11:11 756 [Note] Plugin 'FEDERATED' is disabled.
5642016-12-15 03:11:11 756 [Note] InnoDB: Using atomics to ref count buffer pool pages
5652016-12-15 03:11:11 756 [Note] InnoDB: The InnoDB memory heap is disabled
5662016-12-15 03:11:11 756 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
5672016-12-15 03:11:11 756 [Note] InnoDB: Memory barrier is not used
5682016-12-15 03:11:11 756 [Note] InnoDB: Compressed tables use zlib 1.2.8
5692016-12-15 03:11:11 756 [Note] InnoDB: Using CPU crc32 instructions
5702016-12-15 03:11:11 756 [Note] InnoDB: Initializing buffer pool, size = 128.0M
5712016-12-15 03:11:11 756 [Note] InnoDB: Completed initialization of buffer pool
5722016-12-15 03:11:11 756 [Note] InnoDB: Highest supported file format is Barracuda.
5732016-12-15 03:11:11 756 [Note] InnoDB: The log sequence numbers 20287572 and 20287572 in ibdata files do not match the log sequence number 41938886 in the ib_logfiles!
5742016-12-15 03:11:11 756 [Note] InnoDB: Database was not shutdown normally!
5752016-12-15 03:11:11 756 [Note] InnoDB: Starting crash recovery.
5762016-12-15 03:11:11 756 [Note] InnoDB: Reading tablespace information from the .ibd files...
5772016-12-15 03:11:11 756 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_worker_info uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd. Cannot open tablespace wordpress/wp_term_taxonomy which uses space ID: 5 at filepath: ./wordpress/wp_term_taxonomy.ibd
5782016-12-15 03:11:11 7fff78ad7300  InnoDB: Operating system error number 2 in a file operation.
579InnoDB: The error means the system cannot find the path specified.
580InnoDB: If you are installing InnoDB, remember that you must create
581InnoDB: directories yourself, InnoDB does not create them.
582InnoDB: Error: could not open single-table tablespace file ./wordpress/wp_term_taxonomy.ibd
583InnoDB: We do not continue the crash recovery, because the table may become
584InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
585InnoDB: To fix the problem and start mysqld:
586InnoDB: 1) If there is a permission problem in the file and mysqld cannot
587InnoDB: open the file, you should modify the permissions.
588InnoDB: 2) If the table is not needed, or you can restore it from a backup,
589InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
590InnoDB: crash recovery and ignore that table.
591InnoDB: 3) If the file system or the disk is broken, and you cannot remove
592InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
593InnoDB: and force InnoDB to continue crash recovery here.
594161215 03:11:11 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
595161215 03:28:48 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql56
5962016-12-15 03:28:48 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
5972016-12-15 03:28:48 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.28) starting as process 962 ...
5982016-12-15 03:28:48 962 [Warning] Setting lower_case_table_names=2 because file system for /Applications/MAMP/db/mysql56/ is case insensitive
5992016-12-15 03:28:48 962 [Note] Plugin 'FEDERATED' is disabled.
6002016-12-15 03:28:48 962 [Note] InnoDB: Using atomics to ref count buffer pool pages
6012016-12-15 03:28:48 962 [Note] InnoDB: The InnoDB memory heap is disabled
6022016-12-15 03:28:48 962 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
6032016-12-15 03:28:48 962 [Note] InnoDB: Memory barrier is not used
6042016-12-15 03:28:48 962 [Note] InnoDB: Compressed tables use zlib 1.2.8
6052016-12-15 03:28:48 962 [Note] InnoDB: Using CPU crc32 instructions
6062016-12-15 03:28:48 962 [Note] InnoDB: Initializing buffer pool, size = 128.0M
6072016-12-15 03:28:48 962 [Note] InnoDB: Completed initialization of buffer pool
6082016-12-15 03:28:48 962 [Note] InnoDB: Highest supported file format is Barracuda.
6092016-12-15 03:28:48 962 [Note] InnoDB: The log sequence numbers 20287572 and 20287572 in ibdata files do not match the log sequence number 41938886 in the ib_logfiles!
6102016-12-15 03:28:48 962 [Note] InnoDB: Database was not shutdown normally!
6112016-12-15 03:28:48 962 [Note] InnoDB: Starting crash recovery.
6122016-12-15 03:28:48 962 [Note] InnoDB: Reading tablespace information from the .ibd files...
6132016-12-15 03:28:48 962 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_worker_info uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd. Cannot open tablespace wordpress/wp_term_taxonomy which uses space ID: 5 at filepath: ./wordpress/wp_term_taxonomy.ibd
6142016-12-15 03:28:48 7fff78ad7300  InnoDB: Operating system error number 2 in a file operation.
615InnoDB: The error means the system cannot find the path specified.
616InnoDB: If you are installing InnoDB, remember that you must create
617InnoDB: directories yourself, InnoDB does not create them.
618InnoDB: Error: could not open single-table tablespace file ./wordpress/wp_term_taxonomy.ibd
619InnoDB: We do not continue the crash recovery, because the table may become
620InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
621InnoDB: To fix the problem and start mysqld:
622InnoDB: 1) If there is a permission problem in the file and mysqld cannot
623InnoDB: open the file, you should modify the permissions.
624InnoDB: 2) If the table is not needed, or you can restore it from a backup,
625InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
626InnoDB: crash recovery and ignore that table.
627InnoDB: 3) If the file system or the disk is broken, and you cannot remove
628InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
629InnoDB: and force InnoDB to continue crash recovery here.
630161215 03:28:48 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
631161215 03:29:19 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql56
6322016-12-15 03:29:19 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
6332016-12-15 03:29:19 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.28) starting as process 1136 ...
6342016-12-15 03:29:19 1136 [Warning] Setting lower_case_table_names=2 because file system for /Applications/MAMP/db/mysql56/ is case insensitive
6352016-12-15 03:29:19 1136 [Note] Plugin 'FEDERATED' is disabled.
6362016-12-15 03:29:19 1136 [Note] InnoDB: Using atomics to ref count buffer pool pages
6372016-12-15 03:29:19 1136 [Note] InnoDB: The InnoDB memory heap is disabled
6382016-12-15 03:29:19 1136 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
6392016-12-15 03:29:19 1136 [Note] InnoDB: Memory barrier is not used
6402016-12-15 03:29:19 1136 [Note] InnoDB: Compressed tables use zlib 1.2.8
6412016-12-15 03:29:19 1136 [Note] InnoDB: Using CPU crc32 instructions
6422016-12-15 03:29:19 1136 [Note] InnoDB: Initializing buffer pool, size = 128.0M
6432016-12-15 03:29:19 1136 [Note] InnoDB: Completed initialization of buffer pool
6442016-12-15 03:29:19 1136 [Note] InnoDB: Highest supported file format is Barracuda.
6452016-12-15 03:29:19 1136 [Note] InnoDB: The log sequence numbers 20287572 and 20287572 in ibdata files do not match the log sequence number 41938886 in the ib_logfiles!
6462016-12-15 03:29:19 1136 [Note] InnoDB: Database was not shutdown normally!
6472016-12-15 03:29:19 1136 [Note] InnoDB: Starting crash recovery.
6482016-12-15 03:29:19 1136 [Note] InnoDB: Reading tablespace information from the .ibd files...
6492016-12-15 03:29:19 1136 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_worker_info uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd. Cannot open tablespace wordpress/wp_term_taxonomy which uses space ID: 5 at filepath: ./wordpress/wp_term_taxonomy.ibd
6502016-12-15 03:29:19 7fff78ad7300  InnoDB: Operating system error number 2 in a file operation.
651InnoDB: The error means the system cannot find the path specified.
652InnoDB: If you are installing InnoDB, remember that you must create
653InnoDB: directories yourself, InnoDB does not create them.
654InnoDB: Error: could not open single-table tablespace file ./wordpress/wp_term_taxonomy.ibd
655InnoDB: We do not continue the crash recovery, because the table may become
656InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
657InnoDB: To fix the problem and start mysqld:
658InnoDB: 1) If there is a permission problem in the file and mysqld cannot
659InnoDB: open the file, you should modify the permissions.
660InnoDB: 2) If the table is not needed, or you can restore it from a backup,
661InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
662InnoDB: crash recovery and ignore that table.
663InnoDB: 3) If the file system or the disk is broken, and you cannot remove
664InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
665InnoDB: and force InnoDB to continue crash recovery here.
666161215 03:29:19 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
667161215 10:10:27 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql56
6682016-12-15 10:10:28 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
6692016-12-15 10:10:28 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.28) starting as process 526 ...
6702016-12-15 10:10:28 526 [Warning] Setting lower_case_table_names=2 because file system for /Applications/MAMP/db/mysql56/ is case insensitive
6712016-12-15 10:10:28 526 [Note] Plugin 'FEDERATED' is disabled.
6722016-12-15 10:10:28 526 [Note] InnoDB: Using atomics to ref count buffer pool pages
6732016-12-15 10:10:28 526 [Note] InnoDB: The InnoDB memory heap is disabled
6742016-12-15 10:10:28 526 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
6752016-12-15 10:10:28 526 [Note] InnoDB: Memory barrier is not used
6762016-12-15 10:10:28 526 [Note] InnoDB: Compressed tables use zlib 1.2.8
6772016-12-15 10:10:28 526 [Note] InnoDB: Using CPU crc32 instructions
6782016-12-15 10:10:28 526 [Note] InnoDB: Initializing buffer pool, size = 128.0M
6792016-12-15 10:10:28 526 [Note] InnoDB: Completed initialization of buffer pool
6802016-12-15 10:10:28 526 [Note] InnoDB: Highest supported file format is Barracuda.
6812016-12-15 10:10:28 526 [Note] InnoDB: The log sequence numbers 20287572 and 20287572 in ibdata files do not match the log sequence number 41938886 in the ib_logfiles!
6822016-12-15 10:10:28 526 [Note] InnoDB: Database was not shutdown normally!
6832016-12-15 10:10:28 526 [Note] InnoDB: Starting crash recovery.
6842016-12-15 10:10:28 526 [Note] InnoDB: Reading tablespace information from the .ibd files...
6852016-12-15 10:10:28 526 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_worker_info uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd. Cannot open tablespace wordpress/wp_term_taxonomy which uses space ID: 5 at filepath: ./wordpress/wp_term_taxonomy.ibd
6862016-12-15 10:10:28 7fff710e9300  InnoDB: Operating system error number 2 in a file operation.
687InnoDB: The error means the system cannot find the path specified.
688InnoDB: If you are installing InnoDB, remember that you must create
689InnoDB: directories yourself, InnoDB does not create them.
690InnoDB: Error: could not open single-table tablespace file ./wordpress/wp_term_taxonomy.ibd
691InnoDB: We do not continue the crash recovery, because the table may become
692InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
693InnoDB: To fix the problem and start mysqld:
694InnoDB: 1) If there is a permission problem in the file and mysqld cannot
695InnoDB: open the file, you should modify the permissions.
696InnoDB: 2) If the table is not needed, or you can restore it from a backup,
697InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
698InnoDB: crash recovery and ignore that table.
699InnoDB: 3) If the file system or the disk is broken, and you cannot remove
700InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
701InnoDB: and force InnoDB to continue crash recovery here.
702161215 10:10:28 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
703161215 10:59:25 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql56
7042016-12-15 10:59:25 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
7052016-12-15 10:59:25 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.28) starting as process 1153 ...
7062016-12-15 10:59:25 1153 [Warning] Setting lower_case_table_names=2 because file system for /Applications/MAMP/db/mysql56/ is case insensitive
7072016-12-15 10:59:25 1153 [Note] Plugin 'FEDERATED' is disabled.
7082016-12-15 10:59:25 1153 [Note] InnoDB: Using atomics to ref count buffer pool pages
7092016-12-15 10:59:25 1153 [Note] InnoDB: The InnoDB memory heap is disabled
7102016-12-15 10:59:25 1153 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
7112016-12-15 10:59:25 1153 [Note] InnoDB: Memory barrier is not used
7122016-12-15 10:59:25 1153 [Note] InnoDB: Compressed tables use zlib 1.2.8
7132016-12-15 10:59:25 1153 [Note] InnoDB: Using CPU crc32 instructions
7142016-12-15 10:59:25 1153 [Note] InnoDB: Initializing buffer pool, size = 128.0M
7152016-12-15 10:59:25 1153 [Note] InnoDB: Completed initialization of buffer pool
7162016-12-15 10:59:25 1153 [Note] InnoDB: Highest supported file format is Barracuda.
7172016-12-15 10:59:25 1153 [Note] InnoDB: The log sequence numbers 20287572 and 20287572 in ibdata files do not match the log sequence number 41938886 in the ib_logfiles!
7182016-12-15 10:59:25 1153 [Note] InnoDB: Database was not shutdown normally!
7192016-12-15 10:59:25 1153 [Note] InnoDB: Starting crash recovery.
7202016-12-15 10:59:25 1153 [Note] InnoDB: Reading tablespace information from the .ibd files...
7212016-12-15 10:59:25 1153 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_worker_info uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd. Cannot open tablespace wordpress/wp_term_taxonomy which uses space ID: 5 at filepath: ./wordpress/wp_term_taxonomy.ibd
7222016-12-15 10:59:25 7fff710e9300  InnoDB: Operating system error number 2 in a file operation.
723InnoDB: The error means the system cannot find the path specified.
724InnoDB: If you are installing InnoDB, remember that you must create
725InnoDB: directories yourself, InnoDB does not create them.
726InnoDB: Error: could not open single-table tablespace file ./wordpress/wp_term_taxonomy.ibd
727InnoDB: We do not continue the crash recovery, because the table may become
728InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
729InnoDB: To fix the problem and start mysqld:
730InnoDB: 1) If there is a permission problem in the file and mysqld cannot
731InnoDB: open the file, you should modify the permissions.
732InnoDB: 2) If the table is not needed, or you can restore it from a backup,
733InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
734InnoDB: crash recovery and ignore that table.
735InnoDB: 3) If the file system or the disk is broken, and you cannot remove
736InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
737InnoDB: and force InnoDB to continue crash recovery here.
738161215 10:59:25 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
739161215 10:59:33 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql56
7402016-12-15 10:59:33 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
7412016-12-15 10:59:33 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.28) starting as process 1307 ...
7422016-12-15 10:59:33 1307 [Warning] Setting lower_case_table_names=2 because file system for /Applications/MAMP/db/mysql56/ is case insensitive
7432016-12-15 10:59:33 1307 [Note] Plugin 'FEDERATED' is disabled.
7442016-12-15 10:59:33 1307 [Note] InnoDB: Using atomics to ref count buffer pool pages
7452016-12-15 10:59:33 1307 [Note] InnoDB: The InnoDB memory heap is disabled
7462016-12-15 10:59:33 1307 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
7472016-12-15 10:59:33 1307 [Note] InnoDB: Memory barrier is not used
7482016-12-15 10:59:33 1307 [Note] InnoDB: Compressed tables use zlib 1.2.8
7492016-12-15 10:59:33 1307 [Note] InnoDB: Using CPU crc32 instructions
7502016-12-15 10:59:33 1307 [Note] InnoDB: Initializing buffer pool, size = 128.0M
7512016-12-15 10:59:33 1307 [Note] InnoDB: Completed initialization of buffer pool
7522016-12-15 10:59:33 1307 [Note] InnoDB: Highest supported file format is Barracuda.
7532016-12-15 10:59:33 1307 [Note] InnoDB: The log sequence numbers 20287572 and 20287572 in ibdata files do not match the log sequence number 41938886 in the ib_logfiles!
7542016-12-15 10:59:33 1307 [Note] InnoDB: Database was not shutdown normally!
7552016-12-15 10:59:33 1307 [Note] InnoDB: Starting crash recovery.
7562016-12-15 10:59:33 1307 [Note] InnoDB: Reading tablespace information from the .ibd files...
7572016-12-15 10:59:33 1307 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_worker_info uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd. Cannot open tablespace wordpress/wp_term_taxonomy which uses space ID: 5 at filepath: ./wordpress/wp_term_taxonomy.ibd
7582016-12-15 10:59:33 7fff710e9300  InnoDB: Operating system error number 2 in a file operation.
759InnoDB: The error means the system cannot find the path specified.
760InnoDB: If you are installing InnoDB, remember that you must create
761InnoDB: directories yourself, InnoDB does not create them.
762InnoDB: Error: could not open single-table tablespace file ./wordpress/wp_term_taxonomy.ibd
763InnoDB: We do not continue the crash recovery, because the table may become
764InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
765InnoDB: To fix the problem and start mysqld:
766InnoDB: 1) If there is a permission problem in the file and mysqld cannot
767InnoDB: open the file, you should modify the permissions.
768InnoDB: 2) If the table is not needed, or you can restore it from a backup,
769InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
770InnoDB: crash recovery and ignore that table.
771InnoDB: 3) If the file system or the disk is broken, and you cannot remove
772InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
773InnoDB: and force InnoDB to continue crash recovery here.
774161215 10:59:33 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
775161215 11:12:15 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql56
7762016-12-15 11:12:15 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
7772016-12-15 11:12:15 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.28) starting as process 3361 ...
7782016-12-15 11:12:15 3361 [Warning] Setting lower_case_table_names=2 because file system for /Applications/MAMP/db/mysql56/ is case insensitive
7792016-12-15 11:12:15 3361 [Note] Plugin 'FEDERATED' is disabled.
7802016-12-15 11:12:15 3361 [Note] InnoDB: Using atomics to ref count buffer pool pages
7812016-12-15 11:12:15 3361 [Note] InnoDB: The InnoDB memory heap is disabled
7822016-12-15 11:12:15 3361 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
7832016-12-15 11:12:15 3361 [Note] InnoDB: Memory barrier is not used
7842016-12-15 11:12:15 3361 [Note] InnoDB: Compressed tables use zlib 1.2.8
7852016-12-15 11:12:15 3361 [Note] InnoDB: Using CPU crc32 instructions
7862016-12-15 11:12:15 3361 [Note] InnoDB: Initializing buffer pool, size = 128.0M
7872016-12-15 11:12:15 3361 [Note] InnoDB: Completed initialization of buffer pool
7882016-12-15 11:12:15 3361 [Note] InnoDB: Highest supported file format is Barracuda.
7892016-12-15 11:12:15 3361 [Note] InnoDB: The log sequence numbers 20287572 and 20287572 in ibdata files do not match the log sequence number 41938886 in the ib_logfiles!
7902016-12-15 11:12:15 3361 [Note] InnoDB: Database was not shutdown normally!
7912016-12-15 11:12:15 3361 [Note] InnoDB: Starting crash recovery.
7922016-12-15 11:12:15 3361 [Note] InnoDB: Reading tablespace information from the .ibd files...
7932016-12-15 11:12:15 3361 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_worker_info uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd. Cannot open tablespace wordpress/wp_term_taxonomy which uses space ID: 5 at filepath: ./wordpress/wp_term_taxonomy.ibd
7942016-12-15 11:12:15 7fff710e9300  InnoDB: Operating system error number 2 in a file operation.
795InnoDB: The error means the system cannot find the path specified.
796InnoDB: If you are installing InnoDB, remember that you must create
797InnoDB: directories yourself, InnoDB does not create them.
798InnoDB: Error: could not open single-table tablespace file ./wordpress/wp_term_taxonomy.ibd
799InnoDB: We do not continue the crash recovery, because the table may become
800InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
801InnoDB: To fix the problem and start mysqld:
802InnoDB: 1) If there is a permission problem in the file and mysqld cannot
803InnoDB: open the file, you should modify the permissions.
804InnoDB: 2) If the table is not needed, or you can restore it from a backup,
805InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
806InnoDB: crash recovery and ignore that table.
807InnoDB: 3) If the file system or the disk is broken, and you cannot remove
808InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
809InnoDB: and force InnoDB to continue crash recovery here.
810161215 11:12:15 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
811161215 11:12:31 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql56
8122016-12-15 11:12:31 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
8132016-12-15 11:12:31 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.28) starting as process 3518 ...
8142016-12-15 11:12:31 3518 [Warning] Setting lower_case_table_names=2 because file system for /Applications/MAMP/db/mysql56/ is case insensitive
8152016-12-15 11:12:31 3518 [Note] Plugin 'FEDERATED' is disabled.
8162016-12-15 11:12:31 3518 [Note] InnoDB: Using atomics to ref count buffer pool pages
8172016-12-15 11:12:31 3518 [Note] InnoDB: The InnoDB memory heap is disabled
8182016-12-15 11:12:31 3518 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
8192016-12-15 11:12:31 3518 [Note] InnoDB: Memory barrier is not used
8202016-12-15 11:12:31 3518 [Note] InnoDB: Compressed tables use zlib 1.2.8
8212016-12-15 11:12:31 3518 [Note] InnoDB: Using CPU crc32 instructions
8222016-12-15 11:12:31 3518 [Note] InnoDB: Initializing buffer pool, size = 128.0M
8232016-12-15 11:12:31 3518 [Note] InnoDB: Completed initialization of buffer pool
8242016-12-15 11:12:31 3518 [Note] InnoDB: Highest supported file format is Barracuda.
8252016-12-15 11:12:31 3518 [Note] InnoDB: The log sequence numbers 20287572 and 20287572 in ibdata files do not match the log sequence number 41938886 in the ib_logfiles!
8262016-12-15 11:12:31 3518 [Note] InnoDB: Database was not shutdown normally!
8272016-12-15 11:12:31 3518 [Note] InnoDB: Starting crash recovery.
8282016-12-15 11:12:31 3518 [Note] InnoDB: Reading tablespace information from the .ibd files...
8292016-12-15 11:12:31 3518 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_worker_info uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd. Cannot open tablespace wordpress/wp_term_taxonomy which uses space ID: 5 at filepath: ./wordpress/wp_term_taxonomy.ibd
8302016-12-15 11:12:31 7fff710e9300  InnoDB: Operating system error number 2 in a file operation.
831InnoDB: The error means the system cannot find the path specified.
832InnoDB: If you are installing InnoDB, remember that you must create
833InnoDB: directories yourself, InnoDB does not create them.
834InnoDB: Error: could not open single-table tablespace file ./wordpress/wp_term_taxonomy.ibd
835InnoDB: We do not continue the crash recovery, because the table may become
836InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
837InnoDB: To fix the problem and start mysqld:
838InnoDB: 1) If there is a permission problem in the file and mysqld cannot
839InnoDB: open the file, you should modify the permissions.
840InnoDB: 2) If the table is not needed, or you can restore it from a backup,
841InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
842InnoDB: crash recovery and ignore that table.
843InnoDB: 3) If the file system or the disk is broken, and you cannot remove
844InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
845InnoDB: and force InnoDB to continue crash recovery here.
846161215 11:12:31 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
847161215 11:13:17 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql56
8482016-12-15 11:13:17 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
8492016-12-15 11:13:17 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.28) starting as process 3711 ...
8502016-12-15 11:13:17 3711 [Warning] Setting lower_case_table_names=2 because file system for /Applications/MAMP/db/mysql56/ is case insensitive
8512016-12-15 11:13:17 3711 [Note] Plugin 'FEDERATED' is disabled.
8522016-12-15 11:13:17 3711 [Note] InnoDB: Using atomics to ref count buffer pool pages
8532016-12-15 11:13:17 3711 [Note] InnoDB: The InnoDB memory heap is disabled
8542016-12-15 11:13:17 3711 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
8552016-12-15 11:13:17 3711 [Note] InnoDB: Memory barrier is not used
8562016-12-15 11:13:17 3711 [Note] InnoDB: Compressed tables use zlib 1.2.8
8572016-12-15 11:13:17 3711 [Note] InnoDB: Using CPU crc32 instructions
8582016-12-15 11:13:17 3711 [Note] InnoDB: Initializing buffer pool, size = 128.0M
8592016-12-15 11:13:17 3711 [Note] InnoDB: Completed initialization of buffer pool
8602016-12-15 11:13:17 3711 [Note] InnoDB: Highest supported file format is Barracuda.
8612016-12-15 11:13:17 3711 [Note] InnoDB: The log sequence numbers 20287572 and 20287572 in ibdata files do not match the log sequence number 41938886 in the ib_logfiles!
8622016-12-15 11:13:17 3711 [Note] InnoDB: Database was not shutdown normally!
8632016-12-15 11:13:17 3711 [Note] InnoDB: Starting crash recovery.
8642016-12-15 11:13:17 3711 [Note] InnoDB: Reading tablespace information from the .ibd files...
8652016-12-15 11:13:17 3711 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_worker_info uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd. Cannot open tablespace wordpress/wp_term_taxonomy which uses space ID: 5 at filepath: ./wordpress/wp_term_taxonomy.ibd
8662016-12-15 11:13:17 7fff710e9300  InnoDB: Operating system error number 2 in a file operation.
867InnoDB: The error means the system cannot find the path specified.
868InnoDB: If you are installing InnoDB, remember that you must create
869InnoDB: directories yourself, InnoDB does not create them.
870InnoDB: Error: could not open single-table tablespace file ./wordpress/wp_term_taxonomy.ibd
871InnoDB: We do not continue the crash recovery, because the table may become
872InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
873InnoDB: To fix the problem and start mysqld:
874InnoDB: 1) If there is a permission problem in the file and mysqld cannot
875InnoDB: open the file, you should modify the permissions.
876InnoDB: 2) If the table is not needed, or you can restore it from a backup,
877InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
878InnoDB: crash recovery and ignore that table.
879InnoDB: 3) If the file system or the disk is broken, and you cannot remove
880InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
881InnoDB: and force InnoDB to continue crash recovery here.
882161215 11:13:17 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
883161215 11:31:45 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql56
8842016-12-15 11:31:46 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
8852016-12-15 11:31:46 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.28) starting as process 4121 ...
8862016-12-15 11:31:46 4121 [Warning] Setting lower_case_table_names=2 because file system for /Applications/MAMP/db/mysql56/ is case insensitive
8872016-12-15 11:31:46 4121 [Note] Plugin 'FEDERATED' is disabled.
8882016-12-15 11:31:46 4121 [Note] InnoDB: Using atomics to ref count buffer pool pages
8892016-12-15 11:31:46 4121 [Note] InnoDB: The InnoDB memory heap is disabled
8902016-12-15 11:31:46 4121 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
8912016-12-15 11:31:46 4121 [Note] InnoDB: Memory barrier is not used
8922016-12-15 11:31:46 4121 [Note] InnoDB: Compressed tables use zlib 1.2.8
8932016-12-15 11:31:46 4121 [Note] InnoDB: Using CPU crc32 instructions
8942016-12-15 11:31:46 4121 [Note] InnoDB: Initializing buffer pool, size = 128.0M
8952016-12-15 11:31:46 4121 [Note] InnoDB: Completed initialization of buffer pool
8962016-12-15 11:31:46 4121 [Note] InnoDB: Highest supported file format is Barracuda.
8972016-12-15 11:31:46 4121 [Note] InnoDB: The log sequence numbers 20287572 and 20287572 in ibdata files do not match the log sequence number 41938886 in the ib_logfiles!
8982016-12-15 11:31:46 4121 [Note] InnoDB: Database was not shutdown normally!
8992016-12-15 11:31:46 4121 [Note] InnoDB: Starting crash recovery.
9002016-12-15 11:31:46 4121 [Note] InnoDB: Reading tablespace information from the .ibd files...
9012016-12-15 11:31:46 4121 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_worker_info uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd. Cannot open tablespace wordpress/wp_term_taxonomy which uses space ID: 5 at filepath: ./wordpress/wp_term_taxonomy.ibd
9022016-12-15 11:31:46 7fff710e9300  InnoDB: Operating system error number 2 in a file operation.
903InnoDB: The error means the system cannot find the path specified.
904InnoDB: If you are installing InnoDB, remember that you must create
905InnoDB: directories yourself, InnoDB does not create them.
906InnoDB: Error: could not open single-table tablespace file ./wordpress/wp_term_taxonomy.ibd
907InnoDB: We do not continue the crash recovery, because the table may become
908InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
909InnoDB: To fix the problem and start mysqld:
910InnoDB: 1) If there is a permission problem in the file and mysqld cannot
911InnoDB: open the file, you should modify the permissions.
912InnoDB: 2) If the table is not needed, or you can restore it from a backup,
913InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
914InnoDB: crash recovery and ignore that table.
915InnoDB: 3) If the file system or the disk is broken, and you cannot remove
916InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
917InnoDB: and force InnoDB to continue crash recovery here.
918161215 11:31:46 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended