Le Lundi 22 Octobre 2001 21:17, vous avez �crit :
> Pourquoi le voit-il ? un fichier pid qui reste ? Regarde dans /var
> ( find /var -name '*mysql*' -print ) s'il ne reste pas qque chose m�me
> quand mysqld ne tourne pas en tant que processus.
> Ne reste-il vraiment aucun process ( ps -aux | grep mysqld ) ?

find /var -name '*mysql*' -print donne:

/var/lib/mysql
/var/lib/mysql/mysql.sock
/var/lib/mysql.directory
/var/www/html/nuke/images/powered/mysql2.gif
/var/www/html/nuke/images/powered/mysql.gif
/var/www/html/mysql
/var/lock/subsys/mysql

[root@localhost klaus]# ps -aux | grep mysqld
root      6775  0.0  0.2  1936  760 pts/1    S    21:27   0:00 grep mysqld
[root@localhost klaus]# kill -9 6775
bash: kill: (6775) - No such pid
[root@localhost klaus]# ps -aux | grep mysqld
root      6781  0.0  0.2  1936  760 pts/1    S    21:28   0:00 grep mysqld
[root@localhost klaus]# kill -9 6781
bash: kill: (6781) - No such pid

tr�s curieux non ?


> Tu n'as rien dans /var/log/messages ? Pas une trace dans un log quelconque
> ?

Dans /var/lib/mysql/localhost.localdomain.err, j'ai trouv� tout ce long 
passage:

011022 20:51:22  mysqld started
011022 20:51:22  /usr/sbin/mysqld: Table 'mysql.host' doesn't exist
011022 20:51:22  /usr/sbin/mysqld: Normal shutdown

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 agaist 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=8388600
record_buffer=131072
sort_buffer=2097144
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 225791 K
bytes of memory
Hope that's ok, if not, decrease some variables in the equation

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=0xbf5ff648, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80b39de
0x400363ab
0x80b2e0f
0x80b2f3f
0x400339c7
0x401f176a
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://www.mysql.com/doc/U/s/Using_stack_trace.html and follow 
instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains
information that should help you find out what is causing the crash
Fatal signal 11 while backtracing
011022 20:51:22  mysqld ended

011022 21:01:15  mysqld started
011022 21:01:16  /usr/sbin/mysqld: Table 'mysql.host' doesn't exist
011022 21:01:16  mysqld ended

En fait, il semble s'agir d'un bug mysql, je vais installer la version 4 et 
on va voir

merci
Klaus
-- 
l'annuaire des sites d'allemand:
http://katalogdeutsch.free.fr

Vous souhaitez acquerir votre Pack ou des Services MandrakeSoft?
Rendez-vous sur "http://www.mandrakestore.com";

Répondre à