Mysql başlatma sorunu yardım lutfen

hata vermekde sıteler mysql acılmadıgı ıcın calısmıyor yardım edın lutfen

Waiting for “mysql” to restart ……………………………………………………………………………………………………………………waiting for “mysql” to initialize …………………………………finished.

The service “mysql” failed to start with the message: mysql is not running
/usr/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)'
Check that mysqld is running and that the socket: '/var/lib/mysql/mysql.sock' exists!

Startup Log:
     Starting MySQL. ERROR! The server quit without updating PID file (/var/lib/mysql/vs2552.dus2.alvotech.de.pid).

Log Messages:
     150115 10:58:56 mysqld_safe mysqld from pid file /var/lib/mysql/vs2552.dus2.alvotech.de.pid ended
     150115 10:58:56 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
     150115 10:56:44 mysqld_safe mysqld from pid file /var/lib/mysql/vs2552.dus2.alvotech.de.pid ended
     150115 10:56:43 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
     150115 10:56:30 mysqld_safe mysqld from pid file /var/lib/mysql/vs2552.dus2.alvotech.de.pid ended
     150115 10:56:30 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
     150115 10:55:34 mysqld_safe mysqld from pid file /var/lib/mysql/vs2552.dus2.alvotech.de.pid ended
     150115 10:55:34 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
     150115 10:54:28 mysqld_safe mysqld from pid file /var/lib/mysql/vs2552.dus2.alvotech.de.pid ended
     150115 10:54:28 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
     150115 10:48:03 mysqld_safe mysqld from pid file /var/lib/mysql/vs2552.dus2.alvotech.de.pid ended
     150115 10:48:02 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
     150114 12:14:21 mysqld_safe mysqld from pid file /var/lib/mysql/vs2552.dus2.alvotech.de.pid ended

mysql has failed. Please contact your system administrator if the service does not automagically recover.

Bu sanırım cpanelden restart ettiğinizde ekrana gelen log,

daha detaylı bilgi alabilmek için /var/lib/mysql/(hostname).err dosyasına bakmanız lazım.

veya sunucu bilgilerini gönderirseniz yardımcı olayım.

hocam evet cpanel restrat verdıgımde ssh den verdıgımde ıse

hata verıyor

sorun /var/lib/mysql/vs2552.dus2.alvotech.de.err dosyasında yazıyordur,

tail -n 100 /var/lib/mysql/vs2552.dus2.alvotech.de.err

komutu ile dosyanın son 100 satırını görebilirsiniz.

root@vs2552 [/var/lib/mysql]# /var/lib/mysql/vs2552.dus2.alvotech.de.err
-bash: /var/lib/mysql/vs2552.dus2.alvotech.de.err: Permission denied
.err@vs2552 [/var/lib/mysql]# tail -n 100 /var/lib/mysql/vs2552.dus2.alvotech.de
2015-01-15 14:56:28 10636 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-01-15 14:56:28 10636 [Note] InnoDB: Memory barrier is not used
2015-01-15 14:56:28 10636 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-01-15 14:56:28 10636 [Note] InnoDB: Using Linux native AIO
2015-01-15 14:56:28 10636 [Note] InnoDB: Using CPU crc32 instructions
2015-01-15 14:56:28 10636 [Note] InnoDB: Initializing buffer pool, size = 59.0M
2015-01-15 14:56:28 10636 [Note] InnoDB: Completed initialization of buffer pool
2015-01-15 14:56:28 10636 [Note] InnoDB: Highest supported file format is Barracuda.
2015-01-15 14:56:28 10636 [Note] InnoDB: The log sequence numbers 6525155 and 6525155 in ibdata files do not match the log sequence number 6525452 in the ib_logfiles!
2015-01-15 14:56:28 10636 [Note] InnoDB: Database was not shutdown normally!
2015-01-15 14:56:28 10636 [Note] InnoDB: Starting crash recovery.
2015-01-15 14:56:28 10636 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-01-15 14:56:28 10636 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace webrekla_data/events uses space ID: 120 at filepath: ./webrekla_data/events.ibd. Cannot open tablespace webtasar_web/events which uses space ID: 120 at filepath: ./webtasar_web/events.ibd
2015-01-15 14:56:28 7f616eee6720  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./webtasar_web/events.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
150115 14:56:28 mysqld_safe mysqld from pid file /var/lib/mysql/vs2552.dus2.alvotech.de.pid ended
150115 15:25:04 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
2015-01-15 15:25:05 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2015-01-15 15:25:05 31662 [Note] Plugin 'FEDERATED' is disabled.
2015-01-15 15:25:05 31662 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-01-15 15:25:05 31662 [Note] InnoDB: The InnoDB memory heap is disabled
2015-01-15 15:25:05 31662 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-01-15 15:25:05 31662 [Note] InnoDB: Memory barrier is not used
2015-01-15 15:25:05 31662 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-01-15 15:25:05 31662 [Note] InnoDB: Using Linux native AIO
2015-01-15 15:25:05 31662 [Note] InnoDB: Using CPU crc32 instructions
2015-01-15 15:25:05 31662 [Note] InnoDB: Initializing buffer pool, size = 59.0M
2015-01-15 15:25:05 31662 [Note] InnoDB: Completed initialization of buffer pool
2015-01-15 15:25:05 31662 [Note] InnoDB: Highest supported file format is Barracuda.
2015-01-15 15:25:05 31662 [Note] InnoDB: The log sequence numbers 6525155 and 6525155 in ibdata files do not match the log sequence number 6525452 in the ib_logfiles!
2015-01-15 15:25:05 31662 [Note] InnoDB: Database was not shutdown normally!
2015-01-15 15:25:05 31662 [Note] InnoDB: Starting crash recovery.
2015-01-15 15:25:05 31662 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-01-15 15:25:05 31662 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace webrekla_data/events uses space ID: 120 at filepath: ./webrekla_data/events.ibd. Cannot open tablespace webtasar_web/events which uses space ID: 120 at filepath: ./webtasar_web/events.ibd
2015-01-15 15:25:05 7f34da6c4720  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./webtasar_web/events.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
150115 15:25:05 mysqld_safe mysqld from pid file /var/lib/mysql/vs2552.dus2.alvotech.de.pid ended
150115 15:29:44 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
2015-01-15 15:29:45 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2015-01-15 15:29:45 16009 [Note] Plugin 'FEDERATED' is disabled.
2015-01-15 15:29:45 16009 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-01-15 15:29:45 16009 [Note] InnoDB: The InnoDB memory heap is disabled
2015-01-15 15:29:45 16009 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-01-15 15:29:45 16009 [Note] InnoDB: Memory barrier is not used
2015-01-15 15:29:45 16009 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-01-15 15:29:45 16009 [Note] InnoDB: Using Linux native AIO
2015-01-15 15:29:45 16009 [Note] InnoDB: Using CPU crc32 instructions
2015-01-15 15:29:45 16009 [Note] InnoDB: Initializing buffer pool, size = 59.0M
2015-01-15 15:29:45 16009 [Note] InnoDB: Completed initialization of buffer pool
2015-01-15 15:29:45 16009 [Note] InnoDB: Highest supported file format is Barracuda.
2015-01-15 15:29:45 16009 [Note] InnoDB: The log sequence numbers 6525155 and 6525155 in ibdata files do not match the log sequence number 6525452 in the ib_logfiles!
2015-01-15 15:29:45 16009 [Note] InnoDB: Database was not shutdown normally!
2015-01-15 15:29:45 16009 [Note] InnoDB: Starting crash recovery.
2015-01-15 15:29:45 16009 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-01-15 15:29:45 16009 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace webrekla_data/events uses space ID: 120 at filepath: ./webrekla_data/events.ibd. Cannot open tablespace webtasar_web/events which uses space ID: 120 at filepath: ./webtasar_web/events.ibd
2015-01-15 15:29:45 7f4521ef4720  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./webtasar_web/events.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
150115 15:29:45 mysqld_safe mysqld from pid file /var/lib/mysql/vs2552.dus2.alvotech.de.pid ended

innodb tablolarınız bozulmuş, bunları fixlemeniz lazım, err dosyasını silmenizin bir faydası olmaz, hatayı düzeltmezseniz tekrar dolar.

Kaç tablonuz var, sorun tam olarak nedir, bunları görmeden kesin birşey söylemek zor. düzeltme konusunda duruma göre ücreti ile yardımcı olabilirim.

hocam ben butun datayı sıldım mysql klasorunu temızledım yanlız hala hata verıyor

cpaneldekı hata

Waiting for “mysql” to restart ……………………………………………………………………………………………………………………waiting for “mysql” to initialize …………………………………finished.

The service “mysql” failed to start with the message: mysql is not running
/usr/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)'
Check that mysqld is running and that the socket: '/var/lib/mysql/mysql.sock' exists!

Startup Log:
     Starting MySQL. ERROR! The server quit without updating PID file (/var/lib/mysql/vs2552.dus2.alvotech.de.pid).

Log Messages:
     150115 17:20:00 mysqld_safe mysqld from pid file /var/lib/mysql/vs2552.dus2.alvotech.de.pid ended
     /usr/sbin/mysqld: Table 'mysql.plugin' doesn't exist
     150115 17:19:59 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
     150115 17:17:50 mysqld_safe mysqld from pid file /var/lib/mysql/vs2552.dus2.alvotech.de.pid ended
     /usr/sbin/mysqld: Table 'mysql.plugin' doesn't exist
     150115 17:17:50 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
     150115 17:16:33 mysqld_safe mysqld from pid file /var/lib/mysql/vs2552.dus2.alvotech.de.pid ended

mysql has failed. Please contact your system administrator if the service does not automagically recover.

Veritabanını silmeniz birşey değiştirmez, innodb motorunun tamir edilmesi gerekiyor, eğer mysql veritabanlarına (hepsine) ihtiyacınız yoksa tamamen silip sıfırdan kurarsınız sorun çözülür,

aksi halde /var/lib/mysql/vs2552.dus2.alvotech.de.err bu dosyadaki hatalara bakmanız gerekir, restart ettikten sonra çıkanların size bir faydası olmaz, orda sadece başlatılamadığı yazar sebebi yazmaz. sebebi /var/lib/mysql/vs2552.dus2.alvotech.de.err bu dosya da.

Sanırım mysql ayarlarında tanımlanan soket adresini bulamıyor.

--R10.NET; Flood Engellendi -->-> Yeni yazılan mesaj 18:49:09 -->-> Daha önceki mesaj 18:47:09 --

my.cnf dosyası içinden

Aşağıdaki ayarların doğruluğunu kontrol ediniz.

Bendeki ayarlar şu şekilde gözükmektedir.

pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock

Kolay gelsin...