Dotaz: Mysql nelze spustit

[Knub]

Cau mam problem s Mysql na debianu. po instalaci pomoci apt-get install mysql-server se mi nespusti a hodi tuhle chybu:

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

Už sem hledal zde na diskusi ale nic z popsaných řešení mi nepomohlo.

Díky

Odpovědi

[Michal Čihař]

A přečetl sis co ti mysql píše do logu?

[Knub]

ne, kde ho najdu?

[Michal Čihař]

Třeba ho najdeš po přečtení všeho, co ti spouštění mysql serveru píše.

[Libor Klepac]

a co to pise do logu? (novejsi mysql-server loguje pres syslog)

[Knub]

Kde najdu ten log pls?

[Luboš Doležel (Doli)]

Máte tu službu vůbec spuštěnou?

[Knub]

myslíš jako mysql? to mi právě nejde spustit

[Luboš Doležel (Doli)]

Jsou dvě věci: mysqld a mysql. To první je služba, která zpracovává požadavky klientů. To druhé je jednoduchý klient. Takže nejprve musíte spustit server. Jak ho spustit na Debianu, nevím (/etc/init.d/mysql start?).

[Knub]

tak sem to spustil a vypsalo to tohle:

Starting MySQL database server: mysqld...failed or took more than 6s. Please take a look at the syslog. /usr/bin/mysqladmin: connect to server at 'localhost' failed error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)' Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!

[Michal Čihař]

Please take a look at the syslog.

A podíval jste se?

[Knub]

JO sou tam nesmyslný znaky a plno nic neříkajícího textu

[Luboš Doležel (Doli)]

Zkuste ještě předtím příkaz mysql_config (snad je to to, co myslím).

[Knub]

Command not found

[Luboš Doležel (Doli)]

Tak ne, je to snad mysql_install_db

[Knub]

to uz sem zkousel, vypsalo to tohle:

Installing all prepared tables Fill help tables

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

PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER ! To do so, start the server, then issue the following commands: /usr/bin/mysqladmin -u root password 'new-password' /usr/bin/mysqladmin -u root -h rubick password 'new-password' See the manual for more instructions.

NOTE: If you are upgrading from a MySQL <= 3.22.10 you should run the /usr/bin/mysql_fix_privilege_tables. Otherwise you will not be able to use the new GRANT command!

You can start the MySQL daemon with: cd /usr ; /usr/bin/mysqld_safe &

You can test the MySQL daemon with the benchmarks in the 'sql-bench' directory: cd sql-bench ; perl run-all-tests

Please report any problems with the /usr/bin/mysqlbug script!

The latest information about MySQL is available on the web at http://www.mysql.com Support MySQL by buying support/licenses at https://order.mysql.com

[Luboš Doležel (Doli)]

Tak se podívejte do logu mysql, proč se nechce spustit (u mě /var/log/mysql/mysqld.err).

[Knub]

Tam mám jen soubory mysql-bin.000001 až mysql-bin.000011 a mysql-bin.index a ve vsech sou totalni nesmysly. (ruzne znaky pomochane, nejake SQL dotazy, nic konkretniho). Kdesi sem četl že to někomu pomohlo odinstalovat a znovu to nainstalovat. I když v to moc nevěřím, nemohl byste mi napsat jak to odinstalovat? Zkoušel sem atp-get remove i purge a vzdycky to odstranilo nejakych 70kB. Sice se to tvarilo jako ze uz tam balicek neni ale stale sem mohl spustit vsechny prikazy k mysql. Diky

[Libor Klepac]

mysql-server nejspis zavisi na mysql-server-5.1 nebo -4.1 ... mate pouzivat aptitude ;) ... a loguje to do /var/log/daemon.log

[Knub]

To aptitude sem už taky zkoušel, dělá to to samo co apt-get (odstrani nejakych 70kB) A vtom logu neni nic podstatnyho, proste to pise ze se nemuze connectnout pres ten socket mysql.sock, ktery v /var/run/msqld/ stejne neni a neni ani nikde na disku. Zajimalo by me jak to muzu kompletne odstranit to mysql

[Libor Klepac]

jestli jsi to puvodne nainstalvoal pres apt-get, tak je to jasne, no ale staci se podivat na zavislosti balicku mysql-server a nejspis tam bude ten verzovany balicek

[Knub]

A kde to najdu ty zavislosti? Dival sem se na dselect ale vubec se v tom nevyznam

[Libor Klepac]

najdes balik mysql-server a zmacknes d, cimz uvidis zavislosti ... a nebo dej hledat mysql-server vickrat, ono to tam casem spadne ;)

[Knup]

No nenasel sem ho, neeni to tim ze sem ho odinstaloval ti apt-get?

[iji]

zkuste prejmenovat adresar /lib/tls na neco jineho a opet sluzbu spustit pres skipt v /etc/init.d/.

[iji]

s/skipt/skript/

[Knub]

Myslíte že to jee dobrý nápad? sou tam nějaké linuxácké soubory

[Luboš Doležel (Doli)]

Nejprve nám radši vysvětlete, proč by tohle mělo pomoci - to je trochu hardcore.

[Libor Klepac]

me tohle pomohlo v user-mode-linuxu ;)) ,ale jinak nevim

[Knub]

Mě by asi nejvíc zajímalo proč mi to nevytvořilo ten soubor mysql.sock

[Libor Klepac]

protoze vznikne pri startu mysqld

[Knub]

když sem to spustil to mysqld tak tam začaly lítat nějaký jedničky a nuly jako v matrixu, že to ani Putty nestihal zobrazovat, stačil sem zachytit jen toto:

;InnoDB: End of page dump 060225 21:46:42 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 060225 21:46:42InnoDB: Error: trying to access a stray pointer 0x362bfff8 InnoDB: buf pool start is at 0xb62b0000, end at 0xb6ab0000 InnoDB: Probable reason is database corruption or memory InnoDB: corruption. If this happens in an InnoDB database recovery, InnoDB: you can look from section 6.1 at http://www.innodb.com/ibman.html InnoDB: how to force recovery. 060225 21:46:42InnoDB: Assertion failure in thread 3083409088 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/mysql/en/Forcing_recovery.html InnoDB: about forcing recovery. 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=0xbfa6bd58, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x818f41c 0xffffe420 0xbfa6d0a4 0x831a475 0x82c72bb 0x82c8913 0x82b4399 0x82b2ab4 Stack trace seems successful - bottom reached 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.

[Libor Klepac]

asi je to rozbite ;) ... jestli innodb nepotrebujes, tak do /etc/mysql/my.cnf pridej skip-innodb , snad to pomuze, pripadne se zbav tech souboru, ejstli jsou "rozbite"

[Knub]

Supr, už se tam něco rozjelo :)

Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 1 to server version: 5.0.18-Debian_7-log

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

Ted uz teda muzu rozjet PHPmyAdmin?