091227 06:31:02  mysqld started
091227  6:31:02 [Warning] 'user' entry 'root@GTWebFMaster' ignored in --skip-name-resolve mode.
091227  6:31:02 [Warning] 'user' entry '@GTWebFMaster' ignored in --skip-name-resolve mode.
091227  6:31:02 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.56-enterprise-gpl-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Enterprise Server (GPL)
091227 10:20:18 - 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=2147483648
read_buffer_size=4194304
max_used_connections=188
max_connections=800
threads_connected=46
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 8650752 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0xd77c430
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=0x43d49fd0, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
(nil)
New value of fp=0xd77c430 failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/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
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0xe2f9520 = SELECT
						thread.threadid
						FROM vb_thread AS thread 
						
						INNER JOIN vb_post AS post ON(thread.threadid = post.threadid )
						WHERE MATCH(post.title, post.pagetext) AGAINST ('+hack +huyen +tinh' IN BOOLEAN MODE) AND post.visible = 1
thd->thread_id=191969
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.

Number of processes running now: 0
091227 10:20:19  mysqld restarted
091227 10:20:19 [Warning] 'user' entry 'root@GTWebFMaster' ignored in --skip-name-resolve mode.
091227 10:20:19 [Warning] 'user' entry '@GTWebFMaster' ignored in --skip-name-resolve mode.
091227 10:20:19 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.56-enterprise-gpl-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Enterprise Server (GPL)
091227 11:01:14 - 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=2147483648
read_buffer_size=4194304
max_used_connections=127
max_connections=800
threads_connected=7
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 8650752 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x2aab34243290
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=0x43a57fd0, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
(nil)
Stack trace seems successful - bottom reached
Please read http://dev.mysql.com/doc/mysql/en/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
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0xa823870 = SELECT
						thread.threadid
						FROM vb_thread AS thread 
						
						INNER JOIN vb_post AS post ON(thread.threadid = post.threadid )
						WHERE MATCH(post.title, post.pagetext) AGAINST ('+sever +phung' IN BOOLEAN MODE) AND post.visible = 1
thd->thread_id=51924
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.

Number of processes running now: 0
091227 11:01:14  mysqld restarted
091227 11:01:15 [Warning] 'user' entry 'root@GTWebFMaster' ignored in --skip-name-resolve mode.
091227 11:01:15 [Warning] 'user' entry '@GTWebFMaster' ignored in --skip-name-resolve mode.
091227 11:01:15 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.56-enterprise-gpl-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Enterprise Server (GPL)
091227 11:01:38 - 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=2147483648
read_buffer_size=4194304
max_used_connections=17
max_connections=800
threads_connected=9
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 8650752 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x2aab30031670
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=0x41be3fd0, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
(nil)
Stack trace seems successful - bottom reached
Please read http://dev.mysql.com/doc/mysql/en/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
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x11832d20 = SELECT
						thread.threadid
						FROM vb_thread AS thread 
						
						INNER JOIN vb_post AS post ON(thread.threadid = post.threadid )
						WHERE MATCH(post.title, post.pagetext) AGAINST ('+sever +phung' IN BOOLEAN MODE) AND post.visible = 1
thd->thread_id=346
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.

Number of processes running now: 0
091227 11:01:38  mysqld restarted
091227 11:01:39 [Warning] 'user' entry 'root@GTWebFMaster' ignored in --skip-name-resolve mode.
091227 11:01:39 [Warning] 'user' entry '@GTWebFMaster' ignored in --skip-name-resolve mode.
091227 11:01:39 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.56-enterprise-gpl-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Enterprise Server (GPL)