Hi, I have run into an issue with my ecommerce website database. A restore had to be performed some time ago and it is my belief that I have been experiencing this ever since. It has grown my error log to nearly 2GB.

This is the email that I started to get recently and I do not know what may have changed to cause an issue.

I would appreciate any help in direction as to how I may be able to resolve the issue. It appears that the DB or cache files may be corrupt. I have run CHECK TABLE for all of the mysql and website databases to no avail. I tried to check the MyISAM tables as well:
myisamchk --silent --force */*.MYI
myisamchk: error: 140 when opening MyISAM-table...

"Cpanel::Exception:atabase::Error/(XID ss6qy5) The system received an error from the MySQL database mysql: 2013 (Lost connection to MySQL server during query) at /usr/local/cpanel/Cpanel/Exception/CORE.pm line 336.
Cpanel::Exception::create("Database::Error", ARRAY(0x30e5208)) called at /usr/local/cpanel/Cpanel/Exception.pm line 46
Cpanel::Exception::__ANON__(__CPANEL_HIDDEN__, ARRAY(0x30e5208)) called at /usr/local/cpanel/Cpanel/DBI.pm line 200
Cpanel:BI::_create_exception(Cpanel:BI::Mysql::st=HASH(0x30d3aa0), "DBD::mysql::st execute failed: Lost connection to MySQL serve"..., undef) called at /usr/local/cpanel/Cpanel/DBI.pm line 188
Cpanel:BI::_error_handler("DBD::mysql::st execute failed: Lost connection to MySQL serve"..., Cpanel:BI::Mysql::st=HASH(0x30d3aa0), undef) called at bin/update_db_cache.pl line 333
Script::Update:B::Cache::can_get_mysql_usage(HASH(0xff6ea0), HASH(0x10651b0), Cpanel:B::Map::Collection::Index=HASH(0x3098128)) called at bin/update_db_cache.pl line 60
Script::Update:B::Cache::script("Script::Update:B::Cache") called at bin/update_db_cache.pl line 35"


More info:
It tends to crash ever 2-4 hours and no changes out of the ordinary are being made to my knowledge.

# Environment
CentOS, WHM/CPanel, PHP7, MySQL 5.6.38, eCommerce Website (Magento)

# Below from website.err file:
InnoDB: End of page dump
2017-11-12 08:31:38 7fece4bb5700 InnoDB: uncompressed page, stored checksum in field1 1940515531, calculated checksums for field1: crc32 1062689690, innodb 4217881636, none 3735928559, stored checksum in field2 0, calculated checksums for field2: crc32 1062689690, innodb 145366930, none 3735928559, page LSN 6 2465970045, low 4 bytes of LSN at page end 0, page number (if stored to page already) 1, space id (if created with >= MySQL-4.1.1 and stored already) 84948
InnoDB: Page may be an insert buffer bitmap page
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 1.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also 301 Moved Permanently
InnoDB: about forcing recovery.
InnoDB: Error: Unable to read tablespace 84948 page no 1 into the buffer pool after 100 attempts
InnoDB: The most probable cause of this error may be that the table has been corrupted.
InnoDB: You can try to fix this problem by using innodb_force_recovery.
InnoDB: Please see reference manual for more details.
InnoDB: Aborting...
2017-11-12 08:31:38 7fece4bb5700 InnoDB: Assertion failure in thread 140655426492160 in file buf0buf.cc line 2740
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to 301 Moved Permanently.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: 301 Moved Permanently
InnoDB: about forcing recovery.
13:31:38 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68108 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x3885780
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7fece4bb4e48 thread_stack 0x40000
/usr/sbin/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_P10SQL_I_ListI8st_orderESB_S7_yP13select_ resultP18st_select_lex_unitP13st_select_lex+0x250)[0x702810]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fec98004bb0): is an invalid pointer
Connection ID (thread ID): 29

The manual page at 301 Moved Permanently contains
information that should help you find out what is causing the crash.


Thank you ahead!