Your message dated Thu, 05 Jul 2012 15:53:12 +0000
with message-id <[email protected]>
and subject line Bug#680362: Removed package(s) from unstable
has caused the Debian Bug report #600887,
regarding MySQL Server Crash
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
600887: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600887
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mysql-server
Version: 5.1.49-1
MySQL is crashing about once per day.
101020 18:00:25 - 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=1048576
read_buffer_size=262144
max_used_connections=6
max_threads=151
threads_connected=5
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 50314 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x41120590
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_bottom = 0x410ca36c thread_stack 0x20000
/usr/sbin/mysqld(my_print_stacktrace+0x2d) [0x2b0561ad]
/usr/sbin/mysqld(handle_segfault+0x494) [0x2ad1d8c4]
/lib/libpthread.so.0(+0xde68) [0x40036e68]
/usr/sbin/mysqld(JOIN::optimize()+0x59b) [0x2ad9fddb]
/usr/sbin/mysqld(mysql_select(THD*, Item***, TABLE_LIST*, unsigned
int, List&, Item*, unsigned int, st_order*, st_order*, Item*,
st_order*, unsigned long long, select_result*, st_select_lex_unit*,
st_select_lex*)+0x79) [0x2ada3539]
/usr/sbin/mysqld(handle_select(THD*, st_lex*, select_result*, unsigned
long)+0x164) [0x2ada9744]
/usr/sbin/mysqld(mysql_execute_command(THD*)+0x75eb) [0x2ad37b0b]
/usr/sbin/mysqld(mysql_parse(THD*, char const*, unsigned int, char
const**)+0x42a) [0x2ad38b0a]
/usr/sbin/mysqld(dispatch_command(enum_server_command, THD*, char*,
unsigned int)+0xe75) [0x2ad39995]
/usr/sbin/mysqld(do_command(THD*)+0xf3) [0x2ad3ac63]
/usr/sbin/mysqld(handle_one_connection+0x268) [0x2ad292f8]
/lib/libpthread.so.0(+0x57b0) [0x4002e7b0]
/lib/libc.so.6(clone+0x5e) [0x402b18fe]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x2b3e9840 = insert into `new_q_lines` select * from `v_q_lines`
thd->thread_id=2233
thd->killed=NOT_KILLED
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.
I wish I knew more about the crash, but that's all I've got.
--- End Message ---
--- Begin Message ---
Version: 5.1.62-1+rm
Dear submitter,
as the package mysql-5.1 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see http://bugs.debian.org/680362
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl (the ftpmaster behind the curtain)
--- End Message ---
