I converted my myISAM tables to Innodb format and everything went fine. When I restarted MySQL-Max (2.23.43) I noticed that my query log file was not being accessed anymore so I included "log=/var/lib/mysql/server1.log" to /etc/my.cnf. Running MySQL-Max this time though caused a continuous restarting of the server:
Number of processes running now: 0 011102 10:19:54 mysqld restarted Number of processes running now: 0 011102 10:19:54 mysqld restarted Number of processes running now: 0 011102 10:19:55 mysqld restarted ....etc. I then started mysqld-max manually and got the following message: 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 212830477 011102 10:26:57 InnoDB: Started 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=268431360 record_buffer=1044480 sort_buffer=1048568 max_used_connections=0 max_connections=100 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 466539 K bytes of memoryHope 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... Cannot determine thread, fp=0xbffff108, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x807b90f 0x8253c7a 0x80cf21a 0x8078693 0x807853d 0x80b202b 0x807c656 0x82639fb 0x8048111 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 It seems that the InnoDB crashed and caused some sort of database corruption. On restart, it tried to recover but couldn't. How do I recover the databases? Mysqldump requires the server to be running - right? My system: Redhat7.1, kernel 2.4.2-2, mysql-max 2.23.43 (same results with 2.23.44). Thanks for any help, 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
