MySQL Forums
Forum List  »  Newbie

Re: Lost connection to MySQL server during query
Posted by: Christopher Popplewell
Date: November 12, 2017 08:39PM

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

# Version

# 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
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 line 2740
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
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: 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

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 contains
information that should help you find out what is causing the crash.

Options: ReplyQuote

Written By
Re: Lost connection to MySQL server during query
November 12, 2017 08:39PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.