MySQL Backup Failing after MySQL Update

I updated the MySQL a few days ago to the latest version through the auto updates. Since then, my daily backup throws this error:

Backing up mysql to /media/backupusb/mysql/mysql.sql .. .. backup failed : -- Warning: Skipping the data of table mysql.event. Specify the --events option explicitly.

The rest of the databases update fine. I'm just having problems with this database. I could not find any option that would allow me to "Specify the --events option" as indicated in the error.

Below is the log from the update.

Any thoughts?

Thanks

Phil

Now updating mysql-server ..

Installing package(s) with command apt-get -y install mysql-server ..

Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be upgraded:
  mysql-server
1 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
Need to get 71.4kB of archives.
After this operation, 4096B of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main mysql-server 5.1.69-0ubuntu0.10.04.1 [71.4kB]
Fetched 71.4kB in 0s (252kB/s)
(Reading database ... 128322 files and directories currently installed.)
Preparing to replace mysql-server 5.1.67-0ubuntu0.10.04.1 (using .../mysql-server_5.1.69-0ubuntu0.10.04.1_all.deb) ...
Unpacking replacement mysql-server ...
Setting up mysql-server (5.1.69-0ubuntu0.10.04.1) ...

.. install complete.

Now updating mysql-server-5.1 ..

Installing package(s) with command apt-get -y install mysql-server-5.1 ..

Reading package lists...
Building dependency tree...
Reading state information...
The following extra packages will be installed:
  libmysqlclient16 mysql-client-5.1 mysql-client-core-5.1 mysql-common
  mysql-server-core-5.1
Suggested packages:
  tinyca mailx
The following packages will be upgraded:
  libmysqlclient16 mysql-client-5.1 mysql-client-core-5.1 mysql-common
  mysql-server-5.1 mysql-server-core-5.1
6 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 22.1MB of archives.
After this operation, 283kB of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main mysql-common 5.1.69-0ubuntu0.10.04.1 [75.8kB]
Get:2 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main libmysqlclient16 5.1.69-0ubuntu0.10.04.1 [1905kB]
Get:3 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main mysql-client-core-5.1 5.1.69-0ubuntu0.10.04.1 [159kB]
Get:4 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main mysql-client-5.1 5.1.69-0ubuntu0.10.04.1 [8190kB]
Get:5 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main mysql-server-core-5.1 5.1.69-0ubuntu0.10.04.1 [4749kB]
Get:6 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main mysql-server-5.1 5.1.69-0ubuntu0.10.04.1 [7048kB]
Preconfiguring packages ...
Fetched 22.1MB in 34s (642kB/s)
(Reading database ... 128322 files and directories currently installed.)
Preparing to replace mysql-common 5.1.67-0ubuntu0.10.04.1 (using .../mysql-common_5.1.69-0ubuntu0.10.04.1_all.deb) ...
Unpacking replacement mysql-common ...
Preparing to replace libmysqlclient16 5.1.67-0ubuntu0.10.04.1 (using .../libmysqlclient16_5.1.69-0ubuntu0.10.04.1_i386.deb) ...
Unpacking replacement libmysqlclient16 ...
Preparing to replace mysql-client-core-5.1 5.1.67-0ubuntu0.10.04.1 (using .../mysql-client-core-5.1_5.1.69-0ubuntu0.10.04.1_i386.deb) ...
Unpacking replacement mysql-client-core-5.1 ...
Preparing to replace mysql-client-5.1 5.1.67-0ubuntu0.10.04.1 (using .../mysql-client-5.1_5.1.69-0ubuntu0.10.04.1_i386.deb) ...
Unpacking replacement mysql-client-5.1 ...
Preparing to replace mysql-server-core-5.1 5.1.67-0ubuntu0.10.04.1 (using .../mysql-server-core-5.1_5.1.69-0ubuntu0.10.04.1_i386.deb) ...
Unpacking replacement mysql-server-core-5.1 ...
Processing triggers for man-db ...
Setting up mysql-common (5.1.69-0ubuntu0.10.04.1) ...
(Reading database ... 128322 files and directories currently installed.)
Preparing to replace mysql-server-5.1 5.1.67-0ubuntu0.10.04.1 (using .../mysql-server-5.1_5.1.69-0ubuntu0.10.04.1_i386.deb) ...
mysql stop/waiting
Unpacking replacement mysql-server-5.1 ...
Processing triggers for man-db ...
Processing triggers for ureadahead ...
ureadahead will be reprofiled on next reboot
Setting up libmysqlclient16 (5.1.69-0ubuntu0.10.04.1) ...

Setting up mysql-client-core-5.1 (5.1.69-0ubuntu0.10.04.1) ...
Setting up mysql-client-5.1 (5.1.69-0ubuntu0.10.04.1) ...
Setting up mysql-server-core-5.1 (5.1.69-0ubuntu0.10.04.1) ...
Setting up mysql-server-5.1 (5.1.69-0ubuntu0.10.04.1) ...
mysql start/running, process 32071

Processing triggers for libc-bin ...
ldconfig deferred processing now taking place

.. install complete.
Status: 
Active

Comments

Jamie, this problem sounds like a change in mysqldump behavior.

The mysqldump notice doesn't imply a failure, but was added because MySQL users were confused with mysqldump not dumping the mysql.event table by default.

What would you think about adding the --events switch to mysqldump for MySQL versions 5.1.8 and after (5.1.8 is when MySQL first supported events)?

That will cause it to backup the events table, and then I believe that message would go away.

There's a MySQL bug report on that issue here:

http://bugs.mysql.com/bug.php?id=68376

That's a good idea - in the next Webmin release I will have it add that --events flag.

Automatically closed -- issue fixed for 2 weeks with no activity.

tpnsolutions's picture
Submitted by tpnsolutions on Sun, 05/12/2013 - 21:30

Jamie,

This issue still persists...

-- Warning: Skipping the data of table mysql.event. Specify the --events option explicitly.

I keep getting this message in my backup reports causing all backup emails at first glance to appear like they failed...

Any news on addressing this matter?

-Peter

tpnsolutions's picture
Submitted by tpnsolutions on Sun, 05/12/2013 - 21:31

Jamie,

This issue still persists...

-- Warning: Skipping the data of table mysql.event. Specify the --events option explicitly.

I keep getting this message in my backup reports causing all backup emails at first glance to appear like they failed...

Any news on addressing this matter?

-Peter

We haven't release the new Webmin version to Virtualmin customers yet - it will be coming soon though.