mysql crash

[hanlin]

Bonjour,
Cela devient vra&iment genant pour mes sites.J'ai des crash réguliers de mysql (deux fois par jours). Voici ce que je pux voir dans mes logs mysql :

Code: Tout sélectionner

100510 1:04:20 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.44' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Gentoo Linux mysql-5.0.44-r2
100510 14:11:55 [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/tmp/#sql_77a5_37.MYI'; try to repair it
100510 14:11:56 [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/tmp/#sql_77a5_59.MYI'; try to repair it
100510 14:11:56 [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/tmp/#sql_77a5_18.MYI'; try to repair it
100510 14:11:56 [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/tmp/#sql_77a5_52.MYI'; try to repair it
100510 14:11:56 [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/tmp/#sql_77a5_20.MYI'; try to repair it
100510 14:11:56 [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/tmp/#sql_77a5_49.MYI'; try to repair it
100510 14:11:56 [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/tmp/#sql_77a5_45.MYI'; try to repair it
100510 14:11:56 [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/tmp/#sql_77a5_35.MYI'; try to repair it
100510 14:11:56 [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/tmp/#sql_77a5_14.MYI'; try to repair it
100510 14:11:56 [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/tmp/#sql_77a5_51.MYI'; try to repair it
100510 14:11:56 [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/tmp/#sql_77a5_16.MYI'; try to repair it
100510 14:11:56 [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/tmp/#sql_77a5_30.MYI'; try to repair it
100510 14:11:56 [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/tmp/#sql_77a5_26.MYI'; try to repair it
100510 14:11:56 [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/tmp/#sql_77a5_54.MYI'; try to repair it
100510 19:57:18 [Note] /usr/sbin/mysqld: Normal shutdown

100510 19:57:22 [ERROR] /usr/sbin/mysqld: Sort aborted
100510 19:57:26 [Warning] /usr/sbin/mysqld: Forcing close of thread 73420 user: 'user456'

100510 19:57:26 [Warning] /usr/sbin/mysqld: Forcing close of thread 72935 user: 'user456'

100510 19:57:26 [Warning] /usr/sbin/mysqld: Forcing close of thread 72322 user: 'user456'

100510 19:57:26 [Warning] /usr/sbin/mysqld: Forcing close of thread 72164 user: 'user456'

100510 19:57:26 [Warning] /usr/sbin/mysqld: Forcing close of thread 72037 user: 'user456'

100510 19:57:26 [Warning] /usr/sbin/mysqld: Forcing close of thread 70531 user: 'user456'

100510 19:57:26 [Warning] /usr/sbin/mysqld: Forcing close of thread 70390 user: 'user456'

100510 19:57:26 [Warning] /usr/sbin/mysqld: Forcing close of thread 70319 user: 'user456'

100510 19:57:26 [Warning] /usr/sbin/mysqld: Forcing close of thread 70311 user: 'user456'

100510 19:57:26 [Warning] /usr/sbin/mysqld: Forcing close of thread 70301 user: 'user456'

100510 19:57:26 [Warning] /usr/sbin/mysqld: Forcing close of thread 70293 user: 'user456'

100510 19:57:26 [Warning] /usr/sbin/mysqld: Forcing close of thread 70272 user: 'user456'

100510 19:57:26 [Warning] /usr/sbin/mysqld: Forcing close of thread 70266 user: 'user456'

100510 19:57:26 [Warning] /usr/sbin/mysqld: Forcing close of thread 70257 user: 'user456'

100510 19:57:26 [Warning] /usr/sbin/mysqld: Forcing close of thread 69506 user: 'user456'

100510 19:57:26 [Warning] /usr/sbin/mysqld: Forcing close of thread 69176 user: 'user456'

100510 19:58:37 [Note] /usr/sbin/mysqld: Shutdown complete

100510 19:59:09 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.44' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Gentoo Linux mysql-5.0.44-r2
100510 19:59:16 [Note] /usr/sbin/mysqld: Normal shutdown

100510 19:59:18 [Note] /usr/sbin/mysqld: Shutdown complete

100510 19:59:35 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.44' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Gentoo Linux mysql-5.0.44-r2
100510 20:35:09 [ERROR] /usr/sbin/mysqld: Table '' is marked as crashed and should be repaired
100510 20:35:09 [ERROR] /usr/sbin/mysqld: Sort aborted
100511 22:47:09 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
100511 22:47:09 [ERROR] Do you already have another mysqld server running on port: 3306 ?
100511 22:47:09 [ERROR] Aborting

100511 22:47:09 [Note] /usr/sbin/mysqld: Shutdown complete

100511 22:48:15 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
100511 22:48:15 [ERROR] Do you already have another mysqld server running on port: 3306 ?
100511 22:48:15 [ERROR] Aborting

100511 22:48:15 [Note] /usr/sbin/mysqld: Shutdown complete

100511 22:48:46 [Note] /usr/sbin/mysqld: Normal shutdown

100511 22:48:52 [Warning] /usr/sbin/mysqld: Forcing close of thread 129906 user: 'tarevue'

100511 22:48:52 [Warning] /usr/sbin/mysqld: Forcing close of thread 129676 user: 'user456'

100511 22:48:52 [Warning] /usr/sbin/mysqld: Forcing close of thread 129430 user: 'user456'

100511 22:48:52 [Warning] /usr/sbin/mysqld: Forcing close of thread 129396 user: 'user456'

100511 22:48:52 [Warning] /usr/sbin/mysqld: Forcing close of thread 129375 user: 'user456'

100511 22:48:52 [Warning] /usr/sbin/mysqld: Forcing close of thread 129168 user: 'user456'

A chaque fois pour relancer le serveur je tape :

Code: Tout sélectionner

killall mysqld
ps ax | grep mysqld
rm /var/run/mysqld/mysqld.pid
/etc/init.d/mysql zap
/etc/init.d/mysql start

Ce n'est pas un solution, car cela se reproduit a chaque fois.

Pour info, voici ce que donnne la commande df -k

Code: Tout sélectionner

Sys. de fich.        1K-blocs       Occupé Disponible Capacité Monté sur
/dev/md/1             10317752   3775556   6018084  39% /
udev                   1020724       192   1020532   1% /dev
/dev/md/2            469887224 154131388 291886868  35% /home
shm                    1020724         0   1020724   0% /dev/shm


J'ai recherché sur google des solutions relatives à "[Warning] /usr/sbin/mysqld: Forcing close of thread " Il n'y en a pas de vraiment explicite
Une solution ? Je suis preneur !!
Merci encore !

[tamzac]

Salut,

quelle est ta requête ? Peut être une erreur logique

il y a ici une solution qui a été donné (sur un autre forum)

Il semblerait en fait que tu manques de place sur ton disque dur ?!? Cherche donc à savoir combien d'espace libre il te reste !

[jcaron]

C''est effectivement la première chose qui m'est venue à l'esprit vu les messages, mais ton df semble indiquer que tu aurais 6 Go disponibles, ça me paraît quand même difficile à remplir avec des tables temporaires (ou alors tu as un gros problème d'optimisation de tes requêtes...). Que disent /var/log/messages et/ou dmesg?

Jacques.

[hanlin]

danns les messages log :

Code: Tout sélectionner

May 12 14:44:17 nsXXXXX collectd[4357]: rrd_update failed: apache/apache_bytes.rrd: illegal attempt to update using time 1273668202 when last update time is 1273668202 (minimum one second step)
May 12 14:44:17 nsXXXXX collectd[31761]: rrd_update failed: apache/apache_scoreboard-waiting.rrd: could not lock RRD
May 12 14:44:17 nsXXXXX collectd[4357]: rrd_update failed: apache/apache_scoreboard-starting.rrd: could not lock RRD
May 12 14:44:18 nsXXXXX collectd[4357]: rrd_update failed: apache/apache_scoreboard-reading.rrd: could not lock RRD
May 12 14:44:18 nsXXXXX collectd[4357]: rrd_update failed: apache/apache_scoreboard-sending.rrd: could not lock RRD
May 12 14:44:18 nsXXXXX collectd[4357]: rrd_update failed: apache/apache_scoreboard-keepalive.rrd: could not lock RRD
May 12 14:44:19 nsXXXXX collectd[31761]: rrd_update failed: apache/apache_scoreboard-dnslookup.rrd: could not lock RRD
May 12 14:44:19 nsXXXXX collectd[31761]: rrd_update failed: apache/apache_scoreboard-closing.rrd: could not lock RRD
May 12 14:44:20 nsXXXXX collectd[31761]: rrd_update failed: apache/apache_scoreboard-logging.rrd: could not lock RRD
May 12 14:44:20 nsXXXXX collectd[31761]: rrd_update failed: apache/apache_scoreboard-finishing.rrd: could not lock RRD
May 12 14:44:20 nsXXXXX collectd[31761]: rrd_update failed: apache/apache_scoreboard-idle_cleanup.rrd: could not lock RRD
May 12 14:44:20 nsXXXXX collectd[31761]: No sleeping because `timeval_sub_timespec' returned non-zero!
May 12 14:44:20 nsXXXXX collectd[4357]: No sleeping because `timeval_sub_timespec' returned non-zero!
May 12 14:44:20 nsXXXXX collectd[4357]: rrd_update failed: traffic-lo.rrd: could not lock RRD
May 12 14:44:20 nsXXXXX collectd[31761]: rrd_update failed: traffic-dummy0.rrd: could not lock RRD
May 12 14:44:20 nsXXXXX collectd[4357]: rrd_update failed: traffic-eth0.rrd: could not lock RRD
May 12 14:44:20 nsXXXXX collectd[31761]: rrd_update failed: traffic-tunl0.rrd: could not lock RRD
May 12 14:44:20 nsXXXXX collectd[4357]: rrd_update failed: traffic-gre0.rrd: could not lock RRD
May 12 14:44:20 nsXXXXX collectd[31761]: rrd_update failed: swap.rrd: illegal attempt to update using time 1273668260 when last update time is 1273668260 (minimum one second step)
May 12 14:44:20 nsXXXXX collectd[4357]: rrd_update failed: processes.rrd: could not lock RRD
May 12 14:44:20 nsXXXXX collectd[31761]: rrd_update failed: memory.rrd: could not lock RRD
May 12 14:44:20 nsXXXXX collectd[31761]: rrd_update failed: load.rrd: could not lock RRD
May 12 14:44:20 nsXXXXX collectd[4357]: rrd_update failed: disk-8-0.rrd: could not lock RRD
May 12 14:44:21 nsXXXXX collectd[31761]: rrd_update failed: disk-8-1.rrd: illegal attempt to update using time 1273668260 when last update time is 1273668260 (minimum one second step)
May 12 14:44:21 nsXXXXX collectd[31761]: rrd_update failed: disk-8-2.rrd: could not lock RRD
May 12 14:44:21 nsXXXXX collectd[4357]: rrd_update failed: disk-8-3.rrd: could not lock RRD
May 12 14:44:21 nsXXXXX collectd[31761]: rrd_update failed: disk-8-16.rrd: could not lock RRD
May 12 14:44:21 nsXXXXX collectd[4357]: rrd_update failed: disk-8-17.rrd: could not lock RRD
May 12 14:44:22 nsXXXXX collectd[31761]: rrd_update failed: disk-8-18.rrd: illegal attempt to update using time 1273668260 when last update time is 1273668260 (minimum one second step)
May 12 14:44:22 nsXXXXX collectd[31761]: rrd_update failed: disk-8-19.rrd: illegal attempt to update using time 1273668260 when last update time is 1273668260 (minimum one second step)
May 12 14:44:22 nsXXXXX collectd[31761]: rrd_update failed: disk-9-2.rrd: could not lock RRD
May 12 14:44:24 nsXXXXX collectd[4357]: rrd_update failed: disk-9-1.rrd: could not lock RRD
May 12 14:44:39 nsXXXXX collectd[31761]: rrd_update failed: df-root.rrd: could not lock RRD
May 12 14:44:40 nsXXXXX collectd[4357]: rrd_update failed: df-home.rrd: could not lock RRD
May 12 14:44:40 nsXXXXX collectd[31761]: rrd_update failed: df-dev.rrd: could not lock RRD
May 12 14:44:41 nsXXXXX collectd[31761]: rrd_update failed: df-dev-shm.rrd: illegal attempt to update using time 1273668260 when last update time is 1273668260 (minimum one second step)
May 12 14:44:41 nsXXXXX collectd[4357]: rrd_update failed: cpu-0.rrd: could not lock RRD
May 12 14:44:41 nsXXXXX collectd[31761]: rrd_update failed: cpu-1.rrd: could not lock RRD
May 12 14:44:46 nsXXXXX collectd[31761]: rrd_update failed: apache/apache_requests.rrd: could not lock RRD
May 12 14:44:46 nsXXXXX collectd[31761]: rrd_update failed: apache/apache_scoreboard-open.rrd: could not lock RRD
May 12 14:44:47 nsXXXXX collectd[31761]: rrd_update failed: apache/apache_scoreboard-waiting.rrd: could not lock RRD
May 12 14:44:47 nsXXXXX collectd[31761]: rrd_update failed: apache/apache_scoreboard-sending.rrd: could not lock RRD
May 12 14:44:47 nsXXXXX collectd[31761]: rrd_update failed: apache/apache_scoreboard-dnslookup.rrd: could not lock RRD
May 12 14:44:46 nsXXXXX collectd[4357]: rrd_update failed: apache/apache_bytes.rrd: could not lock RRD
May 12 14:44:47 nsXXXXX collectd[4357]: rrd_update failed: apache/apache_scoreboard-starting.rrd: could not lock RRD
May 12 14:44:47 nsXXXXX collectd[4357]: rrd_update failed: apache/apache_scoreboard-reading.rrd: could not lock RRD
May 12 14:44:47 nsXXXXX collectd[4357]: rrd_update failed: apache/apache_scoreboard-keepalive.rrd: could not lock RRD
May 12 14:44:47 nsXXXXX collectd[4357]: rrd_update failed: apache/apache_scoreboard-closing.rrd: could not lock RRD
May 12 14:44:47 nsXXXXX collectd[31761]: rrd_update failed: apache/apache_scoreboard-logging.rrd: could not lock RRD
May 12 14:44:48 nsXXXXX collectd[4357]: rrd_update failed: apache/apache_scoreboard-finishing.rrd: could not lock RRD
May 12 14:44:48 nsXXXXX collectd[31761]: rrd_update failed: apache/apache_scoreboard-idle_cleanup.rrd: could not lock RRD
May 12 14:44:48 nsXXXXX collectd[31761]: No sleeping because `timeval_sub_timespec' returned non-zero!
May 12 14:44:48 nsXXXXX collectd[4357]: No sleeping because `timeval_sub_timespec' returned non-zero!
May 12 14:44:48 nsXXXXX collectd[4357]: rrd_update failed: traffic-lo.rrd: could not lock RRD
May 12 14:44:49 nsXXXXX collectd[31761]: rrd_update failed: traffic-dummy0.rrd: could not lock RRD
May 12 14:44:49 nsXXXXX collectd[4357]: rrd_update failed: traffic-eth0.rrd: could not lock RRD
May 12 14:44:49 nsXXXXX collectd[31761]: rrd_update failed: traffic-tunl0.rrd: could not lock RRD
May 12 14:44:50 nsXXXXX collectd[4357]: rrd_update failed: traffic-gre0.rrd: could not lock RRD
May 12 14:44:50 nsXXXXX collectd[31761]: rrd_update failed: swap.rrd: could not lock RRD
May 12 14:44:51 nsXXXXX collectd[31761]: rrd_update failed: processes.rrd: could not lock RRD
May 12 14:44:51 nsXXXXX collectd[31761]: rrd_update failed: memory.rrd: could not lock RRD
May 12 14:44:52 nsXXXXX collectd[31761]: rrd_update failed: load.rrd: could not lock RRD
May 12 14:44:52 nsXXXXX collectd[31761]: rrd_update failed: disk-8-0.rrd: could not lock RRD
May 12 14:44:52 nsXXXXX collectd[4357]: rrd_update failed: disk-8-1.rrd: could not lock RRD
May 12 14:44:53 nsXXXXX collectd[31761]: rrd_update failed: disk-8-2.rrd: could not lock RRD
May 12 14:44:53 nsXXXXX collectd[4357]: rrd_update failed: disk-8-3.rrd: could not lock RRD
May 12 14:44:56 nsXXXXX collectd[4357]: rrd_update failed: disk-8-16.rrd: could not lock RRD
May 12 14:44:56 nsXXXXX collectd[31761]: rrd_update failed: disk-8-17.rrd: could not lock RRD
May 12 14:44:56 nsXXXXX collectd[4357]: rrd_update failed: disk-8-18.rrd: could not lock RRD
May 12 14:44:58 nsXXXXX collectd[31761]: rrd_update failed: disk-8-19.rrd: illegal attempt to update using time 1273668288 when last update time is 1273668288 (minimum one second step)
May 12 14:44:58 nsXXXXX collectd[31761]: rrd_update failed: disk-9-2.rrd: illegal attempt to update using time 1273668288 when last update time is 1273668288 (minimum one second step)
May 12 14:44:58 nsXXXXX collectd[31761]: rrd_update failed: disk-9-1.rrd: could not lock RRD
May 12 14:44:58 nsXXXXX collectd[4357]: rrd_update failed: df-root.rrd: illegal attempt to update using time 1273668288 when last update time is 1273668288 (minimum one second step)
May 12 14:44:58 nsXXXXX collectd[4357]: rrd_update failed: df-dev.rrd: illegal attempt to update using time 1273668288 when last update time is 1273668288 (minimum one second step)
May 12 14:44:58 nsXXXXX collectd[4357]: rrd_update failed: df-home.rrd: could not lock RRD
May 12 14:44:58 nsXXXXX collectd[31761]: rrd_update failed: df-dev-shm.rrd: could not lock RRD
May 12 14:45:01 nsXXXXX collectd[4357]: rrd_update failed: cpu-0.rrd: could not lock RRD
May 12 14:45:05 nsXXXXX collectd[4357]: rrd_update failed: cpu-1.rrd: could not lock RRD
May 12 14:45:05 nsXXXXX cron[4354]: (root) CMD (/usr/local/rtm/bin/rtm 24 > /dev/null 2> /dev/null)
May 12 14:45:08 nsXXXXX collectd[4357]: rrd_update failed: apache/apache_requests.rrd: could not lock RRD
May 12 14:45:09 nsXXXXX collectd[31761]: rrd_update failed: apache/apache_bytes.rrd: illegal attempt to update using time 1273668288 when last update time is 1273668288 (minimum one second step)
May 12 14:45:09 nsXXXXX collectd[31761]: rrd_update failed: apache/apache_scoreboard-open.rrd: illegal attempt to update using time 1273668288 when last update time is 1273668288 (minimum one second step)
May 12 14:45:09 nsXXXXX collectd[31761]: rrd_update failed: apache/apache_scoreboard-waiting.rrd: illegal attempt to update using time 1273668288 when last update time is 1273668288 (minimum one second step)
May 12 14:45:09 nsXXXXX collectd[31761]: rrd_update failed: apache/apache_scoreboard-starting.rrd: illegal attempt to update using time 1273668288 when last update time is 1273668288 (minimum one second step)
May 12 14:45:09 nsXXXXX collectd[31761]: rrd_update failed: apache/apache_scoreboard-reading.rrd: illegal attempt to update using time 1273668288 when last update time is 1273668288 (minimum one second step)
May 12 14:45:09 nsXXXXX collectd[31761]: rrd_update failed: apache/apache_scoreboard-sending.rrd: illegal attempt to update using time 1273668288 when last update time is 1273668288 (minimum one second step)
May 12 14:45:09 nsXXXXX collectd[31761]: rrd_update failed: apache/apache_scoreboard-keepalive.rrd: illegal attempt to update using time 1273668288 when last update time is 1273668288 (minimum one second step)
May 12 14:45:09 nsXXXXX collectd[31761]: rrd_update failed: apache/apache_scoreboard-dnslookup.rrd: illegal attempt to update using time 1273668288 when last update time is 1273668288 (minimum one second step)
May 12 14:45:09 nsXXXXX collectd[31761]: rrd_update failed: apache/apache_scoreboard-closing.rrd: illegal attempt to update using time 1273668288 when last update time is 1273668288 (minimum one second step)
May 12 14:45:09 nsXXXXX collectd[31761]: rrd_update failed: apache/apache_scoreboard-logging.rrd: illegal attempt to update using time 1273668288 when last update time is 1273668288 (minimum one second step)
May 12 14:45:09 nsXXXXX collectd[31761]: rrd_update failed: apache/apache_scoreboard-finishing.rrd: illegal attempt to update using time 1273668288 when last update time is 1273668288 (minimum one second step)
May 12 14:45:09 nsXXXXX collectd[31761]: rrd_update failed: apache/apache_scoreboard-idle_cleanup.rrd: could not lock RRD
May 12 14:45:09 nsXXXXX collectd[31761]: No sleeping because `timeval_sub_timespec' returned non-zero!
May 12 14:45:09 nsXXXXX collectd[4357]: No sleeping because `timeval_sub_timespec' returned non-zero!
May 12 14:45:09 nsXXXXX collectd[4357]: rrd_update failed: traffic-lo.rrd: could not lock RRD
May 12 14:45:09 nsXXXXX collectd[31761]: rrd_update failed: traffic-dummy0.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:09 nsXXXXX collectd[31761]: rrd_update failed: traffic-eth0.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:09 nsXXXXX collectd[31761]: rrd_update failed: traffic-tunl0.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:09 nsXXXXX collectd[31761]: rrd_update failed: traffic-gre0.rrd: could not lock RRD
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: swap.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: processes.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: memory.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: load.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: disk-8-0.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: disk-8-1.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: disk-8-2.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: disk-8-3.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: disk-8-16.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: disk-8-17.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: disk-8-18.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: disk-8-19.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: disk-9-2.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: disk-9-1.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: df-root.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: df-dev.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: df-home.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: df-dev-shm.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: cpu-0.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: cpu-1.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: apache/apache_requests.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: apache/apache_bytes.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: apache/apache_scoreboard-open.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: apache/apache_scoreboard-waiting.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: apache/apache_scoreboard-starting.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: apache/apache_scoreboard-reading.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: apache/apache_scoreboard-sending.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: apache/apache_scoreboard-keepalive.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: apache/apache_scoreboard-dnslookup.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: apache/apache_scoreboard-closing.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: apache/apache_scoreboard-logging.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: apache/apache_scoreboard-finishing.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:14 nsXXXXX collectd[4357]: rrd_update failed: apache/apache_scoreboard-idle_cleanup.rrd: illegal attempt to update using time 1273668309 when last update time is 1273668309 (minimum one second step)
May 12 14:45:20 nsXXXXX collectd[31761]: rrd_update failed: traffic-dummy0.rrd: could not lock RRD
May 12 14:45:20 nsXXXXX collectd[31761]: rrd_update failed: traffic-tunl0.rrd: could not lock RRD


J'ai pas tout mis mais les lignes sont à peu prêt les mêmes dans le reste du fichier

[Julia41]

Je dis peut-être des conneries, mais pas mal de personnes avaient eu ce genre de soucis sur des noyaux OVH GRS en 64 bits...
Il m'ait aussi arrivé il y a quelques jours de voir une requête "temporaire" écrire un fichier de plus de 12Go (qui a dit site codé avec les pieds ?)
Voilà pour 2/3 pistes, aucune idée donc mais possible que...

[tamzac]

A priori, je pencherai pour un problème d'accès (ou de non-accès).

Fais donc un essai en ouvrant plus de droits sur tes fichiers de base ...

le user utilisé pour déclencher les process a-t-il des droits suffisants ?

[jcaron]

Et un "grep -v collected /var/log/messages"? Parce que collectd on s'en fout un peu.

Evidemment, si tu as une requête du genre select * from table t1,table t2 non qualifiée, tu peux très vite te retrouver avec une table temporaire énorme. 10 000 lignes ^ 2 ça fait tout de suite une table de plusieurs Go. Et le df, c'est après avoir relancé le tout, ou c'est pendant le problème?

Jacques.

[hanlin]

Ce sont des sites qui tournent sous joomla.
voici un extrait du top :
Tasks: 163 total, 5 running, 158 sleeping, 0 stopped, 0 zombie
Cpu(s): 56.4% us, 28.7% sy, 0.0% ni, 1.5% id, 11.9% wa, 0.2% hi, 1.3% si
Mem: 2041448k total, 1501968k used, 539480k free, 123620k buffers
Swap: 1044208k total, 105144k used, 939064k free, 997104k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
8470 mysql 40 0 215m 126m 4456 S 130 6.3 59:25.12 mysqld

[hanlin]

le df c'est apres avoir relancé.

[tamzac]

Ce sont des sites qui tournent sous joomla.

Oui je m'en suis douté en visitant les sites que vous réalisez.

Le problème est peut-être alors lié à un add-on, si vous en utilisez un.

Le problème est spécifique à un serveur ou à tous ?

[hanlin]

Je ne comprends pas la question. L'ensemble de mes sites sont hebergés sur un serveur unique

[tamzac]

Dans le cas où vous utilisiez plusieurs serveurs, il aurait été intéressant de constater la redondance du problème et donc de déterminer si c'était un problème en commun à tous vos serveurs ou simplement un problème isolé sur un seul serveur !

[hanlin]

Si j'utilisais plusieurs serveurs je l'aurais précisé au départ...

[jcaron]

Ben ton top il nous apprend que ta machine était plutôt ras la gueule au moment où tu l'as capturé, mais (a priori) pas de lien avec ton problème initial. Regarde un peu les slow-queries de mysql, et éventuellement ce que dit show full processlist, et explain sur les requêtes les plus lourdes. Regarde aussi s'il y a des variations plus ou moins importantes de l'espace disque disponible sur / et/ou le nombre et la taille des fichiers temporaires mysql dans /tmp.

Le but du jeu, c'est de savoir si c'est effectivement dû à un problème de place lié à des requêtes qui ont besoin de tables temporaires trop grosses. Si c'est le cas, il y a deux solutions:
- déplacer /tmp (ou l'endroit où mysql crée ses tables temporaires) dans une partition où il y a plus de place (mais ça n'enlève rien au fait qu'il crée des tables temporaires énoooormes qui bouffent probablement des ressources pour pas grand chose).
- trouver les requêtes problématiques et les corriger (la bonne solution), directement ou indirectement (il est possible qu'avec des index bien placés le problème puisse être résolu).

Jacques.

[hanlin]

j'utilise un composant de rewriting pour joomla shsef404 il a 302094 urls enregistrées. Cela signifie que pour l'ensemble de ces urls il doit parcourir la table pour attribuer l'url reecrite.
Peut etre est ce du à cela mais je ne suis pas sur.