Mysql Dump 1.2 released
Re: Mysql Dump 1.2 released
I don't understand. Mysql Dump uses the same connection settings as any other CMSMS routines, directly from the config file. I'll look into it.
Re: Mysql Dump 1.2 released
Perhaps it's another problem, but that's what the message seemed to be saying (it indicated localhost in the feedback page). Thanks for looking into it.
Re: Mysql Dump 1.2 released
Okay, found it!
I'll be releasing a new build in the next hour.
---------------
Done. Patched build released as 1.2.3
I'll be releasing a new build in the next hour.
---------------
Done. Patched build released as 1.2.3
Last edited by mahjong on Wed Nov 01, 2006 3:37 am, edited 1 time in total.
Re: Mysql Dump 1.2 released
Close, it;s now trying to connect with the correct database, thank you. But I get another login error, possibly related to the username (there's no '@%' at the end of my username):
Mysql Dump
Please wait until task is fully completed
May take a few minutes with large databases.
Task started
Executing...
(username and password not displayed)
'/usr/bin/mysqldump' --user=######## --password=######## --host=sqlc1d.megasqlservers.com --opt --verbose --default-character-set=latin1 cms_the-doctors-office_ca >>backups/backup-2006-11-01_08-55-35.sql 2>../modules/MysqlDump/dump-verbose.txt
Output...
-- Connecting to sqlc1d.megasqlservers.com...
/usr/bin/mysqldump: Got error: 1044: Access denied for user: 'thedoctors####@%' to database 'cms_the-doctors-office_ca' when using LOCK TABLES
Task completed
-- Linux MysqlDump 1.2.3 module [ --opt --verbose --default-character-set=latin1 ] prefix=ALL
-- MySQL dump 8.22
--
-- Host: sqlc1d.megasqlservers.com Database: cms_the-doctors-office_ca
---------------------------------------------------------
-- Server version 4.0.27-standard
-- Filesize : 282 bytesERROR : backups/backup-2006-11-01_08-55-35.sql MISSING or TOO SMALL
Mysql Dump
Please wait until task is fully completed
May take a few minutes with large databases.
Task started
Executing...
(username and password not displayed)
'/usr/bin/mysqldump' --user=######## --password=######## --host=sqlc1d.megasqlservers.com --opt --verbose --default-character-set=latin1 cms_the-doctors-office_ca >>backups/backup-2006-11-01_08-55-35.sql 2>../modules/MysqlDump/dump-verbose.txt
Output...
-- Connecting to sqlc1d.megasqlservers.com...
/usr/bin/mysqldump: Got error: 1044: Access denied for user: 'thedoctors####@%' to database 'cms_the-doctors-office_ca' when using LOCK TABLES
Task completed
-- Linux MysqlDump 1.2.3 module [ --opt --verbose --default-character-set=latin1 ] prefix=ALL
-- MySQL dump 8.22
--
-- Host: sqlc1d.megasqlservers.com Database: cms_the-doctors-office_ca
---------------------------------------------------------
-- Server version 4.0.27-standard
-- Filesize : 282 bytesERROR : backups/backup-2006-11-01_08-55-35.sql MISSING or TOO SMALL
Re: Mysql Dump 1.2 released

Re: Mysql Dump 1.2 released
No the username is only alphanumeric (I physically altered the username with # symbols in the output given below); CMSMS works perfect otherwise. I just made the assumption of username since in the error report it has appended '@%' to the otherwise valid and complete username. To update the files I just uploaded the newest version over top. Was that correct?
Re: Mysql Dump 1.2 released
Yes. You could have also used the module manager.websherpa wrote:To update the files I just uploaded the newest version over top. Was that correct?
Something to try : open MysqlDump.module.php with a text editor (notepad, textpad, vi, ...) and change $safe_mode to true. The user name and password won't be obfuscated.
Code: Select all
// Turns off additional info on execution (default = false)
var $safe_mode = true;
Last edited by mahjong on Thu Nov 02, 2006 6:17 am, edited 1 time in total.
Re: Mysql Dump 1.2 released
Changing that flag didn't change anything, it still doesn't connect (doesn't that flag just display or not display the command message (and obfuscate it?))
I changed the code to view the actual command (without obfuscation), and the command itself appears to display the correct username, database and password (I have no idea abotu syntax), it's only the Output... back from the server where the username gets the two extra characters @% appended to it. So perhaps this is related to permissions at the database end and I will check with my host. Here's the Output from Mysql Dump in case you have any suggestions or insights to ask my host (I appreciate all your help and work on this):
----
Please wait until task is fully completed
May take a few minutes with large databases.
Task started
Executing...
(username and password not displayed)
'/usr/bin/mysqldump' --user=####### --password=####### --host=sqlc1d.megasqlservers.com --opt --verbose --default-character-set=latin1 cms_the-doctors-office_ca >>backups/backup-2006-11-02_08-57-04.sql 2>../modules/MysqlDump/dump-verbose.txt
Output...
-- Connecting to sqlc1d.megasqlservers.com...
/usr/bin/mysqldump: Got error: 1044: Access denied for user: 'thedoctors165732@%' to database 'cms_the-doctors-office_ca' when using LOCK TABLES
Task completed
-- Linux MysqlDump 1.2.3.3 module [ --opt --verbose --default-character-set=latin1 ] prefix=ALL
-- MySQL dump 8.22
--
-- Host: sqlc1d.megasqlservers.com Database: cms_the-doctors-office_ca
---------------------------------------------------------
-- Server version 4.0.27-standard
-- Filesize : 284 bytes
ERROR : backups/backup-2006-11-02_08-57-04.sql MISSING or TOO SMALL
I changed the code to view the actual command (without obfuscation), and the command itself appears to display the correct username, database and password (I have no idea abotu syntax), it's only the Output... back from the server where the username gets the two extra characters @% appended to it. So perhaps this is related to permissions at the database end and I will check with my host. Here's the Output from Mysql Dump in case you have any suggestions or insights to ask my host (I appreciate all your help and work on this):
----
Please wait until task is fully completed
May take a few minutes with large databases.
Task started
Executing...
(username and password not displayed)
'/usr/bin/mysqldump' --user=####### --password=####### --host=sqlc1d.megasqlservers.com --opt --verbose --default-character-set=latin1 cms_the-doctors-office_ca >>backups/backup-2006-11-02_08-57-04.sql 2>../modules/MysqlDump/dump-verbose.txt
Output...
-- Connecting to sqlc1d.megasqlservers.com...
/usr/bin/mysqldump: Got error: 1044: Access denied for user: 'thedoctors165732@%' to database 'cms_the-doctors-office_ca' when using LOCK TABLES
Task completed
-- Linux MysqlDump 1.2.3.3 module [ --opt --verbose --default-character-set=latin1 ] prefix=ALL
-- MySQL dump 8.22
--
-- Host: sqlc1d.megasqlservers.com Database: cms_the-doctors-office_ca
---------------------------------------------------------
-- Server version 4.0.27-standard
-- Filesize : 284 bytes
ERROR : backups/backup-2006-11-02_08-57-04.sql MISSING or TOO SMALL
Re: Mysql Dump 1.2 released
On other quick thing, if my problem is unrelated to the username login and the MysqlDump module, is it possible that my MySQL doesn't have the Priviliedge granted to my username for the LOCK TABLES command? And if so, is this Administrator level command required by the routine (I have only glancing knowledge of MySQL, so I'm stabbing in the dark here).
Re: Mysql Dump 1.2 released
Yes.is it possible that my MySQL doesn't have the Priviliedge granted to my username for the LOCK TABLES command?
In the Preferences tab, remove the --opt command from the Dump parameters. Maybe you'll have to even replace it by --skip-opt.And if so, is this Administrator level command required by the routine (I have only glancing knowledge of MySQL, so I'm stabbing in the dark here).
Re: Mysql Dump 1.2 released
removing the --opt parameter allows the script to complete without a hitch. now, without risking my current dataset by doing a restore, how do I check the integrity fo the back-up to make certain that the routine worked as it should?
Many thanks again for all your help, this is such an important module.
Many thanks again for all your help, this is such an important module.
Re: Mysql Dump 1.2 released
The only perfectly safe way of doing this is to recreate the entire setup on a local drive.
But, since the backup is a regular text file, you can inspect it visually with any text editor. Click on the link provided at the bottom of the dump page.
But, since the backup is a regular text file, you can inspect it visually with any text editor. Click on the link provided at the bottom of the dump page.
Or, fetched it by ftp from the admin/backups folder.
Re: Mysql Dump 1.2 released
So if have any problems with MISSING or TOO SMALL with Got error: 1044 for Mysql Dump plugin
The SOLUTION for all version is:
Go to admin panel (Control Panel) of yuor host and change the password for your DB, and make corrections to your config.php.
The problem with password is: some special symbols make a bug and the Mysql Dump dont work.
Just create new password only with Leters Digits small small and big.

The SOLUTION for all version is:
Go to admin panel (Control Panel) of yuor host and change the password for your DB, and make corrections to your config.php.
The problem with password is: some special symbols make a bug and the Mysql Dump dont work.
Just create new password only with Leters Digits small small and big.

- FirstGateDreamer
- Forum Members
- Posts: 15
- Joined: Mon Nov 10, 2008 5:42 am
- Location: Ottawa, Canada
Re: Mysql Dump 1.2 released
Thanks for this reply. I've been searching everywhere trying to figure this out. This is a great module.toto wrote:So if have any problems with MISSING or TOO SMALL with Got error: 1044 for Mysql Dump plugin
The SOLUTION for all version is:
Go to admin panel (Control Panel) of yuor host and change the password for your DB, and make corrections to your config.php.
The problem with password is: some special symbols make a bug and the Mysql Dump dont work.
Just create new password only with Leters Digits small small and big.
I still have one problem though... I have the password but I don't have access to the admin control panel and my contact who does have access is unreachable for some time.
Is there any possible way around this at all? Will this bug be fixed in the next release?
thanks