Re: LOAD - failure for a non-admin user
Reyna.Sabina schrieb: Hi, I am using MySQL 5.0.45, for redhat-linux-gnu (x86_64). I created a new database called HYDRO (user: admin). I created a new user called 'hydro' in the 'localhost' ([EMAIL PROTECTED]) without a password. User 'hydro' has given all provileges except the ' Grant_priv'. Any clues? issued flush privileges after creating the user ? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Using Flush Hosts in cron
Hank schrieb: I have the blocked connection problem between three of my servers, all behind two firewalls and on one switch. Occaisionally the mysql servers start blocking the hosts. What's the downside to running a Flush hosts once per minute on these mysql servers? better solution: increases max_connect_errors if you are sure, that there ist really no network-problem e.g. --max_connect_errors=10 Werner -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Using Flush Hosts in cron
Hank schrieb: On Tue, Sep 9, 2008 at 11:48 AM, Werner D. [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hank schrieb: I have the blocked connection problem between three of my servers, all behind two firewalls and on one switch. Occaisionally the mysql servers start blocking the hosts. What's the downside to running a Flush hosts once per minute on these mysql servers? better solution: increases max_connect_errors if you are sure, that there ist really no network-problem e.g. --max_connect_errors=10 mysql set global max_connect_errors=1; -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Need Help Migrating DB from MySQL 5.0.x to MySQL 4.0.x
Shaun Adams schrieb: When I perform a dump in mysql5 to mysql 4 DB, I get the error (below). Does anyone know how I can resolve this? QUERY (windows server from the cmd prompt) mysqldump --lock-tables --user=root [SOURCE DB] | mysql --user=[USERNAME] --password=[PASSWORD] --host=[HOST] [TARGET DB] ERROR MESSAGE RETURNED ERROR 1193 (0) at line 23: Unknown system variable 'character_set_client' mysqldump: Got errno 22 on write try the mysqldump-option --compatible=mysql40 Werner -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL-Backup incremental Backups in a Master/Slave Environment
Hi, first thanks for your response Are you using InnoDb or MyISAM? If you are using Inno, I would add --single-transaction to your mysqldump command within the Perl script and flush the logs prior to doing the backup and not backup the new bin-log file until the next. No, there is a mixture beetween MyISAM and InnoDB Tables. You suggest, changing the Order of FLUSH LOGS and place it before the Dumps are generated. Also, have you thought about doing the hourly backups against the master instead of a slave and do full backups off the slave since they naturally take longer? You mean saving the binlogs from the master ? Well currently that's not the case. I want to do the Backup from the Slave, also the hourly Backup of the Binlogs. As for your missing data, and I am not sure this will make sence, the logs you replayed on the test box where until that point you were doing the comparison and not just to the next full backup? Could it be that i need to execute a FLUSH TABLES before doing the mysqldumps on the Slave to force Data in the Cache to be written into the DB ? Thank you, Werner -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
MySQL-Backup incremental Backups in a Master/Slave Environment
Hello everybody, i have a Question concering MySQL-Backups in a Master/Slave Replication-Setup (MYISAM and InnoDB Tables) and incremental Backups using the Binary-Logs from the Slave. Well, in case something will go wrong (hopefully not) I'm currently trying to implement a recovery System. Therefor the Slave logs all events it executes in it's own binary-log (log-bin and log_slave_updates activated). Logical Backups are performed with the help of a Perl-Script and mysqldump every 24 hours. The Script stops the Slave (STOP SLAVE), verifies that it's really stopped and performs the Backup for each Database with mysqldump (--opt). After all dumps are created, the script performs FLUSH LOGS to force the start of a new binary-log. Afterwards the Replication is initialized again (START SLAVE). In addition the master.info, the Output of SHOW SLAVE STATUS and finally the relay-log.info and relay-log.index are also backed up after the Slave is stopped. To verify the functionality of the Recovery Process i've copied a Backup from the 03.08.2008 for a specific Database to a Lab-Server. Also the Backup for the same Database from today (04.08.2008) and the binlogs that cover the events starting after the Backup from 03.08 to 04.08. Well and here is my Problem: After Recovering the Backup from 03.08 to my test-Server and replaying the Binary-Logs i compared the results to the Dump from today. In the Dump from today there are more ROWS in specific Tables then in the Dump from yesterday with applied binary logs :-( Why do I miss some ROWS? What is wrong within my recovery procedure? Any hints are greatly appreciated :-) Thanks, Werner -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
