Groesbeek, view of the 'National Liberation Museum 1944-1945' in Groesbeek. © Ton Kersten
Fork me on GitHub
Posts tagged as mysql

MySQL backup error

2012-08-09 (126) by Ton Kersten, tagged as linux, mysql

After upgrading my MySQL database server from version 5.0.95 to 5.1.61 I suddenly got these errors in the backup logging.

mysqldump: Couldn't execute 'SELECT /*!40001 SQL_NO_CACHE */ * FROM `EVENTS`': Cannot
proceed because system tables used by Event Scheduler were found damaged at server start
(1577)
dbdump gave errorcode 2 for database 'information_schema'
2012-08-09 09:07:53 -> Finished MySQL backup on host 'xxx.tonkersten.com'

Hmm, no idea what has happened. I hope I didn't do something stupid.

Asking Google I found out that the information_schema tables where changed during the upgrade and that I could recreate the error with:

mysql> use information_schema
Database changed

mysql> SELECT /*!40001 SQL_NO_CACHE */ * FROM EVENTS;
ERROR 1577 (HY000): Cannot proceed because system tables used by Event Scheduler were found damaged at server start
mysql> Bye

So I tried to repair the error with:

mysql_upgrade -u root -h localhost -p --verbose

but still the same error.

Turns out that the MySQL server needs to be restarted for this to work.

Now I get

mysql> use information_schema
Database changed

mysql> SELECT /*!40001 SQL_NO_CACHE */ * FROM EVENTS;
Empty set (0.00 sec)
mysql> Bye

MySQL database replication

2012-01-20 (110) by Ton Kersten, tagged as mysql

This week I was asked to setup a system with a single MySQL master server and a couple of slave servers. I have done that before, so there is no problem. The problem is that I do not do that on a daily basis, so I need to check the commands every time I set it up. So, as a note to myself I describe how to setup a single MySQL master with multiple slaves.

MySQL master with multiple slaves

Read more »

New MySQL backup

2010-12-03 (80) by Ton Kersten, tagged as mysql

I was playing around and configuring the MySQL backup on a customers database server and I ran into little problems. One of the defaults was not parsed correctly and a configuration setting made things run amok.

So I decided to streamline things and create some extra program options to set and show the default settings and the settings after the configuration file.

The help now shows:

mysqlbackup version 1.50
Syntax: mysqlbackup [ -h|-v|-s|-c|-d|]
    -h           Display this help and exit
    -v           Display the version number and exit
    -s           Show the defaults and their values
    -d           Show a description of the defaults and their values
    -c           Show a default configuration file
    -a           Show settings after the config file is processed
    configfile   Use this file as the configuration file
                 instead of the default.
                 Default: /usr/local/bin/mysqlbackup.conf

Come and g[ei]t it. It's in the download section or on GitHub.

Read more »

Bugfix in Mysqlbackup

2010-10-14 (74) by Ton Kersten, tagged as mysql

Harry Sappe reported a bug in Mysqlbackup.

When only dumping one database the program gives an "unbound variable".

I repaired id an a new version is now online. It's in the Files section or on Github.

New MySQL backup

2010-07-26 (59) by Ton Kersten, tagged as mysql

It's been a while, but now there is a new version of the MySQLBackup script.

This version (1.42) has a few enhancements and some configuration options were added.

The main new feature is that it now supports multiple dumps per day and database checks. The old backups will be removed, of course, but only when they are over a day old.

An added configuration option is that it's now possible to choose whether you want the databases locked during the backup.

If you want to use it, go ahead, but make sure you have a look at the new config file as well.

Have fun with it. It's in the Download section.

New MySQLBackup

2010-07-21 (57) by Ton Kersten, tagged as mysql

It's been a while, but now there is a new version of the MySQLBackup script.

This version (1.42) has a few enhancements and some configuration options were added.

The main new feature is that it now supports multiple dumps per day and database checks. The old backups will be removed, of course, but only when they are over a day old.

An added configuration option is that it's now possible to choose whether you want the databases locked during the backup.

Have fun with it. It's in the Downloads section.