Killall mysql service cannot be started after mysql Service

Source: Internet
Author: User

Can "t init tc log Aborting | mysql transaction log causes startup failure. After the killall mysql process, mysql cannot be started;

Question 1:

After kill all mysql processes, restart and fail to start. The following error occurs:

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] cocould 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 the mysql-bin.000041 file, delete, restart, still not good, 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] cocould not open log file

110303 14:04:07 [ERROR] Can't init tc log

110303 14:04:07 [ERROR] Aborting

Touch, modify the permission, restart, or fail. An error is returned (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

Solution:

Remove the mysql/data/mysql-bin.index file, restart mysql, a new mysql-bin.index file is automatically generated, started successfully

Question 2:

After startup, an error is reported:

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 to free space... (Keep CT up to 60 secs delay for server to continue after freeing disk space)

This is because there are too many mysql-bin logs. log on to the mysql/data/directory, delete all mysql-bin. * files, restart, and start successfully.

Question 3:

After startup, an error is reported:

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 you already have another mysqld server running on port: 43306?

110303 14:21:37 [ERROR] Aborting

According to the prompts, port 43306 should be occupied, but it is not found that the port is occupied after viewing, do not go deep, and decisively change it my. the port in the cnf file is changed to a new port, restarted, and started successfully. After it is disabled, change the port in my. cnf back to 43306, restart, and start again.

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.