MySql 5, my.cnf und InnoDB DISABLED
2 Tage suchen hat endlich ein Ende. Ich habe einen standard Fehler gehabt. Und war wieder Stunden um Stunden am Suchen. Die Lösung des Problems erscheint einem wieder einfach wenn man weiß auf was zu achten ist. Aber zuerst einmal mein Problem.
Ich habe am Freitag ein Testsystem im Haus neu konfigurieren müssen. Der Festplattenspeicher hat nicht mehr ausgereicht und so wurde ich dazu gezwungen eine neue virtuelle Platte dem System hinzuzufügen. Ich wollte kein LVM aufsetzen und möglichen Datenverlust beim erstellen und resizen von Platten zu riskieren. Nachdem das Debian System auch auf einem älteren Stand war und die Etch Version nicht mehr supported wird habe ich kurzerhand das ganze System auf Lenny geupgradet.
Meine my.cnf:
#
# This is for a large system with memory of 1G-2G where the system runs mainly
# MySQL.
#
# You can copy this file to
# /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is /usr/local/mysql/var) or
# ~/.my.cnf to set user-specific options.
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the “–help” option.
# The following options will be passed to all MySQL clients
[client]
#password = your_password
#host = 0.0.0.0
port = 3306
socket = /var/run/mysqld/mysqld.sock
# Here follows entries for some specific programs
# The MySQL server
[mysqld]
port = 3306
socket = /var/run/mysqld/mysqld.sock
# skip-locking
key_buffer = 384M
max_allowed_packet = 1M
table_cache = 512
sort_buffer_size = 2M
read_buffer_size = 2M
read_rnd_buffer_size = 8M
myisam_sort_buffer_size = 64M
thread_cache_size = 8
query_cache_size = 32M
# Try number of CPU’s*2 for thread_concurrency
thread_concurrency = 8
datadir = /hdd/mysql/mysql
tmpdir = /hdd/mysql/tmp
language = /usr/share/mysql/german
log = /hdd/mysql/log/mysql.log
log_error = /hdd/mysql/log/error.log
#collation_database = utf8_unicode_ci
#collation_server = utf8_unicode_ci
# Don’t listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the “enable-named-pipe” option) will render mysqld useless!
#
#skip-networking
# Disable Federated by default
# skip-federated
# Replication Master Server (default)
# binary logging is required for replication
# log-bin=mysql-bin
# required unique id between 1 and 2^32 – 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
# server-id = 1
# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
# the syntax is:
#
# CHANGE MASTER TO MASTER_HOST=
# MASTER_USER=
#
# where you replace
#
#
# Example:
#
# CHANGE MASTER TO MASTER_HOST=’125.564.12.1′, MASTER_PORT=3306,
# MASTER_USER=’joe’, MASTER_PASSWORD=’secret’;
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
# start replication for the first time (even unsuccessfully, for example
# if you mistyped the password in master-password and the slave fails to
# connect), the slave will create a master.info file, and any later
# change in this file to the variables’ values below will be ignored and
# overridden by the content of the master.info file, unless you shutdown
# the slave server, delete master.info and restart the slaver server.
# For that reason, you may want to leave the lines below untouched
# (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 – 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id = 2
#
# The replication master for this slave – required
#master-host =
#
# The username the slave will use for authentication when connecting
# to the master – required
#master-user =
#
# The password the slave will authenticate with when connecting to
# the master – required
#master-password =
# The port the master is listening on.
# optional – defaults to 3306
#master-port =
# binary logging – not required for slaves, but recommended
#log-bin=mysql-bin
#
# binary logging format – mixed recommended
#binlog_format=mixed
# Point the following paths to different dedicated disks
#tmpdir = /tmp/
#log-update = /path-to-dedicated-directory/hostname
# Uncomment the following if you are using InnoDB tables
innodb_data_home_dir = /hdd/mysql/mysql/
innodb_data_file_path = ibdata1:200M;ibdata2:10M:autoextend
innodb_log_group_home_dir = /hdd/mysql/log/
innodb_log_arch_dir = /hdd/mysql/log/
innodb_log_archive = ON
innodb_rollback_on_timeout = ON
# You can set .._buffer_pool_size up to 50 – 80 %
# of RAM but beware of setting memory usage too high
innodb_buffer_pool_size = 384M
innodb_additional_mem_pool_size = 20M
innodb_file_per_table = ON
# Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 20M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50
[mysqldump]
quick
max_allowed_packet = 16M
[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates
[isamchk]
key_buffer = 256M
sort_buffer_size = 256M
read_buffer = 2M
write_buffer = 2M
[myisamchk]
key_buffer = 256M
sort_buffer_size = 256M
read_buffer = 2M
write_buffer = 2M
[mysqlhotcopy]
interactive-timeout
In der ganzen Config wurde das System so aufgebaut das auf alle Fälle innodb verfügbar sein muss. Es war aber ein Problem mit den ibdata1, ibdata2 und den zugehörigen log files von innodb die es erst unmöglich gemacht haben die Engine richtig zu starten. Anhand der wieder eingefügten log_error wurde das Problem in kürzester Zeit gelöst. ib_logfile1 und ib_logfile2 waren die Ursache des Problems. Der standard Lösungsansatz zum wiederaktivieren der InnoDB Engine war das Löschen der ibdata1 & ibdata2. Wenn aber der Fehler weiterhin existiert liegt es an den Logfiles des MySQL Servers.
Als aller erstes Server stoppen, mein Fehler war es das der Server beim wiederkonfigurieren des Systems nicht angehalten hatte.
Zweitens, alle Daten verschieben und my.cnf anpassen.
Drittens ibdata1 & ibdata2 incl. ib_logfile1 & ib_lofile2 löschen sonst wird die Engine wieder deaktiviert.
Zu guter letzt startet den Server wieder und habt viel Spaß mit dem System.