[MYSQL] InnoDB probleem.

[Verwijderd]

Hoi Tweakers,

Nou ik heb innodb op mijn SQL geinstalleerd en na een paar minuten crasht hij en met het opstarten krijg ik deze melding wie weet misschien hoe ik dit kan oplossen (want ik heb al mijn tabellen in die paar minuten al omgezet naar innodb en krijg dit niet meer terug.)

code:

root@main:~/mysql# /usr/local/libexec/mysqld --user=root
020501  0:34:55  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 14348
InnoDB: Last MySQL binlog file offset 0 28936, file name ./main-bin.013
020501  0:34:55  InnoDB: Flushing modified pages from the buffer pool...
020501  0:34:56  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=16773120
record_buffer=131072
sort_buffer=524280
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 = 80379 K
bytes of memory
Hope 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=0xbfffee34, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80c1b84
0x400227c6
0x810e06e
0x80bed5f
0x80bec0b
0x80f9dd8
0x80c2912
0x400f5577
0x8091d3d
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
The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains
information that should help you find out what is causing the crash

Dank jullie wel want ik kom er niet uit.

[Femme]

Welke versie is het?

[Verwijderd]

code:

MySQL 3.23.49-log running on localhost as root@localhost

Hij draait dus nu zonder innodb. En als ik de innodb weer enable krijg ik dus die foutmelding.

Ik heb de maker ook al gemaild en hoop daar ook antwoord van te krijgen. Want het lijkt er gewoon op dat de database corrupt is. Want ik heb zelfs mijn gecompilde versie vervangen door een binary ook de .49 van mysql. En die werkte dus ook niet.

Wat ik nog niet heb geprobeerd is de .48 of .47 met innodb te gebruiken maar ik weet niet of dit verstandig is.

En dit is de config van my.cnf

code:

# The following options will be passed to all MySQL clients
[client]
#password    = your_password
port        = 3306
socket      = /tmp/mysql.sock

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port        = 3306
socket      = /tmp/mysql.sock
skip-locking
set-variable    = key_buffer=16M
set-variable    = max_allowed_packet=1M
set-variable    = table_cache=64
set-variable    = sort_buffer=512K
set-variable    = net_buffer_length=8K
set-variable    = myisam_sort_buffer_size=8M
log-bin
server-id    = 1

# Point the following paths to different dedicated disks
tmpdir      = /tmp/
log-update  = /var/log/

# Uncomment the following if you are using BDB tables
#set-variable   = bdb_cache_size=4M
#set-variable   = bdb_max_lock=10000

# Uncomment the following if you are using Innobase tables
innodb_data_file_path = ibdata1:400M
innodb_data_home_dir = /mysql/
innodb_log_group_home_dir = /mysql/
innodb_log_arch_dir = /mysql/
set-variable = innodb_mirrored_log_groups=1
set-variable = innodb_log_files_in_group=3
set-variable = innodb_log_file_size=5M
set-variable = innodb_log_buffer_size=4M
innodb_flush_log_at_trx_commit=1
innodb_log_archive=0
set-variable = innodb_buffer_pool_size=4M
set-variable = innodb_additional_mem_pool_size=1M
set-variable = innodb_file_io_threads=4
set-variable = innodb_lock_wait_timeout=50

[mysqldump]
quick
set-variable    = max_allowed_packet=16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
set-variable    = key_buffer=20M
set-variable    = sort_buffer=20M
set-variable    = read_buffer=2M
set-variable    = write_buffer=2M

[myisamchk]
set-variable    = key_buffer=20M
set-variable    = sort_buffer=20M
set-variable    = read_buffer=2M
set-variable    = write_buffer=2M

[mysqlhotcopy]
interactive-timeout

En zo ziet de directory eruit:

code:

root@main:/mysql# pwd
/mysql
root@main:/mysql# ls -al
total 425452
drwxrwxrwx   2 root     root       8192 May  1 00:35 ./
drwxr-xr-x  21 root     root       4096 May  1 00:09 ../
-rw-r-----   1 root     root       8958 May  1 00:35 host.frm
-rw-r-----   1 root     root      25088 May  1 00:35 ib_arch_log_0000000000
-rw-r-----   1 root     root    5242880 May  1 00:35 ib_logfile0
-rw-r-----   1 root     root    5242880 May  1 00:35 ib_logfile1
-rw-r-----   1 root     root    5242880 May  1 00:35 ib_logfile2
-rw-r-----   1 root     root     419430400 May  1 00:36 ibdata1

Dus hij draait fijn op ISAM en MYISAM maar zodra de innodb aangaat (de grootste) dan crashed ie. En ik weet niet hoe ik hem zonder de SQL weer kan converteren naar MyISAM.

[Verwijderd]

Ik ben nu by the way een complete nieuwe machine aan het installeren met .37 erop en ik zal kijken of dit enig effect heeft.