List:General Discussion« Previous MessageNext Message »
From:Roy yeung Date:September 14 2007 2:02am
Subject:mysql shutdow suddenly
View as plain text  
Hello.

   i am using Redhat EL3 linux. and mysql version is 3.23.49a-Max
but sometime will shutdown suddenly. when i read the mysql log file
have found as below.

please help me.. tks
Roy



InnoDB: Assertion failure in thread 143396 in file mem0pool.c line 345
InnoDB: We intentionally generate a memory trap.
InnoDB: Send a detailed bug report to mysql@stripped
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=402649088
record_buffer=2093056
sort_buffer=2097144
max_used_connections=56
max_connections=100
threads_connected=52
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 802411 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...
Stack range sanity check OK, backtrace follows:
0x806e2d4
0x82b12b8
0x8261dc9
0x8260e83
0x81d65aa
0x81d2e63
0x81bcb1e
0x81927df
0x8195441
0x80c02c6
0x8098a37
0x8093a47
0x8093af7
0x8093803
0x808ccbb
0x80750c0
0x80791fc
0x8074284
0x8073637
Stack trace seems successful - bottom reached
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
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x86938b0 = SELECT SUM(D.DRAFT = 'N') WAIT_SIGN,SUM(D.DRAFT
= 'Y') TEMP_SIGN,SUM(D.COMMING_TYPE IN('U','V')) PRESSING_SIGN,SUM(D.DRAFT
= 'N' AND ((A.ROLE_ID = 108 AND D.FLAG LIKE 'N%') OR (A.ROLE_ID != 108 AND
D.FLAG LIKE '%N'))) NEW_SIGN FROM  HS_STATION_ROLE A, HS_STATION B,
HS_FLOW C, HS_SIGNATURE D WHERE A.STATION_ID = B.STATION_ID    AND
A.ROLE_ID IN (108) AND B.ACTIVE != 'N'              AND B.FLOW_ID =
C.FLOW_ID          AND C.ACTIVE = 'Y'               AND D.STATION_ID =
B.STATION_ID    AND D.ROLE_ID = A.ROLE_ID          AND D.USER_SIGNATURE IS
NULL       AND ((A.ROLE_ID = 108 AND (D.FLAG LIKE 'N%' OR D.FLAG LIKE
'O%')) OR (A.ROLE_ID != 108 AND D.PROXY_ROLE_ID = 108 AND (D.FLAG LIKE
'%N' OR D.FLAG LIKE '%O')))
thd->thread_id=1056

Successfully dumped variables, if you ran with --log, take a look at the
details of what thread 1056 did to cause the crash.  In some cases of really
bad corruption, the values shown above may be invalid

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

Number of processes running now: 0
070913 14:24:46  mysqld restarted
070913 14:24:46  Can't start server: Bind on TCP/IP port: Address already
in use
070913 14:24:46  Do you already have another mysqld server running on
port: 3306 ?
070913 14:24:46  Aborting

070913 14:24:46  /usr/sbin/mysqld-max: Shutdown Complete


Thread
mysql shutdow suddenlyRoy yeung14 Sep