gistfile1.txt

Attaching to stjean_database_1
database_1   | chmod: changing permissions of '/helpers/add-cert.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/auth.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/binding.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/generate-key.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/get-remote-url.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/lando-entrypoint.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/load-keys.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/mounter.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/pantheon.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/pull.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/push.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/refresh-certs.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/setup-ca.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/sql-export.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/sql-import.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/switch.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/user-perm-helpers.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/user-perms.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/user-perms.sh': Operation not permitted
database_1   | chmod: changing permissions of '/scripts/load-keys.sh': Operation not permitted
database_1   | mkdir: cannot create directory '/etc/ssh': Permission denied
database_1   | Running command /entrypoint.sh /run.sh
database_1   | Running with exec!
database_1   | 
database_1   | Welcome to the Bitnami mariadb container
database_1   | Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-mariadb
database_1   | Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-mariadb/issues
database_1   | Send us your feedback at containers@bitnami.com
database_1   | 
database_1   | INFO  ==> ** Starting MariaDB setup **
database_1   | INFO  ==> Validating settings in MYSQL_*/MARIADB_* env vars..
database_1   | WARN  ==> You set the environment variable ALLOW_EMPTY_PASSWORD=yes. For safety reasons, do not use this flag in a production environment.
database_1   | INFO  ==> Initializing mariadb database...
database_1   | DEBUG ==> Custom configuration detected. Injecting...
database_1   | DEBUG ==> Ensuring expected directories/files exist...
database_1   | DEBUG ==> Creating main configuration file...
database_1   | INFO  ==> Persisted data detected. Restoring...
database_1   | INFO  ==> Stopping mariadb...
database_1   | INFO  ==> ** MariaDB setup finished! **
database_1   | 
database_1   | INFO  ==> ** Starting MariaDB **
database_1   | 2019-03-03 11:53:24 140509069342592 [Note] /opt/bitnami/mariadb/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 1 ...
database_1   | 2019-03-03 11:53:24 140509069342592 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
database_1   | 
database_1   | 2019-03-03 11:53:24 140509069342592 [Note] InnoDB: Using mutexes to ref count buffer pool pages
database_1   | 2019-03-03 11:53:24 140509069342592 [Note] InnoDB: The InnoDB memory heap is disabled
database_1   | 2019-03-03 11:53:24 140509069342592 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
database_1   | 2019-03-03 11:53:24 140509069342592 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
database_1   | 2019-03-03 11:53:24 140509069342592 [Note] InnoDB: Compressed tables use zlib 1.2.8
database_1   | 2019-03-03 11:53:24 140509069342592 [Note] InnoDB: Using Linux native AIO
database_1   | 2019-03-03 11:53:24 140509069342592 [Note] InnoDB: Using SSE crc32 instructions
database_1   | 2019-03-03 11:53:24 140509069342592 [Note] InnoDB: Initializing buffer pool, size = 128.0M
database_1   | 2019-03-03 11:53:24 140509069342592 [Note] InnoDB: Completed initialization of buffer pool
database_1   | 2019-03-03 11:53:24 140509069342592 [Note] InnoDB: Highest supported file format is Barracuda.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'mysql/gtid_slave_pos'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"mysql"."gtid_slave_pos"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'mysql/innodb_index_stats'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"mysql"."innodb_index_stats"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'mysql/innodb_table_stats'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"mysql"."innodb_table_stats"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_commentmeta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_commentmeta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_comments'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_comments"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_gf_draft_submissions'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_gf_draft_submissions"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_gf_entry'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_gf_entry"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_gf_entry_meta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_gf_entry_meta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_gf_entry_notes'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_gf_entry_notes"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_gf_form'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_gf_form"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_gf_form_meta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_gf_form_meta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_gf_form_revisions'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_gf_form_revisions"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_gf_form_view'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_gf_form_view"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_links'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_links"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_mailpoet_custom_fields'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_mailpoet_custom_fields"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_mailpoet_forms'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_mailpoet_forms"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_mailpoet_log'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_mailpoet_log"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_mailpoet_mapping_to_external_entities'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_mailpoet_mapping_to_external_entities"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_mailpoet_newsletter_links'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_mailpoet_newsletter_links"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_mailpoet_newsletter_option'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_mailpoet_newsletter_option"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_mailpoet_newsletter_option_fields'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_mailpoet_newsletter_option_fields"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_mailpoet_newsletter_posts'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_mailpoet_newsletter_posts"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_mailpoet_newsletter_segment'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_mailpoet_newsletter_segment"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_mailpoet_newsletter_templates'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_mailpoet_newsletter_templates"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_mailpoet_newsletters'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_mailpoet_newsletters"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_mailpoet_scheduled_task_subscribers'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_mailpoet_scheduled_task_subscribers"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_mailpoet_scheduled_tasks'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_mailpoet_scheduled_tasks"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_mailpoet_segments'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_mailpoet_segments"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_mailpoet_sending_queues'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_mailpoet_sending_queues"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_mailpoet_settings'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_mailpoet_settings"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_mailpoet_statistics_clicks'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_mailpoet_statistics_clicks"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_mailpoet_statistics_forms'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_mailpoet_statistics_forms"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_mailpoet_statistics_newsletters'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_mailpoet_statistics_newsletters"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_mailpoet_statistics_opens'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_mailpoet_statistics_opens"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_mailpoet_statistics_unsubscribes'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_mailpoet_statistics_unsubscribes"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_mailpoet_subscriber_custom_field'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_mailpoet_subscriber_custom_field"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_mailpoet_subscriber_ips'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_mailpoet_subscriber_ips"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_mailpoet_subscriber_segment'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_mailpoet_subscriber_segment"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_mailpoet_subscribers'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_mailpoet_subscribers"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_mbdb_books'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_mbdb_books"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_mbdbma_authors'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_mbdbma_authors"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_mediafromftp_log'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_mediafromftp_log"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_options'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_options"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_postmeta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_postmeta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_posts'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_posts"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_redirection_404'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_redirection_404"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_redirection_groups'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_redirection_groups"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_redirection_items'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_redirection_items"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_redirection_logs'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_redirection_logs"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_revslider_css'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_revslider_css"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_revslider_layer_animations'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_revslider_layer_animations"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_revslider_navigations'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_revslider_navigations"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_revslider_sliders'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_revslider_sliders"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_revslider_slides'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_revslider_slides"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_revslider_static_slides'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_revslider_static_slides"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_term_relationships'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_term_relationships"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_term_taxonomy'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_term_taxonomy"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_termmeta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_termmeta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_10_terms'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_10_terms"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_gf_draft_submissions'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_gf_draft_submissions"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_gf_entry'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_gf_entry"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_gf_entry_meta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_gf_entry_meta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_gf_entry_notes'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_gf_entry_notes"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_gf_form'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_gf_form"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_gf_form_meta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_gf_form_meta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_gf_form_revisions'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_gf_form_revisions"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_gf_form_view'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_gf_form_view"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_mailpoet_custom_fields'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_mailpoet_custom_fields"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_mailpoet_forms'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_mailpoet_forms"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_mailpoet_log'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_mailpoet_log"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_mailpoet_mapping_to_external_entities'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_mailpoet_mapping_to_external_entities"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_mailpoet_newsletter_links'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_mailpoet_newsletter_links"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_mailpoet_newsletter_option'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_mailpoet_newsletter_option"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_mailpoet_newsletter_option_fields'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_mailpoet_newsletter_option_fields"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_mailpoet_newsletter_posts'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_mailpoet_newsletter_posts"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_mailpoet_newsletter_segment'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_mailpoet_newsletter_segment"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_mailpoet_newsletter_templates'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_mailpoet_newsletter_templates"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_mailpoet_newsletters'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_mailpoet_newsletters"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_mailpoet_scheduled_task_subscribers'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_mailpoet_scheduled_task_subscribers"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_mailpoet_scheduled_tasks'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_mailpoet_scheduled_tasks"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_mailpoet_segments'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_mailpoet_segments"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_mailpoet_sending_queues'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_mailpoet_sending_queues"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_mailpoet_settings'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_mailpoet_settings"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_mailpoet_statistics_clicks'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_mailpoet_statistics_clicks"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_mailpoet_statistics_forms'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_mailpoet_statistics_forms"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_mailpoet_statistics_newsletters'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_mailpoet_statistics_newsletters"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_mailpoet_statistics_opens'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_mailpoet_statistics_opens"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_mailpoet_statistics_unsubscribes'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_mailpoet_statistics_unsubscribes"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_mailpoet_subscriber_custom_field'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_mailpoet_subscriber_custom_field"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_mailpoet_subscriber_ips'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_mailpoet_subscriber_ips"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_mailpoet_subscriber_segment'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_mailpoet_subscriber_segment"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_mailpoet_subscribers'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_mailpoet_subscribers"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_mediafromftp_log'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_mediafromftp_log"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_wpgmza'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_wpgmza"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_wpgmza_categories'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_wpgmza_categories"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_wpgmza_category_maps'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_wpgmza_category_maps"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_wpgmza_datasets'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_wpgmza_datasets"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_wpgmza_maps'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_wpgmza_maps"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_wpgmza_polygon'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_wpgmza_polygon"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_11_wpgmza_polylines'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_11_wpgmza_polylines"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_12_commentmeta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_12_commentmeta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_12_comments'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_12_comments"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_12_gf_draft_submissions'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_12_gf_draft_submissions"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_12_gf_entry'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_12_gf_entry"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_12_gf_entry_meta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_12_gf_entry_meta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_12_gf_entry_notes'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_12_gf_entry_notes"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_12_gf_form'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_12_gf_form"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_12_gf_form_meta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_12_gf_form_meta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_12_gf_form_revisions'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_12_gf_form_revisions"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_12_gf_form_view'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_12_gf_form_view"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_12_links'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_12_links"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_12_options'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_12_options"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_12_postmeta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_12_postmeta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_12_posts'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_12_posts"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_12_revslider_css'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_12_revslider_css"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_12_revslider_layer_animations'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_12_revslider_layer_animations"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_12_revslider_navigations'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_12_revslider_navigations"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_12_revslider_sliders'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_12_revslider_sliders"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_12_revslider_slides'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_12_revslider_slides"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_12_revslider_static_slides'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_12_revslider_static_slides"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_12_term_relationships'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_12_term_relationships"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_12_term_taxonomy'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_12_term_taxonomy"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_12_termmeta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_12_termmeta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_12_terms'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_12_terms"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_gf_draft_submissions'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_gf_draft_submissions"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_gf_entry'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_gf_entry"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_gf_entry_meta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_gf_entry_meta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_gf_entry_notes'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_gf_entry_notes"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_gf_form'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_gf_form"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_gf_form_meta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_gf_form_meta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_gf_form_revisions'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_gf_form_revisions"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_gf_form_view'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_gf_form_view"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_mailpoet_custom_fields'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_mailpoet_custom_fields"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_mailpoet_forms'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_mailpoet_forms"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_mailpoet_log'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_mailpoet_log"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_mailpoet_mapping_to_external_entities'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_mailpoet_mapping_to_external_entities"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_mailpoet_newsletter_links'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_mailpoet_newsletter_links"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_mailpoet_newsletter_option'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_mailpoet_newsletter_option"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_mailpoet_newsletter_option_fields'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_mailpoet_newsletter_option_fields"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_mailpoet_newsletter_posts'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_mailpoet_newsletter_posts"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_mailpoet_newsletter_segment'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_mailpoet_newsletter_segment"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_mailpoet_newsletter_templates'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_mailpoet_newsletter_templates"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_mailpoet_newsletters'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_mailpoet_newsletters"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_mailpoet_scheduled_task_subscribers'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_mailpoet_scheduled_task_subscribers"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_mailpoet_scheduled_tasks'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_mailpoet_scheduled_tasks"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_mailpoet_segments'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_mailpoet_segments"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_mailpoet_sending_queues'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_mailpoet_sending_queues"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_mailpoet_settings'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_mailpoet_settings"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_mailpoet_statistics_clicks'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_mailpoet_statistics_clicks"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_mailpoet_statistics_forms'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_mailpoet_statistics_forms"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_mailpoet_statistics_newsletters'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_mailpoet_statistics_newsletters"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_mailpoet_statistics_opens'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_mailpoet_statistics_opens"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_mailpoet_statistics_unsubscribes'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_mailpoet_statistics_unsubscribes"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_mailpoet_subscriber_custom_field'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_mailpoet_subscriber_custom_field"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_mailpoet_subscriber_ips'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_mailpoet_subscriber_ips"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_mailpoet_subscriber_segment'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_mailpoet_subscriber_segment"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_mailpoet_subscribers'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_mailpoet_subscribers"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_mediafromftp_log'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_mediafromftp_log"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_wpgmza'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_wpgmza"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_wpgmza_categories'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_wpgmza_categories"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_wpgmza_category_maps'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_wpgmza_category_maps"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_wpgmza_datasets'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_wpgmza_datasets"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_wpgmza_maps'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_wpgmza_maps"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_wpgmza_polygon'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_wpgmza_polygon"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_2_wpgmza_polylines'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_2_wpgmza_polylines"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_gf_draft_submissions'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_gf_draft_submissions"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_gf_entry'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_gf_entry"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_gf_entry_meta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_gf_entry_meta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_gf_entry_notes'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_gf_entry_notes"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_gf_form'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_gf_form"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_gf_form_meta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_gf_form_meta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_gf_form_revisions'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_gf_form_revisions"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_gf_form_view'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_gf_form_view"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mailpoet_custom_fields'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mailpoet_custom_fields"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mailpoet_dynamic_segment_filters'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mailpoet_dynamic_segment_filters"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mailpoet_forms'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mailpoet_forms"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mailpoet_log'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mailpoet_log"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mailpoet_mapping_to_external_entities'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mailpoet_mapping_to_external_entities"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mailpoet_newsletter_links'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mailpoet_newsletter_links"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mailpoet_newsletter_option'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mailpoet_newsletter_option"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mailpoet_newsletter_option_fields'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mailpoet_newsletter_option_fields"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mailpoet_newsletter_posts'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mailpoet_newsletter_posts"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mailpoet_newsletter_segment'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mailpoet_newsletter_segment"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mailpoet_newsletter_templates'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mailpoet_newsletter_templates"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mailpoet_newsletters'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mailpoet_newsletters"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mailpoet_premium_newsletter_extra_data'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mailpoet_premium_newsletter_extra_data"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mailpoet_scheduled_task_subscribers'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mailpoet_scheduled_task_subscribers"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mailpoet_scheduled_tasks'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mailpoet_scheduled_tasks"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mailpoet_segments'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mailpoet_segments"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mailpoet_sending_queues'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mailpoet_sending_queues"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mailpoet_settings'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mailpoet_settings"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mailpoet_statistics_clicks'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mailpoet_statistics_clicks"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mailpoet_statistics_forms'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mailpoet_statistics_forms"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mailpoet_statistics_newsletters'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mailpoet_statistics_newsletters"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mailpoet_statistics_opens'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mailpoet_statistics_opens"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mailpoet_statistics_unsubscribes'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mailpoet_statistics_unsubscribes"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mailpoet_subscriber_custom_field'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mailpoet_subscriber_custom_field"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mailpoet_subscriber_ips'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mailpoet_subscriber_ips"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mailpoet_subscriber_segment'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mailpoet_subscriber_segment"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mailpoet_subscribers'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mailpoet_subscribers"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mbdbma_authors'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mbdbma_authors"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_mediafromftp_log'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_mediafromftp_log"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_wpgmza'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_wpgmza"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_wpgmza_categories'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_wpgmza_categories"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_wpgmza_category_maps'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_wpgmza_category_maps"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_wpgmza_datasets'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_wpgmza_datasets"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_wpgmza_maps'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_wpgmza_maps"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_wpgmza_polygon'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_wpgmza_polygon"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_3_wpgmza_polylines'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_3_wpgmza_polylines"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_gf_draft_submissions'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_gf_draft_submissions"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_gf_entry'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_gf_entry"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_gf_entry_meta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_gf_entry_meta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_gf_entry_notes'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_gf_entry_notes"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_gf_form'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_gf_form"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_gf_form_meta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_gf_form_meta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_gf_form_view'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_gf_form_view"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_mailpoet_custom_fields'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_mailpoet_custom_fields"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_mailpoet_forms'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_mailpoet_forms"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_mailpoet_log'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_mailpoet_log"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_mailpoet_mapping_to_external_entities'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_mailpoet_mapping_to_external_entities"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_mailpoet_newsletter_links'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_mailpoet_newsletter_links"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_mailpoet_newsletter_option'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_mailpoet_newsletter_option"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_mailpoet_newsletter_option_fields'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_mailpoet_newsletter_option_fields"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_mailpoet_newsletter_posts'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_mailpoet_newsletter_posts"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_mailpoet_newsletter_segment'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_mailpoet_newsletter_segment"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_mailpoet_newsletter_templates'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_mailpoet_newsletter_templates"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_mailpoet_newsletters'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_mailpoet_newsletters"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_mailpoet_scheduled_task_subscribers'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_mailpoet_scheduled_task_subscribers"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_mailpoet_scheduled_tasks'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_mailpoet_scheduled_tasks"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_mailpoet_segments'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_mailpoet_segments"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_mailpoet_sending_queues'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_mailpoet_sending_queues"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_mailpoet_settings'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_mailpoet_settings"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_mailpoet_statistics_clicks'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_mailpoet_statistics_clicks"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_mailpoet_statistics_forms'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_mailpoet_statistics_forms"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_mailpoet_statistics_newsletters'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_mailpoet_statistics_newsletters"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_mailpoet_statistics_opens'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_mailpoet_statistics_opens"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_mailpoet_statistics_unsubscribes'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_mailpoet_statistics_unsubscribes"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_mailpoet_subscriber_custom_field'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_mailpoet_subscriber_custom_field"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_mailpoet_subscriber_ips'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_mailpoet_subscriber_ips"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_mailpoet_subscriber_segment'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_mailpoet_subscriber_segment"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_mailpoet_subscribers'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_mailpoet_subscribers"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_mbdbma_authors'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_mbdbma_authors"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_mediafromftp_log'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_mediafromftp_log"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_wpgmza'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_wpgmza"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_wpgmza_categories'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_wpgmza_categories"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_wpgmza_category_maps'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_wpgmza_category_maps"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_wpgmza_datasets'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_wpgmza_datasets"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_wpgmza_maps'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_wpgmza_maps"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_wpgmza_polygon'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_wpgmza_polygon"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_4_wpgmza_polylines'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_4_wpgmza_polylines"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_gf_draft_submissions'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_gf_draft_submissions"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_gf_entry'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_gf_entry"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_gf_entry_meta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_gf_entry_meta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_gf_entry_notes'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_gf_entry_notes"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_gf_form'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_gf_form"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_gf_form_meta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_gf_form_meta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_gf_form_revisions'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_gf_form_revisions"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_gf_form_view'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_gf_form_view"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_mailpoet_custom_fields'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_mailpoet_custom_fields"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_mailpoet_forms'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_mailpoet_forms"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_mailpoet_log'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_mailpoet_log"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_mailpoet_mapping_to_external_entities'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_mailpoet_mapping_to_external_entities"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_mailpoet_newsletter_links'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_mailpoet_newsletter_links"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_mailpoet_newsletter_option'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_mailpoet_newsletter_option"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_mailpoet_newsletter_option_fields'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_mailpoet_newsletter_option_fields"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_mailpoet_newsletter_posts'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_mailpoet_newsletter_posts"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_mailpoet_newsletter_segment'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_mailpoet_newsletter_segment"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_mailpoet_newsletter_templates'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_mailpoet_newsletter_templates"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_mailpoet_newsletters'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_mailpoet_newsletters"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_mailpoet_scheduled_task_subscribers'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_mailpoet_scheduled_task_subscribers"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_mailpoet_scheduled_tasks'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_mailpoet_scheduled_tasks"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_mailpoet_segments'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_mailpoet_segments"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_mailpoet_sending_queues'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_mailpoet_sending_queues"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_mailpoet_settings'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_mailpoet_settings"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_mailpoet_statistics_clicks'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_mailpoet_statistics_clicks"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_mailpoet_statistics_forms'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_mailpoet_statistics_forms"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_mailpoet_statistics_newsletters'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_mailpoet_statistics_newsletters"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_mailpoet_statistics_opens'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_mailpoet_statistics_opens"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_mailpoet_statistics_unsubscribes'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_mailpoet_statistics_unsubscribes"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_mailpoet_subscriber_custom_field'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_mailpoet_subscriber_custom_field"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_mailpoet_subscriber_ips'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_mailpoet_subscriber_ips"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_mailpoet_subscriber_segment'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_mailpoet_subscriber_segment"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_mailpoet_subscribers'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_mailpoet_subscribers"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_mbdb_books'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_mbdb_books"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_mbdbma_authors'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_mbdbma_authors"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_mediafromftp_log'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_mediafromftp_log"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_wpgmza'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_wpgmza"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_wpgmza_categories'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_wpgmza_categories"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_wpgmza_category_maps'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_wpgmza_category_maps"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_wpgmza_datasets'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_wpgmza_datasets"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_wpgmza_maps'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_wpgmza_maps"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_wpgmza_polygon'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_wpgmza_polygon"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_5_wpgmza_polylines'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_5_wpgmza_polylines"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_gf_draft_submissions'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_gf_draft_submissions"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_gf_entry'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_gf_entry"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_gf_entry_meta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_gf_entry_meta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_gf_entry_notes'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_gf_entry_notes"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_gf_form'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_gf_form"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_gf_form_meta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_gf_form_meta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_gf_form_revisions'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_gf_form_revisions"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_gf_form_view'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_gf_form_view"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_mailpoet_custom_fields'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_mailpoet_custom_fields"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_mailpoet_forms'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_mailpoet_forms"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_mailpoet_log'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_mailpoet_log"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_mailpoet_mapping_to_external_entities'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_mailpoet_mapping_to_external_entities"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_mailpoet_newsletter_links'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_mailpoet_newsletter_links"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_mailpoet_newsletter_option'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_mailpoet_newsletter_option"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_mailpoet_newsletter_option_fields'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_mailpoet_newsletter_option_fields"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_mailpoet_newsletter_posts'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_mailpoet_newsletter_posts"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_mailpoet_newsletter_segment'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_mailpoet_newsletter_segment"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_mailpoet_newsletter_templates'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_mailpoet_newsletter_templates"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_mailpoet_newsletters'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_mailpoet_newsletters"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_mailpoet_scheduled_task_subscribers'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_mailpoet_scheduled_task_subscribers"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_mailpoet_scheduled_tasks'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_mailpoet_scheduled_tasks"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_mailpoet_segments'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_mailpoet_segments"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_mailpoet_sending_queues'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_mailpoet_sending_queues"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_mailpoet_settings'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_mailpoet_settings"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_mailpoet_statistics_clicks'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_mailpoet_statistics_clicks"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_mailpoet_statistics_forms'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_mailpoet_statistics_forms"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_mailpoet_statistics_newsletters'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_mailpoet_statistics_newsletters"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_mailpoet_statistics_opens'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_mailpoet_statistics_opens"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_mailpoet_statistics_unsubscribes'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_mailpoet_statistics_unsubscribes"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_mailpoet_subscriber_custom_field'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_mailpoet_subscriber_custom_field"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_mailpoet_subscriber_ips'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_mailpoet_subscriber_ips"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_mailpoet_subscriber_segment'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_mailpoet_subscriber_segment"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_mailpoet_subscribers'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_mailpoet_subscribers"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_mbdb_books'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_mbdb_books"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_mbdbma_authors'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_mbdbma_authors"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_mediafromftp_log'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_mediafromftp_log"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_wpgmza'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_wpgmza"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_wpgmza_categories'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_wpgmza_categories"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_wpgmza_category_maps'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_wpgmza_category_maps"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_wpgmza_datasets'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_wpgmza_datasets"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_wpgmza_maps'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_wpgmza_maps"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_wpgmza_polygon'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_wpgmza_polygon"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_6_wpgmza_polylines'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_6_wpgmza_polylines"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_gf_draft_submissions'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_gf_draft_submissions"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_gf_entry'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_gf_entry"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_gf_entry_meta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_gf_entry_meta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_gf_entry_notes'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_gf_entry_notes"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_gf_form'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_gf_form"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_gf_form_meta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_gf_form_meta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_gf_form_revisions'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_gf_form_revisions"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_gf_form_view'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_gf_form_view"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_mailpoet_custom_fields'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_mailpoet_custom_fields"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_mailpoet_forms'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_mailpoet_forms"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_mailpoet_log'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_mailpoet_log"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_mailpoet_mapping_to_external_entities'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_mailpoet_mapping_to_external_entities"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_mailpoet_newsletter_links'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_mailpoet_newsletter_links"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_mailpoet_newsletter_option'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_mailpoet_newsletter_option"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_mailpoet_newsletter_option_fields'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_mailpoet_newsletter_option_fields"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_mailpoet_newsletter_posts'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_mailpoet_newsletter_posts"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_mailpoet_newsletter_segment'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_mailpoet_newsletter_segment"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_mailpoet_newsletter_templates'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_mailpoet_newsletter_templates"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_mailpoet_newsletters'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_mailpoet_newsletters"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_mailpoet_scheduled_task_subscribers'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_mailpoet_scheduled_task_subscribers"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_mailpoet_scheduled_tasks'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_mailpoet_scheduled_tasks"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_mailpoet_segments'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_mailpoet_segments"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_mailpoet_sending_queues'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_mailpoet_sending_queues"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_mailpoet_settings'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_mailpoet_settings"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_mailpoet_statistics_clicks'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_mailpoet_statistics_clicks"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_mailpoet_statistics_forms'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_mailpoet_statistics_forms"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_mailpoet_statistics_newsletters'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_mailpoet_statistics_newsletters"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_mailpoet_statistics_opens'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_mailpoet_statistics_opens"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_mailpoet_statistics_unsubscribes'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_mailpoet_statistics_unsubscribes"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_mailpoet_subscriber_custom_field'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_mailpoet_subscriber_custom_field"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_mailpoet_subscriber_ips'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_mailpoet_subscriber_ips"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_mailpoet_subscriber_segment'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_mailpoet_subscriber_segment"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_mailpoet_subscribers'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_mailpoet_subscribers"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_mbdbma_authors'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_mbdbma_authors"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_mediafromftp_log'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_mediafromftp_log"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_wpgmza'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_wpgmza"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_wpgmza_categories'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_wpgmza_categories"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_wpgmza_category_maps'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_wpgmza_category_maps"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_wpgmza_datasets'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_wpgmza_datasets"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_wpgmza_maps'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_wpgmza_maps"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_wpgmza_polygon'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_wpgmza_polygon"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_7_wpgmza_polylines'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_7_wpgmza_polylines"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_commentmeta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_commentmeta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_comments'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_comments"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_gf_draft_submissions'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_gf_draft_submissions"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_gf_entry'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_gf_entry"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_gf_entry_meta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_gf_entry_meta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_gf_entry_notes'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_gf_entry_notes"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_gf_form'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_gf_form"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_gf_form_meta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_gf_form_meta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_gf_form_revisions'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_gf_form_revisions"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_gf_form_view'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_gf_form_view"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_links'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_links"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_mailpoet_custom_fields'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_mailpoet_custom_fields"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_mailpoet_forms'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_mailpoet_forms"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_mailpoet_log'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_mailpoet_log"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_mailpoet_mapping_to_external_entities'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_mailpoet_mapping_to_external_entities"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_mailpoet_newsletter_links'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_mailpoet_newsletter_links"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_mailpoet_newsletter_option'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_mailpoet_newsletter_option"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_mailpoet_newsletter_option_fields'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_mailpoet_newsletter_option_fields"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_mailpoet_newsletter_posts'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_mailpoet_newsletter_posts"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_mailpoet_newsletter_segment'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_mailpoet_newsletter_segment"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_mailpoet_newsletter_templates'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_mailpoet_newsletter_templates"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_mailpoet_newsletters'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_mailpoet_newsletters"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_mailpoet_scheduled_task_subscribers'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_mailpoet_scheduled_task_subscribers"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_mailpoet_scheduled_tasks'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_mailpoet_scheduled_tasks"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_mailpoet_segments'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_mailpoet_segments"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_mailpoet_sending_queues'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_mailpoet_sending_queues"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_mailpoet_settings'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_mailpoet_settings"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_mailpoet_statistics_clicks'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_mailpoet_statistics_clicks"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_mailpoet_statistics_forms'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_mailpoet_statistics_forms"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_mailpoet_statistics_newsletters'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_mailpoet_statistics_newsletters"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_mailpoet_statistics_opens'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_mailpoet_statistics_opens"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_mailpoet_statistics_unsubscribes'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_mailpoet_statistics_unsubscribes"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_mailpoet_subscriber_custom_field'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_mailpoet_subscriber_custom_field"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_mailpoet_subscriber_ips'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_mailpoet_subscriber_ips"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_mailpoet_subscriber_segment'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_mailpoet_subscriber_segment"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_mailpoet_subscribers'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_mailpoet_subscribers"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_mbdb_books'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_mbdb_books"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_mbdbma_authors'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_mbdbma_authors"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_mediafromftp_log'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_mediafromftp_log"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_options'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_options"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_postmeta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_postmeta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_posts'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_posts"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_redirection_404'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_redirection_404"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_redirection_groups'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_redirection_groups"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_redirection_items'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_redirection_items"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_redirection_logs'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_redirection_logs"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_revslider_css'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_revslider_css"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_revslider_layer_animations'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_revslider_layer_animations"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_revslider_navigations'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_revslider_navigations"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_revslider_sliders'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_revslider_sliders"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_revslider_slides'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_revslider_slides"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_revslider_static_slides'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_revslider_static_slides"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_rg_form'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_rg_form"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_rg_form_meta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_rg_form_meta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_rg_form_view'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_rg_form_view"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_rg_incomplete_submissions'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_rg_incomplete_submissions"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_rg_lead'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_rg_lead"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_rg_lead_detail'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_rg_lead_detail"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_rg_lead_detail_long'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_rg_lead_detail_long"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_rg_lead_meta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_rg_lead_meta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_rg_lead_notes'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_rg_lead_notes"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_term_relationships'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_term_relationships"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_term_taxonomy'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_term_taxonomy"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_termmeta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_termmeta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_8_terms'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_8_terms"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_gf_draft_submissions'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_gf_draft_submissions"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_gf_entry'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_gf_entry"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_gf_entry_meta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_gf_entry_meta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_gf_entry_notes'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_gf_entry_notes"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_gf_form'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_gf_form"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_gf_form_meta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_gf_form_meta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_gf_form_revisions'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_gf_form_revisions"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_gf_form_view'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_gf_form_view"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_mailpoet_custom_fields'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_mailpoet_custom_fields"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_mailpoet_forms'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_mailpoet_forms"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_mailpoet_log'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_mailpoet_log"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_mailpoet_mapping_to_external_entities'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_mailpoet_mapping_to_external_entities"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_mailpoet_newsletter_links'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_mailpoet_newsletter_links"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_mailpoet_newsletter_option'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_mailpoet_newsletter_option"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_mailpoet_newsletter_option_fields'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_mailpoet_newsletter_option_fields"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_mailpoet_newsletter_posts'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_mailpoet_newsletter_posts"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_mailpoet_newsletter_segment'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_mailpoet_newsletter_segment"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_mailpoet_newsletter_templates'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_mailpoet_newsletter_templates"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_mailpoet_newsletters'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_mailpoet_newsletters"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_mailpoet_scheduled_task_subscribers'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_mailpoet_scheduled_task_subscribers"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_mailpoet_scheduled_tasks'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_mailpoet_scheduled_tasks"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_mailpoet_segments'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_mailpoet_segments"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_mailpoet_sending_queues'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_mailpoet_sending_queues"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_mailpoet_settings'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_mailpoet_settings"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_mailpoet_statistics_clicks'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_mailpoet_statistics_clicks"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_mailpoet_statistics_forms'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_mailpoet_statistics_forms"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_mailpoet_statistics_newsletters'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_mailpoet_statistics_newsletters"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_mailpoet_statistics_opens'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_mailpoet_statistics_opens"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_mailpoet_statistics_unsubscribes'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_mailpoet_statistics_unsubscribes"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_mailpoet_subscriber_custom_field'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_mailpoet_subscriber_custom_field"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_mailpoet_subscriber_ips'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_mailpoet_subscriber_ips"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_mailpoet_subscriber_segment'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_mailpoet_subscriber_segment"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_mailpoet_subscribers'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_mailpoet_subscribers"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_mediafromftp_log'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_mediafromftp_log"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_wpgmza'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_wpgmza"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_wpgmza_categories'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_wpgmza_categories"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_wpgmza_category_maps'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_wpgmza_category_maps"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_wpgmza_datasets'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_wpgmza_datasets"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_wpgmza_maps'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_wpgmza_maps"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_wpgmza_polygon'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_wpgmza_polygon"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_9_wpgmza_polylines'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_9_wpgmza_polylines"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_gf_draft_submissions'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_gf_draft_submissions"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_gf_entry'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_gf_entry"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_gf_entry_meta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_gf_entry_meta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_gf_entry_notes'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_gf_entry_notes"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_gf_form'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_gf_form"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_gf_form_meta'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_gf_form_meta"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_gf_form_revisions'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_gf_form_revisions"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_gf_form_view'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_gf_form_view"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_imagify_files'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_imagify_files"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_imagify_folders'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_imagify_folders"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_mailpoet_custom_fields'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_mailpoet_custom_fields"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_mailpoet_forms'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_mailpoet_forms"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_mailpoet_log'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_mailpoet_log"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_mailpoet_mapping_to_external_entities'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_mailpoet_mapping_to_external_entities"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_mailpoet_newsletter_links'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_mailpoet_newsletter_links"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_mailpoet_newsletter_option'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_mailpoet_newsletter_option"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_mailpoet_newsletter_option_fields'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_mailpoet_newsletter_option_fields"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_mailpoet_newsletter_posts'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_mailpoet_newsletter_posts"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_mailpoet_newsletter_segment'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_mailpoet_newsletter_segment"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_mailpoet_newsletter_templates'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_mailpoet_newsletter_templates"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_mailpoet_newsletters'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_mailpoet_newsletters"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_mailpoet_scheduled_task_subscribers'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_mailpoet_scheduled_task_subscribers"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_mailpoet_scheduled_tasks'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_mailpoet_scheduled_tasks"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_mailpoet_segments'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_mailpoet_segments"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_mailpoet_sending_queues'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_mailpoet_sending_queues"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_mailpoet_settings'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_mailpoet_settings"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_mailpoet_statistics_clicks'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_mailpoet_statistics_clicks"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_mailpoet_statistics_forms'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_mailpoet_statistics_forms"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_mailpoet_statistics_newsletters'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_mailpoet_statistics_newsletters"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_mailpoet_statistics_opens'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_mailpoet_statistics_opens"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_mailpoet_statistics_unsubscribes'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_mailpoet_statistics_unsubscribes"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_mailpoet_subscriber_custom_field'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_mailpoet_subscriber_custom_field"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_mailpoet_subscriber_ips'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_mailpoet_subscriber_ips"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_mailpoet_subscriber_segment'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_mailpoet_subscriber_segment"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_mailpoet_subscribers'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_mailpoet_subscribers"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_mbdb_books'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_mbdb_books"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_mbdbma_authors'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_mbdbma_authors"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_mediafromftp_log'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_mediafromftp_log"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_wpgmza'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_wpgmza"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_wpgmza_categories'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_wpgmza_categories"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_wpgmza_category_maps'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_wpgmza_category_maps"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_wpgmza_datasets'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_wpgmza_datasets"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_wpgmza_maps'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_wpgmza_maps"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_wpgmza_polygon'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_wpgmza_polygon"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_wpgmza_polylines'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_wpgmza_polylines"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_wsal_metadata'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_wsal_metadata"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_wsal_occurrences'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_wsal_occurrences"', ignored.
database_1   | 2019-03-03 11:53:24 7fcad12a7780  InnoDB: Operating system error number 13 in a file operation.
database_1   | InnoDB: The error means mysqld does not have the access rights to
database_1   | InnoDB: the directory.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Could not find a valid tablespace file for 'wordpress/stjean_wsal_options'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] InnoDB: Tablespace open failed for '"wordpress"."stjean_wsal_options"', ignored.
database_1   | 2019-03-03 11:53:24 140509069342592 [Note] InnoDB: 128 rollback segment(s) are active.
database_1   | 2019-03-03 11:53:24 140509069342592 [Note] InnoDB: Waiting for purge to start
database_1   | 2019-03-03 11:53:24 140509069342592 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.42-84.2 started; log sequence number 359695675
database_1   | 2019-03-03 11:53:24 140509069342592 [Note] Plugin 'FEEDBACK' is disabled.
database_1   | 2019-03-03 11:53:24 140508328359680 [Note] InnoDB: Dumping buffer pool(s) not yet started
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
database_1   | 2019-03-03 11:53:24 140509069342592 [Note] Server socket created on IP: '0.0.0.0'.
database_1   | 2019-03-03 11:53:24 140509069342592 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist
database_1   | chmod: changing permissions of '/helpers/add-cert.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/auth.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/binding.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/generate-key.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/get-remote-url.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/lando-entrypoint.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/load-keys.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/mounter.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/pantheon.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/pull.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/push.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/refresh-certs.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/setup-ca.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/sql-export.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/sql-import.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/switch.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/user-perm-helpers.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/user-perms.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/user-perms.sh': Operation not permitted
database_1   | chmod: changing permissions of '/scripts/load-keys.sh': Operation not permitted
database_1   | mkdir: cannot create directory '/etc/ssh': Permission denied
database_1   | Running command /entrypoint.sh /run.sh
database_1   | Running with exec!
database_1   | 
database_1   | Welcome to the Bitnami mariadb container
database_1   | Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-mariadb
database_1   | Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-mariadb/issues
database_1   | Send us your feedback at containers@bitnami.com
database_1   | 
database_1   | INFO  ==> ** Starting MariaDB setup **
database_1   | INFO  ==> Validating settings in MYSQL_*/MARIADB_* env vars..
database_1   | WARN  ==> You set the environment variable ALLOW_EMPTY_PASSWORD=yes. For safety reasons, do not use this flag in a production environment.
database_1   | INFO  ==> Initializing mariadb database...
database_1   | DEBUG ==> Custom configuration detected. Injecting...
database_1   | DEBUG ==> Ensuring expected directories/files exist...
database_1   | INFO  ==> Persisted data detected. Restoring...
database_1   | 
database_1   | INFO  ==> Stopping mariadb...
database_1   | INFO  ==> ** MariaDB setup finished! **
database_1   | INFO  ==> ** Starting MariaDB **
database_1   | 2019-03-03 11:53:36 140448170350464 [Note] /opt/bitnami/mariadb/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 1 ...
database_1   | 2019-03-03 11:53:36 140448170350464 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
database_1   | 
database_1   | 2019-03-03 11:53:36 140448170350464 [Note] InnoDB: Using mutexes to ref count buffer pool pages
database_1   | 2019-03-03 11:53:36 140448170350464 [Note] InnoDB: The InnoDB memory heap is disabled
database_1   | 2019-03-03 11:53:36 140448170350464 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
database_1   | 2019-03-03 11:53:36 140448170350464 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
database_1   | 2019-03-03 11:53:36 140448170350464 [Note] InnoDB: Compressed tables use zlib 1.2.8
database_1   | 2019-03-03 11:53:36 140448170350464 [Note] InnoDB: Using Linux native AIO
database_1   | 2019-03-03 11:53:36 140448170350464 [Note] InnoDB: Using SSE crc32 instructions
database_1   | 2019-03-03 11:53:36 140448170350464 [Note] InnoDB: Initializing buffer pool, size = 128.0M
database_1   | 2019-03-03 11:53:36 140448170350464 [Note] InnoDB: Completed initialization of buffer pool
database_1   | 2019-03-03 11:53:36 140448170350464 [Note] InnoDB: Highest supported file format is Barracuda.
database_1   | 2019-03-03 11:53:36 140448170350464 [Note] InnoDB: The log sequence number 359695675 in ibdata file do not match the log sequence number 359695685 in the ib_logfiles!
database_1   | 2019-03-03 11:53:36 140448170350464 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table mysql/gtid_slave_pos in the InnoDB data dictionary has tablespace id 3, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table mysql/innodb_index_stats in the InnoDB data dictionary has tablespace id 2, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table mysql/innodb_table_stats in the InnoDB data dictionary has tablespace id 1, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_commentmeta in the InnoDB data dictionary has tablespace id 4, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_comments in the InnoDB data dictionary has tablespace id 5, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_gf_draft_submissions in the InnoDB data dictionary has tablespace id 6, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_gf_entry in the InnoDB data dictionary has tablespace id 7, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_gf_entry_meta in the InnoDB data dictionary has tablespace id 8, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_gf_entry_notes in the InnoDB data dictionary has tablespace id 9, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_gf_form in the InnoDB data dictionary has tablespace id 10, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_gf_form_meta in the InnoDB data dictionary has tablespace id 11, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_gf_form_revisions in the InnoDB data dictionary has tablespace id 12, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_gf_form_view in the InnoDB data dictionary has tablespace id 13, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_links in the InnoDB data dictionary has tablespace id 14, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_custom_fields in the InnoDB data dictionary has tablespace id 15, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_forms in the InnoDB data dictionary has tablespace id 16, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_log in the InnoDB data dictionary has tablespace id 17, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_mapping_to_external_entities in the InnoDB data dictionary has tablespace id 18, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_newsletter_links in the InnoDB data dictionary has tablespace id 19, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_newsletter_option in the InnoDB data dictionary has tablespace id 20, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_newsletter_option_fields in the InnoDB data dictionary has tablespace id 21, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_newsletter_posts in the InnoDB data dictionary has tablespace id 22, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_newsletter_segment in the InnoDB data dictionary has tablespace id 23, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_newsletter_templates in the InnoDB data dictionary has tablespace id 24, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_newsletters in the InnoDB data dictionary has tablespace id 25, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_scheduled_task_subscribers in the InnoDB data dictionary has tablespace id 26, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_scheduled_tasks in the InnoDB data dictionary has tablespace id 27, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_segments in the InnoDB data dictionary has tablespace id 28, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_sending_queues in the InnoDB data dictionary has tablespace id 29, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_settings in the InnoDB data dictionary has tablespace id 30, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_statistics_clicks in the InnoDB data dictionary has tablespace id 31, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_statistics_forms in the InnoDB data dictionary has tablespace id 32, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_statistics_newsletters in the InnoDB data dictionary has tablespace id 33, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_statistics_opens in the InnoDB data dictionary has tablespace id 34, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_statistics_unsubscribes in the InnoDB data dictionary has tablespace id 35, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_subscriber_custom_field in the InnoDB data dictionary has tablespace id 36, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_subscriber_ips in the InnoDB data dictionary has tablespace id 37, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_subscriber_segment in the InnoDB data dictionary has tablespace id 38, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_subscribers in the InnoDB data dictionary has tablespace id 39, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_mbdb_books in the InnoDB data dictionary has tablespace id 40, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_mbdbma_authors in the InnoDB data dictionary has tablespace id 41, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_mediafromftp_log in the InnoDB data dictionary has tablespace id 42, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_options in the InnoDB data dictionary has tablespace id 43, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_postmeta in the InnoDB data dictionary has tablespace id 44, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_posts in the InnoDB data dictionary has tablespace id 45, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_redirection_404 in the InnoDB data dictionary has tablespace id 46, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_redirection_groups in the InnoDB data dictionary has tablespace id 47, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_redirection_items in the InnoDB data dictionary has tablespace id 48, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_redirection_logs in the InnoDB data dictionary has tablespace id 49, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_revslider_css in the InnoDB data dictionary has tablespace id 50, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_revslider_layer_animations in the InnoDB data dictionary has tablespace id 51, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_revslider_navigations in the InnoDB data dictionary has tablespace id 52, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_revslider_sliders in the InnoDB data dictionary has tablespace id 53, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_revslider_slides in the InnoDB data dictionary has tablespace id 54, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_revslider_static_slides in the InnoDB data dictionary has tablespace id 55, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_term_relationships in the InnoDB data dictionary has tablespace id 56, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_term_taxonomy in the InnoDB data dictionary has tablespace id 57, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_termmeta in the InnoDB data dictionary has tablespace id 58, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_10_terms in the InnoDB data dictionary has tablespace id 59, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_gf_draft_submissions in the InnoDB data dictionary has tablespace id 60, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_gf_entry in the InnoDB data dictionary has tablespace id 61, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_gf_entry_meta in the InnoDB data dictionary has tablespace id 62, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_gf_entry_notes in the InnoDB data dictionary has tablespace id 63, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_gf_form in the InnoDB data dictionary has tablespace id 64, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_gf_form_meta in the InnoDB data dictionary has tablespace id 65, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_gf_form_revisions in the InnoDB data dictionary has tablespace id 66, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_gf_form_view in the InnoDB data dictionary has tablespace id 67, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_custom_fields in the InnoDB data dictionary has tablespace id 68, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_forms in the InnoDB data dictionary has tablespace id 69, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_log in the InnoDB data dictionary has tablespace id 70, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_mapping_to_external_entities in the InnoDB data dictionary has tablespace id 71, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_newsletter_links in the InnoDB data dictionary has tablespace id 72, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_newsletter_option in the InnoDB data dictionary has tablespace id 73, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_newsletter_option_fields in the InnoDB data dictionary has tablespace id 74, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_newsletter_posts in the InnoDB data dictionary has tablespace id 75, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_newsletter_segment in the InnoDB data dictionary has tablespace id 76, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_newsletter_templates in the InnoDB data dictionary has tablespace id 77, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_newsletters in the InnoDB data dictionary has tablespace id 78, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_scheduled_task_subscribers in the InnoDB data dictionary has tablespace id 79, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_scheduled_tasks in the InnoDB data dictionary has tablespace id 80, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_segments in the InnoDB data dictionary has tablespace id 81, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_sending_queues in the InnoDB data dictionary has tablespace id 82, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_settings in the InnoDB data dictionary has tablespace id 83, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_statistics_clicks in the InnoDB data dictionary has tablespace id 84, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_statistics_forms in the InnoDB data dictionary has tablespace id 85, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_statistics_newsletters in the InnoDB data dictionary has tablespace id 86, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_statistics_opens in the InnoDB data dictionary has tablespace id 87, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_statistics_unsubscribes in the InnoDB data dictionary has tablespace id 88, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_subscriber_custom_field in the InnoDB data dictionary has tablespace id 89, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_subscriber_ips in the InnoDB data dictionary has tablespace id 90, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_subscriber_segment in the InnoDB data dictionary has tablespace id 91, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_subscribers in the InnoDB data dictionary has tablespace id 92, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_mediafromftp_log in the InnoDB data dictionary has tablespace id 93, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_wpgmza in the InnoDB data dictionary has tablespace id 94, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_wpgmza_categories in the InnoDB data dictionary has tablespace id 95, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_wpgmza_category_maps in the InnoDB data dictionary has tablespace id 96, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_wpgmza_datasets in the InnoDB data dictionary has tablespace id 97, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_wpgmza_maps in the InnoDB data dictionary has tablespace id 98, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_wpgmza_polygon in the InnoDB data dictionary has tablespace id 99, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_11_wpgmza_polylines in the InnoDB data dictionary has tablespace id 100, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_12_commentmeta in the InnoDB data dictionary has tablespace id 101, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_12_comments in the InnoDB data dictionary has tablespace id 102, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_12_gf_draft_submissions in the InnoDB data dictionary has tablespace id 103, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_12_gf_entry in the InnoDB data dictionary has tablespace id 104, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_12_gf_entry_meta in the InnoDB data dictionary has tablespace id 105, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_12_gf_entry_notes in the InnoDB data dictionary has tablespace id 106, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_12_gf_form in the InnoDB data dictionary has tablespace id 107, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_12_gf_form_meta in the InnoDB data dictionary has tablespace id 108, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_12_gf_form_revisions in the InnoDB data dictionary has tablespace id 109, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_12_gf_form_view in the InnoDB data dictionary has tablespace id 110, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_12_links in the InnoDB data dictionary has tablespace id 111, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_12_options in the InnoDB data dictionary has tablespace id 112, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_12_postmeta in the InnoDB data dictionary has tablespace id 113, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_12_posts in the InnoDB data dictionary has tablespace id 114, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_12_revslider_css in the InnoDB data dictionary has tablespace id 115, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_12_revslider_layer_animations in the InnoDB data dictionary has tablespace id 116, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_12_revslider_navigations in the InnoDB data dictionary has tablespace id 117, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_12_revslider_sliders in the InnoDB data dictionary has tablespace id 118, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_12_revslider_slides in the InnoDB data dictionary has tablespace id 119, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_12_revslider_static_slides in the InnoDB data dictionary has tablespace id 120, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_12_term_relationships in the InnoDB data dictionary has tablespace id 121, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_12_term_taxonomy in the InnoDB data dictionary has tablespace id 122, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_12_termmeta in the InnoDB data dictionary has tablespace id 123, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_12_terms in the InnoDB data dictionary has tablespace id 124, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_gf_draft_submissions in the InnoDB data dictionary has tablespace id 125, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_gf_entry in the InnoDB data dictionary has tablespace id 126, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_gf_entry_meta in the InnoDB data dictionary has tablespace id 127, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_gf_entry_notes in the InnoDB data dictionary has tablespace id 128, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_gf_form in the InnoDB data dictionary has tablespace id 129, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_gf_form_meta in the InnoDB data dictionary has tablespace id 130, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_gf_form_revisions in the InnoDB data dictionary has tablespace id 131, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_gf_form_view in the InnoDB data dictionary has tablespace id 132, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_custom_fields in the InnoDB data dictionary has tablespace id 133, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_forms in the InnoDB data dictionary has tablespace id 134, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_log in the InnoDB data dictionary has tablespace id 135, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_mapping_to_external_entities in the InnoDB data dictionary has tablespace id 136, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_newsletter_links in the InnoDB data dictionary has tablespace id 137, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_newsletter_option in the InnoDB data dictionary has tablespace id 138, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_newsletter_option_fields in the InnoDB data dictionary has tablespace id 139, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_newsletter_posts in the InnoDB data dictionary has tablespace id 140, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_newsletter_segment in the InnoDB data dictionary has tablespace id 141, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_newsletter_templates in the InnoDB data dictionary has tablespace id 142, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_newsletters in the InnoDB data dictionary has tablespace id 143, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_scheduled_task_subscribers in the InnoDB data dictionary has tablespace id 144, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_scheduled_tasks in the InnoDB data dictionary has tablespace id 145, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_segments in the InnoDB data dictionary has tablespace id 146, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_sending_queues in the InnoDB data dictionary has tablespace id 147, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_settings in the InnoDB data dictionary has tablespace id 148, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_statistics_clicks in the InnoDB data dictionary has tablespace id 149, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_statistics_forms in the InnoDB data dictionary has tablespace id 150, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_statistics_newsletters in the InnoDB data dictionary has tablespace id 151, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_statistics_opens in the InnoDB data dictionary has tablespace id 152, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_statistics_unsubscribes in the InnoDB data dictionary has tablespace id 153, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_subscriber_custom_field in the InnoDB data dictionary has tablespace id 154, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_subscriber_ips in the InnoDB data dictionary has tablespace id 155, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_subscriber_segment in the InnoDB data dictionary has tablespace id 156, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_subscribers in the InnoDB data dictionary has tablespace id 157, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_mediafromftp_log in the InnoDB data dictionary has tablespace id 158, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_wpgmza in the InnoDB data dictionary has tablespace id 159, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_wpgmza_categories in the InnoDB data dictionary has tablespace id 160, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_wpgmza_category_maps in the InnoDB data dictionary has tablespace id 161, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_wpgmza_datasets in the InnoDB data dictionary has tablespace id 162, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_wpgmza_maps in the InnoDB data dictionary has tablespace id 163, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_wpgmza_polygon in the InnoDB data dictionary has tablespace id 164, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_2_wpgmza_polylines in the InnoDB data dictionary has tablespace id 165, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_gf_draft_submissions in the InnoDB data dictionary has tablespace id 166, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_gf_entry in the InnoDB data dictionary has tablespace id 167, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_gf_entry_meta in the InnoDB data dictionary has tablespace id 168, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_gf_entry_notes in the InnoDB data dictionary has tablespace id 169, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_gf_form in the InnoDB data dictionary has tablespace id 170, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_gf_form_meta in the InnoDB data dictionary has tablespace id 171, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_gf_form_revisions in the InnoDB data dictionary has tablespace id 172, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_gf_form_view in the InnoDB data dictionary has tablespace id 173, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_custom_fields in the InnoDB data dictionary has tablespace id 174, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_dynamic_segment_filters in the InnoDB data dictionary has tablespace id 175, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_forms in the InnoDB data dictionary has tablespace id 176, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_log in the InnoDB data dictionary has tablespace id 177, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_mapping_to_external_entities in the InnoDB data dictionary has tablespace id 178, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_newsletter_links in the InnoDB data dictionary has tablespace id 179, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_newsletter_option in the InnoDB data dictionary has tablespace id 180, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_newsletter_option_fields in the InnoDB data dictionary has tablespace id 181, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_newsletter_posts in the InnoDB data dictionary has tablespace id 182, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_newsletter_segment in the InnoDB data dictionary has tablespace id 183, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_newsletter_templates in the InnoDB data dictionary has tablespace id 184, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_newsletters in the InnoDB data dictionary has tablespace id 185, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_premium_newsletter_extra_data in the InnoDB data dictionary has tablespace id 186, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_scheduled_task_subscribers in the InnoDB data dictionary has tablespace id 187, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_scheduled_tasks in the InnoDB data dictionary has tablespace id 188, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_segments in the InnoDB data dictionary has tablespace id 189, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_sending_queues in the InnoDB data dictionary has tablespace id 190, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_settings in the InnoDB data dictionary has tablespace id 191, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_statistics_clicks in the InnoDB data dictionary has tablespace id 192, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_statistics_forms in the InnoDB data dictionary has tablespace id 193, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_statistics_newsletters in the InnoDB data dictionary has tablespace id 194, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_statistics_opens in the InnoDB data dictionary has tablespace id 195, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_statistics_unsubscribes in the InnoDB data dictionary has tablespace id 196, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_subscriber_custom_field in the InnoDB data dictionary has tablespace id 197, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_subscriber_ips in the InnoDB data dictionary has tablespace id 198, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_subscriber_segment in the InnoDB data dictionary has tablespace id 199, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_subscribers in the InnoDB data dictionary has tablespace id 200, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mbdbma_authors in the InnoDB data dictionary has tablespace id 201, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_mediafromftp_log in the InnoDB data dictionary has tablespace id 202, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_wpgmza in the InnoDB data dictionary has tablespace id 203, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_wpgmza_categories in the InnoDB data dictionary has tablespace id 204, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_wpgmza_category_maps in the InnoDB data dictionary has tablespace id 205, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_wpgmza_datasets in the InnoDB data dictionary has tablespace id 206, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_wpgmza_maps in the InnoDB data dictionary has tablespace id 207, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_wpgmza_polygon in the InnoDB data dictionary has tablespace id 208, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_3_wpgmza_polylines in the InnoDB data dictionary has tablespace id 209, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_gf_draft_submissions in the InnoDB data dictionary has tablespace id 210, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_gf_entry in the InnoDB data dictionary has tablespace id 211, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_gf_entry_meta in the InnoDB data dictionary has tablespace id 212, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_gf_entry_notes in the InnoDB data dictionary has tablespace id 213, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_gf_form in the InnoDB data dictionary has tablespace id 214, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_gf_form_meta in the InnoDB data dictionary has tablespace id 215, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_gf_form_view in the InnoDB data dictionary has tablespace id 216, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_custom_fields in the InnoDB data dictionary has tablespace id 217, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_forms in the InnoDB data dictionary has tablespace id 218, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_log in the InnoDB data dictionary has tablespace id 219, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_mapping_to_external_entities in the InnoDB data dictionary has tablespace id 220, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_newsletter_links in the InnoDB data dictionary has tablespace id 221, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_newsletter_option in the InnoDB data dictionary has tablespace id 222, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_newsletter_option_fields in the InnoDB data dictionary has tablespace id 223, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_newsletter_posts in the InnoDB data dictionary has tablespace id 224, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_newsletter_segment in the InnoDB data dictionary has tablespace id 225, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_newsletter_templates in the InnoDB data dictionary has tablespace id 226, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_newsletters in the InnoDB data dictionary has tablespace id 227, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_scheduled_task_subscribers in the InnoDB data dictionary has tablespace id 228, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_scheduled_tasks in the InnoDB data dictionary has tablespace id 229, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_segments in the InnoDB data dictionary has tablespace id 230, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_sending_queues in the InnoDB data dictionary has tablespace id 231, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_settings in the InnoDB data dictionary has tablespace id 232, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_statistics_clicks in the InnoDB data dictionary has tablespace id 233, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_statistics_forms in the InnoDB data dictionary has tablespace id 234, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_statistics_newsletters in the InnoDB data dictionary has tablespace id 235, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_statistics_opens in the InnoDB data dictionary has tablespace id 236, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_statistics_unsubscribes in the InnoDB data dictionary has tablespace id 237, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_subscriber_custom_field in the InnoDB data dictionary has tablespace id 238, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_subscriber_ips in the InnoDB data dictionary has tablespace id 239, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_subscriber_segment in the InnoDB data dictionary has tablespace id 240, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_subscribers in the InnoDB data dictionary has tablespace id 241, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_mbdbma_authors in the InnoDB data dictionary has tablespace id 242, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_mediafromftp_log in the InnoDB data dictionary has tablespace id 243, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_wpgmza in the InnoDB data dictionary has tablespace id 244, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_wpgmza_categories in the InnoDB data dictionary has tablespace id 245, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_wpgmza_category_maps in the InnoDB data dictionary has tablespace id 246, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_wpgmza_datasets in the InnoDB data dictionary has tablespace id 247, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_wpgmza_maps in the InnoDB data dictionary has tablespace id 248, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_wpgmza_polygon in the InnoDB data dictionary has tablespace id 249, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_4_wpgmza_polylines in the InnoDB data dictionary has tablespace id 250, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_gf_draft_submissions in the InnoDB data dictionary has tablespace id 251, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_gf_entry in the InnoDB data dictionary has tablespace id 252, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_gf_entry_meta in the InnoDB data dictionary has tablespace id 253, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_gf_entry_notes in the InnoDB data dictionary has tablespace id 254, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_gf_form in the InnoDB data dictionary has tablespace id 255, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_gf_form_meta in the InnoDB data dictionary has tablespace id 256, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_gf_form_revisions in the InnoDB data dictionary has tablespace id 257, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_gf_form_view in the InnoDB data dictionary has tablespace id 258, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_custom_fields in the InnoDB data dictionary has tablespace id 259, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_forms in the InnoDB data dictionary has tablespace id 260, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_log in the InnoDB data dictionary has tablespace id 261, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_mapping_to_external_entities in the InnoDB data dictionary has tablespace id 262, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_newsletter_links in the InnoDB data dictionary has tablespace id 263, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_newsletter_option in the InnoDB data dictionary has tablespace id 264, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_newsletter_option_fields in the InnoDB data dictionary has tablespace id 265, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_newsletter_posts in the InnoDB data dictionary has tablespace id 266, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_newsletter_segment in the InnoDB data dictionary has tablespace id 267, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_newsletter_templates in the InnoDB data dictionary has tablespace id 268, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_newsletters in the InnoDB data dictionary has tablespace id 269, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_scheduled_task_subscribers in the InnoDB data dictionary has tablespace id 270, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_scheduled_tasks in the InnoDB data dictionary has tablespace id 271, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_segments in the InnoDB data dictionary has tablespace id 272, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_sending_queues in the InnoDB data dictionary has tablespace id 273, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_settings in the InnoDB data dictionary has tablespace id 274, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_statistics_clicks in the InnoDB data dictionary has tablespace id 275, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_statistics_forms in the InnoDB data dictionary has tablespace id 276, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_statistics_newsletters in the InnoDB data dictionary has tablespace id 277, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_statistics_opens in the InnoDB data dictionary has tablespace id 278, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_statistics_unsubscribes in the InnoDB data dictionary has tablespace id 279, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_subscriber_custom_field in the InnoDB data dictionary has tablespace id 280, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_subscriber_ips in the InnoDB data dictionary has tablespace id 281, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_subscriber_segment in the InnoDB data dictionary has tablespace id 282, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_subscribers in the InnoDB data dictionary has tablespace id 283, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_mbdb_books in the InnoDB data dictionary has tablespace id 284, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_mbdbma_authors in the InnoDB data dictionary has tablespace id 285, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_mediafromftp_log in the InnoDB data dictionary has tablespace id 286, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_wpgmza in the InnoDB data dictionary has tablespace id 287, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_wpgmza_categories in the InnoDB data dictionary has tablespace id 288, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_wpgmza_category_maps in the InnoDB data dictionary has tablespace id 289, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_wpgmza_datasets in the InnoDB data dictionary has tablespace id 290, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_wpgmza_maps in the InnoDB data dictionary has tablespace id 291, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_wpgmza_polygon in the InnoDB data dictionary has tablespace id 292, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_5_wpgmza_polylines in the InnoDB data dictionary has tablespace id 293, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_gf_draft_submissions in the InnoDB data dictionary has tablespace id 294, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_gf_entry in the InnoDB data dictionary has tablespace id 295, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_gf_entry_meta in the InnoDB data dictionary has tablespace id 296, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_gf_entry_notes in the InnoDB data dictionary has tablespace id 297, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_gf_form in the InnoDB data dictionary has tablespace id 298, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_gf_form_meta in the InnoDB data dictionary has tablespace id 299, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_gf_form_revisions in the InnoDB data dictionary has tablespace id 300, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_gf_form_view in the InnoDB data dictionary has tablespace id 301, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_mailpoet_custom_fields in the InnoDB data dictionary has tablespace id 302, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_mailpoet_forms in the InnoDB data dictionary has tablespace id 303, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_mailpoet_log in the InnoDB data dictionary has tablespace id 304, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_mailpoet_mapping_to_external_entities in the InnoDB data dictionary has tablespace id 305, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_mailpoet_newsletter_links in the InnoDB data dictionary has tablespace id 306, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_mailpoet_newsletter_option in the InnoDB data dictionary has tablespace id 307, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_mailpoet_newsletter_option_fields in the InnoDB data dictionary has tablespace id 308, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_mailpoet_newsletter_posts in the InnoDB data dictionary has tablespace id 309, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_mailpoet_newsletter_segment in the InnoDB data dictionary has tablespace id 310, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_mailpoet_newsletter_templates in the InnoDB data dictionary has tablespace id 311, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_mailpoet_newsletters in the InnoDB data dictionary has tablespace id 312, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_mailpoet_scheduled_task_subscribers in the InnoDB data dictionary has tablespace id 313, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_mailpoet_scheduled_tasks in the InnoDB data dictionary has tablespace id 314, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_mailpoet_segments in the InnoDB data dictionary has tablespace id 315, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_mailpoet_sending_queues in the InnoDB data dictionary has tablespace id 316, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_mailpoet_settings in the InnoDB data dictionary has tablespace id 317, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_mailpoet_statistics_clicks in the InnoDB data dictionary has tablespace id 318, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_mailpoet_statistics_forms in the InnoDB data dictionary has tablespace id 319, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_mailpoet_statistics_newsletters in the InnoDB data dictionary has tablespace id 320, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_mailpoet_statistics_opens in the InnoDB data dictionary has tablespace id 321, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_mailpoet_statistics_unsubscribes in the InnoDB data dictionary has tablespace id 322, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_mailpoet_subscriber_custom_field in the InnoDB data dictionary has tablespace id 323, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_mailpoet_subscriber_ips in the InnoDB data dictionary has tablespace id 324, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_mailpoet_subscriber_segment in the InnoDB data dictionary has tablespace id 325, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_mailpoet_subscribers in the InnoDB data dictionary has tablespace id 326, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_mbdb_books in the InnoDB data dictionary has tablespace id 327, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_mbdbma_authors in the InnoDB data dictionary has tablespace id 328, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_mediafromftp_log in the InnoDB data dictionary has tablespace id 329, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_wpgmza in the InnoDB data dictionary has tablespace id 330, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_wpgmza_categories in the InnoDB data dictionary has tablespace id 331, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_wpgmza_category_maps in the InnoDB data dictionary has tablespace id 332, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_wpgmza_datasets in the InnoDB data dictionary has tablespace id 333, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_wpgmza_maps in the InnoDB data dictionary has tablespace id 334, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_wpgmza_polygon in the InnoDB data dictionary has tablespace id 335, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_6_wpgmza_polylines in the InnoDB data dictionary has tablespace id 336, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_gf_draft_submissions in the InnoDB data dictionary has tablespace id 337, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_gf_entry in the InnoDB data dictionary has tablespace id 338, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_gf_entry_meta in the InnoDB data dictionary has tablespace id 339, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_gf_entry_notes in the InnoDB data dictionary has tablespace id 340, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_gf_form in the InnoDB data dictionary has tablespace id 341, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_gf_form_meta in the InnoDB data dictionary has tablespace id 342, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_gf_form_revisions in the InnoDB data dictionary has tablespace id 343, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_gf_form_view in the InnoDB data dictionary has tablespace id 344, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_mailpoet_custom_fields in the InnoDB data dictionary has tablespace id 345, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_mailpoet_forms in the InnoDB data dictionary has tablespace id 346, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_mailpoet_log in the InnoDB data dictionary has tablespace id 347, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_mailpoet_mapping_to_external_entities in the InnoDB data dictionary has tablespace id 348, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_mailpoet_newsletter_links in the InnoDB data dictionary has tablespace id 349, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_mailpoet_newsletter_option in the InnoDB data dictionary has tablespace id 350, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_mailpoet_newsletter_option_fields in the InnoDB data dictionary has tablespace id 351, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_mailpoet_newsletter_posts in the InnoDB data dictionary has tablespace id 352, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_mailpoet_newsletter_segment in the InnoDB data dictionary has tablespace id 353, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_mailpoet_newsletter_templates in the InnoDB data dictionary has tablespace id 354, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_mailpoet_newsletters in the InnoDB data dictionary has tablespace id 355, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_mailpoet_scheduled_task_subscribers in the InnoDB data dictionary has tablespace id 356, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_mailpoet_scheduled_tasks in the InnoDB data dictionary has tablespace id 357, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_mailpoet_segments in the InnoDB data dictionary has tablespace id 358, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_mailpoet_sending_queues in the InnoDB data dictionary has tablespace id 359, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_mailpoet_settings in the InnoDB data dictionary has tablespace id 360, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_mailpoet_statistics_clicks in the InnoDB data dictionary has tablespace id 361, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_mailpoet_statistics_forms in the InnoDB data dictionary has tablespace id 362, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_mailpoet_statistics_newsletters in the InnoDB data dictionary has tablespace id 363, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_mailpoet_statistics_opens in the InnoDB data dictionary has tablespace id 364, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_mailpoet_statistics_unsubscribes in the InnoDB data dictionary has tablespace id 365, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_mailpoet_subscriber_custom_field in the InnoDB data dictionary has tablespace id 366, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_mailpoet_subscriber_ips in the InnoDB data dictionary has tablespace id 367, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_mailpoet_subscriber_segment in the InnoDB data dictionary has tablespace id 368, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_mailpoet_subscribers in the InnoDB data dictionary has tablespace id 369, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_mbdbma_authors in the InnoDB data dictionary has tablespace id 370, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_mediafromftp_log in the InnoDB data dictionary has tablespace id 371, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_wpgmza in the InnoDB data dictionary has tablespace id 372, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_wpgmza_categories in the InnoDB data dictionary has tablespace id 373, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_wpgmza_category_maps in the InnoDB data dictionary has tablespace id 374, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_wpgmza_datasets in the InnoDB data dictionary has tablespace id 375, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_wpgmza_maps in the InnoDB data dictionary has tablespace id 376, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_wpgmza_polygon in the InnoDB data dictionary has tablespace id 377, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_7_wpgmza_polylines in the InnoDB data dictionary has tablespace id 378, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_commentmeta in the InnoDB data dictionary has tablespace id 379, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_comments in the InnoDB data dictionary has tablespace id 380, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_gf_draft_submissions in the InnoDB data dictionary has tablespace id 381, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_gf_entry in the InnoDB data dictionary has tablespace id 382, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_gf_entry_meta in the InnoDB data dictionary has tablespace id 383, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_gf_entry_notes in the InnoDB data dictionary has tablespace id 384, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_gf_form in the InnoDB data dictionary has tablespace id 385, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_gf_form_meta in the InnoDB data dictionary has tablespace id 386, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_gf_form_revisions in the InnoDB data dictionary has tablespace id 387, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_gf_form_view in the InnoDB data dictionary has tablespace id 388, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_links in the InnoDB data dictionary has tablespace id 389, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_mailpoet_custom_fields in the InnoDB data dictionary has tablespace id 390, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_mailpoet_forms in the InnoDB data dictionary has tablespace id 391, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_mailpoet_log in the InnoDB data dictionary has tablespace id 392, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_mailpoet_mapping_to_external_entities in the InnoDB data dictionary has tablespace id 393, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_mailpoet_newsletter_links in the InnoDB data dictionary has tablespace id 394, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_mailpoet_newsletter_option in the InnoDB data dictionary has tablespace id 395, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_mailpoet_newsletter_option_fields in the InnoDB data dictionary has tablespace id 396, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_mailpoet_newsletter_posts in the InnoDB data dictionary has tablespace id 397, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_mailpoet_newsletter_segment in the InnoDB data dictionary has tablespace id 398, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_mailpoet_newsletter_templates in the InnoDB data dictionary has tablespace id 399, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_mailpoet_newsletters in the InnoDB data dictionary has tablespace id 400, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_mailpoet_scheduled_task_subscribers in the InnoDB data dictionary has tablespace id 401, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_mailpoet_scheduled_tasks in the InnoDB data dictionary has tablespace id 402, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_mailpoet_segments in the InnoDB data dictionary has tablespace id 403, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_mailpoet_sending_queues in the InnoDB data dictionary has tablespace id 404, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_mailpoet_settings in the InnoDB data dictionary has tablespace id 405, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_mailpoet_statistics_clicks in the InnoDB data dictionary has tablespace id 406, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_mailpoet_statistics_forms in the InnoDB data dictionary has tablespace id 407, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_mailpoet_statistics_newsletters in the InnoDB data dictionary has tablespace id 408, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_mailpoet_statistics_opens in the InnoDB data dictionary has tablespace id 409, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_mailpoet_statistics_unsubscribes in the InnoDB data dictionary has tablespace id 410, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_mailpoet_subscriber_custom_field in the InnoDB data dictionary has tablespace id 411, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_mailpoet_subscriber_ips in the InnoDB data dictionary has tablespace id 412, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_mailpoet_subscriber_segment in the InnoDB data dictionary has tablespace id 413, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_mailpoet_subscribers in the InnoDB data dictionary has tablespace id 414, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_mbdb_books in the InnoDB data dictionary has tablespace id 415, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_mbdbma_authors in the InnoDB data dictionary has tablespace id 416, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_mediafromftp_log in the InnoDB data dictionary has tablespace id 417, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_options in the InnoDB data dictionary has tablespace id 418, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_postmeta in the InnoDB data dictionary has tablespace id 419, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_posts in the InnoDB data dictionary has tablespace id 420, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_redirection_404 in the InnoDB data dictionary has tablespace id 421, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_redirection_groups in the InnoDB data dictionary has tablespace id 422, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_redirection_items in the InnoDB data dictionary has tablespace id 423, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_redirection_logs in the InnoDB data dictionary has tablespace id 424, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_revslider_css in the InnoDB data dictionary has tablespace id 425, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_revslider_layer_animations in the InnoDB data dictionary has tablespace id 426, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_revslider_navigations in the InnoDB data dictionary has tablespace id 427, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_revslider_sliders in the InnoDB data dictionary has tablespace id 428, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_revslider_slides in the InnoDB data dictionary has tablespace id 429, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_revslider_static_slides in the InnoDB data dictionary has tablespace id 430, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_rg_form in the InnoDB data dictionary has tablespace id 431, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_rg_form_meta in the InnoDB data dictionary has tablespace id 432, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_rg_form_view in the InnoDB data dictionary has tablespace id 433, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_rg_incomplete_submissions in the InnoDB data dictionary has tablespace id 434, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_rg_lead in the InnoDB data dictionary has tablespace id 435, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_rg_lead_detail in the InnoDB data dictionary has tablespace id 436, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_rg_lead_detail_long in the InnoDB data dictionary has tablespace id 437, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_rg_lead_meta in the InnoDB data dictionary has tablespace id 438, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_rg_lead_notes in the InnoDB data dictionary has tablespace id 439, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_term_relationships in the InnoDB data dictionary has tablespace id 440, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_term_taxonomy in the InnoDB data dictionary has tablespace id 441, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_termmeta in the InnoDB data dictionary has tablespace id 442, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_8_terms in the InnoDB data dictionary has tablespace id 443, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_gf_draft_submissions in the InnoDB data dictionary has tablespace id 444, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_gf_entry in the InnoDB data dictionary has tablespace id 445, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_gf_entry_meta in the InnoDB data dictionary has tablespace id 446, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_gf_entry_notes in the InnoDB data dictionary has tablespace id 447, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_gf_form in the InnoDB data dictionary has tablespace id 448, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_gf_form_meta in the InnoDB data dictionary has tablespace id 449, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_gf_form_revisions in the InnoDB data dictionary has tablespace id 450, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_gf_form_view in the InnoDB data dictionary has tablespace id 451, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_mailpoet_custom_fields in the InnoDB data dictionary has tablespace id 452, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_mailpoet_forms in the InnoDB data dictionary has tablespace id 453, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_mailpoet_log in the InnoDB data dictionary has tablespace id 454, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_mailpoet_mapping_to_external_entities in the InnoDB data dictionary has tablespace id 455, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_mailpoet_newsletter_links in the InnoDB data dictionary has tablespace id 456, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_mailpoet_newsletter_option in the InnoDB data dictionary has tablespace id 457, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_mailpoet_newsletter_option_fields in the InnoDB data dictionary has tablespace id 458, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_mailpoet_newsletter_posts in the InnoDB data dictionary has tablespace id 459, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_mailpoet_newsletter_segment in the InnoDB data dictionary has tablespace id 460, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_mailpoet_newsletter_templates in the InnoDB data dictionary has tablespace id 461, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_mailpoet_newsletters in the InnoDB data dictionary has tablespace id 462, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_mailpoet_scheduled_task_subscribers in the InnoDB data dictionary has tablespace id 463, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_mailpoet_scheduled_tasks in the InnoDB data dictionary has tablespace id 464, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_mailpoet_segments in the InnoDB data dictionary has tablespace id 465, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_mailpoet_sending_queues in the InnoDB data dictionary has tablespace id 466, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_mailpoet_settings in the InnoDB data dictionary has tablespace id 467, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_mailpoet_statistics_clicks in the InnoDB data dictionary has tablespace id 468, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_mailpoet_statistics_forms in the InnoDB data dictionary has tablespace id 469, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_mailpoet_statistics_newsletters in the InnoDB data dictionary has tablespace id 470, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_mailpoet_statistics_opens in the InnoDB data dictionary has tablespace id 471, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_mailpoet_statistics_unsubscribes in the InnoDB data dictionary has tablespace id 472, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_mailpoet_subscriber_custom_field in the InnoDB data dictionary has tablespace id 473, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_mailpoet_subscriber_ips in the InnoDB data dictionary has tablespace id 474, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_mailpoet_subscriber_segment in the InnoDB data dictionary has tablespace id 475, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_mailpoet_subscribers in the InnoDB data dictionary has tablespace id 476, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_mediafromftp_log in the InnoDB data dictionary has tablespace id 477, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_wpgmza in the InnoDB data dictionary has tablespace id 478, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_wpgmza_categories in the InnoDB data dictionary has tablespace id 479, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_wpgmza_category_maps in the InnoDB data dictionary has tablespace id 480, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_wpgmza_datasets in the InnoDB data dictionary has tablespace id 481, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_wpgmza_maps in the InnoDB data dictionary has tablespace id 482, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_wpgmza_polygon in the InnoDB data dictionary has tablespace id 483, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_9_wpgmza_polylines in the InnoDB data dictionary has tablespace id 484, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_gf_draft_submissions in the InnoDB data dictionary has tablespace id 485, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_gf_entry in the InnoDB data dictionary has tablespace id 486, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_gf_entry_meta in the InnoDB data dictionary has tablespace id 487, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_gf_entry_notes in the InnoDB data dictionary has tablespace id 488, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_gf_form in the InnoDB data dictionary has tablespace id 489, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_gf_form_meta in the InnoDB data dictionary has tablespace id 490, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_gf_form_revisions in the InnoDB data dictionary has tablespace id 491, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_gf_form_view in the InnoDB data dictionary has tablespace id 492, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_imagify_files in the InnoDB data dictionary has tablespace id 493, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_imagify_folders in the InnoDB data dictionary has tablespace id 494, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_mailpoet_custom_fields in the InnoDB data dictionary has tablespace id 495, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_mailpoet_forms in the InnoDB data dictionary has tablespace id 496, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_mailpoet_log in the InnoDB data dictionary has tablespace id 497, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_mailpoet_mapping_to_external_entities in the InnoDB data dictionary has tablespace id 498, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_mailpoet_newsletter_links in the InnoDB data dictionary has tablespace id 499, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_mailpoet_newsletter_option in the InnoDB data dictionary has tablespace id 500, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_mailpoet_newsletter_option_fields in the InnoDB data dictionary has tablespace id 501, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_mailpoet_newsletter_posts in the InnoDB data dictionary has tablespace id 502, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_mailpoet_newsletter_segment in the InnoDB data dictionary has tablespace id 503, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_mailpoet_newsletter_templates in the InnoDB data dictionary has tablespace id 504, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_mailpoet_newsletters in the InnoDB data dictionary has tablespace id 505, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_mailpoet_scheduled_task_subscribers in the InnoDB data dictionary has tablespace id 506, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_mailpoet_scheduled_tasks in the InnoDB data dictionary has tablespace id 507, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_mailpoet_segments in the InnoDB data dictionary has tablespace id 508, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_mailpoet_sending_queues in the InnoDB data dictionary has tablespace id 509, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_mailpoet_settings in the InnoDB data dictionary has tablespace id 510, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_mailpoet_statistics_clicks in the InnoDB data dictionary has tablespace id 511, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_mailpoet_statistics_forms in the InnoDB data dictionary has tablespace id 512, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_mailpoet_statistics_newsletters in the InnoDB data dictionary has tablespace id 513, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_mailpoet_statistics_opens in the InnoDB data dictionary has tablespace id 514, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_mailpoet_statistics_unsubscribes in the InnoDB data dictionary has tablespace id 515, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_mailpoet_subscriber_custom_field in the InnoDB data dictionary has tablespace id 516, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_mailpoet_subscriber_ips in the InnoDB data dictionary has tablespace id 517, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_mailpoet_subscriber_segment in the InnoDB data dictionary has tablespace id 518, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_mailpoet_subscribers in the InnoDB data dictionary has tablespace id 519, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_mbdb_books in the InnoDB data dictionary has tablespace id 520, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_mbdbma_authors in the InnoDB data dictionary has tablespace id 521, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_mediafromftp_log in the InnoDB data dictionary has tablespace id 522, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_wpgmza in the InnoDB data dictionary has tablespace id 523, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_wpgmza_categories in the InnoDB data dictionary has tablespace id 524, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_wpgmza_category_maps in the InnoDB data dictionary has tablespace id 525, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_wpgmza_datasets in the InnoDB data dictionary has tablespace id 526, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_wpgmza_maps in the InnoDB data dictionary has tablespace id 527, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_wpgmza_polygon in the InnoDB data dictionary has tablespace id 528, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_wpgmza_polylines in the InnoDB data dictionary has tablespace id 529, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_wsal_metadata in the InnoDB data dictionary has tablespace id 530, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_wsal_occurrences in the InnoDB data dictionary has tablespace id 531, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [ERROR] InnoDB: Table wordpress/stjean_wsal_options in the InnoDB data dictionary has tablespace id 532, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:53:36 140448170350464 [Note] InnoDB: 128 rollback segment(s) are active.
database_1   | 2019-03-03 11:53:36 140448170350464 [Note] InnoDB: Waiting for purge to start
database_1   | 2019-03-03 11:53:36 140448170350464 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.42-84.2 started; log sequence number 359695685
database_1   | 2019-03-03 11:53:37 140448170350464 [Note] Plugin 'FEEDBACK' is disabled.
database_1   | 2019-03-03 11:53:37 140448170350464 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
database_1   | 2019-03-03 11:53:37 140448170350464 [Note] Recovering after a crash using tc.log
database_1   | 2019-03-03 11:53:37 140448170350464 [Note] Starting crash recovery...
database_1   | 2019-03-03 11:53:37 140448170350464 [Note] Crash recovery finished.
database_1   | 2019-03-03 11:53:37 140447422871296 [Note] InnoDB: Dumping buffer pool(s) not yet started
database_1   | 2019-03-03 11:53:37 140448170350464 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
database_1   | 2019-03-03 11:53:37 140448170350464 [Note] Server socket created on IP: '0.0.0.0'.
database_1   | 2019-03-03 11:53:37 140448170350464 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist
database_1   | chmod: changing permissions of '/helpers/add-cert.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/auth.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/binding.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/generate-key.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/get-remote-url.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/lando-entrypoint.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/load-keys.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/mounter.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/pantheon.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/pull.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/push.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/refresh-certs.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/setup-ca.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/sql-export.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/sql-import.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/switch.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/user-perm-helpers.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/user-perms.sh': Operation not permitted
database_1   | chmod: changing permissions of '/helpers/user-perms.sh': Operation not permitted
database_1   | chmod: changing permissions of '/scripts/load-keys.sh': Operation not permitted
database_1   | mkdir: cannot create directory '/etc/ssh': Permission denied
database_1   | Running command /entrypoint.sh /run.sh
database_1   | Running with exec!
database_1   | 
database_1   | Welcome to the Bitnami mariadb container
database_1   | Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-mariadb
database_1   | Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-mariadb/issues
database_1   | Send us your feedback at containers@bitnami.com
database_1   | 
database_1   | INFO  ==> ** Starting MariaDB setup **
database_1   | INFO  ==> Validating settings in MYSQL_*/MARIADB_* env vars..
database_1   | WARN  ==> You set the environment variable ALLOW_EMPTY_PASSWORD=yes. For safety reasons, do not use this flag in a production environment.
database_1   | INFO  ==> Initializing mariadb database...
database_1   | DEBUG ==> Custom configuration detected. Injecting...
database_1   | DEBUG ==> Ensuring expected directories/files exist...
database_1   | INFO  ==> Persisted data detected. Restoring...
database_1   | INFO  ==> Stopping mariadb...
database_1   | INFO  ==> ** MariaDB setup finished! **
database_1   | 
database_1   | INFO  ==> ** Starting MariaDB **
database_1   | 2019-03-03 11:54:10 140058238515072 [Note] /opt/bitnami/mariadb/sbin/mysqld (mysqld 10.1.38-MariaDB) starting as process 1 ...
database_1   | 2019-03-03 11:54:10 140058238515072 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
database_1   | 
database_1   | 2019-03-03 11:54:10 140058238515072 [Note] InnoDB: Using mutexes to ref count buffer pool pages
database_1   | 2019-03-03 11:54:10 140058238515072 [Note] InnoDB: The InnoDB memory heap is disabled
database_1   | 2019-03-03 11:54:10 140058238515072 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
database_1   | 2019-03-03 11:54:10 140058238515072 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
database_1   | 2019-03-03 11:54:10 140058238515072 [Note] InnoDB: Compressed tables use zlib 1.2.8
database_1   | 2019-03-03 11:54:10 140058238515072 [Note] InnoDB: Using Linux native AIO
database_1   | 2019-03-03 11:54:10 140058238515072 [Note] InnoDB: Using SSE crc32 instructions
database_1   | 2019-03-03 11:54:10 140058238515072 [Note] InnoDB: Initializing buffer pool, size = 128.0M
database_1   | 2019-03-03 11:54:10 140058238515072 [Note] InnoDB: Completed initialization of buffer pool
database_1   | 2019-03-03 11:54:10 140058238515072 [Note] InnoDB: Highest supported file format is Barracuda.
database_1   | 2019-03-03 11:54:10 140058238515072 [Note] InnoDB: The log sequence number 359695675 in ibdata file do not match the log sequence number 359695695 in the ib_logfiles!
database_1   | 2019-03-03 11:54:10 140058238515072 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table mysql/gtid_slave_pos in the InnoDB data dictionary has tablespace id 3, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table mysql/innodb_index_stats in the InnoDB data dictionary has tablespace id 2, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table mysql/innodb_table_stats in the InnoDB data dictionary has tablespace id 1, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_commentmeta in the InnoDB data dictionary has tablespace id 4, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_comments in the InnoDB data dictionary has tablespace id 5, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_gf_draft_submissions in the InnoDB data dictionary has tablespace id 6, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_gf_entry in the InnoDB data dictionary has tablespace id 7, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_gf_entry_meta in the InnoDB data dictionary has tablespace id 8, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_gf_entry_notes in the InnoDB data dictionary has tablespace id 9, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_gf_form in the InnoDB data dictionary has tablespace id 10, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_gf_form_meta in the InnoDB data dictionary has tablespace id 11, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_gf_form_revisions in the InnoDB data dictionary has tablespace id 12, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_gf_form_view in the InnoDB data dictionary has tablespace id 13, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_links in the InnoDB data dictionary has tablespace id 14, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_custom_fields in the InnoDB data dictionary has tablespace id 15, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_forms in the InnoDB data dictionary has tablespace id 16, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_log in the InnoDB data dictionary has tablespace id 17, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_mapping_to_external_entities in the InnoDB data dictionary has tablespace id 18, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_newsletter_links in the InnoDB data dictionary has tablespace id 19, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_newsletter_option in the InnoDB data dictionary has tablespace id 20, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_newsletter_option_fields in the InnoDB data dictionary has tablespace id 21, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_newsletter_posts in the InnoDB data dictionary has tablespace id 22, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_newsletter_segment in the InnoDB data dictionary has tablespace id 23, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_newsletter_templates in the InnoDB data dictionary has tablespace id 24, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_newsletters in the InnoDB data dictionary has tablespace id 25, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_scheduled_task_subscribers in the InnoDB data dictionary has tablespace id 26, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_scheduled_tasks in the InnoDB data dictionary has tablespace id 27, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_segments in the InnoDB data dictionary has tablespace id 28, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_sending_queues in the InnoDB data dictionary has tablespace id 29, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_settings in the InnoDB data dictionary has tablespace id 30, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_statistics_clicks in the InnoDB data dictionary has tablespace id 31, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_statistics_forms in the InnoDB data dictionary has tablespace id 32, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_statistics_newsletters in the InnoDB data dictionary has tablespace id 33, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_statistics_opens in the InnoDB data dictionary has tablespace id 34, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_statistics_unsubscribes in the InnoDB data dictionary has tablespace id 35, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_subscriber_custom_field in the InnoDB data dictionary has tablespace id 36, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_subscriber_ips in the InnoDB data dictionary has tablespace id 37, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_subscriber_segment in the InnoDB data dictionary has tablespace id 38, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_mailpoet_subscribers in the InnoDB data dictionary has tablespace id 39, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_mbdb_books in the InnoDB data dictionary has tablespace id 40, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_mbdbma_authors in the InnoDB data dictionary has tablespace id 41, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_mediafromftp_log in the InnoDB data dictionary has tablespace id 42, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_options in the InnoDB data dictionary has tablespace id 43, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_postmeta in the InnoDB data dictionary has tablespace id 44, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_posts in the InnoDB data dictionary has tablespace id 45, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_redirection_404 in the InnoDB data dictionary has tablespace id 46, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_redirection_groups in the InnoDB data dictionary has tablespace id 47, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_redirection_items in the InnoDB data dictionary has tablespace id 48, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_redirection_logs in the InnoDB data dictionary has tablespace id 49, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_revslider_css in the InnoDB data dictionary has tablespace id 50, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_revslider_layer_animations in the InnoDB data dictionary has tablespace id 51, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_revslider_navigations in the InnoDB data dictionary has tablespace id 52, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_revslider_sliders in the InnoDB data dictionary has tablespace id 53, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_revslider_slides in the InnoDB data dictionary has tablespace id 54, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_revslider_static_slides in the InnoDB data dictionary has tablespace id 55, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_term_relationships in the InnoDB data dictionary has tablespace id 56, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_term_taxonomy in the InnoDB data dictionary has tablespace id 57, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_termmeta in the InnoDB data dictionary has tablespace id 58, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_10_terms in the InnoDB data dictionary has tablespace id 59, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_gf_draft_submissions in the InnoDB data dictionary has tablespace id 60, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_gf_entry in the InnoDB data dictionary has tablespace id 61, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_gf_entry_meta in the InnoDB data dictionary has tablespace id 62, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_gf_entry_notes in the InnoDB data dictionary has tablespace id 63, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_gf_form in the InnoDB data dictionary has tablespace id 64, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_gf_form_meta in the InnoDB data dictionary has tablespace id 65, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_gf_form_revisions in the InnoDB data dictionary has tablespace id 66, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_gf_form_view in the InnoDB data dictionary has tablespace id 67, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_custom_fields in the InnoDB data dictionary has tablespace id 68, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_forms in the InnoDB data dictionary has tablespace id 69, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_log in the InnoDB data dictionary has tablespace id 70, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_mapping_to_external_entities in the InnoDB data dictionary has tablespace id 71, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_newsletter_links in the InnoDB data dictionary has tablespace id 72, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_newsletter_option in the InnoDB data dictionary has tablespace id 73, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_newsletter_option_fields in the InnoDB data dictionary has tablespace id 74, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_newsletter_posts in the InnoDB data dictionary has tablespace id 75, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_newsletter_segment in the InnoDB data dictionary has tablespace id 76, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_newsletter_templates in the InnoDB data dictionary has tablespace id 77, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_newsletters in the InnoDB data dictionary has tablespace id 78, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_scheduled_task_subscribers in the InnoDB data dictionary has tablespace id 79, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_scheduled_tasks in the InnoDB data dictionary has tablespace id 80, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_segments in the InnoDB data dictionary has tablespace id 81, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_sending_queues in the InnoDB data dictionary has tablespace id 82, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_settings in the InnoDB data dictionary has tablespace id 83, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_statistics_clicks in the InnoDB data dictionary has tablespace id 84, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_statistics_forms in the InnoDB data dictionary has tablespace id 85, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_statistics_newsletters in the InnoDB data dictionary has tablespace id 86, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_statistics_opens in the InnoDB data dictionary has tablespace id 87, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_statistics_unsubscribes in the InnoDB data dictionary has tablespace id 88, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_subscriber_custom_field in the InnoDB data dictionary has tablespace id 89, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_subscriber_ips in the InnoDB data dictionary has tablespace id 90, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_subscriber_segment in the InnoDB data dictionary has tablespace id 91, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_mailpoet_subscribers in the InnoDB data dictionary has tablespace id 92, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_mediafromftp_log in the InnoDB data dictionary has tablespace id 93, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_wpgmza in the InnoDB data dictionary has tablespace id 94, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_wpgmza_categories in the InnoDB data dictionary has tablespace id 95, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_wpgmza_category_maps in the InnoDB data dictionary has tablespace id 96, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_wpgmza_datasets in the InnoDB data dictionary has tablespace id 97, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_wpgmza_maps in the InnoDB data dictionary has tablespace id 98, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_wpgmza_polygon in the InnoDB data dictionary has tablespace id 99, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_11_wpgmza_polylines in the InnoDB data dictionary has tablespace id 100, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_12_commentmeta in the InnoDB data dictionary has tablespace id 101, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_12_comments in the InnoDB data dictionary has tablespace id 102, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_12_gf_draft_submissions in the InnoDB data dictionary has tablespace id 103, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_12_gf_entry in the InnoDB data dictionary has tablespace id 104, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_12_gf_entry_meta in the InnoDB data dictionary has tablespace id 105, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_12_gf_entry_notes in the InnoDB data dictionary has tablespace id 106, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_12_gf_form in the InnoDB data dictionary has tablespace id 107, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_12_gf_form_meta in the InnoDB data dictionary has tablespace id 108, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_12_gf_form_revisions in the InnoDB data dictionary has tablespace id 109, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_12_gf_form_view in the InnoDB data dictionary has tablespace id 110, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_12_links in the InnoDB data dictionary has tablespace id 111, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_12_options in the InnoDB data dictionary has tablespace id 112, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_12_postmeta in the InnoDB data dictionary has tablespace id 113, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_12_posts in the InnoDB data dictionary has tablespace id 114, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_12_revslider_css in the InnoDB data dictionary has tablespace id 115, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_12_revslider_layer_animations in the InnoDB data dictionary has tablespace id 116, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_12_revslider_navigations in the InnoDB data dictionary has tablespace id 117, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_12_revslider_sliders in the InnoDB data dictionary has tablespace id 118, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_12_revslider_slides in the InnoDB data dictionary has tablespace id 119, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_12_revslider_static_slides in the InnoDB data dictionary has tablespace id 120, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_12_term_relationships in the InnoDB data dictionary has tablespace id 121, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_12_term_taxonomy in the InnoDB data dictionary has tablespace id 122, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_12_termmeta in the InnoDB data dictionary has tablespace id 123, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_12_terms in the InnoDB data dictionary has tablespace id 124, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_gf_draft_submissions in the InnoDB data dictionary has tablespace id 125, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_gf_entry in the InnoDB data dictionary has tablespace id 126, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_gf_entry_meta in the InnoDB data dictionary has tablespace id 127, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_gf_entry_notes in the InnoDB data dictionary has tablespace id 128, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_gf_form in the InnoDB data dictionary has tablespace id 129, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_gf_form_meta in the InnoDB data dictionary has tablespace id 130, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_gf_form_revisions in the InnoDB data dictionary has tablespace id 131, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_gf_form_view in the InnoDB data dictionary has tablespace id 132, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_custom_fields in the InnoDB data dictionary has tablespace id 133, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_forms in the InnoDB data dictionary has tablespace id 134, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_log in the InnoDB data dictionary has tablespace id 135, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_mapping_to_external_entities in the InnoDB data dictionary has tablespace id 136, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_newsletter_links in the InnoDB data dictionary has tablespace id 137, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_newsletter_option in the InnoDB data dictionary has tablespace id 138, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_newsletter_option_fields in the InnoDB data dictionary has tablespace id 139, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_newsletter_posts in the InnoDB data dictionary has tablespace id 140, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_newsletter_segment in the InnoDB data dictionary has tablespace id 141, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_newsletter_templates in the InnoDB data dictionary has tablespace id 142, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_newsletters in the InnoDB data dictionary has tablespace id 143, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_scheduled_task_subscribers in the InnoDB data dictionary has tablespace id 144, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_scheduled_tasks in the InnoDB data dictionary has tablespace id 145, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_segments in the InnoDB data dictionary has tablespace id 146, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_sending_queues in the InnoDB data dictionary has tablespace id 147, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_settings in the InnoDB data dictionary has tablespace id 148, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_statistics_clicks in the InnoDB data dictionary has tablespace id 149, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_statistics_forms in the InnoDB data dictionary has tablespace id 150, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_statistics_newsletters in the InnoDB data dictionary has tablespace id 151, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_statistics_opens in the InnoDB data dictionary has tablespace id 152, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_statistics_unsubscribes in the InnoDB data dictionary has tablespace id 153, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_subscriber_custom_field in the InnoDB data dictionary has tablespace id 154, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_subscriber_ips in the InnoDB data dictionary has tablespace id 155, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_subscriber_segment in the InnoDB data dictionary has tablespace id 156, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_mailpoet_subscribers in the InnoDB data dictionary has tablespace id 157, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_mediafromftp_log in the InnoDB data dictionary has tablespace id 158, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_wpgmza in the InnoDB data dictionary has tablespace id 159, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_wpgmza_categories in the InnoDB data dictionary has tablespace id 160, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_wpgmza_category_maps in the InnoDB data dictionary has tablespace id 161, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_wpgmza_datasets in the InnoDB data dictionary has tablespace id 162, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_wpgmza_maps in the InnoDB data dictionary has tablespace id 163, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_wpgmza_polygon in the InnoDB data dictionary has tablespace id 164, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_2_wpgmza_polylines in the InnoDB data dictionary has tablespace id 165, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_gf_draft_submissions in the InnoDB data dictionary has tablespace id 166, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_gf_entry in the InnoDB data dictionary has tablespace id 167, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_gf_entry_meta in the InnoDB data dictionary has tablespace id 168, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_gf_entry_notes in the InnoDB data dictionary has tablespace id 169, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_gf_form in the InnoDB data dictionary has tablespace id 170, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_gf_form_meta in the InnoDB data dictionary has tablespace id 171, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_gf_form_revisions in the InnoDB data dictionary has tablespace id 172, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_gf_form_view in the InnoDB data dictionary has tablespace id 173, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_custom_fields in the InnoDB data dictionary has tablespace id 174, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_dynamic_segment_filters in the InnoDB data dictionary has tablespace id 175, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_forms in the InnoDB data dictionary has tablespace id 176, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_log in the InnoDB data dictionary has tablespace id 177, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_mapping_to_external_entities in the InnoDB data dictionary has tablespace id 178, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_newsletter_links in the InnoDB data dictionary has tablespace id 179, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_newsletter_option in the InnoDB data dictionary has tablespace id 180, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_newsletter_option_fields in the InnoDB data dictionary has tablespace id 181, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_newsletter_posts in the InnoDB data dictionary has tablespace id 182, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_newsletter_segment in the InnoDB data dictionary has tablespace id 183, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_newsletter_templates in the InnoDB data dictionary has tablespace id 184, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_newsletters in the InnoDB data dictionary has tablespace id 185, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_premium_newsletter_extra_data in the InnoDB data dictionary has tablespace id 186, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_scheduled_task_subscribers in the InnoDB data dictionary has tablespace id 187, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_scheduled_tasks in the InnoDB data dictionary has tablespace id 188, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_segments in the InnoDB data dictionary has tablespace id 189, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_sending_queues in the InnoDB data dictionary has tablespace id 190, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_settings in the InnoDB data dictionary has tablespace id 191, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_statistics_clicks in the InnoDB data dictionary has tablespace id 192, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_statistics_forms in the InnoDB data dictionary has tablespace id 193, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_statistics_newsletters in the InnoDB data dictionary has tablespace id 194, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_statistics_opens in the InnoDB data dictionary has tablespace id 195, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_statistics_unsubscribes in the InnoDB data dictionary has tablespace id 196, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_subscriber_custom_field in the InnoDB data dictionary has tablespace id 197, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_subscriber_ips in the InnoDB data dictionary has tablespace id 198, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_subscriber_segment in the InnoDB data dictionary has tablespace id 199, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mailpoet_subscribers in the InnoDB data dictionary has tablespace id 200, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mbdbma_authors in the InnoDB data dictionary has tablespace id 201, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_mediafromftp_log in the InnoDB data dictionary has tablespace id 202, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_wpgmza in the InnoDB data dictionary has tablespace id 203, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_wpgmza_categories in the InnoDB data dictionary has tablespace id 204, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_wpgmza_category_maps in the InnoDB data dictionary has tablespace id 205, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_wpgmza_datasets in the InnoDB data dictionary has tablespace id 206, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_wpgmza_maps in the InnoDB data dictionary has tablespace id 207, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_wpgmza_polygon in the InnoDB data dictionary has tablespace id 208, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_3_wpgmza_polylines in the InnoDB data dictionary has tablespace id 209, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_gf_draft_submissions in the InnoDB data dictionary has tablespace id 210, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_gf_entry in the InnoDB data dictionary has tablespace id 211, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_gf_entry_meta in the InnoDB data dictionary has tablespace id 212, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_gf_entry_notes in the InnoDB data dictionary has tablespace id 213, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_gf_form in the InnoDB data dictionary has tablespace id 214, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_gf_form_meta in the InnoDB data dictionary has tablespace id 215, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_gf_form_view in the InnoDB data dictionary has tablespace id 216, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_custom_fields in the InnoDB data dictionary has tablespace id 217, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_forms in the InnoDB data dictionary has tablespace id 218, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_log in the InnoDB data dictionary has tablespace id 219, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_mapping_to_external_entities in the InnoDB data dictionary has tablespace id 220, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_newsletter_links in the InnoDB data dictionary has tablespace id 221, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_newsletter_option in the InnoDB data dictionary has tablespace id 222, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_newsletter_option_fields in the InnoDB data dictionary has tablespace id 223, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_newsletter_posts in the InnoDB data dictionary has tablespace id 224, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_newsletter_segment in the InnoDB data dictionary has tablespace id 225, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_newsletter_templates in the InnoDB data dictionary has tablespace id 226, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_newsletters in the InnoDB data dictionary has tablespace id 227, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_scheduled_task_subscribers in the InnoDB data dictionary has tablespace id 228, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_scheduled_tasks in the InnoDB data dictionary has tablespace id 229, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_segments in the InnoDB data dictionary has tablespace id 230, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_sending_queues in the InnoDB data dictionary has tablespace id 231, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_settings in the InnoDB data dictionary has tablespace id 232, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_statistics_clicks in the InnoDB data dictionary has tablespace id 233, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_statistics_forms in the InnoDB data dictionary has tablespace id 234, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_statistics_newsletters in the InnoDB data dictionary has tablespace id 235, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_statistics_opens in the InnoDB data dictionary has tablespace id 236, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_statistics_unsubscribes in the InnoDB data dictionary has tablespace id 237, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_subscriber_custom_field in the InnoDB data dictionary has tablespace id 238, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_subscriber_ips in the InnoDB data dictionary has tablespace id 239, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_subscriber_segment in the InnoDB data dictionary has tablespace id 240, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_mailpoet_subscribers in the InnoDB data dictionary has tablespace id 241, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_mbdbma_authors in the InnoDB data dictionary has tablespace id 242, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_mediafromftp_log in the InnoDB data dictionary has tablespace id 243, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_wpgmza in the InnoDB data dictionary has tablespace id 244, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_wpgmza_categories in the InnoDB data dictionary has tablespace id 245, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_wpgmza_category_maps in the InnoDB data dictionary has tablespace id 246, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_wpgmza_datasets in the InnoDB data dictionary has tablespace id 247, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_wpgmza_maps in the InnoDB data dictionary has tablespace id 248, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_wpgmza_polygon in the InnoDB data dictionary has tablespace id 249, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_4_wpgmza_polylines in the InnoDB data dictionary has tablespace id 250, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_5_gf_draft_submissions in the InnoDB data dictionary has tablespace id 251, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_5_gf_entry in the InnoDB data dictionary has tablespace id 252, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_5_gf_entry_meta in the InnoDB data dictionary has tablespace id 253, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_5_gf_entry_notes in the InnoDB data dictionary has tablespace id 254, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_5_gf_form in the InnoDB data dictionary has tablespace id 255, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_5_gf_form_meta in the InnoDB data dictionary has tablespace id 256, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_5_gf_form_revisions in the InnoDB data dictionary has tablespace id 257, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_5_gf_form_view in the InnoDB data dictionary has tablespace id 258, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_custom_fields in the InnoDB data dictionary has tablespace id 259, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_forms in the InnoDB data dictionary has tablespace id 260, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_log in the InnoDB data dictionary has tablespace id 261, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_mapping_to_external_entities in the InnoDB data dictionary has tablespace id 262, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_newsletter_links in the InnoDB data dictionary has tablespace id 263, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_newsletter_option in the InnoDB data dictionary has tablespace id 264, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_newsletter_option_fields in the InnoDB data dictionary has tablespace id 265, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_newsletter_posts in the InnoDB data dictionary has tablespace id 266, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_newsletter_segment in the InnoDB data dictionary has tablespace id 267, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_newsletter_templates in the InnoDB data dictionary has tablespace id 268, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_newsletters in the InnoDB data dictionary has tablespace id 269, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_scheduled_task_subscribers in the InnoDB data dictionary has tablespace id 270, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_scheduled_tasks in the InnoDB data dictionary has tablespace id 271, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_segments in the InnoDB data dictionary has tablespace id 272, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_sending_queues in the InnoDB data dictionary has tablespace id 273, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_settings in the InnoDB data dictionary has tablespace id 274, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
database_1   | InnoDB: for how to resolve the issue.
database_1   | 2019-03-03 11:54:10 140058238515072 [ERROR] InnoDB: Table wordpress/stjean_5_mailpoet_statistics_clicks in the InnoDB data dictionary has tablespace id 275, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
database_1   | InnoDB: Please refer to
database_1   | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datad