Re: error 134 cause mysql to run out connections
Is this server a replication master? If it isn't then the warning is not an issue for you.
If it is a replication master, then replication will break if you rename the host.
The binlog files are named with the host name as default. The replication slave is looking for a binlog file with the host name. If you rename the host, the binlog file name will change and the slave won't find it.
To avoid this, you specify a name for the binlog file in the startup command line.
But, if this isn't a replication master, then it is not an issue for you.
If your tables are getting corrupted again straight after repairing them, then maybe you have a hardware problem with your server.
Good luck,
Barry.
Subject
Written By
Posted
Re: error 134 cause mysql to run out connections
October 28, 2009 04:00PM
Sorry, you can't reply to this topic. It has been closed.
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.