Package: mysql-server-5.0
Version: 5.0.45-1
Severity: important
One of my mysql server crashes 3-4 times a week, with signal 11. I
downloaded mysql-5.0.45-linux-i686.tar.gz from mysql.com and this server
runs without any problems, with the same command line.
The diff of the mysqladmin variables:
| expire_logs_days | 0 | |
expire_logs_days | 10
| have_dynamic_loading | NO | |
have_dynamic_loading | YES
| have_example_engine | YES | |
have_example_engine | NO
| key_buffer_size | 8388600 | |
key_buffer_size | 16777216
| log_bin | OFF | | log_bin
| ON
| max_allowed_packet | 1048576 | |
max_allowed_packet | 16776192
| max_binlog_size | 1073741824 | |
max_binlog_size | 104857600
| query_cache_size | 0 | |
query_cache_size | 16777216
| server_id | 0 | | server_id
| 1
| storage_engine | MyISAM | |
storage_engine | InnoDB
| table_type | MyISAM | | table_type
| InnoDB
| thread_cache_size | 0 | |
thread_cache_size | 8
| thread_stack | 126976 | |
thread_stack | 131072
| tmpdir | /tmp/ | | tmpdir
| /tmp
| version | 5.0.45 | | version
| 5.0.45-Debian_1-log
| version_comment | MySQL Community Server (GPL) | |
version_comment | Debian etch distribution
| version_compile_machine | i686 | |
version_compile_machine | i486
The crashs couldn't be connected to a particular query.
The resolve_stack_dump produces always the same output:
resolve_stack_dump -s mysqld.sym -n /root/mysql_crash_dump | c++filt
0x81ee880 get_one_option(int, my_option const*, char*) + 208
0xb7cf4bdf _end + -1352870937
0x824bf35 select_describe(JOIN*, bool, bool, bool, char const*) + 821
0x824cfba select_describe(JOIN*, bool, bool, bool, char const*) + 5050
0x8254c86 select_insert::prepare(List<Item>&, st_select_lex_unit*) + 1030
0x82556af delayed_insert::handle_inserts() + 1487
0x8207673 dispatch_command(enum_server_command, THD*, char*, unsigned int) + 339
0x820ab60 MYSQLparse(void*) + 672
0x820b119 MYSQLparse(void*) + 2137
The reportbug failed to exec debconf-show, but here is the output of
debconf-show mysql-server-5.0 executed from console:
* mysql-server/root_password: (password omitted)
mysql-server-5.0/really_downgrade: false
* mysql-server-5.0/need_sarge_compat: false
mysql-server-5.0/start_on_boot: true
mysql-server/error_setting_password:
mysql-server-5.0/nis_warning:
mysql-server-5.0/postrm_remove_databases: false
mysql-server-5.0/need_sarge_compat_done: true
The log entrys:
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: 071023 8:33:06 - mysqld
got signal 11;
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: This could be because
you hit a bug. It is also possible that this binary
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: or one of the libraries
it was linked against is corrupt, improperly built,
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: or misconfigured. This
error can also be caused by malfunctioning hardware.
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: We will try our best to
scrape up some info that will hopefully help diagnose
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: the problem, but since
we have already crashed, something is definitely wrong
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: and this may fail.
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]:
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: key_buffer_size=8384512
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: read_buffer_size=131072
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: max_used_connections=101
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: max_connections=100
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: threads_connected=22
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: It is possible that
mysqld could use up to
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: key_buffer_size +
(read_buffer_size + sort_buffer_size)*max_connections = 225787 K
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: bytes of memory
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: Hope that's ok; if not,
decrease some variables in the equation.
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]:
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: thd=0xb1024de8
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: Attempting backtrace.
You can use the following information to find out
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: where mysqld died. If
you see no messages after this, something went
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: terribly wrong...
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: Cannot determine thread,
fp=0xb235b718, backtrace may not be correct.
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: Stack range sanity check
OK, backtrace follows:
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: 0x81ee880
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: 0xb7c76bdf
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: 0x824bf35
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: 0x824cfba
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: 0x8254c86
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: 0x82556af
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: 0x8207673
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: 0x820ab60
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: 0x820b119
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: 0x820c4a7
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: 0x820cfe0
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: 0xb7eb52d3
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: 0xb7cd82fe
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: New value of fp=(nil)
failed sanity check, terminating stack trace!
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: Please read
http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow
instructions on how to resolve the stack trace. Resolved
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: stack trace is much more
helpful in diagnosing the problem, so please do
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: resolve it
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: Trying to get some
variables.
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: Some pointers may be
invalid and cause the dump to abort...
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: thd->query at 0x8f8bae0
= SELECT id,nick,note,UNIX_TIMESTAMP(crdate),email FROM guestbook ORDER BY
crdate DESC LIMIT 9780,12
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: thd->thread_id=101407
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: The manual page at
http://www.mysql.com/doc/en/Crashing.html contains
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[18829]: information that should
help you find out what is causing the crash.
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld_safe[25374]: Number of processes
running now: 0
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld_safe[29681]: restarted
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[29117]: 071023 8:33:06 InnoDB:
Database was not shut down normally!
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[29117]: InnoDB: Starting crash
recovery.
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[29117]: InnoDB: Reading
tablespace information from the .ibd files...
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[29117]: InnoDB: Restoring
possible half-written data pages from the doublewrite
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[29117]: InnoDB: buffer...
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[29117]: 071023 8:33:06 InnoDB:
Starting log scan based on checkpoint at
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[29117]: InnoDB: log sequence
number 0 3801045577.
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[29117]: InnoDB: Doing recovery:
scanned up to log sequence number 0 3801046010
Oct 23 08:33:06 [EMAIL PROTECTED]/mamba mysqld[29117]: 071023 8:33:06 InnoDB:
Starting an apply batch of log records to the database...
Oct 23 08:33:07 [EMAIL PROTECTED]/mamba mysqld[29117]: InnoDB: Progress in
percents: 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93
94 95 96 97 98 99
Oct 23 08:33:07 [EMAIL PROTECTED]/mamba mysqld[29117]: InnoDB: Apply batch
completed
Oct 23 08:33:07 [EMAIL PROTECTED]/mamba mysqld[29117]: InnoDB: In a MySQL
replication slave the last master binlog file
Oct 23 08:33:07 [EMAIL PROTECTED]/mamba mysqld[29117]: InnoDB: position 0 139,
file name mysql-bin.000672
Oct 23 08:33:07 [EMAIL PROTECTED]/mamba mysqld[29117]: InnoDB: Last MySQL
binlog file position 0 1368536, file name /var/log/mysql/mysql-bin.000694
Oct 23 08:33:07 [EMAIL PROTECTED]/mamba mysqld[29117]: 071023 8:33:07 InnoDB:
Started; log sequence number 0 3801046010
Oct 23 08:33:07 [EMAIL PROTECTED]/mamba mysqld[29117]: 071023 8:33:07 [Note]
Recovering after a crash using /var/log/mysql/mysql-bin
Oct 23 08:33:07 [EMAIL PROTECTED]/mamba mysqld[29117]: 071023 8:33:07 [Note]
Starting crash recovery...
Oct 23 08:33:07 [EMAIL PROTECTED]/mamba mysqld[29117]: 071023 8:33:07 [Note]
Crash recovery finished.
Oct 23 08:33:07 [EMAIL PROTECTED]/mamba mysqld[29117]: 071023 8:33:07
[Warning] Found invalid password for user: '[EMAIL PROTECTED]'; Ignoring user
Oct 23 08:33:07 [EMAIL PROTECTED]/mamba mysqld[29117]: 071023 8:33:07
[Warning] Found invalid password for user: '[EMAIL PROTECTED]'; Ignoring user
Oct 23 08:33:07 [EMAIL PROTECTED]/mamba mysqld[29117]: 071023 8:33:07
[Warning] Found invalid password for user: '[EMAIL PROTECTED]'; Ignoring user
Oct 23 08:33:07 [EMAIL PROTECTED]/mamba mysqld[29117]: 071023 8:33:07
[Warning] Found invalid password for user: '[EMAIL PROTECTED]'; Ignoring user
Oct 23 08:33:07 [EMAIL PROTECTED]/mamba mysqld[29117]: 071023 8:33:07
[Warning] Found invalid password for user: '[EMAIL PROTECTED]'; Ignoring user
Oct 23 08:33:07 [EMAIL PROTECTED]/mamba mysqld[29117]: 071023 8:33:07
[Warning] Found invalid password for user: '[EMAIL PROTECTED]'; Ignoring user
Oct 23 08:33:07 [EMAIL PROTECTED]/mamba mysqld[29117]: 071023 8:33:07
[Warning] Found invalid password for user: '[EMAIL PROTECTED]'; Ignoring user
Oct 23 08:33:07 [EMAIL PROTECTED]/mamba mysqld[29117]: 071023 8:33:07
[Warning] Found invalid password for user: '[EMAIL PROTECTED]'; Ignoring user
Oct 23 08:33:07 [EMAIL PROTECTED]/mamba mysqld[29117]: 071023 8:33:07
[Warning] Neither --relay-log nor --relay-log-index were used; so replication
may
break when this MySQL server acts as a slave and has his hostname changed!!
Please use '--relay-log=/var/run/mysqld/mysqld-relay-bin' to avoid this problem.
Oct 23 08:33:07 [EMAIL PROTECTED]/mamba mysqld[29117]: 071023 8:33:07 [Note]
/usr/sbin/mysqld: ready for connections.
Oct 23 08:33:07 [EMAIL PROTECTED]/mamba mysqld[29117]: Version:
'5.0.45-Debian_1-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Debian
etch distribution
Oct 23 08:33:07 [EMAIL PROTECTED]/mamba mysqld[29117]: 071023 8:33:07 [Note]
Slave SQL thread initialized, starting replication in log
'mysql-bin.000691' at position 98, relay log
'/var/run/mysqld/mysqld-relay-bin.000552' position: 235
Oct 23 08:33:07 [EMAIL PROTECTED]/mamba mysqld[29117]: 071023 8:33:07 [Note]
Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication
started in log 'mysql-bin.000691' at position 98
Oct 23 09:39:57 [EMAIL PROTECTED]/mamba mysqld[29117]: 071023 9:39:57 InnoDB:
Error: trying to declare trx to enter InnoDB, but
Oct 23 09:39:57 [EMAIL PROTECTED]/mamba mysqld[29117]: InnoDB: it already is
declared.
Oct 23 09:39:57 [EMAIL PROTECTED]/mamba mysqld[29117]: TRANSACTION 0 45812224,
ACTIVE 0 sec, process no 6713, OS thread id 2987260816, thread declared inside
InnoDB 0
Oct 23 09:39:57 [EMAIL PROTECTED]/mamba mysqld[29117]: mysql tables in use 1,
locked 1
Oct 23 09:39:57 [EMAIL PROTECTED]/mamba mysqld[29117]: 1 lock struct(s), heap
size 320
Oct 23 09:39:57 [EMAIL PROTECTED]/mamba mysqld[29117]: MySQL thread id 1657,
query id 31656 mamba.csn.hu 217.13.33.12 intrnews update
Oct 23 09:39:57 [EMAIL PROTECTED]/mamba mysqld[29117]: INSERT INTO ad_log (ip,
aduserid, action, hely) VALUES ('catv-5985a08c.catv.broadband.hu', '19',
'view', 'intercoolforumfelul')
Oct 23 09:39:57 [EMAIL PROTECTED]/mamba mysqld[29117]:
Regards,
Zsolt
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.18.1-grsec-srv20 (SMP w/1 CPU core; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages mysql-server-5.0 depends on:
ii adduser 3.105 add and remove users and groups
ii debconf [debconf-2.0] 1.5.14 Debian configuration management sy
ii libc6 2.6.1-1+b1 GNU C Library: Shared libraries
ii libdbi-perl 1.59-1 Perl5 database interface by Tim Bu
ii libgcc1 1:4.2.1-4 GCC support library
ii libmysqlclient15off 5.0.45-1 MySQL database client library
ii libncurses5 5.6+20070908-1 Shared libraries for terminal hand
ii libreadline5 5.2-3 GNU readline and history libraries
ii libstdc++6 4.2.1-4 The GNU Standard C++ Library v3
ii libwrap0 7.6.dbs-14 Wietse Venema's TCP wrappers libra
ii lsb-base 3.1-24 Linux Standard Base 3.1 init scrip
ii mysql-client-5.0 5.0.45-1 MySQL database client binaries
ii mysql-common 5.0.45-1 MySQL database common files
ii passwd 1:4.0.18.1-11 change and administer password and
ii perl 5.8.8-7 Larry Wall's Practical Extraction
ii psmisc 22.5-1 Utilities that use the proc filesy
ii zlib1g 1:1.2.3.3.dfsg-6 compression library - runtime
Versions of packages mysql-server-5.0 recommends:
ii mailx 1:8.1.2-0.20070424cvs-1 A simple mail user agent
-- debconf-show failed
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
