Holland is attempting to backup performance_schema
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
holland-backup |
Fix Released
|
High
|
Andrew Garner |
Bug Description
Holland appears to be trying to backup performance_schema on our test box:
2010-10-24 17:22:47,579 [INFO] --- Starting backup run ---
2010-10-24 17:22:47,587 [INFO] Acquired lock /etc/holland/
2010-10-24 17:22:47,696 [INFO] Creating backup path /var/spool/
2010-10-24 17:22:47,697 [INFO] Estimating size of mysqldump backup
2010-10-24 17:22:47,753 [WARNING] The user specified as a definer ('foo'@
2010-10-24 17:22:47,754 [INFO] Estimated Backup Size: 2.29GB
2010-10-24 17:22:47,756 [INFO] Starting backup[
2010-10-24 17:22:47,757 [INFO] Using mysqldump executable: /usr/bin/mysqldump
2010-10-24 17:22:47,767 [INFO] mysqldump version 5.5.6
2010-10-24 17:22:47,769 [INFO] Using /bin/gzip compression level 1
2010-10-24 17:22:47,770 [INFO] Wrote backup manifest /var/spool/
2010-10-24 17:22:47,777 [INFO] Executing: /usr/bin/mysqldump --defaults-
2010-10-24 17:22:52,754 [INFO] Executing: /usr/bin/mysqldump --defaults-
2010-10-24 17:22:52,944 [INFO] Executing: /usr/bin/mysqldump --defaults-
2010-10-24 17:22:52,990 [ERROR] /usr/bin/
2010-10-24 17:22:52,991 [ERROR] Backup failed after 5.30 seconds
2010-10-24 17:22:53,026 [INFO] Purged failed backup: default/
2010-10-24 17:22:53,026 [ERROR] Backup failed: mysqldump exited with non-zero status 2
2010-10-24 17:22:53,026 [INFO] Released lock /etc/holland/
I resolved the issue by manually skipping performance_schema from the backup, though I suspect we will want to account for this in Holland, perhaps by checking to see if the version of MySQL is 5.5 or later and to auto-filter it.
Changed in holland-backup: | |
status: | Fix Committed → Fix Released |
Fix committed to master here:
https:/ /github. com/holland- backup/ holland/ commit/ a8f6f5d67c2d99f 1d75f6448d81c3a 4e7ccd1e85