We've just migrated this app from solaris to linux. for several days, this machine was a tracking slave to this application. last night we actually switched to make this machine the master for the application. this was the master and had a connected slave at the time of failure. the machines are running 3.2.43. 14hrs after the reconfiguration, the mysqld died on the master. this is hardware that has recently been used in other applications. although the load on this application is unique. we hardly ever get mysql crashes on any of our db's so this one is very interesting.
Hardware is a 2x650 Intel box, 2gig of ram, 1 scsi boot drive (34 gig seagate) attached to internal (adaptec something or other, I can get it if it matters) and a 3Ware IDE RAID controller with 4 drives in a stripe that the mysql databases are housed on. Log files go to the internal drive. Is there any other information you need? (is this a mailing list? I'm not on it, so please CC me, and I'll subscribe). here's the stack dump: root@dbacp01d-red:/usr/local/mysql/bin# ./resolve_stack_dump -s /tmp/a -n /tmp/b 0x807b75f handle_segfault__Fi + 383 0x812bcaa pthread_sighandler + 154 0x815059c chunk_free + 596 0x8152573 free + 155 0x811579c my_no_flags_free + 16 0x8077284 net_end__FP6st_net + 16 0x8073acc _._3THD + 36 0x807b48d end_thread__FP3THDb + 53 0x80809cc handle_one_connection__FPv + 996 here's the config file: root@dbacp01d-red:/usr/local/mysql/bin# cat /etc/my.cnf [client] socket = /var/run/mysqld/mysqld.sock [mysqld] set-variable = max_connections=888 set-variable = table_cache=900 set-variable = key_buffer=100M set-variable = connect_timeout=30 set-variable = back_log=64 set-variable = max_connect_errors=999999999 set-variable = wait_timeout=600 basedir = /usr/local/mysql datadir = /data/mysql log-bin = /data/mysql-log/log log-slave-updates tmpdir = /tmp skip-grant-tables skip-locking skip-name-resolve skip-slave-start server-id = 102 socket = /var/run/mysqld/mysqld.sock skip-slave-start [mysql] no-auto-rehash [safe_mysqld] err-log=/var/log/mysqld.log ledir=/usr/local/mysql/bin here's the log entry: 011207 15:36:10 mysqld started /usr/local/mysql/bin/mysqld: ready for connections 011207 15:36:44 Slave: connected to master '[EMAIL PROTECTED]:3306 ', replication started in log 'log.285' at position 73 011210 0:41:44 Slave thread killed while reading event 011210 0:41:44 Slave thread exiting, replication stopped in log 'log.296' at p osition 439508 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=104853504 record_buffer=131072 sort_buffer=2097144 max_used_connections=210 max_connections=888 threads_connected=56 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 2034677 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: 0x807b75f 0x812bcaa 0x815059c 0x8152573 0x811579c 0x8077284 0x8073acc 0x807b48d 0x80809cc Stack trace seems successful - bottom reached Please read http://www.mysql.com/doc/U/s/Using_stack_trace.html and follow instr uctions 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 (nil) is invalid pointer thd->thread_id=1819059 Successfully dumped variables, if you ran with --log, take a look at the details of what thread 1819059 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 011210 15:51:22 mysqld not restarted 011210 15:51:22 mysqld ended -- Share and Enjoy. --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
