Hi, I'm currently running mySQL in a Windows environment. I can start the MySQL services but after about 30 minutes to an hour it crashes. Here's what my logs tell me. Any ideas? This is critical:
130611 9:23:57 InnoDB: Error: page 3 log sequence number 155 1098239154
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 2 log sequence number 155 1098188155
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 199 log sequence number 155 1098023073
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 10 log sequence number 155 1098169648
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 40 log sequence number 155 1097978282
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 301 log sequence number 155 1098193817
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 276 log sequence number 155 1098223910
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 221 log sequence number 155 1098089518
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 197 log sequence number 155 1098070947
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 4 log sequence number 155 1097861747
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 132 log sequence number 155 1098211505
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 49 log sequence number 155 1098089158
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 155 log sequence number 155 1098155816
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 153 log sequence number 155 1098194467
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 137 log sequence number 155 1098240709
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 157 log sequence number 155 1098199532
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 140 log sequence number 155 1098177619
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 384 log sequence number 155 1098072099
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 133 log sequence number 155 1098211556
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 30 log sequence number 155 1098214885
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 61 log sequence number 155 1098241860
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 51 log sequence number 155 1098089208
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 59 log sequence number 155 1098113341
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 18 log sequence number 155 1098137473
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 131 log sequence number 155 1098235173
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 48 log sequence number 155 1098175628
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 120 log sequence number 155 1098238553
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 1864812260 in space 0,
InnoDB: space name .\ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
130611 9:23:57InnoDB: Assertion failure in thread 6292 in file .\fil\fil0fil.c line 3959
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.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
130611 9:23:57 - mysqld got exception 0xc0000005 ;
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.
key_buffer_size=13631488
read_buffer_size=65536
max_used_connections=5
max_connections=800
threads_connected=4
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 269312 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=265CC5F0
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...
0068ABEC mysqld-nt.exe!fil_io()[fil0fil.c:3959]
006D8048 mysqld-nt.exe!buf_read_page_low()[buf0rea.c:147]
006D839A mysqld-nt.exe!buf_read_page()[buf0rea.c:333]
00699C42 mysqld-nt.exe!buf_page_get_gen()[buf0buf.c:1151]
006D7146 mysqld-nt.exe!flst_insert_before()[fut0lst.c:239]
006D7A2B mysqld-nt.exe!flst_add_first()[fut0lst.c:136]
006AA8D7 mysqld-nt.exe!trx_purge_add_update_undo_to_history()[trx0purge.c:298]
006AE443 mysqld-nt.exe!trx_undo_update_cleanup()[trx0undo.c:1883]
00657244 mysqld-nt.exe!trx_commit_off_kernel()[trx0trx.c:788]
006590DE mysqld-nt.exe!trx_commit_for_mysql()[trx0trx.c:1631]
0043EAE3 mysqld-nt.exe!innobase_commit()[ha_innodb.cc:1681]
0044B421 mysqld-nt.exe!ha_commit_one_phase()[handler.cc:765]
0044D6D6 mysqld-nt.exe!ha_commit_trans()[handler.cc:725]
0044D80F mysqld-nt.exe!ha_autocommit_or_rollback()[handler.cc:882]
0052BDBE mysqld-nt.exe!mysql_insert()[sql_insert.cc:935]
0053DA4D mysqld-nt.exe!mysql_execute_command()[sql_parse.cc:3840]
005425F1 mysqld-nt.exe!mysql_parse()[sql_parse.cc:6460]
005435EE mysqld-nt.exe!dispatch_command()[sql_parse.cc:1961]
005448B6 mysqld-nt.exe!do_command()[sql_parse.cc:1644]
00544BD5 mysqld-nt.exe!handle_one_connection()[sql_parse.cc:1233]
005F6F4B mysqld-nt.exe!pthread_start()[my_winthread.c:85]
006E226F mysqld-nt.exe!_threadstart()[thread.c:196]
757A3677 kernel32.dll!BaseThreadInitThunk()
774E9F42 ntdll.dll!RtlInitializeExceptionChain()
774E9F15 ntdll.dll!RtlInitializeExceptionChain()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 265CDA30=insert into leadstore.mysearches (sessid,state,countyfips,cplat,cplon,cornerlat1,cornerlat2,cornerlat3,cornerlat4,cornerlon1,cornerlon2,cornerlon3,cornerlon4,rescount) values
('2afqfhht5cm88c83fpmr4ucm83','MD','017','38.610921129','-76.89130425','38.611718109','38.612661129','38.608857544','38.606527521','-76.90149857','-76.88956425','-76.88870594','-76.90042569',257)
on duplicate key update state='MD',countyfips='017',cplat='38.610921129',cplon='-76.89130425',cornerlat1='38.611718109',cornerlat2='38.612661129',cornerlat3='38.608857544',cornerlat4='38.606527521',cornerlon1='-76.90149857',cornerlon2='-76.88956425',cornerlon3='-76.88870594',cornerlon4='-76.90042569',rescount=257
thd->thread_id=22
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
130611 9:23:57 InnoDB: Error: page 3 log sequence number 155 1098239154
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 2 log sequence number 155 1098188155
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 199 log sequence number 155 1098023073
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 10 log sequence number 155 1098169648
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 40 log sequence number 155 1097978282
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 301 log sequence number 155 1098193817
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 276 log sequence number 155 1098223910
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 221 log sequence number 155 1098089518
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 197 log sequence number 155 1098070947
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 4 log sequence number 155 1097861747
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 132 log sequence number 155 1098211505
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 49 log sequence number 155 1098089158
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 155 log sequence number 155 1098155816
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 153 log sequence number 155 1098194467
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 137 log sequence number 155 1098240709
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 157 log sequence number 155 1098199532
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 140 log sequence number 155 1098177619
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 384 log sequence number 155 1098072099
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 133 log sequence number 155 1098211556
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 30 log sequence number 155 1098214885
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 61 log sequence number 155 1098241860
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 51 log sequence number 155 1098089208
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 59 log sequence number 155 1098113341
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 18 log sequence number 155 1098137473
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 131 log sequence number 155 1098235173
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 48 log sequence number 155 1098175628
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
130611 9:23:57 InnoDB: Error: page 120 log sequence number 155 1098238553
InnoDB: is in the future! Current system log sequence number 155 1097452758.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 1864812260 in space 0,
InnoDB: space name .\ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
130611 9:23:57InnoDB: Assertion failure in thread 6292 in file .\fil\fil0fil.c line 3959
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.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
130611 9:23:57 - mysqld got exception 0xc0000005 ;
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.
key_buffer_size=13631488
read_buffer_size=65536
max_used_connections=5
max_connections=800
threads_connected=4
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 269312 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=265CC5F0
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...
0068ABEC mysqld-nt.exe!fil_io()[fil0fil.c:3959]
006D8048 mysqld-nt.exe!buf_read_page_low()[buf0rea.c:147]
006D839A mysqld-nt.exe!buf_read_page()[buf0rea.c:333]
00699C42 mysqld-nt.exe!buf_page_get_gen()[buf0buf.c:1151]
006D7146 mysqld-nt.exe!flst_insert_before()[fut0lst.c:239]
006D7A2B mysqld-nt.exe!flst_add_first()[fut0lst.c:136]
006AA8D7 mysqld-nt.exe!trx_purge_add_update_undo_to_history()[trx0purge.c:298]
006AE443 mysqld-nt.exe!trx_undo_update_cleanup()[trx0undo.c:1883]
00657244 mysqld-nt.exe!trx_commit_off_kernel()[trx0trx.c:788]
006590DE mysqld-nt.exe!trx_commit_for_mysql()[trx0trx.c:1631]
0043EAE3 mysqld-nt.exe!innobase_commit()[ha_innodb.cc:1681]
0044B421 mysqld-nt.exe!ha_commit_one_phase()[handler.cc:765]
0044D6D6 mysqld-nt.exe!ha_commit_trans()[handler.cc:725]
0044D80F mysqld-nt.exe!ha_autocommit_or_rollback()[handler.cc:882]
0052BDBE mysqld-nt.exe!mysql_insert()[sql_insert.cc:935]
0053DA4D mysqld-nt.exe!mysql_execute_command()[sql_parse.cc:3840]
005425F1 mysqld-nt.exe!mysql_parse()[sql_parse.cc:6460]
005435EE mysqld-nt.exe!dispatch_command()[sql_parse.cc:1961]
005448B6 mysqld-nt.exe!do_command()[sql_parse.cc:1644]
00544BD5 mysqld-nt.exe!handle_one_connection()[sql_parse.cc:1233]
005F6F4B mysqld-nt.exe!pthread_start()[my_winthread.c:85]
006E226F mysqld-nt.exe!_threadstart()[thread.c:196]
757A3677 kernel32.dll!BaseThreadInitThunk()
774E9F42 ntdll.dll!RtlInitializeExceptionChain()
774E9F15 ntdll.dll!RtlInitializeExceptionChain()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 265CDA30=insert into leadstore.mysearches (sessid,state,countyfips,cplat,cplon,cornerlat1,cornerlat2,cornerlat3,cornerlat4,cornerlon1,cornerlon2,cornerlon3,cornerlon4,rescount) values
('2afqfhht5cm88c83fpmr4ucm83','MD','017','38.610921129','-76.89130425','38.611718109','38.612661129','38.608857544','38.606527521','-76.90149857','-76.88956425','-76.88870594','-76.90042569',257)
on duplicate key update state='MD',countyfips='017',cplat='38.610921129',cplon='-76.89130425',cornerlat1='38.611718109',cornerlat2='38.612661129',cornerlat3='38.608857544',cornerlat4='38.606527521',cornerlon1='-76.90149857',cornerlon2='-76.88956425',cornerlon3='-76.88870594',cornerlon4='-76.90042569',rescount=257
thd->thread_id=22
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.