Hello,
our mysql 5.0.67 on a AMD Opteron 2218 with 2 GB RAM is crashing from
time to time.
This what is in the log:
081028 6:37:30 - 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=402653184
read_buffer_size=2097152
max_used_connections=31
max_connections=10000
threads_connected=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections
= 41353216 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x1fa7feb0
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=0x4510b0e0, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
(nil)
New value of fp=0x1fa7feb0 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 0x201766f0 = SELECT DISTINCT session_id,
DATE_FORMAT(access_time,'%Y-%m-%d %H:%i') as fmtDate, substring(
access_time, 1, 0 ) AS dd, COUNT(access_time) as cnt FROM
curry_stattraq WHERE session_id <> 0 GROUP BY session_id ORDER BY dd
DESC LIMIT 0, 1000
thd->thread_id=682597
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
081028 06:37:31 mysqld restarted
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
081028 6:37:31 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
081028 6:37:50 InnoDB: Started; log sequence number 0 1081908061
081028 6:37:51 [Note] /vrmd/mysql/mysql-5.0.67/libexec/mysqld: ready
for connections.
Version: '5.0.67-log' socket: '/tmp/mysql.sock' port: 3306 Source
distribution
Although the log doesn't state the database name, I found out the
specific database. I'm a bit astounded that anything might be wrong with
the tables, since we did a rebuild (mysqldump and import) of all tables.
To be sure, I started a repair table anyway:
mysql> repair table curry_stattraq;
+------------------------+--------+----------+----------+
| Table | Op | Msg_type | Msg_text |
+------------------------+--------+----------+----------+
| db18841.curry_stattraq | repair | status | OK |
+------------------------+--------+----------+----------+
1 row in set (10.06 sec)
Now I was trying to do the sql query:
mysql> SELECT DISTINCT session_id, DATE_FORMAT(access_time,'%Y-%m-%d
%H:%i') as fmtDate, substring( access_time, 1, 0 ) AS dd,
COUNT(access_time) as cnt FROM curry_stattraq WHERE session_id <> 0
GROUP BY session_id ORDER BY dd DESC LIMIT 0, 1000;
ERROR 2013 (HY000): Lost connection to MySQL server during query
What is mysql doing here? Why does it crash? The table seems to be fine
and there is enough RAM and CPU left to process the query. Any ideas?
Kind regards
Marten
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
