MySQL Forums
Forum List  »  InnoDB

InnoDB: Assertion failure in thread 644 in file trx0trx.ic line 213 ( Please Help Neded ASAP is a Production Server )
Posted by: Luis Cavazos
Date: September 16, 2018 08:49AM

Hi, I recently upgraded my db from 5.6.22 to 5.7.23
the way I did was:
1- creating a Dump File with data and structure , triggers and events
2- Altered the sql File replacing the latin to utf8 everywhere
3- importing it to the New Just Initialized 5.7.23.

Running in a Windows Server 2012 Cpu xeon 2.4 Mhz ( double processor ) and 32G Pool size of 48G total Ram.


Every thing went just fine, but the new db keeps crashing every 10 to 24 hours with this error:

2018-09-16 04:04:57 0x284 InnoDB: Assertion failure in thread 644 in file trx0trx.ic line 213


InnoDB: Failing assertion: !trx->has_search_latch
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
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: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
10:04:57 UTC - mysqld got exception 0x80000003 ;
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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=29
max_threads=200
thread_count=25
connection_count=24
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 560515 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0xe67fa09720
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...
7f65ee92222 mysqld.exe!my_sigabrt_handler()[my_thr_init.c:449]
7fff133ee1d MSVCR120.dll!raise()
7fff1344a14 MSVCR120.dll!abort()
7f65efae0e4 mysqld.exe!ut_dbg_assertion_failed()[ut0dbg.cc:67]
7f65eede593 mysqld.exe!TrxInInnoDB::exit()[trx0trx.h:1517]
7f65eedc9f1 mysqld.exe!ha_innobase::end_stmt()[ha_innodb.cc:15359]
7f65e8140fd mysqld.exe!close_thread_table()[sql_base.cc:1760]
7f65e813450 mysqld.exe!close_open_tables()[sql_base.cc:1442]
7f65e814470 mysqld.exe!close_thread_tables()[sql_base.cc:1724]
7f65e957f79 mysqld.exe!Prepared_statement::prepare()[sql_prepare.cc:3340]
7f65e9579fe mysqld.exe!mysqld_stmt_prepare()[sql_prepare.cc:2114]
7f65e774985 mysqld.exe!dispatch_command()[sql_parse.cc:1442]
7f65e775a5a mysqld.exe!do_command()[sql_parse.cc:1027]
7f65e71c10c mysqld.exe!handle_connection()[connection_handler_per_thread.cc:300]
7f65f180672 mysqld.exe!pfs_spawn_thread()[pfs.cc:2193]
7f65ee9208c mysqld.exe!win_thread_start()[my_thread.c:38]
7fff12f4f7f MSVCR120.dll!_beginthreadex()
7fff12f5126 MSVCR120.dll!_endthreadex()
7f8093a1832 KERNEL32.DLL!BaseThreadInitThunk()
7f80b77e379 ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (e682db19d0): insert into indata ( id_port , id_fec , id_sec , datos , EqId ) values ( ? , '2015/01/01' , 0 , ? , ? )
Connection ID (thread ID): 11666
Status: NOT_KILLED

Options: ReplyQuote


Subject
Views
Written By
Posted
InnoDB: Assertion failure in thread 644 in file trx0trx.ic line 213 ( Please Help Neded ASAP is a Production Server )
50
September 16, 2018 08:49AM


Sorry, only registered users may post in this forum.

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.