ridoerdie adlı üyeden alıntı: mesajı görüntüle
mysql --socket=/var/lib/mysql/mysql.sock -uroot
hata vermedi mysql e bağlandı


mysql --socket=/var/lib/mysql/mysql.sock -uroot
Çıktının bir kısmı
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
130417 23:25:39  InnoDB: Unable to open the first data file
InnoDB: Error in opening ./ibdata1
130417 23:25:39  InnoDB: Operating system error number 11 in a file operation.
InnoDB: Error number 11 means 'Resource temporarily unavailable'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.html
InnoDB: Could not open or create data files.
InnoDB: If you tried to add new data files, and it failed here,
InnoDB: you should now edit innodb_data_file_path in my.cnf back
InnoDB: to what it was, and remove the new ibdata files InnoDB created
InnoDB: in this failed attempt. InnoDB only wrote those files full of
InnoDB: zeros, but did not yet use them in any way. But be careful: do not
InnoDB: remove old data files which contain your precious data!
130417 23:25:40 [ERROR] Plugin 'InnoDB' init function returned error.
130417 23:25:40 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
130417 23:25:55 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
130417 23:25:55 [ERROR] Do you already have another mysqld server running on port: 3306 ?
130417 23:25:55 [ERROR] Aborting

130417 23:25:55 [Note] /usr/sbin/mysqld: Shutdown complete

130417 23:25:55 mysqld_safe mysqld from pid file /var/lib/mysql/mail.inkasoft.com.tr.pid ended
130417 23:26:20 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:26:45 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:27:41 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:28:11 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:28:39 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:29:06 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:29:35 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:30:03 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:30:32 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:31:00 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:31:56 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:32:53 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:33:21 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:34:46 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:35:14 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:35:42 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:35:49 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:36:11 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:36:40 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:37:11 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:37:38 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:37:47 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:38:04 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:38:37 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:40:02 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:40:57 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:41:23 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:41:49 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:41:51 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:42:54 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:43:15 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:44:12 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:45:41 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:46:37 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:47:06 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:47:33 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:48:04 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:49:00 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:50:27 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:51:25 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:51:53 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:52:23 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:53:49 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:54:46 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:55:16 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:55:47 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:56:13 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:56:43 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:57:11 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:58:09 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
130417 23:58:39 [ERROR] /usr/sbin/mysqld: Table './tribunvi_tvideo/wp_redirection_logs' is marked as crashed and should be repaired
Tamam sende bağlanmak istiyordun sanırım yalnız şuan da mysql'in şifresiz olarak çalışıyor. Özellikle böyle çalışmasını sen mi istedin ?

pkill -9 mysqld
rm -f /etc/my.cnf
service mysqld restart
yaptıktan sonra tekrar bağlanmayı deneyebilirsin tabi eğer /root/.my.cnf dosyanda mysql root şifren yazmıyorsa şifre belirterek bağlanabilirsin.

Ardından

tribunvi_tvideo database'ini repair edebilirsin.