[Resolved] mysqldump generating weird files on Interland

[bunner_bob]

I'm running mysqldump on a pretty big database (the dump file I got when testing at home was around 1.2 M😎.

I got it so it's giving me a dump file, but it seems to be just header - it looks like this:

-- MySQL dump 8.23

-- Host: (my host) Database: (my db)

-- Server version 4.1.9-standard

I'm using the following string:

$command ="mysqldump --opt --host=$myhost --user=$myuser --password=$mypass $dbname >  $mysql_dump_file";
system($command);

I'm thinking either:

1. I'm not using the right "copy" of mysqldump - i.e. I should be specifying the full path - though that gave me nothing when I tried it. Of course it's difficult to work out exactly what the right path IS - Interland's tech support is a bit sketchy.

2. I should somehow be using some additonal or different command.

I tried exec(), I tried "-u $user -p$password syntax - what else should I try?

Could the size of the dump be the problem? I wonder how I could get feedback from mysqldump as to what it's doing, or why it's bailing out.

Any help greatly appreciated!

• Bob

[tunage]

I had the same problem when i upgraded MySQL v4.0 to v4.1 - when it ran my backup script it just showed the header for some reason.

If i created a new database it worked fine, so it was something to do with how MySQL converted my database to 4.1 - i cant remember exactly how i fixed the problem though but i think i had to backup on v4.0, upgrade to v4.1 and then recreate my database and import that dump file.

If you create a small test database does that backup ok?

I use the command -

exec("c:\web\mysql\bin\mysqldump --add-drop-table -h $host -u $user -p$pw $database> $backup_file");

(windows)

[bunner_bob]

Well, it's a brand new account and a brand new database. Unfortunately I don't have privileges to create or delete dbs on this host.

I've got an email in to support - but - the folks here always seem to know a lot more.

I am running 4.0 at home and looks like 4.1 on Interland. I uploaded by dumping from home and uploading (piecemeal - Interland couldn't handle the whole file) via phpMyAdmin. Everything is functioning great on the site, fwiw.

• Bob

[bunner_bob]

Could it have something to do with the size of the dump file (~1.2 M😎? Is there a parameter I can add to tell mysqldump to override a size restriction?

• Bob

[bunner_bob]

Problem solved: apparently Interland's mysqldump doesn't want to see "--opt" in the command line. Take it out and all is hunky dory.

• Bob