First, I'd create a DB Backups storage group (actually, I'd create the
Storage Directory before that.) You can put the directory anywhere
you've got space, but make sure both your own user and the mythtv
user have write permission. That will get rid of the initial errors.
Next, /opt/local/share/mythtv/mythconverg_backup.pl is probably failing
for the reason Craig mentioned above. If the backend's PATH has the
/opt..... directory that the SQL files live in, then I'd be interested in changing
mythconverg_backup.pl around line 49 (for @d_allowed_paths) to see if
adding the proper /opt... directory there helps.
And, 127 is a normal return for a non-existent command firing on the last attempt to
backup the DB. But you can run it from the command line to prove that's what's
happening. Just replace the --defaults-extra-file='/tmp/mythtv_db_backup_conf_rrgylj'
part with -p so you'll get prompted for the mythtv password.
Code: Select all
mysqldump --host='localhost' --port='3306' --user='mythtv' -p --add-drop-table --add-locks --allow-keywords --complete-insert --extended-insert --lock-tables --no-create-db --quick 'mythconverg' > /tmp/just_testing.sql
To answer your last question, it's normal for a file to be created, when
output is redirected. True if the command doesn't even exist or if it's
not in your PATH.