Bug#386337: mysql-server-5.0: crash on INSERT query
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christian Hammers wrote: > INSERT DELAYED and varchar columns sound familiar. Can you take a look at > http://bugs.mysql.com/bug.php?id=17364 and > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=376551 This seems to be the same problem. A crash on INSERT DELAYED after upgrading from MySQL 4.x to 5.0. Like I said on a newly created table it is working. So it seems to be a bug in the way MySQL handles the old tables. I didn't find this bug in the debian database because I was searching for mysql-server-5.0 bugs. - -- http://reboot.animeirc.de (Personal Homepage) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFACLdoHTSdnOy6+ERAgYgAJ9ZCdgoeo6Q6RZpZLXqCPHJbXpNIwCgwXzv GRNAaC4qspqBfzYjOzPopWk= =uTOh -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#386337: mysql-server-5.0: crash on INSERT query
Christian Hammers wrote: >> MySQL crashes every time doing the query below with the following log >> entry: > > Can you provide a > SHOW CREATE TABLE ; CREATE TABLE `log` ( `id` int(11) NOT NULL auto_increment, `ip` varchar(15) default NULL, `agent` varchar(250) default NULL, `timestamp` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP, `request` varchar(250) default NULL, `method` varchar(10) default NULL, `uid` int(11) default NULL, `ulogin` varchar(250) default NULL, `cid` int(11) default NULL, `module` varchar(250) default NULL, `fct` varchar(250) default NULL, `param` varchar(250) default NULL, `iid` int(11) default NULL, PRIMARY KEY (`id`), KEY `rid` (`cid`), KEY `timestamp` (`timestamp`) ) ENGINE=MyISAM AUTO_INCREMENT=4833261 DEFAULT CHARSET=latin1 > and the complete insert (if it was not in the output below)? Yes I think it was in the line starting with "thd->query". I tried to run the query in this line with the mysql client and it crashed too. The original crash was caused by a PHP script. > If the data is not private then the database files itself could > be helpful, too. Can you reproduce the problem after creating a fresh new > table and inserting the relevant query there (maybe it's just a filesystem > corruption on this one table). I tried that and it didn't crash. I could try to clear the other table and see if it still crashes. But maybe that would make the problem unreproduceable for me too. I would not be able to give any further information if it is needed. I think a segfault is not correct even if a table is damaged. > Please provide your /etc/mysql/my.cnf, too, in case it's a bug related to > charsets or special buffer sizes. Attached. I forgot to mention that this problem occured first after I upgraded MySQL to version 5. It was a 4.x version before. -- http://reboot.animeirc.de (Personal Homepage) # # The MySQL database server configuration file. # # You can copy this to one of: # - "/etc/mysql/my.cnf" to set global options, # - "/var/lib/mysql/my.cnf" to set server-specific options or # - "~/.my.cnf" to set user-specific options. # # One can use all long options that the program supports. # Run program with --help to get a list of available options and with # --print-defaults to see which it would actually understand and use. # # This will be passed to all mysql clients [client] #password = my_password port= 3306 socket = /var/run/mysqld/mysqld.sock # Here is entries for some specific programs # The following values assume you have at least 32M ram # This was formally known as [safe_mysqld]. Both versions are currently parsed. [mysqld_safe] err-log = /var/log/mysql/mysql.err socket = /var/run/mysqld/mysqld.sock [mysqld] user= mysql pid-file= /var/run/mysqld/mysqld.pid socket = /var/run/mysqld/mysqld.sock port= 3306 # # The preferred location for the log files is /var/log/mysql/ but the old # file /var/log/mysql.log still gets rotated by the cronjob. # log = /var/log/mysql.log log = /var/log/mysql/mysql.log log-error = /var/log/mysql/mysql.err basedir = /usr datadir = /var/lib/mysql tmpdir = /tmp language= /usr/share/mysql/english skip-locking # # The skip-networkin option will no longer be set via debconf menu. # You have to manually change it if you want networking i.e. the server # listening on port 3306. The default is "disable" - for security reasons. # skip-networking set-variable= key_buffer=16M set-variable= max_allowed_packet=1M set-variable= thread_stack=128K # # Here you can see queries with especially long duration #log-slow-queries = /var/log/mysql/mysql-slow.log # # The following can be used as easy to replay backup logs or for replication server-id = 10001 #log-bin= /var/log/mysql/mysql-bin.log #binlog-do-db = include_database_name #binlog-ignore-db = include_database_name # # Read the manual if you want to enable InnoDB! # skip-innodb # # Read the manual, too, if you want chroot! # chroot = /var/lib/mysql/ # # If you want to enable SSL support (recommended) read the manual or my # HOWTO in /usr/share/doc/mysql-server/SSL-MINI-HOWTO.txt # ssl-ca=/etc/mysql/cacert.pem # ssl-cert=/etc/mysql/server-cert.pem # ssl-key=/etc/mysql/server-key.pem # log-slave-updates skip-slave-start # replicate-do-db=nybria # Uncomment the following if you are using InnoDB tables innodb_data_home_dir = /var/lib/mysql/ innodb_data_file_path = ibdata1:10M:autoextend innodb_log_group_home_dir = /var/lib/mysql/ innodb_log_arch_dir = /var/lib/mysql/ # You can set .._buffer_pool_size up to 50 - 80 % # of RAM but beware of setting memory usage too high innodb_buffer_pool_size = 16M innodb_additional_mem_pool_size = 2M # Set .._log_file_size to 25 % of buffer pool size innodb_log_file_size = 5M innodb_log_buff
Bug#386337: mysql-server-5.0: crash on INSERT query
Package: mysql-server-5.0 Version: 5.0.24a-3 Severity: grave Justification: renders package unusable MySQL crashes every time doing the query below with the following log entry: --->8--- 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=16777216 read_buffer_size=131072 max_used_connections=1 max_connections=100 threads_connected=2 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 233983 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x8b8c980 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=0x4746accc, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x81b98fc handle_segfault + 668 0xe420 _end + -141347824 (nil) 0x821ea07 _Z12mysql_insertP3THDP13st_table_listR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb + 1847 0x81d06b4 _Z21mysql_execute_commandP3THD + 10068 0x81d5009 _Z11mysql_parseP3THDPcj + 329 0x81d5560 _Z16dispatch_command19enum_server_commandP3THDPcj + 1120 0x81d67f8 _Z10do_commandP3THD + 136 0x81d7204 handle_one_connection + 2308 0x40054e60 _end + 932748880 0x402888ee _end + 935057630 New value of fp=(nil) 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 0x8c05110 = INSERT DELAYED INTO log SET ip="10.0.1.1", agent="Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6 (Debian-1.5.dfsg+1.5.0.6-3)", request="/commsy/commsy.php?", method="GET", uid="", ulogin="guest", cid="192261", module="home", fct="index", param="", iid="-1" thd->thread_id=8 The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash. --->8--- If I can give any more information please ask. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.5 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages mysql-server-5.0 depends on: ii adduser 3.85 Add and remove users and groups ii debconf [debconf-2.0] 1.4.72 Debian configuration management sy ii libc6 2.3.6-7GNU C Library: Shared libraries ii libdbi-perl 1.50-2 Perl5 database interface by Tim Bu ii libgcc1 1:4.1.1-13 GCC support library ii libmysqlclient15off 5.0.24a-3 mysql database client library ii libncurses5 5.5-1 Shared libraries for terminal hand ii libreadline5 5.1-7 GNU readline and history libraries ii libstdc++64.1.1-13 The GNU Standard C++ Library v3 ii libwrap0 7.6.dbs-9 Wietse Venema's TCP wrappers libra ii lsb-base 3.1-4 Linux Standard Base 3.1 init scrip ii mysql-client-5.0 5.0.24a-3 mysql database client binaries ii mysql-common 5.0.24a-3 mysql database common files (e.g. ii passwd1:4.0.13-7 change and administer password and ii perl 5.8.8-6.1 Larry Wall's Practical Extraction ii psmisc22.2-1 Utilities that use the proc filesy ii zlib1g1:1.2.3-11 compression library - runtime Versions of packages mysql-server-5.0 recommends: ii mailx1:8.1.2-0.20050715cvs-1 A simple mail user agent -- debconf information: mysql-server-5.0/really_downgrade: false mysql-server-5.0/start_on_boot: true mysql-server-5.0/nis_warning: mysql-server-5.0/postrm_remove_databases: false mysql-server-5.0/no_upgrade_with_isam_tables: * mysql-server-5.0/mysql_install_db_notes: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
