mysql nie startuje

[czaczawik 8]

Na VPS z debianem dzis wyszly kwiatki jakies i nie startuje.

 

root@zbigniewbystrzanowski:~# /etc/init.d/mysqld start
Starting mysqld:                [ OK ]
root@zbigniewbystrzanowski:~# /usr/local/mysql/bin/mysqld_safe: line 144:  5307 Segmentation fault      nohup /usr/local/mysql/bin/mysqld --basedir=/usr/local/mysql --datadir=/usr/local/mysql/data --plugin-dir=/usr/local/mysql/lib/plugin --user=mysql --log-error=/usr/local/mysql/data/zbigniewbystrzanowski.err --open-files-limit=100000 --pid-file=/usr/local/mysql/data/zbigniewbystrzanowski.pid < /dev/null >> /usr/local/mysql/data/zbigniewbystrzanowski.err 2>&1

ostatnie linie z /usr/local/mysql/data/zbigniewbystrzanowski.err

Thread pointer: 0x0
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...
140228 12:25:20 mysqld_safe mysqld from pid file /usr/local/mysql/data/zbigniewbystrzanowski.pid ended
InnoDB: Warning: io_setup() attempt 5 failed.
140228 12:25:21  InnoDB: Error: io_setup() failed with EAGAIN after 5 attempts.
InnoDB: You can disable Linux Native AIO by setting innodb_native_aio = off in my.cnf
140228 12:25:21 InnoDB: Initializing buffer pool, size = 128.0M
140228 12:25:21 InnoDB: Completed initialization of buffer pool
140228 12:25:21 InnoDB: highest supported file format is Barracuda.
140228 12:25:21 - 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=8388608
read_buffer_size=131072
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 = 338487 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.


Thread pointer: 0x0
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...
stack_bottom = (nil) thread_stack 0x40000
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x39)[0x794a09]
140228 12:25:21  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
/usr/local/mysql/bin/mysqld(handle_segfault+0x380)[0x4fcc60]
/lib/libpthread.so.0(+0xeff0)[0x7f079bf8aff0]
/usr/local/mysql/bin/mysqld[0x88c73c]
/usr/local/mysql/bin/mysqld[0x85196e]
/usr/local/mysql/bin/mysqld[0x7de650]
/lib/libpthread.so.0(+0x68ca)[0x7f079bf828ca]
/lib/libc.so.6(clone+0x6d)[0x7f079b424b6d]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
140228 12:25:21 mysqld_safe mysqld from pid file /usr/local/mysql/data/zbigniewbystrzanowski.pid ended

Liczę na pomoc

 

Edytowano Luty 28, 2014 przez czaczawik (zobacz historię edycji)

[czaczawik 8]

jak sie człowiek wczyta w komunikat błędu to i rozwiazanie sie znajdzie.

InnoDB: You can disable Linux Native AIO by setting innodb_native_aio = off in my.cnf