Bonjour,
J'ai le même problème déjà évoqué dans un post mais étant donné qu'il n'a pas reçu de réponse (et marqué comme résolu), je poste mon problème similaire ici :)
A chaque update ou insert dans une de mes tables, j'ai le message suivant qui s'affiche lors d'un myisamchk :
De plus, au bout d'un moment, ça me fait planter mon serveur mysql (et du coup les connexions de mes utilisateurs).Citation:
myisamchk: warning: 1 client IS USING OR hasn't closed the table properly
Voici le message indiqué dans le log de ma base avant le plantage :
J'ai fait un myisamchk -ivc pour avoir des infos sur l'une des tables "not closed" :Citation:
090616 14:37:33 - mysqld got signal 11;
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=67108864
read_buffer_size=520192
max_used_connections=12
max_connections=100
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 167535 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0xb2500480
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...
Cannot determine thread, fp=0xb29bb888, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x818b878
0xb7d3ae87
0x81e43dc
0x81e6efa
0x81e3ac4
0x81e3938
0x81e3a87
0x81e3938
0x81e3a87
0x81e3938
0x81e3a87
0x81ea527
0x81ea6db
0x81e3f08
0x81f20e8
0x81f4242
0x81f48f5
0x81a2e59
0x81a916a
0x81aa14b
0x81aa8ab
0x81ab2b9
0xb7d34d51
0xb7b8de2a
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/us...ack-trace.html and follow instructions on how to resolve the st
ack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
[MA REQUETE]
Quelqu'un saurait d'où cela pourrait venir ? De mon fichier de configuration ? Apparemment, j'ai suffisamment d'espace pourtant.Citation:
Checking MyISAM file: /home/mysql/premierempire/pe_bataillon.MYI
Data records: 1780 Deleted blocks: 0
- check file-size
- check record delete-chain
No recordlinks
- check key delete-chain
block_size 1024:
- check index reference
- check data record references index: 1
Key: 1: Keyblocks used: 70% Packed: 0% Max levels: 2
- check data record references index: 2
Key: 2: Keyblocks used: 92% Packed: 0% Max levels: 2
- check data record references index: 3
Key: 3: Keyblocks used: 92% Packed: 0% Max levels: 2
- check data record references index: 4
Key: 4: Keyblocks used: 95% Packed: 0% Max levels: 2
Total: Keyblocks used: 87% Packed: 0%
- check record links
Records: 1780 M.recordlength: 85 Packed: 41%
Recordspace used: 99% Empty space: 0% Blocks/Record: 1.00
Record blocks: 1781 Delete blocks: 0
Record data: 151901 Deleted data: 0
Lost space: 1365 Linkdata: 6734
User time 0.00, System time 0.00
Maximum resident set size 0, Integral resident set size 0
Non-physical pagefaults 437, Physical pagefaults 0, Swaps 0
Blocks in 0 out 0, Messages in 0 out 0, Signals 0
Voluntary context switches 1, Involuntary context switches 0
Pour info, je suis sur un serveur dédié Kimsufi OVH.
:(
