enterprise-support team mailing list archive

[Scott Gamble <scottgamble@xxxxxxxxxxx>]

Public bug reported:

This may fall under the category of just don't do that but I thought I would report it just in case as it caught me by surprise.
Obvious easy work around for me is to create the directory ahead of time or write the log to a directory that already exists.

If the output directory does not exist when mydumper is executed it is
created. However I was trying to write the log to the same directory as
the backup was in and that failed immediately.

ls -l /home/mysql/backup_test
ls: cannot access /home/mysql/backup_test: No such file or directory

mydumper -o /home/mysql/backup_test -u xxxx -p ppppp -L /home/mysql/backup_test/backup.log
** (mydumper:11322): CRITICAL **:: Could not open log file '/home/mysql/backup_test/backup.log' for writing: 2

Remove the -L (path) and it works perfectly.  The log is just written
ahead of the directory which again may be something not worth fixing
since there is an obvious and easy work around. The only reason I was
trying to do that is we are going to date/timestamp the directory name
and I was thinking of putting the log output for that backup in the same
directory and since mydumper creates the output directory I figured it
would work.

** Affects: mydumper
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to MySQL.
Matching subscriptions: Ubuntu Server/Client Support Team
https://bugs.launchpad.net/bugs/1269464

Title:
  Writing to log file fails if output directory does not exist

To manage notifications about this bug go to:
https://bugs.launchpad.net/mydumper/+bug/1269464/+subscriptions