> 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 0x40000 > > /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
