(win) crash à répétitions - InnoDB Error 1500
Bonjour :)
J'aimerai votre avis sur de curieux crash de mysql (en local sous Win vista), hier alors que je travaillait 1er crash j'ai du refaire mes structures de tables et c'est repartit.
Ce matin je reboot pour l'install du sp2 et hop exactement le meme soucis !
Pour infos hier le crash était sous mysql 5.1.33 (via WAMP) et j'ai tout viré puis installé la 5.1.34 et refait mes tables proprement sans conserver aucun fichier du dossier data.
Et donc avec là 5.1.34 même problème, voici le log mysql :
Code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
| 090615 19:11:20 InnoDB: Started; log sequence number 0 46409
090615 19:11:20 [Note] Event Scheduler: Loaded 0 events
090615 19:11:20 [Note] wampmysqld: ready for connections.
Version: '5.1.34-community-log' socket: '' port: 3306 MySQL Community Server (GPL)
090616 1:01:58 [Note] wampmysqld: Normal shutdown
090616 1:01:58 [Note] Event Scheduler: Purging the queue. 0 events
090616 1:01:58 InnoDB: Starting shutdown...
090616 1:02:01 InnoDB: Shutdown completed; log sequence number 0 29944191
090616 1:02:01 [Warning] Forcing shutdown of 1 plugins
090616 1:02:01 [Note] wampmysqld: Shutdown complete
090616 1:54:29 InnoDB: Started; log sequence number 0 29944191
090616 1:54:30 [Note] Event Scheduler: Loaded 0 events
090616 1:54:30 [Note] wampmysqld: ready for connections.
Version: '5.1.34-community-log' socket: '' port: 3306 MySQL Community Server (GPL)
090616 2:18:37 InnoDB: Error: (1500) Couldn't read the MAX(id_operation_st) autoinc value from the index (PRIMARY).
090616 2:18:37 InnoDB: Assertion failure in thread 1732 in file .\handler\ha_innodb.cc line 2601
InnoDB: Failing assertion: error == DB_SUCCESS
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.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
090616 2:18:37 - 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=2
max_threads=151
threads_connected=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133305 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x4249ed0
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...
InnoDB: Thread 4288 stopped in file .\os\os0sync.c line 574
InnoDB: Thread 4580 stopped in file .\os\os0sync.c line 271
006ADC0B mysqld.exe!???
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0428D848=SHOW TABLE STATUS FROM `challeng`
thd->thread_id=3
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. |
:aie::aie::aie:
