Mysql Server lässt sich nicht starten?

[boldilein]

Hallo,

Ich habe einen Server mit Suse 11.3 und kann meinen Msql Server nicht starten Auszug aus dem log file, Vielen Dank im Voraus:

120918 00:12:00 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
120918 0:12:01 [Warning] '--default-character-set' is deprecated and will be removed in a future release. Please use '--character-set-server' instead.
120918 0:12:01 [Warning] /usr/sbin/mysqld: Option '--set-variable' is deprecated. Use --variable-name=value instead.
120918 0:12:01 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
120918 0:12:02 [Note] Plugin 'ndbcluster' is disabled.
120918 0:12:02 [Note] Plugin 'FEDERATED' is disabled.
/usr/sbin/mysqld: Can't create/write to file '/var/tmp/mysql.mEf2ET/ibTiAIlj' (Errcode: 2)
120918 0:12:02 InnoDB: Error: unable to create temporary file; errno: 2
120918 0:12:02 [ERROR] Plugin 'InnoDB' init function returned error.
120918 0:12:02 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
120918 00:12:02 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
120918 0:12:02 [Warning] '--default-character-set' is deprecated and will be removed in a future release. Please use '--character-set-server' instead.
120918 0:12:02 [Warning] /usr/sbin/mysqld: Option '--set-variable' is deprecated. Use --variable-name=value instead.
120918 0:12:02 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
120918 0:12:02 [Note] Plugin 'ndbcluster' is disabled.
120918 0:12:02 [Note] Plugin 'FEDERATED' is disabled.
120918 0:12:02 InnoDB: Initializing buffer pool, size = 8.0M
120918 0:12:02 InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120918 0:12:02 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
120918 0:12:03 [Note] Event Scheduler: Loaded 0 events
120918 0:12:03 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.57-log' socket: '/var/run/mysql/mysql.sock' port: 3306 SUSE MySQL RPM
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 15 row operations to undo
InnoDB: Trx id counter is 0 6175744
InnoDB: Last MySQL binlog file position 0 258101737, file name ./mysql-bin.000090
InnoDB: Starting in background the rollback of uncommitted transactions
120918 0:12:07 InnoDB: Rolling back trx with id 0 6175278, 15 rows to undo
120918 0:12:07 InnoDB: Started; log sequence number 0 1085097899

InnoDB: Rolling back of trx id 0 6175278 completed
120918 0:12:07 InnoDB: Rollback of non-prepared transactions completed
120918 0:12:07 [Note] Recovering after a crash using mysql-bin
120918 0:12:14 [ERROR] Error in Log_event::read_log_event(): 'read error', data_len: 1476, event_type: 2
120918 0:12:14 [Note] Starting crash recovery...
120918 0:12:14 [Note] Crash recovery finished.
120918 0:12:15 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
120918 0:12:15 [ERROR] Do you already have another mysqld server running on port: 3306 ?
120918 0:12:15 [ERROR] Aborting

120918 0:12:16 InnoDB: Starting shutdown...
120918 0:12:18 InnoDB: Shutdown completed; log sequence number 0 1085099276
120918 0:12:18 [Note] /usr/sbin/mysqld: Shutdown complete

120918 00:12:18 mysqld_safe mysqld from pid file /var/run/mysql/mysqld.pid ended
120918 0:13:17 [ERROR] /usr/sbin/mysqld: Incorrect key file for table './web22_p1/jos_session.MYI'; try to repair it
120918 0:13:55 [ERROR] /usr/sbin/mysqld: Incorrect key file for table './web21_p1/cmos_session.MYI'; try to repair it
120918 0:13:55 [ERROR] /usr/sbin/mysqld: Incorrect key file for table './web21_p1/cmos_session.MYI'; try to repair it
120918 0:13:55 [ERROR] /usr/sbin/mysqld: Incorrect key file for table './web21_p1/cmos_session.MYI'; try to repair it
120918 0:20:10 [ERROR] /usr/sbin/mysqld: Incorrect key file for table './web22_p1/jos_session.MYI'; try to repair it
120918 0:32:56 [ERROR] /usr/sbin/mysqld: Disk is full writing './mysql-bin.000091' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
120918 0:32:56 [ERROR] /usr/sbin/mysqld: Retry in 60 secs. Message reprinted in 600 secs
120918 0:32:57 [ERROR] /usr/sbin/mysqld: Table './web21_p1/cmos_session' is marked as crashed and should be repaired
120918 0:32:57 [ERROR] /usr/sbin/mysqld: Table './web21_p1/cmos_session' is marked as crashed and should be repaired
120918 0:32:57 [ERROR] /usr/sbin/mysqld: Table './web21_p1/cmos_session' is marked as crashed and should be repaired
120918 0:32:57 [ERROR] /usr/sbin/mysqld: Table './web21_p1/cmos_session' is marked as crashed and should be repaired
120918 0:32:57 [ERROR] /usr/sbin/mysqld: Table './web21_p1/cmos_session' is marked as crashed and should be repaired
120918 0:37:41 [ERROR] /usr/sbin/mysqld: Table './web21_p1/cmos_session' is marked as crashed and should be repaired
120918 0:37:41 [ERROR] /usr/sbin/mysqld: Table './web21_p1/cmos_session' is marked as crashed and should be repaired
120918 0:37:41 [ERROR] /usr/sbin/mysqld: Table './web21_p1/cmos_session' is marked as crashed and should be repaired
120918 0:37:41 [ERROR] /usr/sbin/mysqld: Table './web21_p1/cmos_session' is marked as crashed and should be repaired
120918 0:37:41 [ERROR] /usr/sbin/mysqld: Table './web21_p1/cmos_session' is marked as crashed and should be repaired
120918 0:38:13 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 0:38:13 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 0:38:13 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 0:38:13 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 0:38:13 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 0:39:19 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 0:39:19 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 0:39:19 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 0:39:19 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 0:39:19 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 0:39:42 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 0:39:42 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 0:39:42 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 0:39:42 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 0:39:42 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 00:42:02 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
120918 0:42:02 [Warning] '--default-character-set' is deprecated and will be removed in a future release. Please use '--character-set-server' instead.
120918 0:42:02 [Warning] /usr/sbin/mysqld: Option '--set-variable' is deprecated. Use --variable-name=value instead.
120918 0:42:02 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
120918 0:42:02 [Note] Plugin 'ndbcluster' is disabled.
120918 0:42:02 [Note] Plugin 'FEDERATED' is disabled.
120918 0:42:02 InnoDB: Initializing buffer pool, size = 8.0M
120918 0:42:02 InnoDB: Completed initialization of buffer pool
120918 0:42:02 InnoDB: Started; log sequence number 0 1085099276
/usr/s120918 1:22:05 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
120918 1:22:05 [ERROR] Do you already have another mysqld server running on port: 3306 ?
120918 1:22:05 [ERROR] Aborting

120918 1:22:05 InnoDB: Starting shutdown...
120918 1:22:10 InnoDB: Shutdown completed; log sequence number 0 1085099276
120918 1:22:10 [Note] /usr/sbin/mysqld: Shutdown complete

120918 01:22:10 mysqld_safe mysqld from pid file /var/run/mysql/mysqld.pid ended
120918 05:48:52 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
120918 05:48:53 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
120918 5:48:53 [Warning] '--default-character-set' is deprecated and will be removed in a future release. Please use '--character-set-server' instead.
120918 5:48:53 [Warning] /usr/sbin/mysqld: Option '--set-variable' is deprecated. Use --variable-name=value instead.
120918 5:48:53 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
120918 5:48:53 [Warning] '--default-character-set' is deprecated and will be removed in a future release. Please use '--character-set-server' instead.
120918 5:48:53 [Warning] /usr/sbin/mysqld: Option '--set-variable' is deprecated. Use --variable-name=value instead.
120918 5:48:53 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
/usr/sbin/mysqld: Error on delete of '/var/lib/mysql/s15423093.lower-test' (Errcode: 2)
/usr/sbin/mysqld: Error on delete of '/var/lib/mysql/s15423093.lower-test' (Errcode: 2)
120918 5:48:53 [Note] Plugin 'ndbcluster' is disabled.
120918 5:48:53 [Note] Plugin 'ndbcluster' is disabled.
120918 5:48:53 [Note] Plugin 'FEDERATED' is disabled.
120918 5:48:53 [Note] Plugin 'FEDERATED' is disabled.
/usr/sbin/mysqld: Can't create/write to file '/var/tmp/mysql.IxrsJ4/ib5o92Oz' (Errcode: 2)
120918 5:48:53 InnoDB: Error: unable to create temporary file; errno: 2
120918 5:48:53 [ERROR] Plugin 'InnoDB' init function returned error.
120918 5:48:53 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
120918 5:48:53 InnoDB: Initializing buffer pool, size = 8.0M
120918 5:48:53 InnoDB: Completed initialization of buffer pool
120918 5:48:53 [Note] Event Scheduler: Loaded 0 events
120918 5:48:53 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.57-log' socket: '/var/run/mysql/mysql.sock' port: 3306 SUSE MySQL RPM
120918 5:48:53 InnoDB: Started; log sequence number 0 1085099276
120918 5:48:54 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
120918 5:48:54 [ERROR] Do you already have another mysqld server running on port: 3306 ?
120918 5:48:54 [ERROR] Aborting

120918 5:48:54 InnoDB: Starting shutdown...
120918 5:48:59 InnoDB: Shutdown completed; log sequence number 0 1085099276
120918 5:48:59 [Note] /usr/sbin/mysqld: Shutdown complete

120918 05:48:59 mysqld_safe mysqld from pid file /var/run/mysql/mysqld.pid ended
120918 5:50:09 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:50:09 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:50:09 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:50:09 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:50:09 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:50:25 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:50:25 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:50:25 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:50:25 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:50:25 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:51:34 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:51:34 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:51:34 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:51:34 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:51:34 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:52:14 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:52:14 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:52:14 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:52:14 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:52:14 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:52:23 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:52:23 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:52:23 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:52:23 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:52:23 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:53:20 [ERROR] /usr/sbin/mysqld: Table './web21_p1/cmos_session' is marked as crashed and should be repaired
120918 5:53:20 [ERROR] /usr/sbin/mysqld: Table './web21_p1/cmos_session' is marked as crashed and should be repaired
120918 5:53:20 [ERROR] /usr/sbin/mysqld: Table './web21_p1/cmos_session' is marked as crashed and should be repaired
120918 5:53:20 [ERROR] /usr/sbin/mysqld: Table './web21_p1/cmos_session' is marked as crashed and should be repaired
120918 5:55:03 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:55:03 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:55:03 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:55:03 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 5:55:03 [ERROR] /usr/sbin/mysqld: Table './web22_p1/jos_session' is marked as crashed and should be repaired
120918 05:56:28 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
120918 5:56:28 [Warning] '--default-character-set' is deprecated and will be removed in a future release. Please use '--character-set-server' instead.
120918 5:56:28 [Warning] /usr/sbin/mysqld: Option '--set-variable' is deprecated. Use --variable-name=value instead.
120918 5:56:28 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
120918 5:56:28 [Note] Plugin 'ndbcluster' is disabled.
120918 5:56:28 [Note] Plugin 'FEDERATED' is disabled.
120918 5:56:28 InnoDB: Initializing buffer pool, size = 8.0M
120918 5:56:28 InnoDB: Completed initialization of buffer pool
120918 5:56:28 InnoDB: Started; log sequence number 0 1085099276
120918 5:56:28 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
120918 5:56:28 [ERROR] Do you already have another mysqld server running on port: 3306 ?
120918 5:56:28 [ERROR] Aborting

120918 5:56:28 InnoDB: Starting shutdown...
120918 5:56:33 InnoDB: Shutdown completed; log sequence number 0 1085099276
120918 5:56:33 [Note] /usr/sbin/mysqld: Shutdown complete

120918 05:56:33 mysqld_safe mysqld from pid file /var/run/mysql/mysqld.pid ended
120918 05:57:11 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
120918 5:57:11 [Warning] '--default-character-set' is deprecated and will be removed in a future release. Please use '--character-set-server' instead.
120918 5:57:11 [Warning] /usr/sbin/mysqld: Option '--set-variable' is deprecated. Use --variable-name=value instead.
120918 5:57:11 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
120918 5:57:11 [Note] Plugin 'ndbcluster' is disabled.
120918 5:57:11 [Note] Plugin 'FEDERATED' is disabled.
120918 5:57:11 InnoDB: Initializing buffer pool, size = 8.0M
120918 5:57:11 InnoDB: Completed initialization of buffer pool
120918 5:57:11 InnoDB: Started; log sequence number 0 1085099276
/usr/sbin/mysqld: Disk is full writing './mysql-bin.000096' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
/usr/sbin/mysqld: Retry in 60 secs. Message reprinted in 600 secs
120918 5:58:12 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
120918 5:58:12 [ERROR] Do you already have another mysqld server running on port: 3306 ?
120918 5:58:12 [ERROR] Aborting

120918 5:58:12 InnoDB: Starting shutdown...
120918 5:58:17 InnoDB: Shutdown completed; log sequence number 0 1085099276
120918 5:58:17 [Note] /usr/sbin/mysqld: Shutdown complete

120918 05:58:17 mysqld_safe mysqld from pid file /var/run/mysql/mysqld.pid ended
120918 06:05:06 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
120918 6:05:06 [Warning] '--default-character-set' is deprecated and will be removed in a future release. Please use '--character-set-server' instead.
120918 6:05:06 [Warning] /usr/sbin/mysqld: Option '--set-variable' is deprecated. Use --variable-name=value instead.
120918 6:05:06 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
120918 6:05:06 [Note] Plugin 'ndbcluster' is disabled.
120918 6:05:06 [Note] Plugin 'FEDERATED' is disabled.
120918 6:05:06 InnoDB: Initializing buffer pool, size = 8.0M
120918 6:05:06 InnoDB: Completed initialization of buffer pool
120918 6:05:06 InnoDB: Started; log sequence number 0 1085099276
120918 6:05:07 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
120918 6:05:07 [ERROR] Do you already have another mysqld server running on port: 3306 ?
120918 6:05:07 [ERROR] Aborting

120918 6:05:07 InnoDB: Starting shutdown...
120918 6:05:12 InnoDB: Shutdown completed; log sequence number 0 1085099276
120918 6:05:12 [Note] /usr/sbin/mysqld: Shutdown complete

120918 06:05:12 mysqld_safe mysqld from pid file /var/run/mysql/mysqld.pid ended
120918 08:22:42 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
120918 8:22:42 [Warning] '--default-character-set' is deprecated and will be removed in a future release. Please use '--character-set-server' instead.
120918 8:22:42 [Warning] /usr/sbin/mysqld: Option '--set-variable' is deprecated. Use --variable-name=value instead.
120918 8:22:42 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
120918 8:22:42 [Note] Plugin 'ndbcluster' is disabled.
120918 8:22:42 [Note] Plugin 'FEDERATED' is disabled.
120918 8:22:42 InnoDB: Initializing buffer pool, size = 8.0M
120918 8:22:42 InnoDB: Completed initialization of buffer pool
120918 8:22:42 InnoDB: Started; log sequence number 0 1085099276
/usr/sbin/mysqld: Disk is full writing './mysql-bin.~rec~' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
/usr/sbin/mysqld: Retry in 60 secs. Message reprinted in 600 secs
/usr/sbin/mysqld: Retry in 60 secs. Message reprinted in 600 sec

 

[panamajo]

120918 0:32:56 [ERROR] /usr/sbin/mysqld: Disk is full writing './mysql-bin.000091' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)

MySQL versucht die Tabellen zu reparieren (Kaltstart?), aber wenn kein Platz da ist wirds schwierig.
Du solltest - je nach Größe der DBs - ein paar hundert KB auf der Partition freischaufeln, ggf. auch mehr.

 

[boldilein]

Alles klar danke erstmal....

Ich hab hier jede Menge riesige Files kann ich diese bedenkenlos löschen?


-rw-rw---- 1 mysql mysql 74M Apr 25 2011 ./lib/mysql/mysql-bin.000015
-rw-rw---- 1 mysql mysql 85M May 31 2011 ./lib/mysql/mysql-bin.000019
-rw-rw---- 1 mysql mysql 39M Jun 10 2011 ./lib/mysql/mysql-bin.000020
-rw-rw---- 1 mysql mysql 298M Jun 27 2011 ./lib/mysql/mysql-bin.000022
-rw-rw---- 1 mysql mysql 26M Jul 2 2011 ./lib/mysql/mysql-bin.000023
-rw-rw---- 1 mysql mysql 1.1G Aug 8 2011 ./lib/mysql/mysql-bin.000026
-rw-rw---- 1 mysql mysql 1.1G Sep 20 2011 ./lib/mysql/mysql-bin.000027
-rw-rw---- 1 mysql mysql 1.1G Oct 27 2011 ./lib/mysql/mysql-bin.000028
-rw-rw---- 1 mysql mysql 1.1G Nov 29 2011 ./lib/mysql/mysql-bin.000029
-rw-rw---- 1 mysql mysql 1.1G Dec 18 2011 ./lib/mysql/mysql-bin.000030
-rw-rw---- 1 mysql mysql 1.1G Jan 3 2012 ./lib/mysql/mysql-bin.000031
-rw-rw---- 1 mysql mysql 641M Jan 19 2012 ./lib/mysql/mysql-bin.000032
-rw-rw---- 1 mysql mysql 216M Jan 21 2012 ./lib/mysql/mysql-bin.000033
-rw-rw---- 1 mysql mysql 211M Jan 25 2012 ./lib/mysql/mysql-bin.000034
-rw-rw---- 1 mysql mysql 12M Jan 26 2012 ./lib/mysql/mysql-bin.000036
-rw-rw---- 1 mysql mysql 11M Jan 26 2012 ./lib/mysql/mysql-bin.000052
-rw-rw---- 1 mysql mysql 32M Jan 27 2012 ./lib/mysql/mysql-bin.000068
-rw-rw---- 1 mysql mysql 13M Jan 28 2012 ./lib/mysql/mysql-bin.000083
-rw-rw---- 1 mysql mysql 1.1G Mar 2 2012 ./lib/mysql/mysql-bin.000085
-rw-rw---- 1 mysql mysql 1.1G Apr 14 22:52 ./lib/mysql/mysql-bin.000086
-rw-rw---- 1 mysql mysql 1.1G May 18 17:20 ./lib/mysql/mysql-bin.000087
-rw-rw---- 1 mysql mysql 1.1G Jul 19 20:53 ./lib/mysql/mysql-bin.000088
-rw-rw---- 1 mysql mysql 1.1G Sep 5 11:01 ./lib/mysql/mysql-bin.000089
-rw-rw---- 1 mysql mysql 247M Sep 18 00:08 ./lib/mysql/mysql-bin.000090

 

[boldilein]

Hallo nochmal, hab was gefunden (google), mein Problem ist das /var vollgelaufen ist, meine Frage kann ich mittels unterer Anleitung bedenkenlos diese mysql-bin files löschen?

1. Als Administrator am MySQL-Server anmelden (z.B. “mysql -h localhost -u root -p“).
 

SQL-Kommando “FLUSH LOGS;” ausführen, um eine neue “mysql-bin.0000xy“-Datei anzulegen.
 

Mittels “dir -t /var/lib/mysql/mysql-bin.*” prüfen, welche der “mysql-bin.0000xy”-Dateien die Neueste ist. Das genannte Verzeichnis kann je nach Installation abweichen. Dateiname merken, er wird für den nächsten Schritt benötigt.
 

SQL-Kommando “PURGE MASTER LOGS TO ‘mysql-bin.0000xy’;” ausführen. Statt “xy” natürlich die Nummer der neuesten Datei verwenden und auf die Hochkommata achten.
 

Mittels SQL-Kommando “quit” die SQL-Sitzung beenden.

 

[panamajo]

Hallo nochmal, hab was gefunden (google), mein Problem ist das /var vollgelaufen ist, meine Frage kann ich mittels unterer Anleitung bedenkenlos diese mysql-bin files löschen?

Ja. Falls du keine Replikation benötigst kannst du das Erstellen der Dateien durch auskommentieren der log-bin Direktive in der MySQL Konfiguration unterbinden.

 

[tomm.fa]

So nebenbei:
Datei- und Konsolenausgaben.
Dateianhänge.

 

[spoensche]

Hallo nochmal, hab was gefunden (google), mein Problem ist das /var vollgelaufen ist, meine Frage kann ich mittels unterer Anleitung bedenkenlos diese mysql-bin files löschen?

Ja. Falls du keine Replikation benötigst kannst du das Erstellen der Dateien durch auskommentieren der log-bin Direktive in der MySQL Konfiguration unterbinden.

Das ist so nicht ganz korrekt. Die Binlogs können für einen Hotrestore und auch als differentielles Backup verwendet werden, wenn man sie den weg kopiert.

Die maximale Größe und die Vorhaltezeit der Binlogs kann man in der Konfig festlegen.

@boldilein:
Du solltest die Binlogs vorerst nur auf ein anderes Medium verschieben und nicht löschen. Evtl. brauchst du sie noch für den Restore, falls es deine Datenbanken total zerlegt hat und du mit dem neu anlegen der Datenbanken und dem Restore der Binlogs schneller wieder Online bist als mit der Reperatur der Tabellen + Restore.