mysql slave replication with master-retry-count
hello, I would like to set that option in mysql 5.0.45 on my slave server: |master-retry-count=800 my slave status: Slave_IO_State: Queueing master event to the relay log Master_Host: xx.xx.xx.xx Master_User: fmRepl Master_Port: 3306 Connect_Retry: 60 Master_Log_File: mysql-bin.000132 Read_Master_Log_Pos: 353589900 Relay_Log_File: relay-bin.34 Relay_Log_Pos: 26881417 Relay_Master_Log_File: mysql-bin.000154 Slave_IO_Running: Yes Slave_SQL_Running: No Replicate_Do_DB: Replicate_Ignore_DB: Replicate_Do_Table: Replicate_Ignore_Table: Replicate_Wild_Do_Table: Replicate_Wild_Ignore_Table: Last_Errno: 0 Last_Error: Skip_Counter: 0 Exec_Master_Log_Pos: 474572276 Relay_Log_Space: 21673882767 Until_Condition: None Until_Log_File: Until_Log_Pos: 0 Master_SSL_Allowed: No Master_SSL_CA_File: Master_SSL_CA_Path: Master_SSL_Cert: Master_SSL_Cipher: Master_SSL_Key: Seconds_Behind_Master: NULL Yes I know the SQL_THREAD is off but this is because of a script that keeps a reasonable delay. Anyway, so I put those options in my.cnf : master-connect-retry=30 master-retry-count=500 I stoped the slave then deleted the master.info file connect-retry is working fine when I do a : show slave status \G; but master-retry-count doesn't show up. I tried to get the info with: show variables; No success... is there a way to be sure that the value is set properly. Let me know! Tks | -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
MySQL 5.0.27 replication problems
Hi, I keep getting the below in the error log. I can't see any problems (no other errors and replication is working) and the master DB is available the whole time. 070928 12:07:31 [Note] Slave: received end packet from server, apparent master shutdown: 070928 12:07:31 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'mysql-bin.000346' position 69110563 070928 12:07:32 [Note] Slave: connected to master 'username@ip address:3306',replication resumed in log 'mysql-bin.000346' at position 69110563 070928 12:07:32 [Note] Slave: received end packet from server, apparent master shutdown: 070928 12:07:32 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'mysql-bin.000346' position 69110563 070928 12:07:32 [Note] Slave: connected to master 'username@ip address:3306',replication resumed in log 'mysql-bin.000346' at position 69110563 Any ideas what is wrong? Cheers, Andrew Sql, query LOVEFiLM International Limited is a company registered in England and Wales. Registered Number: 04392195. Registered Office: No.9, 6 Portal Way, London W3 6RU, United Kingdom. This e-mail is confidential to the ordinary user of the e-mail address to which it was addressed. If you have received it in error, please delete it from your system and notify the sender immediately. This message has been scanned for viruses by BlackSpider MailControl - www.blackspider.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MYSQL data replication
I don't run any master with that many slaves, for reasons that are irrelevant to this thread, but I know there is a point at which the slaves begin to place too much load on the master because they are all asking to read the binlog. I don't know what that point is exactly, but perhaps others can give some advice on that. I would expect, given the workload you describe, that 50 slaves might work okay -- but you should not listen to me. However, you can do multi-tier replication. Let's imagine the limit is ten slaves, just for a round number. You can chain ten slaves off the master, configure them with log-slave-updates, and then chain ten more slaves off each of them. Now you can scale the system to 110 slaves with two tiers. Baron sol beach wrote: Can 1 Master scale to replicate to 50 - 60 slaves? I have limit experience with Master/Slave replication doubt I can round up the hardware to test a 50 node configuration. On 6/8/07, Baron Schwartz [EMAIL PROTECTED] wrote: Hi sol, sol beach wrote: I have limited experience with MYSQL replication; which is why I am hoping others with more experience can answer a question or two. Let's say I have a MASTER MYSQL database. Let's say there are 50 - 60 other systems where I'd like to have MYSQL running on these slave systems. These slave systems need to be kept in synch with the Master, but it does NOT need to be anywhere near real time. The data in the slaves could lag as much a an hour or two. The amount of data in total in the MASTER is in the range of 100MB - 250MB The rate of changes to the data is in the range 2000 - 5000 DML per 24 hour day. We control the application so we can/will include date/time each record is created or modified. You can assume that no records ever get physically deleted; only INSERT UPDATE (no DELETE). What are some alternative ways to keep the slave systems current? The best, easiest, simplest way to do this is just to use MySQL's built-in replication. Once you learn its (many) strengths and (relatively few) weaknesses, it works extremely well. If you want to avoid some of the gotchas, I have written about my experiences here: http://www.xaprb.com/blog/2007/01/20/how-to-make-mysql-replication-reliable/ Hand-rolling replication is a bad idea in my opinion, so I don't have any alternative methods to suggest. However, if you just need to sync some data efficiently, try MySQL Table Sync (http://mysqltoolkit.sourceforge.net/). Cheers Baron -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MYSQL data replication
Hello, Hmmm, I just reread your post and noticed the requirement of 50-60 slaves hanging off a single master. DRBD would NOT be the right solution here. -- Jimmy Jimmy Guerrero wrote: Hello, Although you state that there is no requirement for near real time synchronization, an alternative might be to look into DRBD. Which if you are not familiar with, is block-level replication. See: http://www.mysql.com/products/enterprise/drbd.html Combining DRBD with Linux Heartbeat also gives you failover capabilities. Mohd posted a blog on his experience yesterday. See: http://blog.irwan.name/?p=118 Jimmy Guerrero Sr Product Manager MySQL, Inc Houston, TX sol beach wrote: I have limited experience with MYSQL replication; which is why I am hoping others with more experience can answer a question or two. Let's say I have a MASTER MYSQL database. Let's say there are 50 - 60 other systems where I'd like to have MYSQL running on these slave systems. These slave systems need to be kept in synch with the Master, but it does NOT need to be anywhere near real time. The data in the slaves could lag as much a an hour or two. The amount of data in total in the MASTER is in the range of 100MB - 250MB The rate of changes to the data is in the range 2000 - 5000 DML per 24 hour day. We control the application so we can/will include date/time each record is created or modified. You can assume that no records ever get physically deleted; only INSERT UPDATE (no DELETE). What are some alternative ways to keep the slave systems current? TIA HAND! -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MYSQL data replication
Hello, Although you state that there is no requirement for near real time synchronization, an alternative might be to look into DRBD. Which if you are not familiar with, is block-level replication. See: http://www.mysql.com/products/enterprise/drbd.html Combining DRBD with Linux Heartbeat also gives you failover capabilities. Mohd posted a blog on his experience yesterday. See: http://blog.irwan.name/?p=118 Jimmy Guerrero Sr Product Manager MySQL, Inc Houston, TX sol beach wrote: I have limited experience with MYSQL replication; which is why I am hoping others with more experience can answer a question or two. Let's say I have a MASTER MYSQL database. Let's say there are 50 - 60 other systems where I'd like to have MYSQL running on these slave systems. These slave systems need to be kept in synch with the Master, but it does NOT need to be anywhere near real time. The data in the slaves could lag as much a an hour or two. The amount of data in total in the MASTER is in the range of 100MB - 250MB The rate of changes to the data is in the range 2000 - 5000 DML per 24 hour day. We control the application so we can/will include date/time each record is created or modified. You can assume that no records ever get physically deleted; only INSERT UPDATE (no DELETE). What are some alternative ways to keep the slave systems current? TIA HAND! -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MYSQL data replication
Hi sol, sol beach wrote: I have limited experience with MYSQL replication; which is why I am hoping others with more experience can answer a question or two. Let's say I have a MASTER MYSQL database. Let's say there are 50 - 60 other systems where I'd like to have MYSQL running on these slave systems. These slave systems need to be kept in synch with the Master, but it does NOT need to be anywhere near real time. The data in the slaves could lag as much a an hour or two. The amount of data in total in the MASTER is in the range of 100MB - 250MB The rate of changes to the data is in the range 2000 - 5000 DML per 24 hour day. We control the application so we can/will include date/time each record is created or modified. You can assume that no records ever get physically deleted; only INSERT UPDATE (no DELETE). What are some alternative ways to keep the slave systems current? The best, easiest, simplest way to do this is just to use MySQL's built-in replication. Once you learn its (many) strengths and (relatively few) weaknesses, it works extremely well. If you want to avoid some of the gotchas, I have written about my experiences here: http://www.xaprb.com/blog/2007/01/20/how-to-make-mysql-replication-reliable/ Hand-rolling replication is a bad idea in my opinion, so I don't have any alternative methods to suggest. However, if you just need to sync some data efficiently, try MySQL Table Sync (http://mysqltoolkit.sourceforge.net/). Cheers Baron -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
MYSQL data replication
I have limited experience with MYSQL replication; which is why I am hoping others with more experience can answer a question or two. Let's say I have a MASTER MYSQL database. Let's say there are 50 - 60 other systems where I'd like to have MYSQL running on these slave systems. These slave systems need to be kept in synch with the Master, but it does NOT need to be anywhere near real time. The data in the slaves could lag as much a an hour or two. The amount of data in total in the MASTER is in the range of 100MB - 250MB The rate of changes to the data is in the range 2000 - 5000 DML per 24 hour day. We control the application so we can/will include date/time each record is created or modified. You can assume that no records ever get physically deleted; only INSERT UPDATE (no DELETE). What are some alternative ways to keep the slave systems current? TIA HAND!
MySQL docs: Replication Chapter Revamped
Replication Chapter Revamped We have completely reworked the replication chapter for the 5.1 manual. This targets a number of issues, including a major redesign (to make it easier to read and find topics), some updates to the information and processes, and incorporation of numerous bug fixes. You can see the new chapter here: * http://dev.mysql.com/doc/refman/5.1/en/replication.html The main features: * New layout. We've ripped apart the old chapter format and replaced it with a new one. No information has been lost, although a lot of it has been moved around. * We now have four distinct sections: - Replication Configuration - includes details on setup (including How To notes), options and variables, replication formats, and a new section on common replication tasks. - Replication Solutions - this is designed to feature specific scenarios where replication is used. For example, it contains the scale-out solution that was in the FAQ, along with specific notes and guides on backups, splitting replication, and SSL. - Replication Notes and Tips - this collects together sections that were spread about the old structure, including upgrades, compatibility, known features and issues and the FAQ. - Replication Implementation - the innards of the replication system and how it works. In all cases we've either rewritten or hugely expanded the information, and there are also new illustrations with a consistent look and feel to describe layouts and architecture. The new structure will make it easier to add new functionality, scenarios and background information. For example, one other section that is planned, but not in the current documentation yet, is Replication Topologies. Other planned mprovements, such as the MBR/SBR/RBR decision table and implicit commit tables now have a more suitable home in the Replication Implementation section. Regards, Stefan -- Stefan Hinz [EMAIL PROTECTED] MySQL AB Documentation Team Lead. Berlin, Germany (UTC +1:00) Skype:stefanhinz Cell:+491777841069 Desk:+493082702940 Fax:+493082702941 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL docs: Replication Chapter Revamped
Very cool - looking forward to reading it with the new replication options in 5.1 David Stefan Hinz wrote: Replication Chapter Revamped We have completely reworked the replication chapter for the 5.1 manual. This targets a number of issues, including a major redesign (to make it easier to read and find topics), some updates to the information and processes, and incorporation of numerous bug fixes. You can see the new chapter here: * http://dev.mysql.com/doc/refman/5.1/en/replication.html The main features: * New layout. We've ripped apart the old chapter format and replaced it with a new one. No information has been lost, although a lot of it has been moved around. * We now have four distinct sections: - Replication Configuration - includes details on setup (including How To notes), options and variables, replication formats, and a new section on common replication tasks. - Replication Solutions - this is designed to feature specific scenarios where replication is used. For example, it contains the scale-out solution that was in the FAQ, along with specific notes and guides on backups, splitting replication, and SSL. - Replication Notes and Tips - this collects together sections that were spread about the old structure, including upgrades, compatibility, known features and issues and the FAQ. - Replication Implementation - the innards of the replication system and how it works. In all cases we've either rewritten or hugely expanded the information, and there are also new illustrations with a consistent look and feel to describe layouts and architecture. The new structure will make it easier to add new functionality, scenarios and background information. For example, one other section that is planned, but not in the current documentation yet, is Replication Topologies. Other planned mprovements, such as the MBR/SBR/RBR decision table and implicit commit tables now have a more suitable home in the Replication Implementation section. Regards, Stefan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Free chapter of O'Reilly High Performance MySQL on replication
Thought this might be of interest to some on the list: http://www.oreilly.com/catalog/hpmysql/chapter/ch07.pdf -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
MySQL Binlog/Replication and SET @variables
Hello, i have a problem with my replication setup and SET statments. The SET statments seem to be not logged with the queries. An example: CREATE TABLE blablub (ID INT NOT NULL auto_increment PRIMARY KEY, bla text, blub text); SET @bla='bla'; SET @blub='blub'; INSERT INTO blablub VALUES(NULL, @bla, @blub); Now the table blablub on the Master: ++--+--+ | ID | bla | blub | ++--+--+ | 1 | bla | blub | ++--+--+ And on the Slave: ++--+--+ | ID | bla | blub | ++--+--+ | 2 | NULL | NULL | ++--+--+ Here's the binlog entry for the INSERT: #050624 16:46:54 server id 1 log_pos 9162 Intvar SET INSERT_ID=1; # at 9190 #050624 16:46:54 server id 1 log_pos 9190 Query thread_id=7 exec_tim e=0 error_code=0 SET TIMESTAMP=1119624414; INSERT INTO blablub VALUES(NULL, @bla, @blub); Same should happen when the binlog is replayed while restoring a backup. I'm using mysql release 4.0.24. regards, Markus -- Siemens AG ITO AS 4 Internetteam -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL Binlog/Replication and SET @variables
On Jun 24, 2005, at 10:56 AM, Markus Benning wrote: i have a problem with my replication setup and SET statments. The SET statments seem to be not logged with the queries. This is a replication limitation in versions prior to 4.1: Update statements that refer to user variables (that is, variables of the form @var_name) are badly replicated in 3.23 and 4.0. This is fixed in 4.1. Note that user variable names are case insensitive starting from MySQL 5.0. You should take this into account when setting up replication between 5.0 and an older version. http://dev.mysql.com/doc/mysql/en/replication-features.html --Ware -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL Binlog/Replication and SET @variables
Hello. It seems like a documented bug. Switch to 4.1.12. See: http://dev.mysql.com/doc/mysql/en/replication-features.html Markus Benning [EMAIL PROTECTED] wrote: Hello, i have a problem with my replication setup and SET statments. The SET statments seem to be not logged with the queries. An example: CREATE TABLE blablub (ID INT NOT NULL auto_increment PRIMARY KEY, bla text, blub text); SET @bla='bla'; SET @blub='blub'; INSERT INTO blablub VALUES(NULL, @bla, @blub); Now the table blablub on the Master: ++--+--+ | ID | bla | blub | ++--+--+ | 1 | bla | blub | ++--+--+ And on the Slave: ++--+--+ | ID | bla | blub | ++--+--+ | 2 | NULL | NULL | ++--+--+ Here's the binlog entry for the INSERT: #050624 16:46:54 server id 1 log_pos 9162 Intvar SET INSERT_ID=1; # at 9190 #050624 16:46:54 server id 1 log_pos 9190 Query thread_id=7 exec_tim e=0 error_code=0 SET TIMESTAMP=1119624414; INSERT INTO blablub VALUES(NULL, @bla, @blub); Same should happen when the binlog is replayed while restoring a backup. I'm using mysql release 4.0.24. regards, Markus -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
mysql total replication question
Hi All! I'm using the latest mysql 4.0.x and I've successfully set-up database replication on it over 2 machines. I have noticed though that mysql doesn't seem to replicate CREATE TABLE operations on the master to the slave. Is this a limitation? Or I just missed something. If so, can someone please give me a clue or point me to the right place documentations? Also, is it possible to setup replication so that everything in the master is replicated to the slave, included CREATE DATABASE operations? Many Thanks! Shannon __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysql total replication question
Hello. In my replication setup with 4.1.11 master and 5.0.4 slave CREATE TABLE and CREATE DATABASE statements are replicated perfectly. Shannon R. [EMAIL PROTECTED] wrote: Hi All! I'm using the latest mysql 4.0.x and I've successfully set-up database replication on it over 2 machines. I have noticed though that mysql doesn't seem to replicate CREATE TABLE operations on the master to the slave. Is this a limitation? Or I just missed something. If so, can someone please give me a clue or point me to the right place documentations? Also, is it possible to setup replication so that everything in the master is replicated to the slave, included CREATE DATABASE operations? Many Thanks! Shannon __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Upgrade MySQL and replication dies
I use Debian Sarge as my Linux distribution on two servers who replicate MySQL. Every time I upgrade the MySQL package my replication dies. Any ideas why? Thanks, Jacob -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Upgrade MySQL and replication dies
Hello. Does Debian package preserve a master.info and relay-log.info files? Do you stop slave before the upgrade? What does the 'SHOW SLAVE STATUS' statement report? Jacob Friis Larsen [EMAIL PROTECTED] wrote: I use Debian Sarge as my Linux distribution on two servers who replicate MySQL. Every time I upgrade the MySQL package my replication dies. Any ideas why? Thanks, Jacob -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Upgrade MySQL and replication dies
Does Debian package preserve a master.info and relay-log.info files? I'll check with some Debian experts. Do you stop slave before the upgrade? No. What does the 'SHOW SLAVE STATUS' statement report? Before that everything is ok, after I don't know now that it is running ok, but I'll check next time. Thanks, Jacob Jacob Friis Larsen [EMAIL PROTECTED] wrote: I use Debian Sarge as my Linux distribution on two servers who replicate MySQL. Every time I upgrade the MySQL package my replication dies. Any ideas why? Thanks, Jacob -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Oracle 2 MySQL updates/replication?
Hello, I found a question about Oracle 2 MySQL replication in the archive on Sep. 2001 but no mention since? We have a department using Oracle 8.1.7 and I'm running MySQL 4.0 and neither of us wants to change :-) I could call a Perl, C++ or Java program from cron to periodically update the MySQL instance from Oracle but was hoping to use a trigger/stored procedure to initiate the update so it seems more real time. Does this seem possible? Of course it may turn out non-trivial to write the synchronization code so I'll take suggestions on that front also. Thanks for any ideas, -Carl Edwards -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Oracle 2 MySQL updates/replication?
On Tue, Jul 13, 2004 at 06:11:22PM -0700, Carl Edwards wrote: Hello, I found a question about Oracle 2 MySQL replication in the archive on Sep. 2001 but no mention since? We have a department using Oracle 8.1.7 and I'm running MySQL 4.0 and neither of us wants to change :-) I could call a Perl, C++ or Java program from cron to periodically update the MySQL instance from Oracle but was hoping to use a trigger/stored procedure to initiate the update so it seems more real time. Does this seem possible? Of course it may turn out non-trivial to write the synchronization code so I'll take suggestions on that front also. Golden Gate Software makes a product that does this. I'd have a look at what they offer. Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! [EMAIL PROTECTED] | http://jeremy.zawodny.com/ [book] High Performance MySQL -- http://highperformancemysql.com/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Oracle 2 MySQL updates/replication?
An option would be a log reader program that uses Oracle log miner to only show commited transactions from the redo logs. You could then replay the SQL that is being executed on the oracle box on the mysql server as long as the tables are defined the same. 9i has an enhanced log miner that can be used to read 8i redo logs as well, so you might want to use the newer 9i client if you go this way. Updates to the oracle database could be processed the same way using the mysql binary log as long as no mysql extensions were used like inserting multiple rows with a single insert statement. --- Jeremy Zawodny [EMAIL PROTECTED] wrote: On Tue, Jul 13, 2004 at 06:11:22PM -0700, Carl Edwards wrote: Hello, I found a question about Oracle 2 MySQL replication in the archive on Sep. 2001 but no mention since? We have a department using Oracle 8.1.7 and I'm running MySQL 4.0 and neither of us wants to change :-) I could call a Perl, C++ or Java program from cron to periodically update the MySQL instance from Oracle but was hoping to use a trigger/stored procedure to initiate the update so it seems more real time. Does this seem possible? Of course it may turn out non-trivial to write the synchronization code so I'll take suggestions on that front also. Golden Gate Software makes a product that does this. I'd have a look at what they offer. Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! [EMAIL PROTECTED] | http://jeremy.zawodny.com/ [book] High Performance MySQL -- http://highperformancemysql.com/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Is there any good soul out there who can help me with mysql 4.0.17 replication.
Hi, I am new to mysql and having some trouble with replication. Simple stuff like, 1. How to restart the stopped resplication, 2. How to check if the replication is working, 3. How to bring the slave into master status when master crashes, 4. How to restore master and re-enable replication. Thanks and appreciate very much if some one could donate the time and help. Ravi T. - Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger
Re: MySQL 4.1 replication relay log control
Victoria Reznichenko wrote: relay-log-purge is available from 4.1.1. Do you use 4.1.1 or 4.1.0? Is it in the manual because relay-log-purge is available in 4.0.x? AFAICT, 4.1.1 isn't available for download from the mysql.com site. 4.1.0-alpha is. How would one obtain 4.1.1? Would this work to manage the relay log size: 1. restart the slave server to make it start a new realy log 2. monitor the slave server status until we see that its on the new relay log 3. at that point stop the slave server again 4. delete the extra logs and edit the relay log index by hand. 5. start the slave server. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL 4.1 replication relay log control
At 13:26 -0500 10/11/03, Christopher L. Everett wrote: Victoria Reznichenko wrote: relay-log-purge is available from 4.1.1. Do you use 4.1.1 or 4.1.0? Is it in the manual because relay-log-purge is available in 4.0.x? Sorry, what? AFAICT, 4.1.1 isn't available for download from the mysql.com site. 4.1.0-alpha is. How would one obtain 4.1.1? It's available from the BitKeeper repository: http://www.mysql.com/doc/en/Installing_source_tree.html Would this work to manage the relay log size: 1. restart the slave server to make it start a new realy log 2. monitor the slave server status until we see that its on the new relay log 3. at that point stop the slave server again 4. delete the extra logs and edit the relay log index by hand. 5. start the slave server. You don't need to stop and restart the server to make it start a new relay log. Just issue a FLUSH LOGS statement... -- Paul DuBois, Senior Technical Writer Madison, Wisconsin, USA MySQL AB, www.mysql.com Are you MySQL certified? http://www.mysql.com/certification/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL 4.1 replication relay log control
Christopher L. Everett [EMAIL PROTECTED] wrote: The online manual at http://www.mysql.com/doc/en/Replication_Options.html says that these two variables: max-relay-log-size=# relay-log-purge=0|1 exist to control the size of the relay log. But when I try to start my slave server with: set-variable = max-relay-log-size=192MB set-variable = relay-log-purge=1 in my.cnf it won't start. Am I using them right? relay-log-purge is available from 4.1.1. Do you use 4.1.1 or 4.1.0? -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Victoria Reznichenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
MySQL 4.1 replication relay log control
The online manual at http://www.mysql.com/doc/en/Replication_Options.html says that these two variables: max-relay-log-size=# relay-log-purge=0|1 exist to control the size of the relay log. But when I try to start my slave server with: set-variable = max-relay-log-size=192MB set-variable = relay-log-purge=1 in my.cnf it won't start. Am I using them right? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
MySQL crash (replication?)
Hi folks, I just set up a slave server and it seemed to be working alright, catching up with the new data, and then the server suddenly went away. Looking at the slave's data directory, there are approximately 2 relay-bin files. I can't even restart the server now, because it gets a signal 11 immediately. Most of the relay-bin files have nothing in them, but the ones that do have data give me something like this: [EMAIL PROTECTED] data]# mysqlbinlog stout-relay-bin.1588 # at 4 #700101 0:00:00 server id 3 log_pos 0 Rotate to kazoo-binlog.020 pos: 560177478 ERROR: Error in Log_event::read_log_event(): 'read error', data_len: 302717, event_type: 2 ERROR: Could not read entry at offset 47 : Error in log format or read error [EMAIL PROTECTED] data]# I'm not even sure where to start here...I figure I'm going to have to get a fresh copy of all the data from the master, but it's about 350 gigs so that will take a while. Meanwhile I'm trying to figure out how to make this not happen again... Here's a bit from my .err file: 030929 15:28:29 mysqld started 030929 15:28:30 InnoDB: Started 030929 15:28:30 Found invalid password for user: '[EMAIL PROTECTED]'; Ignoring user /usr/sbin/mysqld-max: ready for connections. Version: '4.0.14-Max' socket: '/var/lib/mysql/mysql.sock' port: 3306 030929 19:39:59 mysqld started 030929 19:40:00 InnoDB: Started 030929 19:40:00 Found invalid password for user: '[EMAIL PROTECTED]'; Ignoring user /usr/sbin/mysqld-max: ready for connections. Version: '4.0.14-Max' socket: '/var/lib/mysql/mysql.sock' port: 3306 mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=268435456 read_buffer_size=2093056 max_used_connections=2 max_connections=100 threads_connected=2 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1187439 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x885ff10 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Cannot determine thread, fp=0x41f08b78, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x80dbe1f 0x40037f75 0x420828fc 0x8351165 0x8350f93 0x8350f54 0x8350f54 0x8350f54 0x8350f54 0x8351b6f 0x83711b9 0x837118d 0x83711c9 0x837118d 0x83711c9 0x837118d 0x837118d 0x83711c9 0x837118d 0x83709b9 0x83520fa 0x8351ed5 0x83508df 0x8136669 0x81108b8 0x814d74c 0x814cf7c 0x80e9363 0x80ea88b 0x80e5ed3 0x80ebe0e 0x80e50bf 0x40034fef 0x420e779a New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://www.mysql.com/doc/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd-query at 0x8870968 = load data local infile '/db2/data/tmp/FcstHr_ece.txt' replace into table FcstHr_ece thd-thread_id=49 The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash. Number of processes running now: 0 031001 00:57:10 mysqld restarted 031001 0:57:11 InnoDB: Started 031001 0:57:11 Found invalid password for user: '[EMAIL PROTECTED]'; Ignoring user /usr/sbin/mysqld-max: ready for connections. Version: '4.0.14-Max' socket: '/var/lib/mysql/mysql.sock' port: 3306 mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=268435456 read_buffer_size=2093056 max_used_connections=1 max_connections=100 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1187439 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x88323e8 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Cannot determine thread, fp=0x41ed7b48, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x80dbe1f 0x40037f75
Fw: mysql 4.0.14 + replication + windows XP PROF
No one has replied to my post. - Original Message - From: I.P. [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, August 18, 2003 1:01 PM Subject: mysql 4.0.14 + replication + windows XP PROF Hi, it's my story. I have two 4.0.14 mysql server on one machine with win XP Professional polish version. First acts as master: on port 3300 Second acts as slave: on port 3301 below my configuration: ### FOR MASTER # # This will be passed to all mysql clients [client] #password=my_password port=3300 #socket=MySQL # Here is entries for some specific programs # The following values assume you have at least 32M ram # The MySQL server [mysqld] basedir = c:/mysql4/ datadir = c:/mysql4/data/ port=3300 language=polish default-character-set=latin2 log-bin server-id=1 log-warnings set-variable = key_buffer=16K set-variable = max_allowed_packet=1M set-variable = thread_stack=64K set-variable = table_cache=4 set-variable = sort_buffer=64K set-variable = net_buffer_length=2K query_cache_size = 1024K # Uncomment the following if you are using Innobase tables innodb_data_file_path = ibdata1:50M innodb_data_home_dir = d:\\innodb\\mysql4\\master\\ibdata innodb_log_group_home_dir = d:\\innodb\\mysql4\\master\\iblogs innodb_log_arch_dir = d:\\innodb\\mysql4\\master\\iblogs set-variable = innodb_mirrored_log_groups=1 set-variable = innodb_log_files_in_group=3 set-variable = innodb_log_file_size=5M set-variable = innodb_log_buffer_size=8M innodb_flush_log_at_trx_commit=1 innodb_log_archive=0 set-variable = innodb_buffer_pool_size=16M set-variable = innodb_additional_mem_pool_size=2M set-variable = innodb_file_io_threads=4 set-variable = innodb_lock_wait_timeout=50 [mysqldump] quick set-variable = max_allowed_packet=16M [mysql] no-auto-rehash # Remove the next comment character if you are not familiar with SQL #safe-updates [isamchk] set-variable = key_buffer=8M set-variable = sort_buffer=8M [myisamchk] set-variable = key_buffer=8M set-variable = sort_buffer=8M [mysqlhotcopy] interactive-timeout ### ###FOR SLAVE # # This will be passed to all mysql clients [client] #password=my_password port=3301 #socket=MySQL # Here is entries for some specific programs # The following values assume you have at least 32M ram # The MySQL server [mysqld] basedir = c:/mysql4_slave/ datadir = c:/mysql4_slave/data/ port=3301 language=polish default-character-set=latin2 server-id=2 # log-bin # log-slave-updates master-host=127.0.0.1 master-user=irek master-password=XX master-port=3300 master-connect-retry=30 # log-update=log_updates.log log-warnings set-variable = key_buffer=16K set-variable = max_allowed_packet=1M set-variable = thread_stack=64K set-variable = table_cache=4 set-variable = sort_buffer=64K set-variable = net_buffer_length=2K query_cache_size = 1024K # Uncomment the following if you are using Innobase tables innodb_data_file_path = ibdata1:50M innodb_data_home_dir = d:\\innodb\\mysql4\\slave\\ibdata innodb_log_group_home_dir = d:\\innodb\\mysql4\\slave\\iblogs innodb_log_arch_dir = d:\\innodb\\mysql4\\slave\\iblogs set-variable = innodb_mirrored_log_groups=1 set-variable = innodb_log_files_in_group=3 set-variable = innodb_log_file_size=5M set-variable = innodb_log_buffer_size=8M innodb_flush_log_at_trx_commit=1 innodb_log_archive=0 set-variable = innodb_buffer_pool_size=16M set-variable = innodb_additional_mem_pool_size=2M set-variable = innodb_file_io_threads=4 set-variable = innodb_lock_wait_timeout=50 [mysqldump] quick set-variable = max_allowed_packet=16M [mysql] no-auto-rehash # Remove the next comment character if you are not familiar with SQL #safe-updates [isamchk] set-variable = key_buffer=8M set-variable = sort_buffer=8M [myisamchk] set-variable = key_buffer=8M set-variable = sort_buffer=8M ## END configuration So i have noticed this things. I start replication with master and slave: 1) Master is running ... --- Slave is running ... and at console can i see: 030804 22:55:36 InnoDB: Started 030804 22:55:36 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3300', r eplication started in log 'FIRST' at position 4 030804 22:55:36 Slave SQL thread initialized, starting replication in log 'FIRS T' at position 0, relay log '.\hq-relay-bin.001' position: 4 mysqld-max-nt: ready for connections. Version: '4.0.14-max-nt' socket: '' port: 3301 --- That is ok. 3) checked master data dir: hq-bin.001 hq-bin.index 4) checked slave data dir: hq-relay-bin.001 hq-relay-bin.index master.info relay
mysql 4.0.14 + replication + windows XP PROF
Hi, it's my story. I have two 4.0.14 mysql server on one machine with win XP Professional polish version. First acts as master: on port 3300 Second acts as slave: on port 3301 below my configuration: ### FOR MASTER # # This will be passed to all mysql clients [client] #password=my_password port=3300 #socket=MySQL # Here is entries for some specific programs # The following values assume you have at least 32M ram # The MySQL server [mysqld] basedir = c:/mysql4/ datadir = c:/mysql4/data/ port=3300 language=polish default-character-set=latin2 log-bin server-id=1 log-warnings set-variable = key_buffer=16K set-variable = max_allowed_packet=1M set-variable = thread_stack=64K set-variable = table_cache=4 set-variable = sort_buffer=64K set-variable = net_buffer_length=2K query_cache_size = 1024K # Uncomment the following if you are using Innobase tables innodb_data_file_path = ibdata1:50M innodb_data_home_dir = d:\\innodb\\mysql4\\master\\ibdata innodb_log_group_home_dir = d:\\innodb\\mysql4\\master\\iblogs innodb_log_arch_dir = d:\\innodb\\mysql4\\master\\iblogs set-variable = innodb_mirrored_log_groups=1 set-variable = innodb_log_files_in_group=3 set-variable = innodb_log_file_size=5M set-variable = innodb_log_buffer_size=8M innodb_flush_log_at_trx_commit=1 innodb_log_archive=0 set-variable = innodb_buffer_pool_size=16M set-variable = innodb_additional_mem_pool_size=2M set-variable = innodb_file_io_threads=4 set-variable = innodb_lock_wait_timeout=50 [mysqldump] quick set-variable = max_allowed_packet=16M [mysql] no-auto-rehash # Remove the next comment character if you are not familiar with SQL #safe-updates [isamchk] set-variable = key_buffer=8M set-variable = sort_buffer=8M [myisamchk] set-variable = key_buffer=8M set-variable = sort_buffer=8M [mysqlhotcopy] interactive-timeout ### ###FOR SLAVE # # This will be passed to all mysql clients [client] #password=my_password port=3301 #socket=MySQL # Here is entries for some specific programs # The following values assume you have at least 32M ram # The MySQL server [mysqld] basedir = c:/mysql4_slave/ datadir = c:/mysql4_slave/data/ port=3301 language=polish default-character-set=latin2 server-id=2 # log-bin # log-slave-updates master-host=127.0.0.1 master-user=irek master-password=XX master-port=3300 master-connect-retry=30 # log-update=log_updates.log log-warnings set-variable = key_buffer=16K set-variable = max_allowed_packet=1M set-variable = thread_stack=64K set-variable = table_cache=4 set-variable = sort_buffer=64K set-variable = net_buffer_length=2K query_cache_size = 1024K # Uncomment the following if you are using Innobase tables innodb_data_file_path = ibdata1:50M innodb_data_home_dir = d:\\innodb\\mysql4\\slave\\ibdata innodb_log_group_home_dir = d:\\innodb\\mysql4\\slave\\iblogs innodb_log_arch_dir = d:\\innodb\\mysql4\\slave\\iblogs set-variable = innodb_mirrored_log_groups=1 set-variable = innodb_log_files_in_group=3 set-variable = innodb_log_file_size=5M set-variable = innodb_log_buffer_size=8M innodb_flush_log_at_trx_commit=1 innodb_log_archive=0 set-variable = innodb_buffer_pool_size=16M set-variable = innodb_additional_mem_pool_size=2M set-variable = innodb_file_io_threads=4 set-variable = innodb_lock_wait_timeout=50 [mysqldump] quick set-variable = max_allowed_packet=16M [mysql] no-auto-rehash # Remove the next comment character if you are not familiar with SQL #safe-updates [isamchk] set-variable = key_buffer=8M set-variable = sort_buffer=8M [myisamchk] set-variable = key_buffer=8M set-variable = sort_buffer=8M ## END configuration So i have noticed this things. I start replication with master and slave: 1) Master is running ... --- Slave is running ... and at console can i see: 030804 22:55:36 InnoDB: Started 030804 22:55:36 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3300', r eplication started in log 'FIRST' at position 4 030804 22:55:36 Slave SQL thread initialized, starting replication in log 'FIRS T' at position 0, relay log '.\hq-relay-bin.001' position: 4 mysqld-max-nt: ready for connections. Version: '4.0.14-max-nt' socket: '' port: 3301 --- That is ok. 3) checked master data dir: hq-bin.001 hq-bin.index 4) checked slave data dir: hq-relay-bin.001 hq-relay-bin.index master.info relay-log.info 5) I stopped slave - shutdown nicely. 6) I stopped and started master 3 times. 7) I checked master data dir and i can see: hq-bin.001 hq-bin.002 hq-bin.003 hq-bin.004 hq-bin.index 8) I started master. 9) master data dir: hq-bin.001 hq-bin.002 hq-bin.003 hq-bin.004 hq-bin.005 hq-bin.index 10) I started a slave: 030804 23:07:36 InnoDB: Started 030804 23:07:36 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3300', r eplication started in log 'hq-bin.001' at position 79 030804 23:07:36 Slave SQL thread initialized,
Re: MySQL Secure Replication
Ivan Hoo wrote: how do you secure the replication link between the master and the slave using SSH. i understand that you can do that over mysql client and its server. pls enlighten me coz i m looking high and low for a solution on this issue. On the slave: ssh --local-forward(?) 3307:localhost:3306 foreignhost ...then set up the info for master (on the slave) to be localhost:3307. -- Michael T. Babcock C.T.O., FibreSpeed Ltd. http://www.fibrespeed.net/~mbabcock - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL Secure Replication
On Wed, Jan 22, 2003 at 02:27:40PM -0500, Michael T. Babcock wrote: Ivan Hoo wrote: how do you secure the replication link between the master and the slave using SSH. i understand that you can do that over mysql client and its server. pls enlighten me coz i m looking high and low for a solution on this issue. On the slave: ssh --local-forward(?) 3307:localhost:3306 foreignhost ...then set up the info for master (on the slave) to be localhost:3307. You mean 127.0.0.1:3307, right? Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! [EMAIL PROTECTED] | http://jeremy.zawodny.com/ MySQL 4.0.8: up 4 days, processed 119,323,583 queries (341/sec. avg) - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL Secure Replication
On Fri, 2003-01-17 at 08:51, Ivan Hoo wrote: is there any way you can implement a secure replication via ssh or sth else? Who can implement? As user you can use SSH tunnel with it. There are many tutorial about making SSH tunneling in the internet. I believe if MySQL will have some kind of transport security, it will be SSL (as industry de facto standard for similar things). As usually - if somebody is really interested for new features then they can be speed up if you do the deal with MySQL AB. Otherwise you are one of 5 million MySQL users and MySQL AB develops things in order of own priorities and this is understandable. Tõnu - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL Secure Replication
there seem to be a lack of documentation on this part. Mostly because it can't be done (that I'm aware of). if it can't be done, why is it in the documentation already. i can understand that if 4.0.x is still in alpha or beta stage. but now it is almost near release (gamma). the official mysql documentation (http://www.mysql.com/documentation/mysql/bychapter/manual_MySQL_Database_Ad ministration.html#Replication_Options) actually defines a few variables pertaining to ssl replication (master-ssl, master-ssl-key, master-ssl-cert). doesn't this tell you that ssl replication is already supported? regards, ivan - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL Secure Replication
On Tue, 2003-01-14 at 20:47, Jeremy Zawodny wrote: has anyone been able to setup ssl secure replication for mysql? I don't believe you can do that yet. There's now way to specify the necessary credentials in the slave setup. how do i know whether the replication is actually done over ssl? There are many variables about SSL shown in SHOW STATUS output. They also include cipher currently in use and other similar stuff. This is right way to detect SSL usage because SSL has also ciphers which have no actual encryption at all. Paranoid people must verify if key length in use is long enough. Also I must note that using SSL without having appropriate ACL structure is nonsense. You must use GRANT blahblah REQUIRE SSL CIPHER blahblah. Then MySQL server just won't allow nonencrpyted connection. Otherwise default fallback mechanism will work. You'd have to sniff the network traffic and see. This is always must be done :) there seem to be a lack of documentation on this part. Mostly because it can't be done (that I'm aware of). I think so too. Tõnu - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL Secure Replication
At 23:17 +0800 1/16/03, Ivan Hoo wrote: there seem to be a lack of documentation on this part. Mostly because it can't be done (that I'm aware of). if it can't be done, why is it in the documentation already. i can understand that if 4.0.x is still in alpha or beta stage. but now it is almost near release (gamma). the official mysql documentation (http://www.mysql.com/documentation/mysql/bychapter/manual_MySQL_Database_Ad ministration.html#Replication_Options) actually defines a few variables pertaining to ssl replication (master-ssl, master-ssl-key, master-ssl-cert). doesn't this tell you that ssl replication is already supported? No, it cannot be done. Those options have been added, yes, but they do nothing at the moment. You can specify the options and they'll be parsed, but nothing is done with their values yet. regards, ivan - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL Secure Replication
is there any way you can implement a secure replication via ssh or sth else? regards, ivan At 23:17 +0800 1/16/03, Ivan Hoo wrote: there seem to be a lack of documentation on this part. Mostly because it can't be done (that I'm aware of). if it can't be done, why is it in the documentation already. i can understand that if 4.0.x is still in alpha or beta stage. but now it is almost near release (gamma). the official mysql documentation (http://www.mysql.com/documentation/mysql/bychapter/manual_MySQL_Database_A d ministration.html#Replication_Options) actually defines a few variables pertaining to ssl replication (master-ssl, master-ssl-key, master-ssl-cert). doesn't this tell you that ssl replication is already supported? No, it cannot be done. Those options have been added, yes, but they do nothing at the moment. You can specify the options and they'll be parsed, but nothing is done with their values yet. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL Secure Replication
Jeremy Zawodny wrote: there seem to be a lack of documentation on this part. Mostly because it can't be done (that I'm aware of). Except with stunnel (often recommended) or SSH (which I've had running for months doing this). PS, as with the MySQL daemon, I run my ssh tunnel under 'supervise' so as to make sure its always there and restarts if it gets killed / dies / is stupid / upgraded. -- Michael T. Babcock C.T.O., FibreSpeed Ltd. http://www.fibrespeed.net/~mbabcock - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
RE: MySQL Secure Replication
Mostly because it can't be done (that I'm aware of). Except with stunnel (often recommended) or SSH (which I've had running for months doing this). Another option is CIPE, a method for secure tunnelling of any IP protocol using virtual network interfaces. I believe CIPE comes as standard with RedHat 7.x and above. Regards, Basil Hussain --- Internet Developer, Kodak Weddings E-Mail: [EMAIL PROTECTED] (filter bait: sql, query, queries, smallint) - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL Secure Replication
On Wed, Jan 15, 2003 at 09:18:50AM -0500, Michael T. Babcock wrote: Jeremy Zawodny wrote: there seem to be a lack of documentation on this part. Mostly because it can't be done (that I'm aware of). Except with stunnel (often recommended) or SSH (which I've had running for months doing this). PS, as with the MySQL daemon, I run my ssh tunnel under 'supervise' so as to make sure its always there and restarts if it gets killed / dies / is stupid / upgraded. Right. I should have said there's no built-in way it can be done because folks have doing secure replication via ssh/stunnel for years now. :-) Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! [EMAIL PROTECTED] | http://jeremy.zawodny.com/ MySQL 3.23.51: up 31 days, processed 1,039,952,222 queries (381/sec. avg) - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL Secure Replication
On Wed, Jan 15, 2003 at 04:49:03PM -, Basil Hussain wrote: Mostly because it can't be done (that I'm aware of). Except with stunnel (often recommended) or SSH (which I've had running for months doing this). Another option is CIPE, a method for secure tunnelling of any IP protocol using virtual network interfaces. I believe CIPE comes as standard with RedHat 7.x and above. Right. And if we're shooting for an exhaustive list, some routers have proprietary encryption/tunneling systems. And you could use a more off-the-shelf IPSec or similar VPN scheme. It may be overkill, but they are options. :-) Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! [EMAIL PROTECTED] | http://jeremy.zawodny.com/ MySQL 3.23.51: up 31 days, processed 1,040,383,036 queries (381/sec. avg) - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL Secure Replication
Except with stunnel (often recommended) or SSH (which I've had running for months doing this). PS, as with the MySQL daemon, I run my ssh tunnel under 'supervise' so as to make sure its always there and restarts if it gets killed / dies / is stupid / upgraded. Right. I should have said there's no built-in way it can be done because folks have doing secure replication via ssh/stunnel for years now. :-) how do you secure the replication link between the master and the slave using SSH. i understand that you can do that over mysql client and its server. pls enlighten me coz i m looking high and low for a solution on this issue. regards, ivan --- [This E-mail scanned for viruses by Declude AntiVirus] - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL Secure Replication
On Mon, Jan 13, 2003 at 02:46:45PM +0800, Ivan Hoo wrote: hi All, has anyone been able to setup ssl secure replication for mysql? I don't believe you can do that yet. There's now way to specify the necessary credentials in the slave setup. how do i know whether the replication is actually done over ssl? You'd have to sniff the network traffic and see. there seem to be a lack of documentation on this part. Mostly because it can't be done (that I'm aware of). --- [This E-mail scanned for viruses by Declude AntiVirus] Congratulations. Why do I care which [anti]virus product you use? -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! [EMAIL PROTECTED] | http://jeremy.zawodny.com/ MySQL 3.23.51: up 30 days, processed 1,007,087,318 queries (381/sec. avg) - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
MySQL Secure Replication
hi All, has anyone been able to setup ssl secure replication for mysql? how do i know whether the replication is actually done over ssl? there seem to be a lack of documentation on this part. appreciate a lot if someone could provide some feedback on this. i m currently running mysql-4.0.7-gamma (compiled from source --with-vio --with-openssl=/usr/local/ssl) on a standard redhat linux 7.3. regards, ivan --- [This E-mail scanned for viruses by Declude AntiVirus] - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
MySQL 3.23.47 Replication - Failed Read
Dear Sir/Madam, I have tried the config below, and I successfully see the replicated record in client side but only ONCE. After I have seen the replication works. I continued with my normal transactional work including altering table structure. But later when I checked the replication status. Well, it has been in the state of frozen for some time described below. Now the server position keep in position 69 (show master status) and client side keep staying in position 29 (show slave status). Previously the server position keep staying in 73 but after I done a series of reset master, reset slave and flush logs in server side, it turned to 69 and stay there. The client side is showing the message Waiting to reconnect after failed read (read using show processlist) Here's the series of same error log generated in client-side (mysql.err) 020816 15:31:21 Slave: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'FIRST' at position 29 020816 15:31:21 Slave: received 0 length packet from server, apparent master shutdown: (0) 020816 15:31:21 Slave: Failed reading log event, reconnecting to retry, log 'FIRST' position 29 020816 15:31:48 Slave: reconnected to master '[EMAIL PROTECTED]:3306',replication resumed in log 'FIRST' at position 29 020816 15:31:48 Slave: received 0 length packet from server, apparent master shutdown: (0) 020816 15:32:49 Slave: Failed reading log event, reconnecting to retry, log 'FIRST' position 29 ... I have tried turning off both servers, overwriting of server database over to client's database folder. Deleting off the bin logs and restarting server-side mysql and client-side mysql but it still stay in the position I described above Well, I hope I could get something from MySQL soon. Thank you! The following are my servers settings Both servers are using version 3.23.47 Server (win2000 professional, IP 192.168.100.30) side ini settings [mysqld] basedir=C:/MYSQL #bind-address=192.168.100.30 datadir=C:/MYSQL/data #language=C:/MYSQL/share/your language directory #slow query log#= #tmpdir#= #port=3306 #set-variable=key_buffer=16M server-id=3 binlog-do-db=DISYS_DB log-bin=C:/MYSQL/MyLog/mykhorep.log Client (win98, IP 192.168.100.4) side ini settings [mysqld] basedir=D:/MYSQL #bind-address=192.168.100.4 datadir=D:/MYSQL/data #language=D:/MYSQL/share/your language directory #slow query log#= #tmpdir#= #port=3306 #set-variable=key_buffer=16M master-host=192.168.100.30 master-user=repl master-password=password master-port=3306 server-id=3 master-connect-retry=60 replicate-do-db=DISYS_DB Regards, Khor --- [This E-mail scanned for viruses by Declude antiVirus] - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
MySQL Bothway Replication - Fail Back - Hold Master while Slave is Synchronizing.
MySQL Bothway Replication - Fail Back - Hold Master while Slave is Synchronizing. I have the following question: Is it possible to have a slave on machine M1 synchronizing with a master on another machine M2 while the master on the first machine M1 does not accept requests yet (i.e. it is not available to a client yet)? Background info: Why do I want this? Well, I have a configuration where two machines run MySQL. They are configured to replicate each others updates. Although two masters are effectively running, only one is used at a time. This is taken care of by the client. When the first machine fails, the client detects this and goes to the other machine. So for so good. When machine M1 comes on-line again then our client immediately starts to use it (fail-back) (it has - let's say - a preferred machine and I can't disable this). The database, however, is not correct yet. The slave needs to synchronize with M2 still. So we read old data. This situation could be avoided if we can let the master on M1 wait until the salve on M1 has completed its synchronization, and the databases are in sync again. Thanks, Johan. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL 4.0.2 replication circle broken?
Hello all, I was check up 4.0.3 (from the Development Source Tree), bug still exist. Description: aor I use replication circle (A-B, B-A) with 3.23.51 - all ok. aor But I got problem, when upgrade both my servers to 4.0.2. aor Mysqld create 30 new bin-log files every second at both servers: aor --- aor [www2:/opt/mysql-dev/var]:1303# ls -1 www2-bin.* | wc -l aor2268 aor [www2:/opt/mysql-dev/var]:1306# l www2-bin.00* aor -rw-rw1 mysqlmysql 137 Aug 12 16:31 www2-bin.001 aor -rw-rw1 mysqlmysql 62 Aug 12 16:31 www2-bin.002 aor -rw-rw1 mysqlmysql 62 Aug 12 16:31 www2-bin.003 aor -rw-rw1 mysqlmysql 62 Aug 12 16:31 www2-bin.004 aor -rw-rw1 mysqlmysql 62 Aug 12 16:31 www2-bin.005 aor -rw-rw1 mysqlmysql 62 Aug 12 16:31 www2-bin.006 aor -rw-rw1 mysqlmysql 62 Aug 12 16:31 www2-bin.007 aor -rw-rw1 mysqlmysql 62 Aug 12 16:31 www2-bin.008 aor -rw-rw1 mysqlmysql 62 Aug 12 16:31 www2-bin.009 aor [www2:/opt/mysql-dev/var]:1304# ../bin/mysqlbinlog www2-bin.001 aor # at 4 aor #020812 16:29:30 server id 1 log_pos 4 Start: binlog v 3, server v 4.0. aor 2-alpha-log created 020812 16:29:30 aor # at 79 aor #020812 16:31:13 server id 2 log_pos 79Rotate to www2-bin.002 pos: 4 aor # at 118 aor #020812 16:31:13 server id 1 log_pos 118 Stop aor [www2:/opt/mysql-dev/var]:1305# ../bin/mysqlbinlog www2-bin.002 aor # at 4 aor #020812 16:31:13 server id 2 log_pos 4 Rotate to www2-bin.003 pos: 4 aor # at 43 aor #020812 16:31:13 server id 1 log_pos 43Stop aor [www2:/opt/mysql-dev/var]:1307# ../bin/mysqlbinlog www2-bin.003 aor # at 4 aor #020812 16:31:13 server id 2 log_pos 4 Rotate to www2-bin.004 pos: 4 aor # at 43 aor #020812 16:31:13 server id 1 log_pos 43Stop aor [www2:/opt/mysql-dev/var]:1308# aor -- aor and so on. aor Will be fixed this error in 4.0.3? How-To-Repeat: Fix: Submitter-Id: submitter ID Originator:Artem Ryabov Organization: MySQL support: none Synopsis: too many bin-log files Severity: serious Priority: medium Category: mysql Class: sw-bug Release: mysql-4.0.2-alpha (Source distribution) Environment: aor System: Linux www2.osp.ru 2.2.19 #2 Wed Aug 15 16:02:45 MSD 2001 i686 unknown aor Architecture: i686 aor Some paths: /usr/local/bin/perl /usr/bin/make /usr/bin/gmake /usr/bin/gcc /usr/bin/cc aor GCC: Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs aor gcc version 2.96 2731 (Red Hat Linux 7.1 2.96-85) aor Compilation info: CC='gcc' CFLAGS='' CXX='g++' CXXFLAGS='' LDFLAGS='' aor LIBC: aor lrwxrwxrwx1 root root 11 Nov 25 2000 /lib/libc.so.6 - libc-2.2.so aor -rwxr-xr-x1 root root 5155229 Jan 11 2001 /lib/libc-2.2.so aor -rw-r--r--1 root root 24498288 Jan 11 2001 /usr/lib/libc.a aor -rw-r--r--1 root root 178 Jan 11 2001 /usr/lib/libc.so aor configure command: ./configure --with-mysqld-ldflags=-all-static --disable-shared --prefix=/opt/mysql-dev --with-charset=cp1251 -- Best regards, Artemmailto:[EMAIL PROTECTED] - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Mysql database replication
I highly recommend you update the slave to the same version as the master. Mark D. Wallace wrote: I'm trying to set up a replication database and cannot get the slave to parse the log files on the master. The slave is connecting to the master as indicated in the log file. I have tried to connect directly to the master database from the mysql client on the slave and have no problem using the replication username and password. The master server is mysql-3.23.37-pc-linux-gnu-i686 The slave server is mysql mysql-3.23.51-pc-linux-gnu-i686 From the Mysql site, these two are compatible as a slave master pair. The error message from the slaves error log reads. 14:28:38 Slave: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'FIRST' at position 4 020813 14:28:38 Could not parse log event entry, check the master for binlog corruption This may also be a network problem, or just a bug in the master or slave code. (WHAT IS THE NAME OF THE LOG FILE THE SLAVE IS TRYING TO READ mysql.log?) 020813 14:28:38 Error running query, slave aborted. Fix the problem, and re-start the slave thread with mysqladmin start-slave. We stopped at log 'FIRST' position 4 020813 14:28:38 Slave thread exiting, replication stopped in log 'FIRST' at position 4 WHAT is log 'FIRST' at position 4 referencing? Thanks for any help you can provide. Mark Wallace - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Mysql database replication
I'm trying to set up a replication database and cannot get the slave to parse the log files on the master. The slave is connecting to the master as indicated in the log file. I have tried to connect directly to the master database from the mysql client on the slave and have no problem using the replication username and password. The master server is mysql-3.23.37-pc-linux-gnu-i686 The slave server is mysql mysql-3.23.51-pc-linux-gnu-i686 From the Mysql site, these two are compatible as a slave master pair. The error message from the slaves error log reads. 14:28:38 Slave: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'FIRST' at position 4 020813 14:28:38 Could not parse log event entry, check the master for binlog corruption This may also be a network problem, or just a bug in the master or slave code. (WHAT IS THE NAME OF THE LOG FILE THE SLAVE IS TRYING TO READ mysql.log?) 020813 14:28:38 Error running query, slave aborted. Fix the problem, and re-start the slave thread with mysqladmin start-slave. We stopped at log 'FIRST' position 4 020813 14:28:38 Slave thread exiting, replication stopped in log 'FIRST' at position 4 WHAT is log 'FIRST' at position 4 referencing? Thanks for any help you can provide. Mark Wallace - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
MySQL 4.0.2 replication circle broken?
Description: I use replication circle (A-B, B-A) with 3.23.51 - all ok. But I got problem, when upgrade both my servers to 4.0.2. Mysqld create 30 new bin-log files every second at both servers: --- [www2:/opt/mysql-dev/var]:1303# ls -1 www2-bin.* | wc -l 2268 [www2:/opt/mysql-dev/var]:1306# l www2-bin.00* -rw-rw1 mysqlmysql 137 Aug 12 16:31 www2-bin.001 -rw-rw1 mysqlmysql 62 Aug 12 16:31 www2-bin.002 -rw-rw1 mysqlmysql 62 Aug 12 16:31 www2-bin.003 -rw-rw1 mysqlmysql 62 Aug 12 16:31 www2-bin.004 -rw-rw1 mysqlmysql 62 Aug 12 16:31 www2-bin.005 -rw-rw1 mysqlmysql 62 Aug 12 16:31 www2-bin.006 -rw-rw1 mysqlmysql 62 Aug 12 16:31 www2-bin.007 -rw-rw1 mysqlmysql 62 Aug 12 16:31 www2-bin.008 -rw-rw1 mysqlmysql 62 Aug 12 16:31 www2-bin.009 [www2:/opt/mysql-dev/var]:1304# ../bin/mysqlbinlog www2-bin.001 # at 4 #020812 16:29:30 server id 1 log_pos 4 Start: binlog v 3, server v 4.0. 2-alpha-log created 020812 16:29:30 # at 79 #020812 16:31:13 server id 2 log_pos 79Rotate to www2-bin.002 pos: 4 # at 118 #020812 16:31:13 server id 1 log_pos 118 Stop [www2:/opt/mysql-dev/var]:1305# ../bin/mysqlbinlog www2-bin.002 # at 4 #020812 16:31:13 server id 2 log_pos 4 Rotate to www2-bin.003 pos: 4 # at 43 #020812 16:31:13 server id 1 log_pos 43Stop [www2:/opt/mysql-dev/var]:1307# ../bin/mysqlbinlog www2-bin.003 # at 4 #020812 16:31:13 server id 2 log_pos 4 Rotate to www2-bin.004 pos: 4 # at 43 #020812 16:31:13 server id 1 log_pos 43Stop [www2:/opt/mysql-dev/var]:1308# -- and so on. Will be fixed this error in 4.0.3? How-To-Repeat: Fix: Submitter-Id: submitter ID Originator:Artem Ryabov Organization: MySQL support: none Synopsis: too many bin-log files Severity: serious Priority: medium Category: mysql Class: sw-bug Release: mysql-4.0.2-alpha (Source distribution) Environment: System: Linux www2.osp.ru 2.2.19 #2 Wed Aug 15 16:02:45 MSD 2001 i686 unknown Architecture: i686 Some paths: /usr/local/bin/perl /usr/bin/make /usr/bin/gmake /usr/bin/gcc /usr/bin/cc GCC: Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs gcc version 2.96 2731 (Red Hat Linux 7.1 2.96-85) Compilation info: CC='gcc' CFLAGS='' CXX='g++' CXXFLAGS='' LDFLAGS='' LIBC: lrwxrwxrwx1 root root 11 Nov 25 2000 /lib/libc.so.6 - libc-2.2.so -rwxr-xr-x1 root root 5155229 Jan 11 2001 /lib/libc-2.2.so -rw-r--r--1 root root 24498288 Jan 11 2001 /usr/lib/libc.a -rw-r--r--1 root root 178 Jan 11 2001 /usr/lib/libc.so configure command: ./configure --with-mysqld-ldflags=-all-static --disable-shared --prefix=/opt/mysql-dev --with-charset=cp1251 - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL 4.0.2 replication going bonkers?
On Wed, Jul 17, 2002 at 12:02:08PM +0300, Heikki Tuuri wrote: Jon, replication 4.0.1 - 4.0.2 does not work because the format in the 4.0 series has evolved. Currently, if your master of the 4.0 series, your slave must be of the exact same release. How likely is that to happen again? I just upgraded my last slave to 4.0.3 and all the othres are running various builds of 4.0.2. The master is running 3.23.51. I'm planning to upgrade it to 4.0.x after OSCON. But if this is likely to happen a few more times, I'll wait. I don't want upgrades to be an all servers or no servers situation. Thanks, Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! [EMAIL PROTECTED] | http://jeremy.zawodny.com/ MySQL 3.23.51: up 50 days, processed 1,073,978,230 queries (247/sec. avg) - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL 4.0.2 replication going bonkers?
Jeremy, - Original Message - From: Jeremy Zawodny [EMAIL PROTECTED] To: Heikki Tuuri [EMAIL PROTECTED] Cc: Jon Frisby [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Friday, July 19, 2002 7:17 AM Subject: Re: MySQL 4.0.2 replication going bonkers? On Wed, Jul 17, 2002 at 12:02:08PM +0300, Heikki Tuuri wrote: Jon, replication 4.0.1 - 4.0.2 does not work because the format in the 4.0 series has evolved. Currently, if your master of the 4.0 series, your slave must be of the exact same release. How likely is that to happen again? I just upgraded my last slave to 4.0.3 and all the othres are running various builds of 4.0.2. The master is running 3.23.51. I'm planning to upgrade it to 4.0.x after OSCON. But if this is likely to happen a few more times, I'll wait. I don't want upgrades to be an all servers or no servers situation. 4.0.1 was 6 months old when 4.0.2 came. I guess no changes, except bug fixes, in the 4.0 series happen any more; they are put to to the 4.1 branch. Thanks, Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! [EMAIL PROTECTED] | http://jeremy.zawodny.com/ MySQL 3.23.51: up 50 days, processed 1,073,978,230 queries (247/sec. avg) Best regards, Heikki Tuuri Innobase Oy --- InnoDB - transactions, row level locking, and foreign key support for MySQL See http://www.innodb.com, download MySQL-Max from http://www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL 4.0.2 replication going bonkers?
Jon, replication 4.0.1 - 4.0.2 does not work because the format in the 4.0 series has evolved. Currently, if your master of the 4.0 series, your slave must be of the exact same release. All 3.23 versions after 3.23.33 can be replicated from each other 4.0.0 can only replicate to/from 4.0.0. 4.0.1 slave can replicate from a 3.23.33 and newer 3.23 master, and can only replicate from a 4.0.1 master in the 4.0 branch. 4.0.2 slave can replicate from a 3.23 master, and can only replicate from a 4.0.2 master in the 4.0 branch. || Master || 3.23.33 and up | 4.0.0 | 4.0.1 | 4.0.2 Slave | 3.23.33 and up | yes| no| no| no | 4.0.0 | no | yes | no| no | 4.0.1 | yes| no| yes | no | 4.0.2 | yes| no| no| yes Best regards, Heikki Tuuri Innobase Oy --- Order technical MySQL/InnoDB support at https://order.mysql.com/ See http://www.innodb.com for the online manual and latest news on InnoDB - Original Message - From: Jon Frisby [EMAIL PROTECTED] Newsgroups: mailing.database.mysql Sent: Tuesday, July 16, 2002 4:30 AM Subject: RE: MySQL 4.0.2 replication going bonkers? This seems to have not gotten through... Perhaps the spam filter ate it? (sql, query) -JF -Original Message- From: Jon Frisby [mailto:[EMAIL PROTECTED]] Sent: Monday, July 15, 2002 4:27 PM To: [EMAIL PROTECTED] Subject: MySQL 4.0.2 replication going bonkers? We recently set up a 4.0.2 slave, which worked fine -- we loaded our data snapshot (taken via mysqldump) and were able to perform complex queries without problems... However, as soon as we tried to get this machine to act as a slave to a 4.0.1 server it crashed. Immediately upon executing SLAVE START, we get messages like this in the error log: 020714 01:32:03 mysqld started 020714 1:32:05 InnoDB: Started /usr/sbin/mysqld-max: ready for connections 020714 8:00:28 Slave SQL thread initialized, starting replication in log 'server2-bin.035' at position 579285542, relay log './db1-relay-bin.001' position: 4 020714 8:00:29 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'server2-bin.035' at position 579285542 ERROR: 1146 Table 'test.response' doesn't exist 020714 8:00:30 Slave: error 'Table 'test.response' doesn't exist' on query 'INSERT INTO response SET connect_time=0.073868989944458, page_time=1.53695404529572, site_id='Apt'', error_code=1146 020714 8:00:30 Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with SLAVE START. We stopped at log 'server2-bin.035' position 579285542 020714 8:00:30 Slave SQL thread exiting, replication stopped in log 'server2-bin.035' at position 579285542 020714 8:00:54 Error reading packet from server: (server_errno=1159) 020714 8:00:54 Slave I/O thread killed while reading event 020714 8:00:54 Slave I/O thread exiting, read up to log 'server2-bin.035', position 579993154 020714 8:01:58 /usr/sbin/mysqld-max: Normal shutdown 020714 8:01:58 InnoDB: Starting shutdown... 020714 8:02:05 InnoDB: Shutdown completed 020714 8:02:06 /usr/sbin/mysqld-max: Shutdown Complete 020714 08:02:06 mysqld ended 020714 08:02:16 mysqld started 020714 8:02:17 InnoDB: Started /usr/sbin/mysqld-max: ready for connections 020714 8:02:34 Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-bin.001' position: 4 ERROR: 1146 Table 'test.response' doesn't exist 020714 8:02:34 Slave: error 'Table 'test.response' doesn't exist' on query 'INSERT INTO response SET connect_time=0.073868989944458, page_time=1.53695404529572, site_id='Apt '', error_code=1146 020714 8:02:34 Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with SLAVE START. We stopped at log 'FIRST' position 0 020714 8:02:34 Slave SQL thread exiting, replication stopped in log 'FIRST' at position 0 020714 8:02:34 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'server2-bin.035' at position 579993154 020714 8:03:02 Error reading packet from server: (server_errno=1159) 020714 8:03:02 Slave I/O thread killed while reading event 020714 8:03:02 Slave I/O thread exiting, read up to log 'server2-bin.035', position 579993478 020714 8:03:25 /usr/sbin/mysqld-max: Normal shutdown 020714 8:03:25 InnoDB: Starting shutdown... 020714 8:03:28 InnoDB: Shutdown completed 020714 8:03:28 /usr/sbin/mysqld-max: Shutdown Complete 020714 08:03:28 mysqld ended 020714 08:03:36 mysqld started 020714 8:03:38 InnoDB: Started /usr/sbin/mysqld-max: ready for connections 020714 8:04:02 Slave SQL thread initialized, starting
MySQL 4.0.2 replication going bonkers?
We recently set up a 4.0.2 slave, which worked fine -- we loaded our data snapshot (taken via mysqldump) and were able to perform complex queries without problems... However, as soon as we tried to get this machine to act as a slave to a 4.0.1 server it crashed. Immediately upon executing SLAVE START, we get messages like this in the error log: 020714 01:32:03 mysqld started 020714 1:32:05 InnoDB: Started /usr/sbin/mysqld-max: ready for connections 020714 8:00:28 Slave SQL thread initialized, starting replication in log 'server2-bin.035' at position 579285542, relay log './db1-relay-bin.001' position: 4 020714 8:00:29 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'server2-bin.035' at position 579285542 ERROR: 1146 Table 'test.response' doesn't exist 020714 8:00:30 Slave: error 'Table 'test.response' doesn't exist' on query 'INSERT INTO response SET connect_time=0.073868989944458, page_time=1.53695404529572, site_id='Apt'', error_code=1146 020714 8:00:30 Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with SLAVE START. We stopped at log 'server2-bin.035' position 579285542 020714 8:00:30 Slave SQL thread exiting, replication stopped in log 'server2-bin.035' at position 579285542 020714 8:00:54 Error reading packet from server: (server_errno=1159) 020714 8:00:54 Slave I/O thread killed while reading event 020714 8:00:54 Slave I/O thread exiting, read up to log 'server2-bin.035', position 579993154 020714 8:01:58 /usr/sbin/mysqld-max: Normal shutdown 020714 8:01:58 InnoDB: Starting shutdown... 020714 8:02:05 InnoDB: Shutdown completed 020714 8:02:06 /usr/sbin/mysqld-max: Shutdown Complete 020714 08:02:06 mysqld ended 020714 08:02:16 mysqld started 020714 8:02:17 InnoDB: Started /usr/sbin/mysqld-max: ready for connections 020714 8:02:34 Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-bin.001' position: 4 ERROR: 1146 Table 'test.response' doesn't exist 020714 8:02:34 Slave: error 'Table 'test.response' doesn't exist' on query 'INSERT INTO response SET connect_time=0.073868989944458, page_time=1.53695404529572, site_id='Apt '', error_code=1146 020714 8:02:34 Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with SLAVE START. We stopped at log 'FIRST' position 0 020714 8:02:34 Slave SQL thread exiting, replication stopped in log 'FIRST' at position 0 020714 8:02:34 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'server2-bin.035' at position 579993154 020714 8:03:02 Error reading packet from server: (server_errno=1159) 020714 8:03:02 Slave I/O thread killed while reading event 020714 8:03:02 Slave I/O thread exiting, read up to log 'server2-bin.035', position 579993478 020714 8:03:25 /usr/sbin/mysqld-max: Normal shutdown 020714 8:03:25 InnoDB: Starting shutdown... 020714 8:03:28 InnoDB: Shutdown completed 020714 8:03:28 /usr/sbin/mysqld-max: Shutdown Complete 020714 08:03:28 mysqld ended 020714 08:03:36 mysqld started 020714 8:03:38 InnoDB: Started /usr/sbin/mysqld-max: ready for connections 020714 8:04:02 Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-bin.001' position: 4 mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=67104768 record_buffer=16773120 sort_buffer=16777208 max_used_connections=0 max_connections=100 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 3341931 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x85204a0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Cannot determine thread, fp=0xbfe3f248, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x80722d8 0x82de908 0x82cb534 0x80e9a58 0x80af595 0x80b04f4 0x80ebf71 0x80ece8f 0x82dbf1c 0x831193a New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://www.mysql.com/doc/U/s/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd-query at (nil) is invalid pointer thd-thread_id=3 Successfully dumped
RE: MySQL 4.0.2 replication going bonkers?
This seems to have not gotten through... Perhaps the spam filter ate it? (sql, query) -JF -Original Message- From: Jon Frisby [mailto:[EMAIL PROTECTED]] Sent: Monday, July 15, 2002 4:27 PM To: [EMAIL PROTECTED] Subject: MySQL 4.0.2 replication going bonkers? We recently set up a 4.0.2 slave, which worked fine -- we loaded our data snapshot (taken via mysqldump) and were able to perform complex queries without problems... However, as soon as we tried to get this machine to act as a slave to a 4.0.1 server it crashed. Immediately upon executing SLAVE START, we get messages like this in the error log: 020714 01:32:03 mysqld started 020714 1:32:05 InnoDB: Started /usr/sbin/mysqld-max: ready for connections 020714 8:00:28 Slave SQL thread initialized, starting replication in log 'server2-bin.035' at position 579285542, relay log './db1-relay-bin.001' position: 4 020714 8:00:29 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'server2-bin.035' at position 579285542 ERROR: 1146 Table 'test.response' doesn't exist 020714 8:00:30 Slave: error 'Table 'test.response' doesn't exist' on query 'INSERT INTO response SET connect_time=0.073868989944458, page_time=1.53695404529572, site_id='Apt'', error_code=1146 020714 8:00:30 Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with SLAVE START. We stopped at log 'server2-bin.035' position 579285542 020714 8:00:30 Slave SQL thread exiting, replication stopped in log 'server2-bin.035' at position 579285542 020714 8:00:54 Error reading packet from server: (server_errno=1159) 020714 8:00:54 Slave I/O thread killed while reading event 020714 8:00:54 Slave I/O thread exiting, read up to log 'server2-bin.035', position 579993154 020714 8:01:58 /usr/sbin/mysqld-max: Normal shutdown 020714 8:01:58 InnoDB: Starting shutdown... 020714 8:02:05 InnoDB: Shutdown completed 020714 8:02:06 /usr/sbin/mysqld-max: Shutdown Complete 020714 08:02:06 mysqld ended 020714 08:02:16 mysqld started 020714 8:02:17 InnoDB: Started /usr/sbin/mysqld-max: ready for connections 020714 8:02:34 Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-bin.001' position: 4 ERROR: 1146 Table 'test.response' doesn't exist 020714 8:02:34 Slave: error 'Table 'test.response' doesn't exist' on query 'INSERT INTO response SET connect_time=0.073868989944458, page_time=1.53695404529572, site_id='Apt '', error_code=1146 020714 8:02:34 Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with SLAVE START. We stopped at log 'FIRST' position 0 020714 8:02:34 Slave SQL thread exiting, replication stopped in log 'FIRST' at position 0 020714 8:02:34 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'server2-bin.035' at position 579993154 020714 8:03:02 Error reading packet from server: (server_errno=1159) 020714 8:03:02 Slave I/O thread killed while reading event 020714 8:03:02 Slave I/O thread exiting, read up to log 'server2-bin.035', position 579993478 020714 8:03:25 /usr/sbin/mysqld-max: Normal shutdown 020714 8:03:25 InnoDB: Starting shutdown... 020714 8:03:28 InnoDB: Shutdown completed 020714 8:03:28 /usr/sbin/mysqld-max: Shutdown Complete 020714 08:03:28 mysqld ended 020714 08:03:36 mysqld started 020714 8:03:38 InnoDB: Started /usr/sbin/mysqld-max: ready for connections 020714 8:04:02 Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-bin.001' position: 4 mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=67104768 record_buffer=16773120 sort_buffer=16777208 max_used_connections=0 max_connections=100 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 3341931 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x85204a0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Cannot determine thread, fp=0xbfe3f248, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x80722d8 0x82de908 0x82cb534 0x80e9a58 0x80af595 0x80b04f4 0x80ebf71 0x80ece8f 0x82dbf1c 0x831193a New value of fp=(nil) failed sanity check, terminating stack trace
Is mySQL support replication ??
Hi, all,
May i know is mySQL support replication
regards,
alice
/---\
Confidential and/ or privileged information may be contained in this
e-mail and any attachments transmitted with it ('Message'). If you are
not the addressee indicated in this Message (or responsible for
delivery of this Message to such person),you are hereby notified that
any dissemination, distribution, printing or copying of this Message or
any part thereof is prohibited. Please delete this Message if received
in error and advise the sender by return e-mail. Opinions, conclusions
and other information in this Message that do not relate to the
official business of this company shall be understood as neither given
nor endorsed by this company.
This mail is certified Virus Free by *ProtectNow! (InternetNow Sdn Bhd)
*Scanner Engine powered by Norman Virus Control
\--/
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Is mySQL support replication ??
Yes it does.
http://www.mysql.com/doc/R/e/Replication_Implementation.html
- Original Message -
From: Alice [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, June 24, 2002 6:52 PM
Subject: Is mySQL support replication ??
Hi, all,
May i know is mySQL support replication
regards,
alice
/---
\
Confidential and/ or privileged information may be contained in this
e-mail and any attachments transmitted with it ('Message'). If you are
not the addressee indicated in this Message (or responsible for
delivery of this Message to such person),you are hereby notified that
any dissemination, distribution, printing or copying of this Message or
any part thereof is prohibited. Please delete this Message if received
in error and advise the sender by return e-mail. Opinions, conclusions
and other information in this Message that do not relate to the
official business of this company shall be understood as neither given
nor endorsed by this company.
This mail is certified Virus Free by *ProtectNow! (InternetNow Sdn Bhd)
*Scanner Engine powered by Norman Virus Control
\--/
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail
[EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
MySql Database Replication Question
All, How can I notify an application running on the slave server that the slave database has just updated itself by means of replication. The reason I ask is that I know MySql currently doesn't support triggers, but my application needs to be notified when an update on the slave has just taken place. Once again, thanks for your time. Thi - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySql Database Replication Question
On Thu, Mar 07, 2002 at 08:37:00AM -0600, Thi Cao wrote: All, How can I notify an application running on the slave server that the slave database has just updated itself by means of replication. The reason I ask is that I know MySql currently doesn't support triggers, but my application needs to be notified when an update on the slave has just taken place. Once again, thanks for your time. Hm, that's a little unusual. Could the application look at the output of SHOW SLAVE STATUS once in a while, maybe? -- Jeremy D. Zawodny, [EMAIL PROTECTED] Technical Yahoo - Yahoo Finance Desk: (408) 349-7878 Fax: (408) 349-5454 Cell: (408) 685-5936 MySQL 3.23.47-max: up 28 days, processed 988,263,631 queries (407/sec. avg) - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
RE: MySql Database Replication Question
Jeremy, I'm not sure I follow. What information from that command would the app be looking for specifically. Maybe you're saying the app should look at the position of the master's binary log file. Is that what you suggest? Thi -Original Message- From: Jeremy Zawodny [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 07, 2002 10:42 AM To: Thi Cao Cc: MySQL Subject: Re: MySql Database Replication Question On Thu, Mar 07, 2002 at 08:37:00AM -0600, Thi Cao wrote: All, How can I notify an application running on the slave server that the slave database has just updated itself by means of replication. The reason I ask is that I know MySql currently doesn't support triggers, but my application needs to be notified when an update on the slave has just taken place. Once again, thanks for your time. Hm, that's a little unusual. Could the application look at the output of SHOW SLAVE STATUS once in a while, maybe? -- Jeremy D. Zawodny, [EMAIL PROTECTED] Technical Yahoo - Yahoo Finance Desk: (408) 349-7878 Fax: (408) 349-5454 Cell: (408) 685-5936 MySQL 3.23.47-max: up 28 days, processed 988,263,631 queries (407/sec. avg) - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
RE: MySQL Database Replication
On Wed, 2002-03-06 at 14:26, Thi Cao wrote: When I grant privileges as follows, the slave gets updated: GRANT FILE ON *.* to repl@'%' identified by 'some_password'; Could someone please tell me why I must grant the FILE privilege on all databases for the repl (slave) to be able to update one particular database? MySQL Manual: 4.2.7 Privileges Provided by MySQL: The file privilege gives you permission to read and write files on the server using the LOAD DATA INFILE and SELECT ... INTO OUTFILE statements. Any user to whom this privilege is granted can read or write any file that the MySQL server can read or write. 4.10.3 How To Set Up Replication 2. Set up special a replication user on the master with the FILE privilege and permission to connect from all the slaves. If the user is only doing replication (which is recommended), you don't need to grant any additional privileges. For example, to create a user named repl which can access your master from any host, you might use this command: GRANT FILE ON *.* TO repl@% IDENTIFIED BY 'password'; Thi Cao wrote: Hello everyone, This is my first attempt at MySQL database replication. Can't seem to get it to work yet. The problem reported in the error log of the slave server is as follows: Error reading packet from server: Access denied for user 'repl@slave_host' (Using password: YES) (read_errno 0,server_errno=1045) I believe it has something to do with the way I granted privileges to the user repl. I did the following: GRANT FILE ON dbname.* to repl@'%' identified by 'some_password'; Did you do a FLUSH PRIVILIGES after that? That is needed in some cases. You don't need to flush privileges when using grant/revoke commands. -- dsoares (sql) - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
RE: MySQL Database Replication
ds, If I understand you correctly, that also means that the user repl can access the mysql database where all the privilege info is stored and see the permissions, passwords, and such. Yes/No? Thi -Original Message- From: ds [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 07, 2002 11:02 AM To: Thi Cao Cc: MySQL Subject: RE: MySQL Database Replication On Wed, 2002-03-06 at 14:26, Thi Cao wrote: When I grant privileges as follows, the slave gets updated: GRANT FILE ON *.* to repl@'%' identified by 'some_password'; Could someone please tell me why I must grant the FILE privilege on all databases for the repl (slave) to be able to update one particular database? MySQL Manual: 4.2.7 Privileges Provided by MySQL: The file privilege gives you permission to read and write files on the server using the LOAD DATA INFILE and SELECT ... INTO OUTFILE statements. Any user to whom this privilege is granted can read or write any file that the MySQL server can read or write. 4.10.3 How To Set Up Replication 2. Set up special a replication user on the master with the FILE privilege and permission to connect from all the slaves. If the user is only doing replication (which is recommended), you don't need to grant any additional privileges. For example, to create a user named repl which can access your master from any host, you might use this command: GRANT FILE ON *.* TO repl@% IDENTIFIED BY 'password'; Thi Cao wrote: Hello everyone, This is my first attempt at MySQL database replication. Can't seem to get it to work yet. The problem reported in the error log of the slave server is as follows: Error reading packet from server: Access denied for user 'repl@slave_host' (Using password: YES) (read_errno 0,server_errno=1045) I believe it has something to do with the way I granted privileges to the user repl. I did the following: GRANT FILE ON dbname.* to repl@'%' identified by 'some_password'; Did you do a FLUSH PRIVILIGES after that? That is needed in some cases. You don't need to flush privileges when using grant/revoke commands. -- dsoares (sql) - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
RE: MySQL Database Replication
rep1 would gain FILE access to all ( not sure what the really entails ) it would not have SELECT access, so can not read from it mind you if they have enough info to get in with rep1 access, then they could just replicate everything on thier own server and read till thier hearts content -Original Message- From: Thi Cao [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 07, 2002 12:04 PM To: Thi Cao Cc: MySQL Subject: RE: MySQL Database Replication ds, If I understand you correctly, that also means that the user repl can access the mysql database where all the privilege info is stored and see the permissions, passwords, and such. Yes/No? Thi -Original Message- From: ds [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 07, 2002 11:02 AM To: Thi Cao Cc: MySQL Subject: RE: MySQL Database Replication On Wed, 2002-03-06 at 14:26, Thi Cao wrote: When I grant privileges as follows, the slave gets updated: GRANT FILE ON *.* to repl@'%' identified by 'some_password'; Could someone please tell me why I must grant the FILE privilege on all databases for the repl (slave) to be able to update one particular database? MySQL Manual: 4.2.7 Privileges Provided by MySQL: The file privilege gives you permission to read and write files on the server using the LOAD DATA INFILE and SELECT ... INTO OUTFILE statements. Any user to whom this privilege is granted can read or write any file that the MySQL server can read or write. 4.10.3 How To Set Up Replication 2. Set up special a replication user on the master with the FILE privilege and permission to connect from all the slaves. If the user is only doing replication (which is recommended), you don't need to grant any additional privileges. For example, to create a user named repl which can access your master from any host, you might use this command: GRANT FILE ON *.* TO repl@% IDENTIFIED BY 'password'; Thi Cao wrote: Hello everyone, This is my first attempt at MySQL database replication. Can't seem to get it to work yet. The problem reported in the error log of the slave server is as follows: Error reading packet from server: Access denied for user 'repl@slave_host' (Using password: YES) (read_errno 0,server_errno=1045) I believe it has something to do with the way I granted privileges to the user repl. I did the following: GRANT FILE ON dbname.* to repl@'%' identified by 'some_password'; Did you do a FLUSH PRIVILIGES after that? That is needed in some cases. You don't need to flush privileges when using grant/revoke commands. -- dsoares (sql) - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
RE: MySQL Database Replication
Yes, I did flush the privileges when nothing else worked but that didn't do the trick either. Thanks for trying. -Original Message- From: James Housley [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 05, 2002 6:00 PM To: Thi Cao Cc: MySQL Subject: Re: MySQL Database Replication Thi Cao wrote: Hello everyone, This is my first attempt at MySQL database replication. Can't seem to get it to work yet. The problem reported in the error log of the slave server is as follows: Error reading packet from server: Access denied for user 'repl@slave_host' (Using password: YES) (read_errno 0,server_errno=1045) I believe it has something to do with the way I granted privileges to the user repl. I did the following: GRANT FILE ON dbname.* to repl@'%' identified by 'some_password'; Did you do a FLUSH PRIVILIGES after that? That is needed in some cases. Jim -- /\ ASCII Ribbon Campaign . \ / - NO HTML/RTF in e-mail . X - NO Word docs in e-mail . / \ - [EMAIL PROTECTED] http://www.FreeBSD.org The Power to Serve [EMAIL PROTECTED] http://www.TheHousleys.net [EMAIL PROTECTED] http://www.SimTel.Net - Studies show that 1 out of every 4 Americans suffer some form of mental illness. So look at your three best friends, if they are okay it is YOU! - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
RE: MySQL Database Replication
When I grant privileges as follows, the slave gets updated: GRANT FILE ON *.* to repl@'%' identified by 'some_password'; Could someone please tell me why I must grant the FILE privilege on all databases for the repl (slave) to be able to update one particular database? Thanks everyone. Thi -Original Message- From: James Housley [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 05, 2002 6:00 PM To: Thi Cao Cc: MySQL Subject: Re: MySQL Database Replication Thi Cao wrote: Hello everyone, This is my first attempt at MySQL database replication. Can't seem to get it to work yet. The problem reported in the error log of the slave server is as follows: Error reading packet from server: Access denied for user 'repl@slave_host' (Using password: YES) (read_errno 0,server_errno=1045) I believe it has something to do with the way I granted privileges to the user repl. I did the following: GRANT FILE ON dbname.* to repl@'%' identified by 'some_password'; Did you do a FLUSH PRIVILIGES after that? That is needed in some cases. Jim -- /\ ASCII Ribbon Campaign . \ / - NO HTML/RTF in e-mail . X - NO Word docs in e-mail . / \ - [EMAIL PROTECTED] http://www.FreeBSD.org The Power to Serve [EMAIL PROTECTED] http://www.TheHousleys.net [EMAIL PROTECTED] http://www.SimTel.Net - Studies show that 1 out of every 4 Americans suffer some form of mental illness. So look at your three best friends, if they are okay it is YOU! - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
MySQL Database Replication
Hello everyone, This is my first attempt at MySQL database replication. Can't seem to get it to work yet. The problem reported in the error log of the slave server is as follows: Error reading packet from server: Access denied for user 'repl@slave_host' (Using password: YES) (read_errno 0,server_errno=1045) I believe it has something to do with the way I granted privileges to the user repl. I did the following: GRANT FILE ON dbname.* to repl@'%' identified by 'some_password'; In the slave config file, I have the correct password to connect to the master, so I don't believe that that is the problem. Also included in the config file is replicate-do-db=dbname. If someone has any idea of what I can or should do, your help would be much appreciated. If not, thanks for your time. Thi - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL Database Replication
Thi Cao wrote: Hello everyone, This is my first attempt at MySQL database replication. Can't seem to get it to work yet. The problem reported in the error log of the slave server is as follows: Error reading packet from server: Access denied for user 'repl@slave_host' (Using password: YES) (read_errno 0,server_errno=1045) I believe it has something to do with the way I granted privileges to the user repl. I did the following: GRANT FILE ON dbname.* to repl@'%' identified by 'some_password'; Did you do a FLUSH PRIVILIGES after that? That is needed in some cases. Jim -- /\ ASCII Ribbon Campaign . \ / - NO HTML/RTF in e-mail . X - NO Word docs in e-mail . / \ - [EMAIL PROTECTED] http://www.FreeBSD.org The Power to Serve [EMAIL PROTECTED] http://www.TheHousleys.net [EMAIL PROTECTED] http://www.SimTel.Net - Studies show that 1 out of every 4 Americans suffer some form of mental illness. So look at your three best friends, if they are okay it is YOU! - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
MySql and replication
Hello, I have 2 application running in a master/slave mode. - Application A linked to a database D - Application A' linked to a database D' While A is master, A' is in standby mode and D' replicates D. If a problem occurs on A, A' becomes master and D must replicate D'. 1) Is it possible for a master MySql database to become slave ? 2) Is it possible for A' to tell D' to become master (by lauching a script for instance) ? Thanks in advance, Fabien - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: FW: mysql db replication security across the internet
Duc Chau ([EMAIL PROTECTED]) writes: Can anyone tell me or point me to documentation on how to securely do database replication over the internet? I need to replicate to machines in datacenters in diffrent states. How feasible is this? Has anyone done it? What are the security concerns with doing this via the net? Thanks Not a problem. Use secure shell's port forwarding feature (look in the VPN HOWTO at http://www.linuxdoc.org/HOWTO/VPN-HOWTO.html for more info). -- Ed Carp, N7EKG - [EMAIL PROTECTED] - 214/341-4420 - http://www.pobox.com/~erc Squished Mosquito, Inc. Internet Applications Development Escapade Server-Side Scripting Language Development Team http://www.squishedmosquito.com Pensacola - Dallas - Dresden - London - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
FW: mysql db replication security across the internet
Can anyone tell me or point me to documentation on how to securely do database replication over the internet? I need to replicate to machines in datacenters in diffrent states. How feasible is this? Has anyone done it? What are the security concerns with doing this via the net? Thanks - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
RE: mysql db replication security across the internet
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 05, 2001 3:50 PM To: Duc Chau Subject: Re: mysql db replication security across the internet Your message cannot be posted because it appears to be either spam or simply off topic to our filter. To bypass the filter you must include one of the following words in your message: database,sql,query,table If you just reply to this message, and include the entire text of it in the reply, your reply will go through. However, you should first review the text of the message to make sure it has something to do with MySQL. Just typing the word MySQL once will be sufficient, for example. You have written the following: Can anyone tell me or point me to documentation on how to securely do data replication over the internet? I need to replicate to machines in datacenters in diffrent states. How feasible is this? Has anyone done it? What are the security concerns with doing this via the net? Thanks - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
MySQL and replication?
Anyone has any experience with mySQL in combination with data replication? Are there products available out there that allows this? Thanks Daniel Åkerud
Re: MySQL Database Replication
On Sat, May 19, 2001 at 01:18:42PM -0500, David Gullett wrote: I have 10 or so MySQL servers in the field, all writing data to a database of the same name. I would like to set up replication from all masters back to a single slave server and have each master write to a different database. Is there an easy way to do this, short of running multiple instances of MySQL on the slave server? Currently, each slave can only have a single master. So you're looking at multiple slave instances. If you don't need completely real-time replication, you might consider rsync or something similar. Jeremy -- Jeremy D. Zawodny, [EMAIL PROTECTED] Technical Yahoo - Yahoo Finance Desk: (408) 349-7878Fax: (408) 349-5454Cell: (408) 439-9951 MySQL 3.23.29: up 5 days, processed 35,090,354 queries (79/sec. avg) - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
MySQL Database Replication
I have 10 or so MySQL servers in the field, all writing data to a database of the same name. I would like to set up replication from all masters back to a single slave server and have each master write to a different database. Is there an easy way to do this, short of running multiple instances of MySQL on the slave server? Thanks, David Gullett Circuits Maximus, LLC. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
