Help: Backup mysql problem

[mach]

thank you for the time and info.

I have a ticket into them with this info , I think I have a basic idea of what might be happening. they insist I should use the path

/usr/bib/mysqldump

I'll see what they say,

thanks

[DrByte]

lol ... they're right ... you "should" use that path.
It would seem that the command-line environment they're offering you doesn't allow that.

However, try this for kicks...

1. open the backup_mysql screen
2. click on Backup
3. edit the URL and add this to the end of it:

&debug=ON

...and press Enter
4. now click the backup button on the sidebox

Post the debug info from the top of the screen here.... without your passwords of course.

[mach]

Checking Path: /usr/bin/



COMMAND FILES SELECTED:
mysqlexe="/usr/bin/mysql"

mysqldumpexe="/usr/bin/mysqldump"


COMMAND: "/usr/bin/mysqldump" "--host=localhost" "--user=xuserx" "--password=xpwdx" --opt --complete-insert "--result-file=/home/xxx/public_html/adminxxxxx/backups/db_xdbx-20060904201447.sql" xdbx 2>&1
Result code: 127
valueA:
valueB:
ERROR: Could not locate the MYSQLDUMP backup utility. BACKUP FAILED.

[DrByte]

Okay ... the tool is attempting to run the binary from the prescribed location, but the PHP security settings for chroot are preventing it from happening as required.

It's all up to your host now ...

[mach]

Okay ... the tool is attempting to run the binary from the prescribed location, but the PHP security settings for chroot are preventing it from happening as required.

It's all up to your host now ...

Thank you very much! Now I know what to show them and tell them.

[mach]

maybe they are working on it, because now I get this:



PHP-Disabled-functions: ini_alter,system,passthru,shell_exec,leak,listen,chgrp,apache_setenv,define_sysl og_variables,openlog,syslog,ftp_exec

[DrByte]

If that message is being displayed by the backup_mysql, note that sometimes it's a misnomer ... there's a tiny error in the logic that displays the message, in that it doesn't always detect only what it's supposed to.

You're only concerned if "exec" is disabled. "shell_exec" is not used by this script, so is not a problem. Thus, if "exec" itself is not listed, you should be able to run it (assuming the host has fixed everything else properly too)

[mach]

well, they haven't fixed anything yet. they say they need a way to execute the scripts to produce the error on their end. I am relunctant to give them an admin user name and password, but maybe I should. It's not that I don't trust them.....but my customers details are in there.

[DrByte]

you could set up a demo site for them, with the backup addon installed ...

[mach]

Dr. Byte,

I can't thank you enough! Because of you I sounded like I almost knew what i was talking about and they didn't just blame it on a third party script and looked into it and fixed it.

Thank you. They haven't told me what the problem was though, I asked, and I bet they installed the exec_dir patch on php to chroot requests to binaries and didn't have the permissions set right, like you said.
Thats what i told them i thought the problem was anyway.

Thanks a bunch!