| Bug #29088 | mysqldump renders mysqld unusable on windows when ran with --master-data | ||
|---|---|---|---|
| Submitted: | 13 Jun 2007 20:15 | Modified: | 12 Jul 2007 0:45 |
| Reporter: | Tobias Asplund | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server: Backup | Severity: | S1 (Critical) |
| Version: | 5.1.17/5.1.19 | OS: | Windows |
| Assigned to: | CPU Architecture: | Any | |
[18 Jun 2007 13:55]
MySQL Verification Team
Thank you for the bug report. Could you please provide your my.ini file I was not able to repeat with a source server built 5 days ago. /*!40101 SET SQL_MODE=@OLD_SQL_MODE */; /*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */; /*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */; /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */; /*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */; -- Dump completed on 2007-06-18 13:40:19
[18 Jun 2007 21:59]
Tobias Asplund
I don't have access to that machine anymore, but aside from a normal default installer-generated my.ini I think that those options were enabled: log-bin log log-slow-queries log-output=FILE
[28 Jun 2007 10:03]
Sveta Smirnova
Thank you for the report. Verified as described with version 5.1.19 Option log is cause.
[12 Jul 2007 0:45]
Damien Katz
Most likely fixed. I was able to reproduce in 5.19, but I cannot repeat in 5.1.20+.
Description: when mysqldump runs with --master-data on windows, it somehow makes the server block any other action and new connections afterwards. How to repeat: C:\mysql_logs>net start mysql The MySQL service is starting. The MySQL service was started successfully. C:\>mysqldump --all-databases --master-data -u root -p --flush-logs Enter password: **** -- MySQL dump 10.12 -- -- Host: localhost Database: -- ------------------------------------------------------ -- Server version 5.1.17-beta-community-nt-debug-log /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; /*!40101 SET NAMES utf8 */; /*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */; /*!40103 SET TIME_ZONE='+00:00' */; /*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */; /*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_ CHECKS=0 */; /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; /*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */; ----------------------------------------------------------------------- Hangs here indefinitely ----------------------------------------------------------------------- Checking general log in another session: 070613 13:11:49 1 Connect root@localhost on 1 Query /*!40100 SET @@SQL_MODE='' */ 1 Query /*!40103 SET TIME_ZONE='+00:00' */ 1 Query FLUSH TABLES 1 Query FLUSH TABLES WITH READ LOCK 1 Refresh C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld-nt, Version: 5.1.17- beta-community-nt-debug-log (MySQL Community Server (GPL)). started wit h: TCP Port: 3306, Named Pipe: MySQL Time Id Command Argument