Database Backup Manager or GoDaddy Problem?

[skydealer]

Thanks.

Plugin was just installed into admin dir via CuteFTP.

Backup dir CHMOD to 777 (defaulted).

Results:
Result code 127
ERROR: Could not locate the MYSQLDUMP backup utility. BACKUP FAILED.

(PHP safe mode was on)





I went into Plesk and turned off PHP safe mode and I was able to do a proper dump. The SQL file opened nice in wordpad and I was able to mod things and then upload it. I changed a manufacturer name and then uploaded it & it updated the database fine!

I'm kind of paranoid about operating a site with php safemode disabled though. I hunt down spam kings and they tend to attack my sites every now and then, so I use ScanAlert to monitor my IPs and they freak out on the safe mode being turned off.

Nice mod! It took about 5 seconds to install. This may actually prove to be an easier workaround for me to populate fields in the database.

So it does work on a Godaddy VDS.

That may be an overkill for the original poster though, as GD's virtual dedicated servers are kind of expensive & not needed for the majority of ecommerce requirements. I lease one mainly for the wait_timeout requirements of a forum website.

[DrByte]

Some would say having to run a server in safe mode suggests poor security practices are in place, thus "requiring" safe mode as a catch-all. Definitely needed with systems that don't take security seriously though. Zen Cart will operate with it on or off, but some advanced functions will be crippled with it on. This backup plugin is one example.

Try turning safe mode on again and run the module in debug mode:
- click Backup
- now you have the sidebox that has another Backup button below the checkboxes.
- edit the URL and add &debug=ON to it, and press Enter
- now click Backup in the sidebox
- what new debug info is shown next to the error message ?

[skydealer]

Here's what was displayed when I ran it in debug mode with safemode back on. I edited the post to remove database names and passwords:
Checking Path: /usr/bin/
Checking Path: /usr/bin/mysql/
Checking Path: /usr/bin/
Checking Path: /usr/local/bin/
Checking Path: /usr/local/mysql/bin/
Checking Path: c:/mysql/bin/
Checking Path: d:/mysql/bin/
Checking Path: e:/mysql/bin/
Checking Path: c:/apache2triad/mysql/bin/
Checking Path: d:/apache2triad/mysql/bin/
Checking Path: e:/apache2triad/mysql/bin/
Checking Path: c:/server/mysql/bin/
Checking Path: c:/Program Files/MySQL/MySQL Server 5.0/bin/
Checking Path: d:\Program Files\MySQL\MySQL Server 5.0\bin\
Checking Path: c:/Program Files/MySQL/MySQL Server 4.1/bin/
Checking Path: /

COMMAND FILES SELECTED:
mysqlexe="mysql"
mysqldumpexe="mysqldump"

COMMAND: "mysqldump" "--host=localhost" "--user=**removed by skydealer**" "-- password==**removed by skydealer**" --opt --complete-insert "--result-file=/var/www/vhosts/=**removed by skydealer**.com/httpdocs/admin/backups/db_=**removed by skydealer**-20070831114545.sql" =**removed by skydealer** 2>&1
Result code: 127
valueA: valueB:
ERROR: Could not locate the MYSQLDUMP backup utility.
BACKUP FAILED.


----------------------------------
So it also looks in local directories for a mysqldump utility?

[DrByte]

So it also looks in local directories for a mysqldump utility?

The "local directories" you're referring to are common directories where the files would be found on Windows servers.
It checks all "common" folders to see if it can locate the mysqldump binary/program. If it can't find it, it keeps looking through a list of known common locations.

As per the readme for the contrib, you can hard-code "your" server's proper path in the language file.


Try running the same without safe mode, and see what path it says it finds the binary in.

[skydealer]

OK - here's the results.

Checking Path: /usr/bin/
Checking Path: /usr/bin/mysql/
Checking Path: /usr/bin/
Checking Path: /usr/local/bin/
Checking Path: /usr/local/mysql/bin/
Checking Path: c:/mysql/bin/
Checking Path: d:/mysql/bin/
Checking Path: e:/mysql/bin/
Checking Path: c:/apache2triad/mysql/bin/
Checking Path: d:/apache2triad/mysql/bin/
Checking Path: e:/apache2triad/mysql/bin/
Checking Path: c:/server/mysql/bin/
Checking Path: c:/Program Files/MySQL/MySQL Server 5.0/bin/
Checking Path: d:\Program Files\MySQL\MySQL Server 5.0\bin\
Checking Path: c:/Program Files/MySQL/MySQL Server 4.1/bin/
Checking Path: /

COMMAND FILES SELECTED:
mysqlexe="mysql"

mysqldumpexe="mysqldump"

COMMAND: "mysqldump" "--host=localhost" "--user=**removed by skydealer**n" "--password=**removed by skydealer**" --opt --complete-insert "--result-file=/var/www/vhosts/**removed by skydealer**.com/httpdocs/admin/backups/db_**removed by skydealer**-20070831124441.sql" **removed by skydealer** 2>&1
Result code: 0
valueA:
valueB:
Success: The database has been saved.

-------------------

[DrByte]

Hmm ... 127 means it failed to find the program.
I guess safe-mode is blocking execution of certain files.
Not surprising really.