MySQL Forums
Forum List  »  French

Plantage serveur : mysqld got signal 11
Posted by: James Fabioso
Date: February 08, 2010 07:24AM

Hello !

Je m'en remets à vous, experts de MySQL, pour un problème assez préocuppant sur mon serveur : Il y a des plantages à répétition (une fois / jour ou tous les 2 jours) qui provoquent une "error establishing a database connection".
Le seul site que j'héberge sur mon serveur est un blog Wordpress (version la plus récente).

Quand aux logs, voici l'erreur :
Feb 8 12:17:14 ns210031 mysqld[998]: 100208 12:17:14 - mysqld got signal 11;
Feb 8 12:17:14 ns210031 mysqld[998]: This could be because you hit a bug. It is also possible that this binary
Feb 8 12:17:14 ns210031 mysqld[998]: or one of the libraries it was linked against is corrupt, improperly built,
Feb 8 12:17:14 ns210031 mysqld[998]: or misconfigured. This error can also be caused by malfunctioning hardware.
Feb 8 12:17:14 ns210031 mysqld[998]: We will try our best to scrape up some info that will hopefully help diagnose
Feb 8 12:17:14 ns210031 mysqld[998]: the problem, but since we have already crashed, something is definitely wrong
Feb 8 12:17:14 ns210031 mysqld[998]: and this may fail.
Feb 8 12:17:14 ns210031 mysqld[998]:
Feb 8 12:17:14 ns210031 mysqld[998]: key_buffer_size=16777216
Feb 8 12:17:14 ns210031 mysqld[998]: read_buffer_size=131072
Feb 8 12:17:14 ns210031 mysqld[998]: max_used_connections=38
Feb 8 12:17:14 ns210031 mysqld[998]: max_connections=2000
Feb 8 12:17:14 ns210031 mysqld[998]: threads_connected=8
Feb 8 12:17:14 ns210031 mysqld[998]: It is possible that mysqld could use up to
Feb 8 12:17:14 ns210031 mysqld[998]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 4368368 K
Feb 8 12:17:14 ns210031 mysqld[998]: bytes of memory
Feb 8 12:17:14 ns210031 mysqld[998]: Hope that's ok; if not, decrease some variables in the equation.
Feb 8 12:17:14 ns210031 mysqld[998]:
Feb 8 12:17:14 ns210031 mysqld[998]: thd=0x7f58701cf510
Feb 8 12:17:14 ns210031 mysqld[998]: Attempting backtrace. You can use the following information to find out
Feb 8 12:17:14 ns210031 mysqld[998]: where mysqld died. If you see no messages after this, something went
Feb 8 12:17:14 ns210031 mysqld[998]: terribly wrong...
Feb 8 12:17:14 ns210031 mysqld[998]: Cannot determine thread, fp=0x7f58701cf510, backtrace may not be correct.
Feb 8 12:17:14 ns210031 mysqld[998]: Bogus stack limit or frame pointer, fp=0x7f58701cf510, stack_bottom=0x446d0000, thread_stack=131072, aborting backtrace.
Feb 8 12:17:14 ns210031 mysqld[998]: Trying to get some variables.
Feb 8 12:17:14 ns210031 mysqld[998]: Some pointers may be invalid and cause the dump to abort...
Feb 8 12:17:14 ns210031 mysqld[998]: thd->query at 0x24b6d70 = SELECT SQL_CALC_FOUND_ROWS distinct wp_posts.* FROM wp_posts LEFT JOIN wp_term_relationships ON (wp_posts.ID = wp_term_relationships.object_id = wp_posts.ID AND wp_term_taxonomy.taxonomy = 'category' AND wp_term_taxonomy.term_id IN (8975) ) ORDER BY wp_posts.post_date DESC LIMIT 0, 30
Feb 8 12:17:14 ns210031 mysqld[998]: thd->thread_id=28238
Feb 8 12:17:14 ns210031 mysqld[998]: The manual page at http://www.mysql.com/doc/en/Crashing.html contains
Feb 8 12:17:14 ns210031 mysqld[998]: information that should help you find out what is causing the crash.


Erreur qui a lieu chaque jour à peu près :
Feb 5 23:31:41 ns210031 mysqld[12731]: 100205 23:31:41 - mysqld got signal 11;
Feb 6 11:42:26 ns210031 mysqld[9763]: 100206 11:42:26 - mysqld got signal 11;
Feb 8 12:17:14 ns210031 mysqld[998]: 100208 12:17:14 - mysqld got signal 11;
Feb 8 12:46:26 ns210031 mysqld[9345]: 100208 12:46:26 - mysqld got signal 11;

Est-ce que vos esprits éclairés auraient un élément de réponse au sujet de ce bug ?

Ma config :
debian, avec mysql 5.0.51a-24
16GB de ram

Merci.

Options: ReplyQuote


Subject
Views
Written By
Posted
Plantage serveur : mysqld got signal 11
4243
February 08, 2010 07:24AM


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.