problem z uruchomieniem mysql

[ml0dy 0]

Witam.

Mam problem z uruchomieniem mysql.

root@vps:/var/db/mysql # /usr/local/etc/rc.d/mysql-server start

Starting mysql.

root@vps:/var/db/mysql # mysql -u root -p

Enter password:

ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)

root@vps:/var/db/mysql # /usr/local/etc/rc.d/mysql-server status

mysql is not running.

root@vps:/usr/home/admin01 # cat /usr/local/etc/my.cnf

# 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-external-locking

key_buffer_size = 16M

max_allowed_packet = 10M

table_open_cache = 64

sort_buffer_size = 512K

net_buffer_length = 8K

read_buffer_size = 256K

read_rnd_buffer_size = 512K

myisam_sort_buffer_size = 8M

#innodb_force_recovery = 1

#

expire_logs_days = 7

# Replication Master Server (default)

# binary logging is required for replication

log-bin=mysql-bin

# binary logging format - mixed recommended

binlog_format=mixed

# 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

# Uncomment the following if you are using InnoDB tables

innodb_data_home_dir = /var/db/mysql

innodb_data_file_path = ibdata1:10M:autoextend

innodb_log_group_home_dir = /var/db/mysql

# You can set .._buffer_pool_size up to 50 - 80 %

# of RAM but beware of setting memory usage too high

innodb_buffer_pool_size = 16M

innodb_additional_mem_pool_size = 2M

# Set .._log_file_size to 25 % of buffer pool size

innodb_log_file_size = 5M

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

[myisamchk]

key_buffer_size = 20M

sort_buffer_size = 20M

read_buffer = 2M

write_buffer = 2M

[mysqlhotcopy]

interactive-timeout

Zrzut logów:

root@vps:/var/db/mysql # cat /var/db/mysql/vps.mojanazwa.com.pl.err

InnoDB: End of page dump

140422 13:20:30 InnoDB: Page checksum 3901004751, prior-to-4.0.14-form checksum 4133747994

InnoDB: stored checksum 3901004751, prior-to-4.0.14-form stored checksum 394340168

InnoDB: Page lsn 0 2593319967, low 4 bytes of lsn at page end 2593183091

InnoDB: Page number (if stored to page already) 249,

InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0

InnoDB: Page may be a system page

InnoDB: Database page corruption on disk or a failed

InnoDB: file read of page 249.

InnoDB: You may have to recover from a backup.

InnoDB: It is also possible that your operating

InnoDB: system has corrupted its own file cache

InnoDB: and rebooting your computer removes the

InnoDB: error.

InnoDB: If the corrupt page is an index page

InnoDB: you can also try to fix the corruption

InnoDB: by dumping, dropping, and reimporting

InnoDB: the corrupt table. You can use CHECK

InnoDB: TABLE to scan your table for corruption.

InnoDB: See also http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html

InnoDB: about forcing recovery.

InnoDB: Ending processing because of a corrupt database page.

140422 13:20:30 InnoDB: Assertion failure in thread 683688704 in file buf0buf.c line 3602

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.5/en/forcing-innodb-recovery.html

InnoDB: about forcing recovery.

11:20:30 UTC - mysqld got signal 6 ;

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=16777216

read_buffer_size=262144

max_used_connections=0

max_threads=151

thread_count=0

connection_count=0

It is possible that mysqld could use up to

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133417 K bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

140422 13:20:30 mysqld_safe mysqld from pid file /var/db/mysql/vps.mojanazwa.com.pl.pid ended

root@vps:/var/db/mysql #

Liczę na waszą pomoc, dodam tylko że nie mam żadnego dumpa bazy

A jak dodam do my.cnf wpis:

innodb_force_recovery = 6

To mysql działa i strony ładnie się ładują ale nie bardzo wiem co z tym dalej zrobić bo jak dodam # przed innodb_force_recovery = 6 i zrobie restart mysql to przestaje działać.

Dzięki.

 

Edytowano Kwiecień 22, 2014 przez ml0dy (zobacz historię edycji)

[LANcaster (kotkowicz.pl) 52]

Uruchom z innodb_force_recovery=1 zrób kompletny dump bazy, upewnij się, że zrobił się poprawnie, wyczyść zupełnie katalog z danymi mysql, przygotuj nowe bazy systemowe przy użyciu mysql_install_db, załaduj dumpa.

Jeśli nie wstaje z innodb_force_recovery=1 - zwiększaj numerek o 1 aż wstanie. Jeśli nic Ci nie pomoże, zgłoś się do mnie na priv, zrobię Ci to za nieduże pieniądze.