stable

holland-1.0.12-4.el6

FEDORA-EPEL-2016-f9db8b22de created by carlgeorge 7 years ago for Fedora EPEL 6

This update has been submitted for testing by carlgeorge.

7 years ago

This update has been pushed to testing.

7 years ago
User Icon troyengel commented & provided feedback 7 years ago
karma

I have updated CentOS 6 and CentOS 7 servers, the standard functionality for mysqldump is working as expected. I'm unable to test the exact use case this fix is intended for on these servers, however do confirm basic functionality has not broken.

User Icon mgriffin commented & provided feedback 7 years ago
karma

I just deployed 1.0.12-4 to a production box where 1.0.12 was failing with "unknown encoding". This resolved the issue.

User Icon tonyskapunk commented & provided feedback 7 years ago
karma

Tested successfully:

# holland bk 
Holland 1.0.12 started with pid 5109
--- Starting backup run ---
Creating backup path /var/spool/holland/mysqldump-lvm/20160303_162649
Estimating size of mysqldump backup
Estimated Backup Size: 675.86KB
Starting backup[mysqldump-lvm/20160303_162649] via plugin mysqldump-lvm
Backing up /var/lib/mysql via snapshot
Auto-sizing snapshot-size to 1.28GB (327 extents)
Acquiring read-lock and flushing tables
This MySQL server does not have binary logs enabled. Nothing to record from SHOW MASTER STATUS.
Removing temporary mountpoint /tmp/tmpv7SROL
unknown encoding: binary
Backup failed after 0.19 seconds
Purged failed backup: mysqldump-lvm/20160303_162649
Backup failed: Error occurred during snapshot process. Aborting.
Released lock /etc/holland/backupsets/mysqldump-lvm.conf
--- Ending backup run ---

After the update:

# holland bk
Holland 1.0.12 started with pid 10777
--- Starting backup run ---
Creating backup path /var/spool/holland/mysqldump-lvm/20160303_162921
Estimating size of mysqldump backup
Estimated Backup Size: 675.86KB
Starting backup[mysqldump-lvm/20160303_162921] via plugin mysqldump-lvm
Backing up /var/lib/mysql via snapshot
Auto-sizing snapshot-size to 1.28GB (327 extents)
Acquiring read-lock and flushing tables
This MySQL server does not have binary logs enabled. Nothing to record from SHOW MASTER STATUS.
Recorded slave replication status: master_binlog = mysql-bin.000002 master_position = 2856
Created snapshot volume /dev/vg0/root_snapshot
Releasing read-lock
Mounted /dev/vg0/root_snapshot on /tmp/tmpVX0gQO
Handing-off to mysqldump plugin
Starting /usr/libexec/mysqld --defaults-file=/tmp/tmpVX0gQO/var/lib/mysql/my.bootstrap.cnf
Waiting for /usr/libexec/mysqld to start
/usr/libexec/mysqld accepting connections on unix socket /tmp/tmpVX0gQO/var/lib/mysql/holland_mysqldump.sock
Using mysqldump executable: /usr/bin/mysqldump
mysqldump version 10.0.23
Using mysqldump option --flush-privileges
Using mysqldump option --max-allowed-packet=128M
Using gzip compression level 1 with args 
Wrote backup manifest /var/spool/holland/mysqldump-lvm/20160303_162921/backup_data/MANIFEST.txt
Executing: /usr/bin/mysqldump --defaults-file=/var/spool/holland/mysqldump-lvm/20160303_162921/my.cnf --flush-privileges --max-allowed-packet=128M --lock-tables mysql
Executing: /usr/bin/mysqldump --defaults-file=/var/spool/holland/mysqldump-lvm/20160303_162921/my.cnf --flush-privileges --max-allowed-packet=128M --lock-tables test
Executing: /usr/bin/mysqldump --defaults-file=/var/spool/holland/mysqldump-lvm/20160303_162921/my.cnf --flush-privileges --max-allowed-packet=128M --lock-tables testing
Stopping /usr/libexec/mysqld
Waiting for MySQL to stop
/usr/libexec/mysqld stopped
Unmounted /dev/vg0/root_snapshot
Final LVM snapshot size for /dev/vg0/root_snapshot is 1.31MB
Removed snapshot /dev/vg0/root_snapshot
Removing temporary mountpoint /tmp/tmpVX0gQO
Final on-disk backup size 162.33KB
24.02% of estimated size 675.86KB
Backup completed in 4.19 seconds
Purged mysqldump-lvm/20160303_162529
1 backups purged
Released lock /etc/holland/backupsets/mysqldump-lvm.conf
--- Ending backup run ---
User Icon moisesq commented & provided feedback 7 years ago
karma

Tested successfully on CentOS 6 .7. Backup no longer fails after ~6 seconds.

2016-03-01 04:52:26,096 [ERROR] unknown encoding: binary 2016-03-01 04:52:26,096 [ERROR] Backup failed after 6.29 seconds

carlgeorge edited this update.

7 years ago

ausil edited this update.

7 years ago

lmacken edited this update.

7 years ago

This update has been submitted for stable by bodhi.

7 years ago
User Icon lmacken provided feedback 7 years ago
karma

This update has been pushed to stable.

7 years ago

Please login to add feedback.

Metadata
Type
bugfix
Karma
5
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
3
Stable by Time
disabled
Dates
submitted
7 years ago
in testing
7 years ago
in stable
7 years ago
modified
7 years ago

Automated Test Results