MySQL Forums
Forum List  »  General

Finding the cause of a crashed table
Posted by: MC Potgieter
Date: January 13, 2015 03:53AM

I'm using MySQL 5.5.8-log with Delphi XE and dbExpress. I'm not a DB expert and would appreciate some advice.

Every now and then I get a crashed table (See info below).

How do I go about finding the cause of the table crash and how to I resolve it?




150110 13:00:23 [ERROR] Got an error from thread_id=8, ..\..\..\mysql-5.5.8\storage\myisam\mi_locking.c:69
150110 13:00:23 [ERROR] MySQL thread id 8, query id 361830152 127.0.0.1 distribution closing tables
INSERT INTO trafficlog (UnitID,UnitType,ConnectionPort,UnitAddress,DestinationID,Message,Time,Size) VALUES(233,0,10000,'10.1.8.134',0,'Event sent','2015-01-10 13:00:23',35)
150110 13:00:23 [ERROR] c:\xampp\mysql\bin\mysqld.exe: Incorrect key file for table '.\rdc_gl\trafficlog.MYI'; try to repair it
150110 13:00:23 [ERROR] Got an error from thread_id=8, ..\..\..\mysql-5.5.8\storage\myisam\mi_locking.c:116
150110 13:00:23 [ERROR] MySQL thread id 8, query id 361830152 127.0.0.1 distribution closing tables
INSERT INTO trafficlog (UnitID,UnitType,ConnectionPort,UnitAddress,DestinationID,Message,Time,Size) VALUES(233,0,10000,'10.1.8.134',0,'Event sent','2015-01-10 13:00:23',35)
150110 13:00:24 - 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=16777216
read_buffer_size=262144
max_used_connections=601
max_threads=600
thread_count=257
connection_count=257
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 481538 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x3f9b7b0
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...
014C8DA5 mysqld.exe!end_key_cache()
01000000
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 04019FC0=INSERT INTO trafficlog (UnitID,UnitType,ConnectionPort,UnitAddress,DestinationID,Message,Time,Size) VALUES(233,0,10000,'10.1.8.134',0,'Event sent','2015-01-10 13:00:24',35)
thd->thread_id=8
thd->killed=NOT_KILLED
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.
150110 13:01:38 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use Windows interlocked functions
InnoDB: Compressed tables use zlib 1.2.3
150110 13:01:38 InnoDB: Initializing buffer pool, size = 16.0M
150110 13:01:38 InnoDB: Completed initialization of buffer pool
150110 13:01:38 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
150110 13:01:38 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Last MySQL binlog file position 0 77960817, file name .\mysql-bin.001695
150110 13:01:38 InnoDB: 1.1.4 started; log sequence number 19754991
150110 13:01:38 [Note] Recovering after a crash using mysql-bin
150110 13:01:43 [Note] Starting crash recovery...
150110 13:01:43 [Note] Crash recovery finished.
150110 13:01:44 [Warning] 'tables_priv' entry 'columns_priv root@*' ignored in --skip-name-resolve mode.
150110 13:01:44 [Warning] 'tables_priv' entry 'db root@*' ignored in --skip-name-resolve mode.
150110 13:01:44 [Warning] 'tables_priv' entry 'event root@*' ignored in --skip-name-resolve mode.
150110 13:01:44 [Warning] 'tables_priv' entry 'func root@*' ignored in --skip-name-resolve mode.
150110 13:01:44 [Warning] 'tables_priv' entry 'host root@*' ignored in --skip-name-resolve mode.
150110 13:01:44 [Warning] 'tables_priv' entry 'proc root@*' ignored in --skip-name-resolve mode.
150110 13:01:44 [Warning] 'tables_priv' entry 'procs_priv root@*' ignored in --skip-name-resolve mode.
150110 13:01:44 [Warning] 'tables_priv' entry 'tables_priv root@*' ignored in --skip-name-resolve mode.
150110 13:01:44 [Warning] 'tables_priv' entry 'user root@*' ignored in --skip-name-resolve mode.
150110 13:01:44 [Note] Event Scheduler: Loaded 0 events
150110 13:01:44 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.5.8-log' socket: '' port: 3306 MySQL Community Server (GPL)
150110 13:01:45 [ERROR] c:\xampp\mysql\bin\mysqld.exe: Table '.\rdc_gl\trafficlog' is marked as crashed and should be repaired

Options: ReplyQuote


Subject
Written By
Posted
Finding the cause of a crashed table
January 13, 2015 03:53AM


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.