MySQL Forums
Forum List  »  MySQL Administrator

Advanced Search
New Topic

Re: error 134 cause mysql to run out connections
Posted by: Barry Galbraith
Date: October 27, 2009 03:22PM

running perror 134 shows

MySQL error code 134: Record was already deleted (or record file crashed)

Is your application trying to read deleted records?

Can you repair the table with mysqlcheck?

>mysqlcheck <dbname> <table>

The warning about the binary log file is only an issue if you have a replication slave running of this server as master, and you rename the host this master is running on.

Good luck,
Barry.

Navigate: Previous Message• Next Message
Options: Reply• Quote


Subject
Written By
Posted
error 134 cause mysql to run out connections
khalid touati
October 27, 2009 11:50AM
Re: error 134 cause mysql to run out connections
Barry Galbraith
October 27, 2009 03:22PM
Re: error 134 cause mysql to run out connections
khalid touati
October 28, 2009 08:17AM
Re: error 134 cause mysql to run out connections
khalid touati
October 28, 2009 11:49AM
Re: error 134 cause mysql to run out connections
Barry Galbraith
October 28, 2009 04:00PM
Re: error 134 cause mysql to run out connections
khalid touati
October 28, 2009 06:30PM


Sorry, you can't reply to this topic. It has been closed.
This forum is currently read only. You can not log in or make any changes. This is a temporary situation.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.