Killall MySQL service MySQL service does not start

Can "T init TC Log Aborting | MySQL transaction log causes startup failure problem, killall MySQL process, MySQL failed to start the problem center;

Question 1:

After the MySQL all process kill, reboot, unable to start, error:

110303 14:01:45 innodb:started; Log sequence number 0 138710263

/usr/local/mysql/bin/mysqld:file './mysql-bin.000041′not found (errcode:13)

110303 14:01:45 [ERROR] Failed to open log (file './mysql-bin.000041′, errno 13)

110303 14:01:45 [ERROR] could not open log file

110303 14:01:45 [ERROR] Can ' t init TC Log

110303 14:01:45 [ERROR] Aborting

In the mysql/data/directory to find mysql-bin.000041 files, delete, restart, still not, error:

110303 14:04:07 innodb:started; Log sequence number 0 138710263

/usr/local/mysql/bin/mysqld:file './mysql-bin.000041′not found (errcode:2)

110303 14:04:07 [ERROR] Failed to open log (file './mysql-bin.000041′, errno 2)

110303 14:04:07 [ERROR] could not open log file

110303 14:04:07 [ERROR] Can ' t init TC Log

110303 14:04:07 [ERROR] Aborting

Touch, modify permissions, restart, no, error (www.45it.com):

110303 14:05:41 innodb:started; Log sequence number 0 138710263

110303 14:05:41 [ERROR] I/O ERROR reading the header from the binary log, errno=-1, IO cache code=0

110303 14:05:41 [ERROR] I/O ERROR reading the header from the binary log

110303 14:05:41 [ERROR] Can ' t init TC Log

110303 14:05:41 [ERROR] Aborting

Final Solution:

Delete mysql/data/mysql-bin.index file, restart MySQL, automatically generate new Mysql-bin.index file, start successful

Question 2:

After startup, error:

innodb:started; Log sequence number 0 1004308157

110303 14:15:01 [note] recovering after a crash using Mysql-bin

110303 14:15:01 [ERROR] Error in log_event::read_log_event (): ' Read ERROR ', data_len:169, Event_type:2

110303 14:15:01 [note] Starting crash recovery ...

110303 14:15:01 [note] Crash recovery finished.

/opt/31306/mysql/bin/mysqld:disk is full writing './mysql-bin.~rec~ ' (errcode:28). Waiting for someone. (Expect up to secs delay for server to continue after freeing disk spaces)

This is due to mysql-bin log too much, into the mysql/data/directory, decisively delete all mysql-bin.* files, reboot, start successful

Question 3:

After startup, error:

110303 14:21:37 innodb:started; Log sequence number 0 487312871

110303 14:21:37 [ERROR] Can ' t start server:bind on TCP/IP port:address already in use

110303 14:21:37 [ERROR] Do your already have another MYSQLD server running on port:43306?

110303 14:21:37 [ERROR] Aborting

According to the prompt, should be 43306 port occupancy, but did not find that the port is occupied, do not delve into it, decisively will its my.cnf file in the port modified into a new ports, restart, start successfully. After the shutdown, reset the port in the MY.CNF to 43306, restart it, and it will start again successfully.