CMS Made Simple Forums

I use the MySQL dump module extensively for site development and management. All of a sudden on my most recent install it just stopped working...it goes through all the motions of backing up and restoring but nothing really changes. No error messages are displayed but all that's listed under the "output" is: /usr/bin/mysqldump: unrecognized option `--compatible=mysql40'

The MySQL dump module still works in all my prior sites (either GoDaddy or 1and1 shared Linux). But even when I do a new test install of CMSMS and the MySQL Dump Module in a subdirectory of a working site, with a new database, it doesn't work.

After painstakingly trying to eliminate as many possible factors here's the area where I think the issue may lie:

On the older installs that are still working:

It tells me "You are running MySQL 4.0.27-standard-log."
And has these dump parameters "--opt --verbose --default-character-set=latin1" even though it also recommends below that "--compatible=mysql40" be added

Compared to on the new installs that are not working:

It tells me "You are running MySQL 4.1.22-max-log." (I've also have the exact same issue when running MySQL 5.0.37)
And the default dump parameters are: "--opt --verbose --compatible=mysql40 --default-character-set=latin1"

My first try was to simply remove the "--compatible=mysql40" from the preferences but when I do, I get an error message when backing up: "Error: backups/backup-2007-04-14_10-21-39.sql MISSING or TOO SMALL"


Also, I have the same results when trying to import/restore a database that was created on an older install...something that I've done on a regular basis for the last 6 months or so.

Any help or insight you can provide would be greatly appreciated!

I have similar problems with mysqldump not restoring from a backup.  Can anyone help?

The only thing i can think of, would be to trying to re-install the dumb module. 

Yeah, good call. Many times when a module gets funked up (e.g. FCK Editor) a reinstall of that module has often mysteriously solved the issue for me. Unfortunately, it is not the case for me with MySQL dump.  I'm quite certain it has to do with the newer MySQL version in my shared hosting environment.

My solution has been to start using the Backup module instead which has been much more consistent across various platforms and CMSMS versions. I'm not sure what the pros and cons might be between the two modules but as of now, I only have one real option.

I'm hoping to get a response and solution sometime from one of the power posters in this forum:)