MySQL Bugs: #11436: Backup cron job set properly and kicks off, but no backup file created.

Bug #11436	Backup cron job set properly and kicks off, but no backup file created.
Submitted:	19 Jun 2005 19:40	Modified:	28 Jun 2005 12:35
Reporter:	Trevor Jacques	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Administrator	Severity:	S1 (Critical)
Version:	1.0.22	OS:	MacOS (Mac OS X 10.4.1)
Assigned to:		CPU Architecture:	Any

Description:
MySQL Administrator creates the cron job and the ACtivity monitor notes a short spike in crom activity at the time the job is supposed to start, butno backup file is created. Could not find any crash log, or other problem og with details. 

The cron tab file had this added by MySQL Administrator:

# added automatically by MySQL Administrator - do not edit Daily Backup
26 13 * * * "/Applications/MySQL Administrator.app/Contents/Resources/mabackup" --directory="" --connection="My Intake" Daily Backup

This addition to the file seems to be fine, which is likely why the cron job starts on time, but I can't determine why the job does not produce a backup. 

How to repeat:
Define a backup job for a connection set it to execute daily at a particular time. Wait for that time to pass.

duplicate of http://bugs.mysql.com/bug.php?id=11545

>Aleksey Kishkin wrote: duplicate of http://bugs.mysql.com/bug.php?id=11545

But my problem is on Mac, whereas 11545 is on Linux. It would seem that the problem is on both platforms in slightly different ways.