Matt, ----- Original Message ----- From: ""Matt Allen"" <[EMAIL PROTECTED]> Newsgroups: mailing.database.mysql Sent: Tuesday, December 10, 2002 8:10 PM Subject: safe_mysqld will not start correctly
> > Could someone please tell me how to fix this problem: what happened before this? Did mysqld crash? Or did you move ibdata or ib_logfiles? What MySQL version is this? I guess this is on Linux? The assertion below means there is a garbage pointer in the log file. Look at http://www.innodb.com/ibman.html#Forcing_recovery. You have to put set-variable=innodb_force_recovery=6 to the [mysqld] section of your my.cnf and start mysqld. Then dump your tables, recreate the whole InnoDB tablespace, and import the tables again. Please upgrade to MySQL-Max-3.23.53a because it is the stablest version so far. Best regards, Heikki Tuuri Innobase Oy --- Order technical MySQL/InnoDB support at https://order.mysql.com/ See http://www.innodb.com for the online manual and latest news on InnoDB sql query > 021210 12:50:49 mysqld started > 021210 12:50:52 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 2785410520 > InnoDB: Doing recovery: scanned up to log sequence number 0 2785410520 > InnoDB: Assertion failure in thread 1 in file ../include/buf0buf.ic line 265 > 021210 12:50:49 mysqld started > 021210 12:50:52 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 2785410520 > InnoDB: Doing recovery: scanned up to log sequence number 0 2785410520 > InnoDB: Assertion failure in thread 1 in file ../include/buf0buf.ic line 265 > InnoDB: We intentionally generate a memory trap. > InnoDB: Send a detailed bug report to [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 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=12288 > record_buffer=131072 > sort_buffer=2097144 > 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 = 217611 K > bytes of memory > Hope that's ok, if not, decrease some variables in the equation > > 021210 12:50:52 mysqld ended > > > > > _________________________________________________________________ > Add photos to your messages with MSN 8. Get 2 months FREE*. > http://join.msn.com/?page=features/featuredemail > > > --------------------------------------------------------------------- > 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
