RE: MySQL crashed..
120711 8:12:22 [ERROR] /usr/sbin/mysqld: Incorrect key file for table './mydb/wp_posts.MYI'; try to repair it 120711 8:12:22 [ERROR] Got error 126 when reading table './mydb/wp_posts' Well, do REPAIR TABLE wp_posts; -Original Message- From: J M [mailto:jerom...@gmail.com] Sent: Wednesday, July 11, 2012 7:11 AM To: MySql Subject: Re: MySQL crashed.. sorry.. im using 5.1 On Wed, Jul 11, 2012 at 10:09 AM, J M jerom...@gmail.com wrote: hi all, our DB crashed for some reason... any inputs would be greatly appreciated.. 120711 8:12:21 - 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=268435456 read_buffer_size=262144 max_used_connections=148 max_threads=600 threads_connected=35 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1650750 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x2aaafc19ddb0 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 = 0x43705f08 thread_stack 0x4 /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x85836e] /usr/sbin/mysqld(handle_segfault+0x34f)[0x5c7c6f] /lib64/libpthread.so.0[0x3486c0eb10] /lib64/libc.so.6[0x348607051b] /lib64/libc.so.6[0x3486072bbc] /lib64/libc.so.6(__libc_malloc+0x6e)[0x3486074e2e] /usr/sbin/mysqld(my_malloc+0x32)[0x847842] /usr/sbin/mysqld(_ZN6String10real_allocEj+0x35)[0x5c1535] /usr/sbin/mysqld(handle_one_connection+0x687)[0x5cc4a7] /lib64/libpthread.so.0[0x3486c0673d] /lib64/libc.so.6(clone+0x6d)[0x34860d40cd] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query ((nil)): is an invalid pointer Connection ID (thread ID): 8415116 Status: 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. 120711 8:12:22 [ERROR] /usr/sbin/mysqld: Incorrect key file for table './mydb/wp_posts.MYI'; try to repair it 120711 8:12:22 [ERROR] Got error 126 when reading table './mydb/wp_posts' ** OS error code 126: Required key not available Im using MySQL 5.0 tia, -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL crashed..
hi all, our DB crashed for some reason... any inputs would be greatly appreciated.. 120711 8:12:21 - 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=268435456 read_buffer_size=262144 max_used_connections=148 max_threads=600 threads_connected=35 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1650750 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x2aaafc19ddb0 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 = 0x43705f08 thread_stack 0x4 /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x85836e] /usr/sbin/mysqld(handle_segfault+0x34f)[0x5c7c6f] /lib64/libpthread.so.0[0x3486c0eb10] /lib64/libc.so.6[0x348607051b] /lib64/libc.so.6[0x3486072bbc] /lib64/libc.so.6(__libc_malloc+0x6e)[0x3486074e2e] /usr/sbin/mysqld(my_malloc+0x32)[0x847842] /usr/sbin/mysqld(_ZN6String10real_allocEj+0x35)[0x5c1535] /usr/sbin/mysqld(handle_one_connection+0x687)[0x5cc4a7] /lib64/libpthread.so.0[0x3486c0673d] /lib64/libc.so.6(clone+0x6d)[0x34860d40cd] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query ((nil)): is an invalid pointer Connection ID (thread ID): 8415116 Status: 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. 120711 8:12:22 [ERROR] /usr/sbin/mysqld: Incorrect key file for table './mydb/wp_posts.MYI'; try to repair it 120711 8:12:22 [ERROR] Got error 126 when reading table './mydb/wp_posts' ** OS error code 126: Required key not available Im using MySQL 5.0 tia, -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: MySQL crashed..
sorry.. im using 5.1 On Wed, Jul 11, 2012 at 10:09 AM, J M jerom...@gmail.com wrote: hi all, our DB crashed for some reason... any inputs would be greatly appreciated.. 120711 8:12:21 - 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=268435456 read_buffer_size=262144 max_used_connections=148 max_threads=600 threads_connected=35 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1650750 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x2aaafc19ddb0 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 = 0x43705f08 thread_stack 0x4 /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x85836e] /usr/sbin/mysqld(handle_segfault+0x34f)[0x5c7c6f] /lib64/libpthread.so.0[0x3486c0eb10] /lib64/libc.so.6[0x348607051b] /lib64/libc.so.6[0x3486072bbc] /lib64/libc.so.6(__libc_malloc+0x6e)[0x3486074e2e] /usr/sbin/mysqld(my_malloc+0x32)[0x847842] /usr/sbin/mysqld(_ZN6String10real_allocEj+0x35)[0x5c1535] /usr/sbin/mysqld(handle_one_connection+0x687)[0x5cc4a7] /lib64/libpthread.so.0[0x3486c0673d] /lib64/libc.so.6(clone+0x6d)[0x34860d40cd] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query ((nil)): is an invalid pointer Connection ID (thread ID): 8415116 Status: 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. 120711 8:12:22 [ERROR] /usr/sbin/mysqld: Incorrect key file for table './mydb/wp_posts.MYI'; try to repair it 120711 8:12:22 [ERROR] Got error 126 when reading table './mydb/wp_posts' ** OS error code 126: Required key not available Im using MySQL 5.0 tia, -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
How can I know if Mysql Crashed or stopped gracefully
I have an environment where upon boot of a machine I need to know if mysql shutdown nicely or if it crashed. How can I know for sure which was the case so that I can take action if needed? I notice that issuing a reboot or shutdown -r now command, (in Linux) that the 'service mysql stop' is never run... it just seems to catch the sig 15 and does its own shutdown... I have scripted in the stop section of my init script to touch a file that I look for on restart, but if the stop is never executed on reboot/shutdown, then I have a problem. Thanks for the help, Bryancan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: How can I know if Mysql Crashed or stopped gracefully
Signal 15 is pretty much equal to a regular shutdown, except that if your shutdown script doesn't run, you may be left with lockfiles, pidfiles and the like. A crash would most likely be visible in the logfile, and even if it isn't (machine loses power), your log should show innodb running a recovery procedure at startup. On Tue, Oct 27, 2009 at 3:51 PM, Bryan Cantwell bcantw...@firescope.comwrote: I have an environment where upon boot of a machine I need to know if mysql shutdown nicely or if it crashed. How can I know for sure which was the case so that I can take action if needed? I notice that issuing a reboot or shutdown -r now command, (in Linux) that the 'service mysql stop' is never run... it just seems to catch the sig 15 and does its own shutdown... I have scripted in the stop section of my init script to touch a file that I look for on restart, but if the stop is never executed on reboot/shutdown, then I have a problem. Thanks for the help, Bryancan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=vegiv...@tuxera.be
Re: How can I know if Mysql Crashed or stopped gracefully
On Tue, Oct 27, 2009 at 7:51 AM, Bryan Cantwell bcantw...@firescope.com wrote: I notice that issuing a reboot or shutdown -r now command, (in Linux) that the 'service mysql stop' is never run... it just seems to catch the sig 15 and does its own shutdown... I have scripted in the stop section of my init script to touch a file that I look for on restart, but if the stop is never executed on reboot/shutdown, then I have a problem. What distro? Which version of mysql? My comments below apply to our InnoDB heavy CentOS systems. Older versions of mysql (5.0.x on our CentOS machines) wait 60 seconds for the mysqld process to completely die. If mysql has a lot of data to flush to disk, it can take longer than that 60 seconds. The init script assumes that the kill command didn't succeed, it prints out FAILED, and the system shutdown process moves on to the next init script. Near the end of the system shutdown process, the shutdown script issues a final SIGKILL to remaining running processes. If mysqld didn't finish flushing that data before this final KILL signal, the mysqld process is killed instantly and you have an unclean shutdown. One quick solution is to manually stop mysql, watching to see when the process finally goes away (top, ps, etc), then do your shutdown -r now. Modern versions of mysql (5.1.x) seem to handle this better because it waits as long as it takes for mysqld to shut down properly or to start up (and accept connections). At least in my testing so far, I've not hit a timeout or received an incorrect OK or FAILED message in the 5.1.x series. -- Regards... Todd The best thing about pair programming is that you have the perfect audience for your genius. -- Kent Beck -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
MySQL crashed InnoDB: Error: semaphore wait has lasted 600 seconds
Hi, MySQL 4.0.16 running on Red Hat Linux release 8.0 with 4 Intel XEON 2.40 GHz with InnoDB tables. This is the stack trace : 0x81077c6 handle_segfault + 474 0x4002a929 _end + 935891041 0x8272ff8 sync_array_print_long_waits + 580 0x81a7328 srv_error_monitor_thread + 96 0x40024ada _end + 935866898 0x402868c7 _end + 938364927 Error message from log : InnoDB: Warning: a long semaphore wait: --Thread 294923 has waited at ../../innobase/include/btr0btr.ic line 28 for 625.00 seconds the semaphore: X-lock on RW-latch at 40cb26e4 created in file buf0buf.c line 444 a writer (thread id 294923) has reserved it in mode exclusive number of readers 0, waiters flag 1 Last time read locked in file btr0sea.c line 753 Last time write locked in file buf0buf.c line 1404 InnoDB: Error: semaphore wait has lasted 600 seconds InnoDB: We intentionally crash the server, because it appears to be hung. 040812 23:17:29 InnoDB: Assertion failure in thread 98311 in file sync0arr.c line 934 InnoDB: Failing assertion: 0 InnoDB: We intentionally generate a memory trap. InnoDB: Send a detailed bug report to [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] 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=8388600 read_buffer_size=131072 max_used_connections=53 max_connections=200 threads_connected=17 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 443390 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=(nil) 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=0xbedff518, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x81077c6 0x4002a929 0x8272ff8 0x81a7328 0x40024ada 0x402868c7 New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://www.mysql.com/doc/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 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. Number of processes running now: 2 mysqld process hanging, pid 810 - killed mysqld process hanging, pid 810 - killed 040812 23:17:29 mysqld restarted 040812 23:17:29 Can't start server: Bind on TCP/IP port: Address already in use 040812 23:17:29 Do you already have another mysqld server running on port: 3306 ? 040812 23:17:29 Aborting 040812 23:17:29 /usr/kasenna/mysql/bin/mysqld: Shutdown Complete 040812 23:17:29 mysqld ended 040816 13:55:44 mysqld started 040816 13:55:44 InnoDB: Database was not shut down normally. InnoDB: Starting recovery from log files... InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 252191979 InnoDB: Doing recovery: scanned up to log sequence number 0 252191979 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 1 row operations to undo InnoDB: Trx id counter is 0 379596032 InnoDB: Starting rollback of uncommitted transactions InnoDB: Rolling back trx with id 0 379591339, 1 rows to undo InnoDB: Rolling back of trx id 0 379591339 completed InnoDB: Rollback of uncommitted transactions completed 040816 13:55:44 InnoDB: Flushing modified pages from the buffer pool... 040816 13:55:44 InnoDB: Started /usr/kasenna/mysql/bin/mysqld: ready for connections. Version: '4.0.16' socket: '/usr/kasenna/mysql/tmp/mysql.sock' port: 3306 Any insight would be most appreciated. datta Kasenna Inc, -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
mysql crashed
mysql 4.0.5a binary crashed with following error messages. What's the problem? :( 021128 11:06:23 Slave I/O thread: connected to master 'austin@atis1:3306', replication started in log 'FIRST' at position 4 021128 17:35:52 Slave: received 0 length packet from server, apparent master shutdown: 021128 17:35:52 Slave I/O thread: Failed reading log event, reconnecting to retry, log 'atis1-bin.036' position 754 021128 17:35:52 Slave I/O thread: error reconnecting to master 'austin@atis1:3306': Error: 'Can't connect to MySQL server on 'atis1' (111)' errno: 2003 retry-time: 60 retries: 86400 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=268431360 read_buffer_size=1044480 sort_buffer_size=1048568 max_used_connections=1 max_connections=100 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 466539 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x86efad0 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=0xbfe3f2d8, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x806eedb 0x8268018 0x80ad5a5 0x80ae086 0x80e234a 0x80e2e4a 0x82657cc New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://www.mysql.com/doc/U/s/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 (nil) is invalid pointer thd-thread_id=4 Successfully dumped variables, if you ran with --log, take a look at the details of what thread 4 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: 2 -- Chung Ha-nyung alita@[neowiz.com|kldp.org] SayClub http://www.sayclub.com NeoWiz http://www.neowiz.com - 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
mysql crashed and created huge .MYI files. All data lost?
Hi there, during a wrong select query on a table containing over 2 mill. records (involving other tables) mysql and the whole linux server crashed. After rebooting I did run myisamchk and this reported that some tables are damaged but still can be read. So I did shut down the server und run myisamchk --recover --quick *.MYI Right now mysql is recovering a table named #sql-98a_1b.MYI which I do not know where it comes from. I did definatelly not create this table. Recovery is in process now for more than 30 minutes on this table and it is counting a valueup (right now 15) Does anybody know what happened here? I hope I do not need to role out my backup tapes :-( Thanx for any help, Andy - 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
Re: mysql crashed and created huge .MYI files. All data lost?
Andy, I believe that that file is an on disk temporary file that was created during the query. I would suggest you wait for the recover to finish as I think (hope) your data will be returned to a fairly normal state when it does. Ric. - Original Message - From: andy [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, May 19, 2002 6:28 PM Subject: mysql crashed and created huge .MYI files. All data lost? Hi there, during a wrong select query on a table containing over 2 mill. records (involving other tables) mysql and the whole linux server crashed. After rebooting I did run myisamchk and this reported that some tables are damaged but still can be read. So I did shut down the server und run myisamchk --recover --quick *.MYI Right now mysql is recovering a table named #sql-98a_1b.MYI which I do not know where it comes from. I did definatelly not create this table. Recovery is in process now for more than 30 minutes on this table and it is counting a valueup (right now 15) Does anybody know what happened here? I hope I do not need to role out my backup tapes :-( Thanx for any help, Andy - 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 - 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
Mysql Crashed
Dear All, While running our application, mysql suddenly started giving an error as MYD file not found for our database. On restoring the database through backup which was taken withthe help of mysqldump, it now converts all the tables to MyIsam and not Innodb even after specifying the the table type to Innodb; Please help Regards Amit Lonkar __ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com - 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
Re: Mysql Crashed
Hi. Could it be that your MySQL server was upgraded to a version compiled without InnoDB support? If you used InnoDB it should have never complained about MYD files, as they belong to MyISAM table format. Bye, Benjamin. On Mon, Apr 29, 2002 at 01:54:28AM -0700, [EMAIL PROTECTED] wrote: Dear All, While running our application, mysql suddenly started giving an error as MYD file not found for our database. On restoring the database through backup which was taken withthe help of mysqldump, it now converts all the tables to MyIsam and not Innodb even after specifying the the table type to Innodb; Please help Regards Amit Lonkar -- [EMAIL PROTECTED] - 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
MySQL CRASHED after some days with this message in errlog:
Hi, Mysql ran for 6 days.. It is a website with heavy traffic. /usr/libexec/ld-elf.so.1: /usr/local/libexec/mysqld: Undefined symbol strtoull 010423 23:18:08 mysqld restarted /usr/local/libexec/mysqld: ready for connections What is this function about? What feature shouldn't I use to avoid this problem? Thanks in advance Regards, Patric de Waha - 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
