MySQL Bugs: #11545: MySQl Administrator creates invalid scheduled backup entry.

Bug #11545	MySQl Administrator creates invalid scheduled backup entry.
Submitted:	24 Jun 2005 11:01	Modified:	14 Sep 2005 12:22
Reporter:	Rainer Frey	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Administrator	Severity:	S2 (Serious)
Version:	1.0.22a-1.rh9 RPM	OS:	Linux (Linux)
Assigned to:	Vladimir Kolesnikov	CPU Architecture:	Any

Description:
The scheduled backup entry created by MySQL Administrator doesn't work correctly. 

How to repeat:
I created a backup project named "Inxmail" to use the named connection also called "Inxmail", and scheduled it to run daily. The crontab entry is executed (appears in /var/log/cron), but no backup is created. The crontab entry looks like this:
0 9 * * * /usr/bin/mabackup -d /home/mysql/backup -x inxmail_ -c Inxmail Inxmail

I tried to run this command by hand, and it gave me the error:
missing parameter: --user
I then added the parameters --user, --password, --host, then I got "Cannot load profile". With strace I found out that it tried to open
open("/home/user/Library/Application Support/MySQL/administrator/profiles/-x.mbp", O_RDONLY) = -1 ENOENT (No such file or directory). This is a Mac OS X secific file path, and I used the linux version.

 

Suggested fix:
1. check option parsing of mabackup. When a connection profile is given, username, password and host should not be necessary.

2. In mabackup.cc function main, there is a hardcoded Mac OS X path for profiles, and a Unix path is commented out. Use correct path to build linux RPM

tested on slackware. besides it creates crontab entry in my test
0 0 * * * bin/mabackup (etc etc)

obviuosly  crontab will not be able to find bin/mabackup

I have a very similar problem on Mac OS X. It would seem that the problem is on both platforms in slightly different ways.

Sorry. Forgot to link to my problem http://bugs.mysql.com/bug.php?id=11436

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

I recieved the same "Cannot load profile" erro after running a backup created using MySQL Administrator on Mac OS Server 10.4.6. 

I was able to solve this by removing spaces from the "Project Name" in MySQL Administrator.

I had the same problem using v1.2.12 on Debian.

The .mysqlgui dir was located in /home/<myUsername>/  but mabackup tried to access it in /root/ directory.

You can use 
ln -s /home/<myUsername>/.mysqlgui /root/.mysqlgui 
until the next release fixes this bug.