Форум пользователей MySQL

Добрый день.
На виртуальной машине работал мускул.
Основная машину вырубилась, после старта виртуалки мускул не встает.
FreeBSD 7.2-RELEASE
mysql-server-5.0.77_1

Мускул ставил так.
/usr/ports/databases/mysql50-server make install clean
echo 'musql_enable="YES"' >> /etc/rc.conf
------------------------------------------------------------------------------------------------
в /var/db/mysql



    test_virtual# ls -l
    -rw-rw----  1 mysql  mysql   5242880 Apr  1 11:14 ib_logfile0
    -rw-rw----  1 mysql  mysql   5242880 Mar 31 14:46 ib_logfile1
    -rw-rw----  1 mysql  mysql  77594624 Mar 31 14:46 ibdata1
    drwx------  2 mysql  mysql      1536 Mar 24 15:52 mysql
    drwx------  2 mysql  mysql       512 Mar 24 15:52 test
    -rw-rw----  1 mysql  mysql     12689 Apr  1 11:14 test_virtual.local.err
    drwx------  2 mysql  mysql      2048 Mar 31 11:38 zabbix





    test_virtual# /usr/local/etc/rc.d/mysql-server start
    Starting mysql.
    test_virtual# ps ax | grep mysql
      855 con- IWJ    0:00.00 /bin/sh /usr/local/bin/mysqld_safe --defaults-extra-file=/var/db/mysql/my.cnf --user=mysql --datadir=/var/db/mysql --pid-file=/var
      881 con- IJ     1:27.55 /usr/local/libexec/mysqld --defaults-extra-file=/var/db/mysql/my.cnf --basedir=/usr/local --datadir=/var/db/mysql --user=mysql --p
    test_virtual# mysql
    ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)
    test_virtual# /usr/local/etc/rc.d/mysql-server status
    mysql is not running.




    test_virtual# cat test_virtual.local.err

    100401 11:56:02  mysqld started
    100401 11:56:02 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
    100401 11:56:02 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
    InnoDB: Log scan progressed past the checkpoint lsn 0 555386752
    100401 11:56:02  InnoDB: Database was not shut down normally!
    InnoDB: Starting crash recovery.
    InnoDB: Reading tablespace information from the .ibd files...
    InnoDB: Restoring possible half-written data pages from the doublewrite
    InnoDB: buffer...
    InnoDB: Doing recovery: scanned up to log sequence number 0 555404800
    100401 11:56:02  InnoDB: Error: page 2 log sequence number 0 555408648
    InnoDB: is in the future! Current system log sequence number 0 555404789.
    InnoDB: Your database may be corrupt or you may have copied the InnoDB
    InnoDB: tablespace but not the InnoDB log files. See
    InnoDB: http://dev.mysql.com/doc/refman/5.0/en/ … overy.html
    InnoDB: for more information.
    100401 11:56:02  InnoDB: Error: page 45 log sequence number 0 555407695
    InnoDB: is in the future! Current system log sequence number 0 555404789.
    InnoDB: Your database may be corrupt or you may have copied the InnoDB
    InnoDB: tablespace but not the InnoDB log files. See
    InnoDB: http://dev.mysql.com/doc/refman/5.0/en/ … overy.html
    InnoDB: for more information.
    100401 11:56:02  InnoDB: Error: page 542 log sequence number 0 555405190
    InnoDB: is in the future! Current system log sequence number 0 555404789.
    InnoDB: Your database may be corrupt or you may have copied the InnoDB
    InnoDB: tablespace but not the InnoDB log files. See
    InnoDB: http://dev.mysql.com/doc/refman/5.0/en/ … overy.html
    InnoDB: for more information.
    InnoDB: 7 transaction(s) which must be rolled back or cleaned up
    InnoDB: in total 11 row operations to undo
    InnoDB: Trx id counter is 0 5376256
    100401 11:56:02  InnoDB: Starting an apply batch of log records to the database...
    InnoDB: Progress in percents: 100401 11:56:02  InnoDB: Error: page 539 log sequence number 0 555408706
    InnoDB: is in the future! Current system log sequence number 0 555404789.
    InnoDB: Your database may be corrupt or you may have copied the InnoDB
    InnoDB: tablespace but not the InnoDB log files. See
    InnoDB: http://dev.mysql.com/doc/refman/5.0/en/ … overy.html
    InnoDB: for more information.
    0 1 2 3 4 5 6 7 8 9 10 11 12 100401 11:56:02  InnoDB: Error: page 480 log sequence number 0 555407301
    InnoDB: is in the future! Current system log sequence number 0 555404789.
    InnoDB: Your database may be corrupt or you may have copied the InnoDB
    InnoDB: tablespace but not the InnoDB log files. See
    InnoDB: http://dev.mysql.com/doc/refman/5.0/en/ … overy.html
    InnoDB: for more information.
    13 14 15 16 17 100401 11:56:02  InnoDB: Error: page 479 log sequence number 0 555408014
    InnoDB: is in the future! Current system log sequence number 0 555404789.
    InnoDB: Your database may be corrupt or you may have copied the InnoDB
    InnoDB: tablespace but not the InnoDB log files. See
    InnoDB: http://dev.mysql.com/doc/refman/5.0/en/ … overy.html
    InnoDB: for more information.
    18 19 100401 11:56:02  InnoDB: Error: page 2831 log sequence number 0 555407047
    InnoDB: is in the future! Current system log sequence number 0 555404789.
    InnoDB: Your database may be corrupt or you may have copied the InnoDB
    InnoDB: tablespace but not the InnoDB log files. See
    InnoDB: http://dev.mysql.com/doc/refman/5.0/en/ … overy.html
    InnoDB: for more information.
    20 21 22 23 24 25 26 27 28 29 30 31 32 33 100401 11:56:02  InnoDB: Error: page 376 log sequence number 0 555407619
    InnoDB: is in the future! Current system log sequence number 0 555404789.
    InnoDB: Your database may be corrupt or you may have copied the InnoDB
    InnoDB: tablespace but not the InnoDB log files. See
    InnoDB: http://dev.mysql.com/doc/refman/5.0/en/ … overy.html
    InnoDB: for more information.
    34 100401 11:56:02InnoDB: Assertion failure in thread 679482224 in file log0recv.c line 793
    InnoDB: Failing assertion: !page || (ibool)!!page_is_comp(page)==index->table->comp
    InnoDB: We intentionally generate a memory trap.
    InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
    InnoDB: If you get repeated assertion failures or crashes, even
    InnoDB: immediately after the mysqld startup, there may be
    InnoDB: corruption in the InnoDB tablespace. Please refer to
    InnoDB: http://dev.mysql.com/doc/refman/5.0/en/ … overy.html
    InnoDB: about forcing recovery.
    100401 11:56:02 - 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=0
    read_buffer_size=131072
    max_used_connections=0
    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 = 217599 K
    bytes of memory
    Hope that's ok; if not, decrease some variables in the equation.

    100401 11:56:03  mysqld ended



Подскажите пути решения с мускулом практически не работал.

Отредактированно anri (01.04.2010 12:09:40)