MySQL 4.0.18, Tru64 5.1B
The log partition filled up on one of our instances. RESET MASTER fails with:
ERROR 1186: Binlog closed, cannot RESET MASTER
I deleted some older logs by hand, but RESET MASTER still fails.
FLUSH LOGS appears to succeed, but no binary logs are being written, and RESET MASTER still fails.
I have one comment and one question about this:
Question: Is there any way out of this rather than restarting the server?
Comment: Data-modifying queries are still continuing successfully. This worries me. Without binary logs, and with data updates continuing, we don't have a way to restore the instance should the hardware fail. And if there were a replication slave running against this instance, it presumably would by now be far out of date, with no way of updating it without a complete resynchronisation from scratch.
Surely if the binary update log can't be written, inserts and updates should either block, or fail completely?
Or am I missing something?
Many thanks,
Tim
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
