> Stephen, > > At 01:37 PM 11/2/01 -0800, you wrote: >>> Stephen, >>> >>> At 12:38 PM 11/2/01 -0800, you wrote: >>>>Heikki, >>>> >>>>Removal of the log= option and even the log-bin statement did not >>>>help. I used the latest (2.23.44) RPMs from one of the mysql.com >>>>mirrors. I don't think it's a download issue because the problem >>>>originally occured with the 2.23.43 distribution. >>>> >>>>The crash occurs within seconds of starting mysqld-max so the server >>>>never really runs. I did read the Forcing recovery section of the >>>>manual and it suggests that I might have to reboot to clear some >>>>memory condition. I will give that a try. >>>> >>>>Thanks, >>>>Stephen >>>> >>>>> Stephen, >>>>> >>>>> I resolved now with the mysql-max-3.23.44...tar.gz distribution. I >>>>> still do not understand what mysqld is trying to do here. What >>>>> distribution do you use, or did you compile yourself? >>>>> >>>>> 0x807b90f handle_segfault__Fi + 383 >>>>> 0x8253c7a pthread_sighandler + 106 >>>>> 0x80cf21a change_active_index__11ha_innobaseUi + 230 >>>>> 0x8078693 lock_external__FPP8st_tableUi + 107 >>>>> 0x807853d mysql_lock_tables__FP3THDPP8st_tableUi + 333 >>>>> 0x80b202b acl_init__Fb + 411 >>>>> 0x807c656 main + 2454 >>>>> 0x82639fb __libc_start_main + 99 >>>>> 0x8048111 _start + 33 >>> >>> I looked now what MySQL does when it calls lock_external at startup: >>> it initializes MySQL system tables like 'host' and 'user'. I assume >>> you have not converted MySQL system tables to InnoDB format? That is >>> not allowed. They must be MyISAM type. >>> >>> Maybe the MySQL system tables are corrupt? Running inside gdb could >>> reveal if it really crashes there. Please make a copy of MySQL tables >>> in the mysql directory so that they are preserved and we can check if >>> they are ok. >>> >>> Regards, >>> >>> Heikki >> >>Ummm...I think I did convert the system db tables to InnoDB. Now what? >>How do I convert them back to MyISAM? >> >>Thanks, >>Stephen > > if you have good copies of system tables in the MyISAM format - I think > they do not even need to be from the current database - then you can > just copy them to the mysql directory (.frm, .MYI, .MYD files). mysqld > will then use them in startup. > > But please make first a backup of your current mysql directory, and > look if you have host.MYI and host.MYD etc. files there. An InnoDB > table only has the .frm file. So we see if you had really converted > system tables to InnoDB. > > Regards, > > Heikki
Hi Heikki, I backed up the existing mysql system directory (containing only .frm files) and copied the mysql system databases from another operational server to the dead one. Mysqld fired-up nicely upon restarting with skip-innodb in my.cnf. After changing a few permissions, I restarted the server with innodb and my databases reappeared! I'll have a closer look but they appear untainted by my screw-up. I will have to include a warning in the comments section of the MySQL documentation to NOT CONVERT MySQL SYSTEM TABLES FROM myISAM TO INNODB TYPE! Thanks for your generous help! Regards, Stephen --------------------------------------------------------------------- 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
