Closed (works as designed)
Project:
backup
Version:
5.x-2.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Reporter:
Created:
21 May 2007 at 17:36 UTC
Updated:
11 Oct 2007 at 14:58 UTC
System program "mysqldump" not found in $PATH. Please check with your sysadmin for further assistance.
Debugging Information
Click to run phpinfo()
System Path
C: \WINDOWS\system32;C: \WINDOWS;C: \WINDOWS\System32\Wbem;C: \Program Files\Common Files\Adobe\AGL;C: \Program Files\QuickTime\QTSystem\;C: \www\openssl\bin;C: \www\Apache22\bin;C: \www\php5;C: \www\mysql5\bin;C: \www\perl\binPrograms that will be used
mysqldump program NOT found or executable
tar program NOT found or executable
gzip program NOT found or executable
Comments
Comment #1
dmuth commentedThe programs that backup says it cannot find (mysqldump, tar, and gzip) are not on Windows systems by default.
I'm not a Windows guy, so I do not know offhand where to find those programs. You might want to try Googling for "gzip windows", "tar windows", and "mysql windows". Sorry I couldn't be of more help.
-- Doug
Comment #2
WorldFallz commentedThere's got to be more going on here... I'm not on a hosted environment, but in an intranet and i am admin on the WAMP box that is running my drupal. I've got all three programs (sqldump, gzip, & tar) for windows loaded in a directory that is listed in the PATH listing on the backup page. So the backup module is getting the PATH right-- it's just not seeing the programs.
I can access and run them fine from a command line in any directory-- so I know they are accessible to the system and work fine. There has to be something *ix specific in the search for these programs that is breaking on windows boxes. I'm still pretty new to drupal, but I'll take a look at the code and see if I can spot the problem. But it's definitely a bug somewhere-- not a design issue.
Comment #3
jspayne commentedWorldFallz is correct - this is a windows issue. The problem is that the module is looking for the *nix executable, which does not have an extension. If you edit the array in backup.module and add ".exe" to the end of each file name, it will get past that check.
I'm having other issues with the backup - the tar command is failing - but I'll have to look into that later.