Timeout error occurred trying to start MySQL Daemon Опции

[KMUA]

Такие дела, VDS 128 озу, запускаю апач, а потом mysql

Код

[root@vpsadmin /]# service httpd start
Starting httpd: httpd: Could not reliably determine the server's fully qualified domain name, using 209.250.241.187 for ServerName
                                                           [  OK  ]
[root@vpsadmin /]# service mysqld start
Timeout error occurred trying to start MySQL Daemon.
Starting MySQL:                                            [FAILED]

Вычитал что нужно создать базы перед запуском mysql. Создал:

Код

[root@vpsadmin /]# /usr/bin/mysql_install_db
Installing MySQL system tables...
OK
Filling help tables...
OK

To start mysqld at boot time you have to copy
support-files/mysql.server to the right place for your system

Проблема осталась, дальше не знаю куда копать...




Логи мускула:

090625 16:32:23 mysqld started
090625 16:32:23 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...
090625 16:32:24 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 8204.
InnoDB: Doing recovery: scanned up to log sequence number 0 8204
InnoDB: Page directory corruption: supremum not pointed to
090625 16:32:24 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 00000000000000000000000000000000000000000000000000; asc ;InnoDB: End of page dump
090625 16:32:24 InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page directory corruption: supremum not pointed to
090625 16:32:24 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex asc 000000000000000000000000000000 ;InnoDB: End of page dump
090625 16:32:25 InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
090625 16:32:25InnoDB: Error: trying to access a stray pointer 0x375dbff8
InnoDB: buf pool start is at 0xb75cc000, end at 0xb7dcc000
InnoDB: Probable reason is database corruption or memory
InnoDB: corruption. If this happens in an InnoDB database recovery, see
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: how to force recovery.
090625 16:32:25InnoDB: Assertion failure in thread 3086452448 in file ./../include/buf0buf.ic line 259
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/forcing-recovery.html
InnoDB: about forcing recovery.
090625 16:32:25 - 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.

thd=(nil)
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=0xbf949248, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8187393
....
....
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/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/en/Crashing.html contains
information that should help you find out what is causing the crash.
090625 16:32:25 mysqld ended

[Roman Hirauka]

Проверьте права, мускулевские ли стоят на сам мускуль.

[admst]

Код

[root@vpsadmin /]# service httpd start
Starting httpd: httpd: Could not reliably determine the server's fully qualified domain name, using 209.250.241.187 for ServerName
                                                           [  OK  ]

Ну для начала, чтобы избавиться от этого сообщения добавь имя основного виртуального хоста в httpd.conf:
ServerName localhost

Код

[root@vpsadmin /]# service mysqld start
Timeout error occurred trying to start MySQL Daemon.
Starting MySQL:                                            [FAILED]

Что касается данной мессаги, то попробуй для начала выставить права:
chown -R mysql.mysql /var/lib/mysql

P.S: на всякий случай проверь наличие my.cnf

Сообщение отредактировал admst - 26.06.2009, 03:14

[ENELIS]

Код

[root@vpsadmin /]# service httpd start
Starting httpd: httpd: Could not reliably determine the server's fully qualified domain name, using 209.250.241.187 for ServerName
                                                           [  OK  ]

Ну для начала, чтобы избавиться от этого сообщения добавь имя основного виртуального хоста в httpd.conf:
ServerName localhost

Или отключить проверку fqdn

[lazutov]

для несложных проектов где inodb не нужно - раскомментировать в конфе skip-innodb.
Лечит много потенциально острых углов. и высвобождает 100+ mb

[KMUA]

для несложных проектов где inodb не нужно - раскомментировать в конфе skip-innodb.
Лечит много потенциально острых углов. и высвобождает 100+ mb

Вот спасибо. (IMG:style_emoticons/default/wink.gif) Добавил в конф, действительно включился. Тем не менее переставил систему, на этот раз все запустилось нормально, только отжирало практически всю память. Я грешил на утечку памяти, а оказывается это innodb столько занимал.

А можно подробнее, для чего может понадобиться innodb?

Сообщение отредактировал KMUA - 26.06.2009, 09:55

[lazutov]

go wikipedia for details