replication issue from ec2 to my network ..

[umapathi b]

Hi,

I have configured replication from EC2 mysql instance to another mysql
instance on  our network via vpn  in between.  Sometimes it is showing no
errors on the slave but the slave falls behind . When I issue the commands
stop slave ; start slave ; it again catches up with the master.

What is the reason for this ?  how to resolve this ?

Thanks,
Umapathi.
umapath...@gmail.com

Re: Replication issue

[Carl]

Thank you for the information and script.  I will try it out tonight when 
traffic stops.


Thanks,

Carl

- Original Message - 
From: "Reindl Harald" 

To: "Carl" 
Cc: 
Sent: Wednesday, February 16, 2011 7:47 AM
Subject: Re: Replication issue



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: Replication issue

[Reindl Harald]

Am 16.02.2011 13:39, schrieb Carl:
> I was describing how long it takes to do a mysqldump, move the data, 
> load the data in the slave and then restart the slave.  

I would never do this with dumps because

* text-files -> *br*
* size
* overhead

Really important is that you stop the slave before
you stop the master so no newer files can be
on the slave and you probably are very fast
rsync the backup from the master because here also
only diffs going over the network

Below my default-script for re-init a mysql-replication
make sure modify datadir and service-comamnd on non redhat

after that you have under /datadir-bkp/ a 100% consistent copy
without any binlogs and a running master with a fresh binlog

use "--compress" while rsync this backup to your slave
_

echo ""
echo "prepare"
date
rsync --times --perms --owner --group --recursive --delete-after /datadir/ 
/datadir-bkp/
date
echo ""
echo ""

if ([ "$1" != "really" ])
 then
  echo "Please use 'really' as Param to make the cold backup"
  exit
fi

echo "stopping mysqld and make cold backup"
date
echo ""
echo ""

service mysqld stop
cd /datadir/
rm -f /datadir/bin*
rsync --progress --times --perms --owner --group --recursive --delete-after 
/datadir/ /datadir-bkp/
service mysqld start


echo ""
echo ""
echo "backup finsihed and mysqld startet"
date
echo ""
echo ""


I have never used the rsync process... I will try it out in the in the middle 
of the night when I have
> time to recover from a screwup.  Who says systems people need sleep!
> 
> Thanks,
> 
> Carl
> - Original Message - From: "Reindl Harald" 
> To: "Carl" 
> Cc: 
> Sent: Wednesday, February 16, 2011 7:02 AM
> Subject: Re: Replication issue
> 
> 

-- 

Mit besten Grüßen, Reindl Harald
the lounge interactive design GmbH
A-1060 Vienna, Hofmühlgasse 17
CTO / software-development / cms-solutions
p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40
icq: 154546673, http://www.thelounge.net/



signature.asc
Description: OpenPGP digital signature

Re: Replication issue

[Carl]

I was describing how long it takes to do a mysqldump, move the data, load 
the data in the slave and then restart the slave.  I have never used the 
rsync process... I will try it out in the in the middle of the night when I 
have time to recover from a screwup.  Who says systems people need sleep!


Thanks,

Carl
- Original Message - 
From: "Reindl Harald" 

To: "Carl" 
Cc: 
Sent: Wednesday, February 16, 2011 7:02 AM
Subject: Re: Replication issue



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: Replication issue

[Reindl Harald]

I can not believe that this would take 24 hours
since rsync with compression is very efficient
and on the other hand - who cares, the master
is not down if you do this in the order i described

Am 16.02.2011 12:57, schrieb Carl:
>> are you saying to restart the slave in question from a good copy of the
>> master that I know to be good?
> 
> Reindl Harald replied:
> 
> yes!
> 
> there is a reason why the salve stops to work and in my opinion
> the only save way to get a 100% clean slave is clone it again
> from the stopped master
> 
> Carl:
> 
> I was hoping to avoid that because it approximately 24 hours to move the 
> master data to the slave.
> I know that is the only way to be certain they are sync'd but is there any 
> other way?



signature.asc
Description: OpenPGP digital signature

Re: Replication issue

[Carl]

are you saying to restart the slave in question from a good copy of the
master that I know to be good?


Reindl Harald replied:

yes!

there is a reason why the salve stops to work and in my opinion
the only save way to get a 100% clean slave is clone it again
from the stopped master

Carl:

I was hoping to avoid that because it approximately 24 hours to move the 
master data to the slave.
I know that is the only way to be certain they are sync'd but is there any 
other way?


Thanks,

Carl


- Original Message - 
From: "Reindl Harald" 

To: "Carl" 
Cc: 
Sent: Wednesday, February 16, 2011 6:40 AM
Subject: Re: Replication issue



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: Replication issue

[Reindl Harald]

Am 16.02.2011 12:36, schrieb Carl:
> are you saying to restart the slave in question from a good copy of the
> master that I know to be good?

yes!

there is a reason why the salve stops to work and in my opinion
the only save way to get a 100% clean slave is clone it again
from the stopped master



signature.asc
Description: OpenPGP digital signature

Re: Replication issue

[Reindl Harald]

Am 16.02.2011 12:33, schrieb Carl:
> The max_allowed_packet setting is the same on both.

the question is how large the setting is
we have 200M on all machines

> I have tried restarting the slave... didn't work

after replication errors you should every time

* stop the slave
* "hot" rsync the dadadir on the master
* stop the master
* "cold" rsync to get last changes
* remove binlog files in datadir und backup
* start the master
* rsync the backup to the slave
* start the slave
* restart replication

this way the downtime of the master is very short because
the second rsync must only copy changes since the first run



signature.asc
Description: OpenPGP digital signature

Re: Replication issue

[Carl]

I am not quite certain I understand your suggestion:

Forget workarounds to solve replication errors
and re-init you replication if you will be sure
it is really consistent

When you say re-init the replication, are you saying to restart the slave in 
question from a good copy of the master that I know to be good?


Just trying to be really careful.

Thanks,

Carl


- Original Message - 
From: "Reindl Harald" 

To: "Carl" 
Cc: 
Sent: Wednesday, February 16, 2011 6:24 AM
Subject: Re: Replication issue



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: Replication issue

[Carl]

The max_allowed_packet setting is the same on both.

I have tried restarting the slave... didn't work.  I can bounce the master.

Thanks,

Carl


- Original Message - 
From: "Elizabeth Mattijsen" 

To: "Carl" 
Cc: 
Sent: Wednesday, February 16, 2011 6:23 AM
Subject: Re: Replication issue


First make sure that the "max_allowed_packet" setting is the same on both 
masters.


Make sure that setting is active on the slave in question.  Then start 
replication or bounce the master (not sure which I did to fix this the last 
time I ran into this).



Elizabeth Mattijsen
=
On Feb 16, 2011, at 12:20 PM, Carl wrote:
I am running master - master replication between two locations using MySQL 
version 5.1.41 on Slackware Linux 13 (64bit).


The problem from show slave status is:

  Last_Error: Relay log read failure: Could not parse 
relay log event entry. The possible reasons are: the master's binary log 
is corrupted (you can check this by running 'mysqlbinlog' on the binary 
log), the slave's relay log is corrupted (you can check this by running 
'mysqlbinlog' on the relay log), a network problem, or a bug in the 
master's or slave's MySQL code. If you want to check the master's binary 
log or slave's relay log, you will be able to know their names by issuing 
'SHOW SLAVE STATUS' on this slave.

Skip_Counter: 1
 Exec_Master_Log_Pos: 552321409
 Relay_Log_Space: 165412833
 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
Master_SSL_Verify_Server_Cert: No
   Last_IO_Errno: 1236
   Last_IO_Error: Got fatal error 1236 from master when 
reading data from binary log: 'log event entry exceeded 
max_allowed_packet; Increase max_allowed_packet on master'

  Last_SQL_Errno: 1594
  Last_SQL_Error: Relay log read failure: Could not parse 
relay log event entry. The possible reasons are: the master's binary log 
is corrupted (you can check this by running 'mysqlbinlog' on the binary 
log), the slave's relay log is corrupted (you can check this by running 
'mysqlbinlog' on the relay log), a network problem, or a bug in the 
master's or slave's MySQL code. If you want to check the master's binary 
log or slave's relay log, you will be able to know their names by issuing 
'SHOW SLAVE STATUS' on this slave.


I have tried telling it to skip that transaction (set global 
sql_slave_skip_counter = 1) to no avail.


From what I have been able to determine from searching the Internet, it 
appears that the replication is failing replicating blobs ahich are 
basically jpg's of members.  If I understand the problem, it is caused by 
blob containing a character which is the same character that is used to 
mark the end of a transaction in the bin log.


My questions: 1) Is this a reasonable/correct analysis and 2) how do I 
work around the issue?


Thanks,

Carl








--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: Replication issue

[Elizabeth Mattijsen]

First make sure that the "max_allowed_packet" setting is the same on both 
masters.

Make sure that setting is active on the slave in question.  Then start 
replication or bounce the master (not sure which I did to fix this the last 
time I ran into this).


Elizabeth Mattijsen
=
On Feb 16, 2011, at 12:20 PM, Carl wrote:
> I am running master - master replication between two locations using MySQL 
> version 5.1.41 on Slackware Linux 13 (64bit).
> 
> The problem from show slave status is:
> 
>   Last_Error: Relay log read failure: Could not parse relay 
> log event entry. The possible reasons are: the master's binary log is 
> corrupted (you can check this by running 'mysqlbinlog' on the binary log), 
> the slave's relay log is corrupted (you can check this by running 
> 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's 
> or slave's MySQL code. If you want to check the master's binary log or 
> slave's relay log, you will be able to know their names by issuing 'SHOW 
> SLAVE STATUS' on this slave.
> Skip_Counter: 1
>  Exec_Master_Log_Pos: 552321409
>  Relay_Log_Space: 165412833
>  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
> Master_SSL_Verify_Server_Cert: No
>Last_IO_Errno: 1236
>Last_IO_Error: Got fatal error 1236 from master when reading 
> data from binary log: 'log event entry exceeded max_allowed_packet; Increase 
> max_allowed_packet on master'
>   Last_SQL_Errno: 1594
>   Last_SQL_Error: Relay log read failure: Could not parse relay 
> log event entry. The possible reasons are: the master's binary log is 
> corrupted (you can check this by running 'mysqlbinlog' on the binary log), 
> the slave's relay log is corrupted (you can check this by running 
> 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's 
> or slave's MySQL code. If you want to check the master's binary log or 
> slave's relay log, you will be able to know their names by issuing 'SHOW 
> SLAVE STATUS' on this slave.
> 
> I have tried telling it to skip that transaction (set global 
> sql_slave_skip_counter = 1) to no avail.
> 
> From what I have been able to determine from searching the Internet, it 
> appears that the replication is failing replicating blobs ahich are basically 
> jpg's of members.  If I understand the problem, it is caused by blob 
> containing a character which is the same character that is used to mark the 
> end of a transaction in the bin log.
> 
> My questions: 1) Is this a reasonable/correct analysis and 2) how do I work 
> around the issue?
> 
> Thanks,
> 
> Carl
> 
> 
> 
> 


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: Replication issue

[Reindl Harald]

Got fatal error 1236 from master when reading data from binary log:
'log event entry exceeded max_allowed_packet; Increase max_allowed_packet on 
master

So do this in your my.cnf :-)

Forget workarounds to solve replication errors
and re-init you replication if you will be sure
it is really consistent

Am 16.02.2011 12:20, schrieb Carl:
> I am running master - master replication between two locations using MySQL 
> version 5.1.41 
> on Slackware Linux 13 (64bit).
> 
> The problem from show slave status is:
> 
>Last_Error: Relay log read failure: Could not parse relay 
> log event entry. The possible reasons are: the master's binary log is 
> corrupted (you can check this by running 'mysqlbinlog' on the binary log), 
> the slave's relay log is corrupted (you can check this by running 
> 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's 
> or slave's MySQL code. If you want to check the master's binary log or 
> slave's relay log, you will be able to know their names by issuing 'SHOW 
> SLAVE STATUS' on this slave.
>  Skip_Counter: 1
>   Exec_Master_Log_Pos: 552321409
>   Relay_Log_Space: 165412833
>   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
> Master_SSL_Verify_Server_Cert: No
> Last_IO_Errno: 1236
> Last_IO_Error: Got fatal error 1236 from master when reading 
> data from binary log: 'log event entry exceeded max_allowed_packet; Increase 
> max_allowed_packet on master'
>Last_SQL_Errno: 1594
>Last_SQL_Error: Relay log read failure: Could not parse relay 
> log event entry. The possible reasons are: the master's binary log is 
> corrupted (you can check this by running 'mysqlbinlog' on the binary log), 
> the slave's relay log is corrupted (you can check this by running 
> 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's 
> or slave's MySQL code. If you want to check the master's binary log or 
> slave's relay log, you will be able to know their names by issuing 'SHOW 
> SLAVE STATUS' on this slave.
> 
> I have tried telling it to skip that transaction (set global 
> sql_slave_skip_counter = 1) to no avail.
> 
> From what I have been able to determine from searching the Internet, it 
> appears that the replication is failing replicating blobs ahich are basically 
> jpg's of members.  If I understand the problem, it is caused by blob 
> containing a character which is the same character that is used to mark the 
> end of a transaction in the bin log.
> 
> My questions: 1) Is this a reasonable/correct analysis and 2) how do I work 
> around the issue?
> 
> Thanks,
> 
> Carl
> 
> 
> 
> 
> 

-- 

Mit besten Grüßen, Reindl Harald
the lounge interactive design GmbH
A-1060 Vienna, Hofmühlgasse 17
CTO / software-development / cms-solutions
p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40
icq: 154546673, http://www.thelounge.net/



signature.asc
Description: OpenPGP digital signature

Re: Replication issue

[Suresh Kuna]

Run the change master again to get the relay logs from master server again.

On Wed, Feb 16, 2011 at 4:50 PM, Carl  wrote:

> I am running master - master replication between two locations using MySQL
> version 5.1.41 on Slackware Linux 13 (64bit).
>
> The problem from show slave status is:
>
>   Last_Error: Relay log read failure: Could not parse relay
> log event entry. The possible reasons are: the master's binary log is
> corrupted (you can check this by running 'mysqlbinlog' on the binary log),
> the slave's relay log is corrupted (you can check this by running
> 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's
> or slave's MySQL code. If you want to check the master's binary log or
> slave's relay log, you will be able to know their names by issuing 'SHOW
> SLAVE STATUS' on this slave.
> Skip_Counter: 1
>  Exec_Master_Log_Pos: 552321409
>  Relay_Log_Space: 165412833
>  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
> Master_SSL_Verify_Server_Cert: No
>Last_IO_Errno: 1236
>Last_IO_Error: Got fatal error 1236 from master when reading
> data from binary log: 'log event entry exceeded max_allowed_packet; Increase
> max_allowed_packet on master'
>   Last_SQL_Errno: 1594
>   Last_SQL_Error: Relay log read failure: Could not parse relay
> log event entry. The possible reasons are: the master's binary log is
> corrupted (you can check this by running 'mysqlbinlog' on the binary log),
> the slave's relay log is corrupted (you can check this by running
> 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's
> or slave's MySQL code. If you want to check the master's binary log or
> slave's relay log, you will be able to know their names by issuing 'SHOW
> SLAVE STATUS' on this slave.
>
> I have tried telling it to skip that transaction (set global
> sql_slave_skip_counter = 1) to no avail.
>
> From what I have been able to determine from searching the Internet, it
> appears that the replication is failing replicating blobs ahich are
> basically jpg's of members.  If I understand the problem, it is caused by
> blob containing a character which is the same character that is used to mark
> the end of a transaction in the bin log.
>
> My questions: 1) Is this a reasonable/correct analysis and 2) how do I work
> around the issue?
>
> Thanks,
>
> Carl
>
>
>
>
>


-- 
Thanks
Suresh Kuna
MySQL DBA

Replication issue

[Carl]

I am running master - master replication between two locations using MySQL 
version 5.1.41 on Slackware Linux 13 (64bit).

The problem from show slave status is:

   Last_Error: Relay log read failure: Could not parse relay 
log event entry. The possible reasons are: the master's binary log is corrupted 
(you can check this by running 'mysqlbinlog' on the binary log), the slave's 
relay log is corrupted (you can check this by running 'mysqlbinlog' on the 
relay log), a network problem, or a bug in the master's or slave's MySQL code. 
If you want to check the master's binary log or slave's relay log, you will be 
able to know their names by issuing 'SHOW SLAVE STATUS' on this slave.
 Skip_Counter: 1
  Exec_Master_Log_Pos: 552321409
  Relay_Log_Space: 165412833
  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
Master_SSL_Verify_Server_Cert: No
Last_IO_Errno: 1236
Last_IO_Error: Got fatal error 1236 from master when reading 
data from binary log: 'log event entry exceeded max_allowed_packet; Increase 
max_allowed_packet on master'
   Last_SQL_Errno: 1594
   Last_SQL_Error: Relay log read failure: Could not parse relay 
log event entry. The possible reasons are: the master's binary log is corrupted 
(you can check this by running 'mysqlbinlog' on the binary log), the slave's 
relay log is corrupted (you can check this by running 'mysqlbinlog' on the 
relay log), a network problem, or a bug in the master's or slave's MySQL code. 
If you want to check the master's binary log or slave's relay log, you will be 
able to know their names by issuing 'SHOW SLAVE STATUS' on this slave.

I have tried telling it to skip that transaction (set global 
sql_slave_skip_counter = 1) to no avail.

>From what I have been able to determine from searching the Internet, it 
>appears that the replication is failing replicating blobs ahich are basically 
>jpg's of members.  If I understand the problem, it is caused by blob 
>containing a character which is the same character that is used to mark the 
>end of a transaction in the bin log.

My questions: 1) Is this a reasonable/correct analysis and 2) how do I work 
around the issue?

Thanks,

Carl

Re: Replication Issue with Upgrade from 4.0.x to 5.0.x

[dpgirago]

> Dave:
> There are no uncommented entries in /etc/hosts.deny
>
> Baron:
> The all servers have a unique server-id in their respective my.cnf's
>
> When I try to connect directly from the slave to the new master, I get: 
>
> ERROR 2003 (HY000): Can't connect to MySQL server on '1xx.1xx.1xx.xx' 
(113)
>
> I'll make a super user to test... 

Duh. I needed to explicitly allow port 3306 on the new master.

Thanks for the hints, guys.

David

Re: Replication Issue with Upgrade from 4.0.x to 5.0.x

[dpgirago]

David Campbell wrote:
> [EMAIL PROTECTED] wrote:
>> I'm in process of upgrading a master server from 4.0.24-log to 
5.0.22-log 
>> in a single master-slave environment.  I've previously upgraded the 
slave 
>> to 5.0.22-log and restarted replication without issue. 
>> 
>> The current master is running on RH9 and the slave is running on CentOS 
5, 
>> which is what I'm trying to upgrade the master to, also. 
>> 
>> After synchronizing the databases, I've run 'reset master' and 'reset 
>> slave' on their respective servers, then 'change master to...' on the 
>> slave, but 'show slave status' always displays:   'Slave_IO_Running: 
No'
>> 
>> And here is the log entry from the slave:
>> 
>> 071113  9:16:19 [ERROR] Slave I/O thread: error connecting to master 
>> '[EMAIL PROTECTED]:3306': Error: 'Lost connection to MySQL server 

>> during query'  errno: 2013  retry-time: 60  retries: 86400
>> 071113  9:17:35 [Note] Slave I/O thread killed while connecting to 
master>

> grep deny /etc/hosts.deny

> Dave

Dave:
There are no uncommented entries in /etc/hosts.deny

Baron:
The all servers have a unique server-id in their respective my.cnf's


When I try to connect directly from the slave to the new master, I get: 

ERROR 2003 (HY000): Can't connect to MySQL server on '1xx.1xx.1xx.xx' (113)

I'll make a super user to test... 

David

Re: Replication Issue with Upgrade from 4.0.x to 5.0.x

[David Campbell]

[EMAIL PROTECTED] wrote:
I'm in process of upgrading a master server from 4.0.24-log to 5.0.22-log 
in a single master-slave environment.  I've previously upgraded the slave 
to 5.0.22-log and restarted replication without issue. 

The current master is running on RH9 and the slave is running on CentOS 5, 
which is what I'm trying to upgrade the master to, also. 

After synchronizing the databases, I've run 'reset master' and 'reset 
slave' on their respective servers, then 'change master to...' on the 
slave, but 'show slave status' always displays:   'Slave_IO_Running: No'


And here is the log entry from the slave:

071113  9:16:19 [ERROR] Slave I/O thread: error connecting to master 
'[EMAIL PROTECTED]:3306': Error: 'Lost connection to MySQL server 
during query'  errno: 2013  retry-time: 60  retries: 86400

071113  9:17:35 [Note] Slave I/O thread killed while connecting to master


grep deny /etc/hosts.deny

Dave

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Replication Issue with Upgrade from 4.0.x to 5.0.x

[Baron Schwartz]

Hi,

[EMAIL PROTECTED] wrote:
I'm in process of upgrading a master server from 4.0.24-log to 5.0.22-log 
in a single master-slave environment.  I've previously upgraded the slave 
to 5.0.22-log and restarted replication without issue. 

The current master is running on RH9 and the slave is running on CentOS 5, 
which is what I'm trying to upgrade the master to, also. 

After synchronizing the databases, I've run 'reset master' and 'reset 
slave' on their respective servers, then 'change master to...' on the 
slave, but 'show slave status' always displays:   'Slave_IO_Running: No'


And here is the log entry from the slave:

071113  9:16:19 [ERROR] Slave I/O thread: error connecting to master 
'[EMAIL PROTECTED]:3306': Error: 'Lost connection to MySQL server 
during query'  errno: 2013  retry-time: 60  retries: 86400

071113  9:17:35 [Note] Slave I/O thread killed while connecting to master

The replication user has 'replication slave' privileges, and basically 
I've duplicated my.cnf from the old to the new master.


I've done some Googling and searching of archives but not much luck.

Fortunately, I've been trying out the master upgrade on a temp machine, 
and it's fairly easy to revert back to the current master server. 

But if anyone has thoughts or suggestions about what to try next, I'd be 
most appreciative.


Check the server_id on each server.  Sounds like one or more of the 
servers either doesn't have it explicitly set in my.cnf, or there is a 
duplicated server ID somewhere.


Note that the default value doesn't count as "being set" in MySQL 5.  It 
has to be in the my.cnf file.  That's my experience anyway.


Baron

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Replication Issue with Upgrade from 4.0.x to 5.0.x

[dpgirago]

I'm in process of upgrading a master server from 4.0.24-log to 5.0.22-log 
in a single master-slave environment.  I've previously upgraded the slave 
to 5.0.22-log and restarted replication without issue. 

The current master is running on RH9 and the slave is running on CentOS 5, 
which is what I'm trying to upgrade the master to, also. 

After synchronizing the databases, I've run 'reset master' and 'reset 
slave' on their respective servers, then 'change master to...' on the 
slave, but 'show slave status' always displays:   'Slave_IO_Running: No'

And here is the log entry from the slave:

071113  9:16:19 [ERROR] Slave I/O thread: error connecting to master 
'[EMAIL PROTECTED]:3306': Error: 'Lost connection to MySQL server 
during query'  errno: 2013  retry-time: 60  retries: 86400
071113  9:17:35 [Note] Slave I/O thread killed while connecting to master

The replication user has 'replication slave' privileges, and basically 
I've duplicated my.cnf from the old to the new master.

I've done some Googling and searching of archives but not much luck.

Fortunately, I've been trying out the master upgrade on a temp machine, 
and it's fairly easy to revert back to the current master server. 

But if anyone has thoughts or suggestions about what to try next, I'd be 
most appreciative.

Thanks,

David. 

Re: Possible Replication Issue?

[Baron Schwartz]

Brown, Charles wrote:

Mysql Replication is not scope to one database. Rather it was intended
for the entire instance. The slave reads its master's transaction log
and applies those changes. Before it applies the changes, it will query
the master just to make sure the values are the same -- meaning the
master and slave are insyn. Interesting hand-shaking. 


Thanks


Not so, as far as I know.  The binary log is copied to the slave, 
written to the "relay log" on disk, and then another thread on the slave 
reads and executes from the relay log.  It trusts the relay log and 
doesn't further communicate with the master.


If you want to know if a slave is identical to its master, I know of no 
other way to do it than checksumming the data.  I wrote MySQL Table 
Checksum for this purpose (http://sourceforge.net/projects/mysqltoolkit).


Regards
Baron






-Original Message-
From: Baron Schwartz [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, April 24, 2007 9:53 AM

To: Jesse
Cc: MySQL List
Subject: Re: Possible Replication Issue?

Hi Jesse,

Jesse wrote:

I'm running MySQL version 5.0.22-community-nt on a Windows 2003
server.  

I a
noticing A LOT of errors in there like the following:

C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Incorrect 
information

in file: '.\nfcamp\societies.frm'

This spans multiple databases and tables.  I am using replication, but

I

thought that I was replication only one of the databases. It could be

that

it's attempting to replicate these other databases that I don't want
replicated.  It's been a while since I set up the replication, so I

don't

remember where I need to look for this.


It sounds more like you had an ungraceful shutdown or other filesystem 
corruption; replication seems unlikely.  Try CHECK TABLE and/or REPAIR 
TABLE.  You may want to back up what data you still have BEFORE you run 
these :-)  Read the relevant sections of the manual for more help.


Regards
Baron



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Possible Replication Issue?

[Baron Schwartz]

Hi Jesse,

Jesse wrote:
I'm running MySQL version 5.0.22-community-nt on a Windows 2003 server.  
I a

noticing A LOT of errors in there like the following:

C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Incorrect 
information

in file: '.\nfcamp\societies.frm'

This spans multiple databases and tables.  I am using replication, but I
thought that I was replication only one of the databases. It could be that
it's attempting to replicate these other databases that I don't want
replicated.  It's been a while since I set up the replication, so I don't
remember where I need to look for this.


It sounds more like you had an ungraceful shutdown or other filesystem 
corruption; replication seems unlikely.  Try CHECK TABLE and/or REPAIR 
TABLE.  You may want to back up what data you still have BEFORE you run 
these :-)  Read the relevant sections of the manual for more help.


Regards
Baron

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Possible Replication Issue?

[Jesse]

I'm running MySQL version 5.0.22-community-nt on a Windows 2003 server.  I a
noticing A LOT of errors in there like the following:

C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Incorrect information
in file: '.\nfcamp\societies.frm'

This spans multiple databases and tables.  I am using replication, but I
thought that I was replication only one of the databases. It could be that
it's attempting to replicate these other databases that I don't want
replicated.  It's been a while since I set up the replication, so I don't
remember where I need to look for this.

Does anyone have any pointers?

Thanks,
Jesse 



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Replication issue: I/O thread dies immediately after START SLAVE with no logged errors

[Gleb Paharenko]

Hello.



Have you done a FLUSH PRIVILEGES after granting the rights

to the slave user (not needed if you used GRANT clause).



I didn't see this statement in your previous message? 



Do you execute a 'RESET SLAVE' on your slave host, when

you make another attempt to setup the replication? Does replication 

work without replicate-xxx rules? 









Tierney Thurban <[EMAIL PROTECTED]> wrote:

> In response to Gleb Paharenko and Bruce Dembecki:

> 

> Gleb Paharenko wrote:

> 

>>Please send us an output of SHOW MASTER STATUS ans SHOW SLAVE STATUS.

>>Can you reproduce the problem using official binaries?

> 

> I have included the output of those two commands below.  I will try to

> reproduce the problem using non-debian-specific binaries.

> 

> (As a side note, I originally attempted to set these servers up with

> version 4.0.23-4 (debian package) before reinstalling with version

> 4.1.9-2 (debian package), and I appeared to have the same problem in

> both cases.)

> 

> 

> Bruce Dembecki wrote:

> 

>>Looking at your my.cnf files I don't see where you've told the slave what

>>server to connect to. The slave needs to know what server is the master.

>>This is usually accomplished by including a couple of lines in my.cnf.

>>

>> [...]

>>

>>If the master.info file exists and

>>is blank or doesn't include enough information, delete it. If it's there and

>>looks right, include it's contents in your next mail here (you can blank out

>>the username/password info).

> 

> I used the CHANGE MASTER TO command interactively, rather than setting

> the master in the config file.  I assumed that this would be

> sufficient, and from the log on the master (see my original email) it

> does appear that the slave is logging in, at least very briefly.

> 

> I've included the contents of my master.info file below.  It seems

> appropriate to me, but I've never seen one before.  :)

> 

> Thanks,

> 

> Tierney

> 

> 

> mysql> SHOW MASTER STATUS\G

> *** 1. row ***

>File: mysql-bin.01

>Position: 79

>Binlog_Do_DB: replicated

> Binlog_Ignore_DB: mysql,test

> 1 row in set (0.00 sec)

> 

> 

> mysql> SHOW SLAVE STATUS\G

> *** 1. row ***

> Slave_IO_State:

>Master_Host: 192.168.0.19

>Master_User: slave

>Master_Port: 3306

>  Connect_Retry: 60

>Master_Log_File: mysql-bin.01

>Read_Master_Log_Pos: 79

> Relay_Log_File: training1-relay-bin.07

>  Relay_Log_Pos: 4

>  Relay_Master_Log_File: mysql-bin.01

>   Slave_IO_Running: No

>  Slave_SQL_Running: Yes

>Replicate_Do_DB: replicated

>Replicate_Ignore_DB: mysql,test

> 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: 79

>Relay_Log_Space: 4

>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

> 1 row in set (0.00 sec)

> 

> 

> # cat master.info

> 14

> mysql-bin.01

> 79

> 192.168.0.19

> 

> 

> 3306

> 60

> 0

> 

> 

>>Tierney Thurban <[EMAIL PROTECTED]> wrote:

>>

>>>Hi all.  Sorry if you get this twice -- it was posted to

>>>mysql-replication earlier, but it doesn't look like that list is

>>>really used.

>>>

>>>I'm having a problem with my replication setup.  This is my first time

>>>setting up replication, so this may be a simple problem.  I'm using

>>>one master and one slave, both running debian-testing, and they both

>>>have brand new 4.1.9 mysql installs (via apt-get).

>>>

>>>The problem is that each time I do a START SLAVE, the I/O thread dies

>>>almost immediately.  I can see it running only if I do START SLAVE;

>>>SHOW SLAVE STATUS\G on a single line.

>>>

>>>The master's log shows the following each time I START SLAVE or START

>>>SLAVE IO_THREAD:

>>>

>>>6 Connect slave@ on

>>>6 Query   SELECT UNIX_TIMESTAMP()

>>>6 Query   SHOW VARIABLES LIKE 'SERVER_ID'

>>>6 Query   SELECT @@GLOBAL.COLLATION_SERVER

>>>6 Query   SELECT @@GLOBAL.TIME_ZONE

>>>6 Query   SHOW SLAVE HOSTS

>>>6 Quit

>>>

>>>There are no error messages in the .err file on either server, even

>>>with --log-warnings on both.  I've added everything appropriate that

>>>I've been able to find to my.cnf on each server (see below).

>>>

>>>If anyone has 

Re: Replication issue: I/O thread dies immediately after START SLAVE with no logged errors

[Tierney Thurban]

In response to Gleb Paharenko and Bruce Dembecki:

Gleb Paharenko wrote:

>Please send us an output of SHOW MASTER STATUS ans SHOW SLAVE STATUS.
>Can you reproduce the problem using official binaries?

I have included the output of those two commands below.  I will try to
reproduce the problem using non-debian-specific binaries.

(As a side note, I originally attempted to set these servers up with
version 4.0.23-4 (debian package) before reinstalling with version
4.1.9-2 (debian package), and I appeared to have the same problem in
both cases.)


Bruce Dembecki wrote:

>Looking at your my.cnf files I don't see where you've told the slave what
>server to connect to. The slave needs to know what server is the master.
>This is usually accomplished by including a couple of lines in my.cnf.
>
> [...]
>
>If the master.info file exists and
>is blank or doesn't include enough information, delete it. If it's there and
>looks right, include it's contents in your next mail here (you can blank out
>the username/password info).

I used the CHANGE MASTER TO command interactively, rather than setting
the master in the config file.  I assumed that this would be
sufficient, and from the log on the master (see my original email) it
does appear that the slave is logging in, at least very briefly.

I've included the contents of my master.info file below.  It seems
appropriate to me, but I've never seen one before.  :)

Thanks,

Tierney


mysql> SHOW MASTER STATUS\G
*** 1. row ***
File: mysql-bin.01
Position: 79
Binlog_Do_DB: replicated
Binlog_Ignore_DB: mysql,test
1 row in set (0.00 sec)


mysql> SHOW SLAVE STATUS\G
*** 1. row ***
 Slave_IO_State:
Master_Host: 192.168.0.19
Master_User: slave
Master_Port: 3306
  Connect_Retry: 60
Master_Log_File: mysql-bin.01
Read_Master_Log_Pos: 79
 Relay_Log_File: training1-relay-bin.07
  Relay_Log_Pos: 4
  Relay_Master_Log_File: mysql-bin.01
   Slave_IO_Running: No
  Slave_SQL_Running: Yes
Replicate_Do_DB: replicated
Replicate_Ignore_DB: mysql,test
 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: 79
Relay_Log_Space: 4
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
1 row in set (0.00 sec)


# cat master.info
14
mysql-bin.01
79
192.168.0.19


3306
60
0


>Tierney Thurban <[EMAIL PROTECTED]> wrote:
>
>>Hi all.  Sorry if you get this twice -- it was posted to
>>mysql-replication earlier, but it doesn't look like that list is
>>really used.
>>
>>I'm having a problem with my replication setup.  This is my first time
>>setting up replication, so this may be a simple problem.  I'm using
>>one master and one slave, both running debian-testing, and they both
>>have brand new 4.1.9 mysql installs (via apt-get).
>>
>>The problem is that each time I do a START SLAVE, the I/O thread dies
>>almost immediately.  I can see it running only if I do START SLAVE;
>>SHOW SLAVE STATUS\G on a single line.
>>
>>The master's log shows the following each time I START SLAVE or START
>>SLAVE IO_THREAD:
>>
>>6 Connect slave@ on
>>6 Query   SELECT UNIX_TIMESTAMP()
>>6 Query   SHOW VARIABLES LIKE 'SERVER_ID'
>>6 Query   SELECT @@GLOBAL.COLLATION_SERVER
>>6 Query   SELECT @@GLOBAL.TIME_ZONE
>>6 Query   SHOW SLAVE HOSTS
>>6 Quit
>>
>>There are no error messages in the .err file on either server, even
>>with --log-warnings on both.  I've added everything appropriate that
>>I've been able to find to my.cnf on each server (see below).
>>
>>If anyone has any suggestions, please let me know -- I've been looking
>>through docs and mailing lists for quite some time now, with no luck.
>>
>>Thanks,
>>
>>Tierney
>>
>>Here's what I did to set up replication:
>>
>>I added / changed a number of fields in my.cnf on both machines (see below).
>>
>>Master:
>>Started mysqld.
>>Created a new database, a new table, and put a single row in it.
>>Created a slave account:
>>  GRANT REPLICATION SLAVE ON *.* TO 'slave'@'%' IDENTIFIED BY 'x'
>>Locked the database:
>>  FLUSH TABLES WITH READ LOCK
>>Tar'd the /replicated directory and transferred it to the slave.
>>Checked the binlog file and position and unlocked the database:
>>  SHOW MASTER STATUS
>>  UNLOCK TABLES
>>
>>Slave:

Re: Replication issue: I/O thread dies immediately after START SLAVE with no logged errors

[Bruce Dembecki]

Looking at your my.cnf files I don't see where you've told the slave what
server to connect to. The slave needs to know what server is the master.
This is usually accomplished by including a couple of lines in my.cnf.

If the file master.info is in the data directory it will override the my.cnf
settings because it contains more information.

So you either need to add lines like:

master-host = hostname
master-user = username
master-password = password

to my.cnf on the slave or add an appropriately formatted and constructed
master.info file to the data directory. If the master.info file exists and
is blank or doesn't include enough information, delete it. If it's there and
looks right, include it's contents in your next mail here (you can blank out
the username/password info).

Best Regards, Bruce

Tierney Thurban <[EMAIL PROTECTED]> wrote:
> Hi all.  Sorry if you get this twice -- it was posted to
> mysql-replication earlier, but it doesn't look like that list is
> really used.
> 
> I'm having a problem with my replication setup.  This is my first time
> setting up replication, so this may be a simple problem.  I'm using
> one master and one slave, both running debian-testing, and they both
> have brand new 4.1.9 mysql installs (via apt-get).
> 
> The problem is that each time I do a START SLAVE, the I/O thread dies
> almost immediately.  I can see it running only if I do START SLAVE;
> SHOW SLAVE STATUS\G on a single line.


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Replication issue: I/O thread dies immediately after START SLAVE with no logged errors

[Gleb Paharenko]

Hello.



Please send us an output of SHOW MASTER STATUS ans SHOW SLAVE STATUS.

Can you reproduce the problem using official binaries?







Tierney Thurban <[EMAIL PROTECTED]> wrote:

> Hi all.  Sorry if you get this twice -- it was posted to

> mysql-replication earlier, but it doesn't look like that list is

> really used.

> 

> I'm having a problem with my replication setup.  This is my first time

> setting up replication, so this may be a simple problem.  I'm using

> one master and one slave, both running debian-testing, and they both

> have brand new 4.1.9 mysql installs (via apt-get).

> 

> The problem is that each time I do a START SLAVE, the I/O thread dies

> almost immediately.  I can see it running only if I do START SLAVE;

> SHOW SLAVE STATUS\G on a single line.

> 

> The master's log shows the following each time I START SLAVE or START

> SLAVE IO_THREAD:

> 

> 6 Connect slave@ on

> 6 Query   SELECT UNIX_TIMESTAMP()

> 6 Query   SHOW VARIABLES LIKE 'SERVER_ID'

> 6 Query   SELECT @@GLOBAL.COLLATION_SERVER

> 6 Query   SELECT @@GLOBAL.TIME_ZONE

> 6 Query   SHOW SLAVE HOSTS

> 6 Quit

> 

> There are no error messages in the .err file on either server, even

> with --log-warnings on both.  I've added everything appropriate that

> I've been able to find to my.cnf on each server (see below).

> 

> If anyone has any suggestions, please let me know -- I've been looking

> through docs and mailing lists for quite some time now, with no luck.

> 

> Thanks,

> 

> Tierney

> 

> Here's what I did to set up replication:

> 

> I added / changed a number of fields in my.cnf on both machines (see below).

> 

> Master:

> Started mysqld.

> Created a new database, a new table, and put a single row in it.

> Created a slave account:

>   GRANT REPLICATION SLAVE ON *.* TO 'slave'@'%' IDENTIFIED BY 'x'

> Locked the database:

>   FLUSH TABLES WITH READ LOCK

> Tar'd the /replicated directory and transferred it to the slave.

> Checked the binlog file and position and unlocked the database:

>   SHOW MASTER STATUS

>   UNLOCK TABLES

> 

> Slave:

> Started mysqld.

> Set the master:

>   CHANGE MASTER TO

> MASTER_HOST='',

> MASTER_USER='slave',

> MASTER_PASSWORD='x',

> MASTER_LOG_FILE='',

> MASTER_LOG_POS=;

> Began replication:

>   START SLAVE;

> 

> Master's my.cnf (comment lines removed):

> 

> [client]

> port= 3306

> socket  = /var/run/mysqld/mysqld.sock

> 

> [mysqld_safe]

> socket  = /var/run/mysqld/mysqld.sock

> nice= 0

> 

> [mysqld]

> user= mysql

> pid-file= /var/run/mysqld/mysqld.pid

> socket  = /var/run/mysqld/mysqld.sock

> port= 3306

> log = /var/log/mysql/mysql.log

> basedir = /usr

> datadir = /var/lib/mysql

> tmpdir  = /tmp

> language= /usr/share/mysql/english

> skip-external-locking

> 

> old-passwords   = 1

> 

> key_buffer  = 16M

> max_allowed_packet  = 16M

> thread_stack= 128K

> 

> query_cache_limit   = 1048576

> query_cache_size= 26214400

> query_cache_type= 1

> 

> server-id   = 1

> log-bin = /var/log/mysql/mysql-bin.log

> binlog-do-db= replicated

> log-warnings

> binlog-ignore-db= mysql

> binlog-ignore-db= test

> 

> [mysqldump]

> quick

> quote-names

> max_allowed_packet  = 16M

> 

> [mysql]

> 

> [isamchk]

> key_buffer  = 16M

> 

> Slave's my.cnf (comment lines removed)

> 

> [client]

> port= 3306

> socket  = /var/run/mysqld/mysqld.sock

> 

> [mysqld_safe]

> socket  = /var/run/mysqld/mysqld.sock

> nice= 0

> 

> [mysqld]

> user= mysql

> pid-file= /var/run/mysqld/mysqld.pid

> socket  = /var/run/mysqld/mysqld.sock

> port= 3306

> log = /var/log/mysql/mysql.log

> basedir = /usr

> datadir = /var/lib/mysql

> tmpdir  = /tmp

> language= /usr/share/mysql/english

> skip-external-locking

> 

> old-passwords   = 1

> 

> key_buffer  = 16M

> max_allowed_packet  = 16M

> thread_stack= 128K

> 

> query_cache_limit   = 1048576

> query_cache_size= 26214400

> query_cache_type= 1

> 

> server-id   = 2

> replicate-do-db = replicated

> replicate-ignore-db = mysql

> replicate-ignore-db = test

> log-warnings

> log-bin = /var/log/mysql/mysql-bin.log

> 

> [mysqldump]

> quick

> quote-names

> max_allowed_packet  = 16M

> 

> [mysql]

> 

> [isamchk]

> key_buffer  = 16M

> 



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Gleb Paharenko
 / /|_/ / // /\ 

Replication issue: I/O thread dies immediately after START SLAVE with no logged errors

[Tierney Thurban]

Hi all.  Sorry if you get this twice -- it was posted to
mysql-replication earlier, but it doesn't look like that list is
really used.

I'm having a problem with my replication setup.  This is my first time
setting up replication, so this may be a simple problem.  I'm using
one master and one slave, both running debian-testing, and they both
have brand new 4.1.9 mysql installs (via apt-get).

The problem is that each time I do a START SLAVE, the I/O thread dies
almost immediately.  I can see it running only if I do START SLAVE;
SHOW SLAVE STATUS\G on a single line.

The master's log shows the following each time I START SLAVE or START
SLAVE IO_THREAD:

6 Connect slave@ on
6 Query   SELECT UNIX_TIMESTAMP()
6 Query   SHOW VARIABLES LIKE 'SERVER_ID'
6 Query   SELECT @@GLOBAL.COLLATION_SERVER
6 Query   SELECT @@GLOBAL.TIME_ZONE
6 Query   SHOW SLAVE HOSTS
6 Quit

There are no error messages in the .err file on either server, even
with --log-warnings on both.  I've added everything appropriate that
I've been able to find to my.cnf on each server (see below).

If anyone has any suggestions, please let me know -- I've been looking
through docs and mailing lists for quite some time now, with no luck.

Thanks,

Tierney

Here's what I did to set up replication:

I added / changed a number of fields in my.cnf on both machines (see below).

Master:
 Started mysqld.
 Created a new database, a new table, and put a single row in it.
 Created a slave account:
   GRANT REPLICATION SLAVE ON *.* TO 'slave'@'%' IDENTIFIED BY 'x'
 Locked the database:
   FLUSH TABLES WITH READ LOCK
 Tar'd the /replicated directory and transferred it to the slave.
 Checked the binlog file and position and unlocked the database:
   SHOW MASTER STATUS
   UNLOCK TABLES

Slave:
 Started mysqld.
 Set the master:
   CHANGE MASTER TO
 MASTER_HOST='',
 MASTER_USER='slave',
 MASTER_PASSWORD='x',
 MASTER_LOG_FILE='',
 MASTER_LOG_POS=;
 Began replication:
   START SLAVE;

Master's my.cnf (comment lines removed):

[client]
port= 3306
socket  = /var/run/mysqld/mysqld.sock

[mysqld_safe]
socket  = /var/run/mysqld/mysqld.sock
nice= 0

[mysqld]
user= mysql
pid-file= /var/run/mysqld/mysqld.pid
socket  = /var/run/mysqld/mysqld.sock
port= 3306
log = /var/log/mysql/mysql.log
basedir = /usr
datadir = /var/lib/mysql
tmpdir  = /tmp
language= /usr/share/mysql/english
skip-external-locking

old-passwords   = 1

key_buffer  = 16M
max_allowed_packet  = 16M
thread_stack= 128K

query_cache_limit   = 1048576
query_cache_size= 26214400
query_cache_type= 1

server-id   = 1
log-bin = /var/log/mysql/mysql-bin.log
binlog-do-db= replicated
log-warnings
binlog-ignore-db= mysql
binlog-ignore-db= test

[mysqldump]
quick
quote-names
max_allowed_packet  = 16M

[mysql]

[isamchk]
key_buffer  = 16M

Slave's my.cnf (comment lines removed)

[client]
port= 3306
socket  = /var/run/mysqld/mysqld.sock

[mysqld_safe]
socket  = /var/run/mysqld/mysqld.sock
nice= 0

[mysqld]
user= mysql
pid-file= /var/run/mysqld/mysqld.pid
socket  = /var/run/mysqld/mysqld.sock
port= 3306
log = /var/log/mysql/mysql.log
basedir = /usr
datadir = /var/lib/mysql
tmpdir  = /tmp
language= /usr/share/mysql/english
skip-external-locking

old-passwords   = 1

key_buffer  = 16M
max_allowed_packet  = 16M
thread_stack= 128K

query_cache_limit   = 1048576
query_cache_size= 26214400
query_cache_type= 1

server-id   = 2
replicate-do-db = replicated
replicate-ignore-db = mysql
replicate-ignore-db = test
log-warnings
log-bin = /var/log/mysql/mysql-bin.log

[mysqldump]
quick
quote-names
max_allowed_packet  = 16M

[mysql]

[isamchk]
key_buffer  = 16M

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Replication Issue

[Friedhelm Betz]

Randy Johnson wrote:
Here is the url sorry:
http://dev.mysql.com/doc/mysql/en/Replication_Compatibility.html

Does this table say that mysql 3.23.33 and up is not compatible to replicate
to a mysql 5.0 slave?
Yes
Friedhelm

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

RE: Replication Issue

[Randy Johnson]

Here is the url sorry:

http://dev.mysql.com/doc/mysql/en/Replication_Compatibility.html


-Original Message-
From: Randy Johnson [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 27, 2004 2:07 PM
To: [EMAIL PROTECTED]
Subject: RE: Replication Issue


Does this table say that mysql 3.23.33 and up is not compatible to replicate
to a mysql 5.0 slave?

Thanks!

Randy

-Original Message-
From: Egor Egorov [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 27, 2004 12:21 PM
To: [EMAIL PROTECTED]
Subject: Re: Replication Issue


"Randy Johnson" <[EMAIL PROTECTED]> wrote:



> I have mysql master and mysql slave on same machine running
> separately.

> I have master and slave setup.

> I was able to do the  LOAD DATA FROM MASTER;

> 

> to get the data but the data does not replicate after that. =20

> 

> Looking at the info below can you tell why replication is not taking =

> place.

> Can I provide you with any other information?



Look in the tail of .err file, which may contain some clue info. 



Are you sure that replication slave is running? 



See http://dev.mysql.com/doc/mysql/en/Replication.html, 

most issues are covered there. 



-- 



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Egor Egorov
 / /|_/ / // /\ \/ /_/ / /__   [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]




--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

RE: Replication Issue

[Randy Johnson]

Does this table say that mysql 3.23.33 and up is not compatible to replicate
to a mysql 5.0 slave?

Thanks!

Randy

-Original Message-
From: Egor Egorov [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 27, 2004 12:21 PM
To: [EMAIL PROTECTED]
Subject: Re: Replication Issue


"Randy Johnson" <[EMAIL PROTECTED]> wrote:



> I have mysql master and mysql slave on same machine running 
> separately.

> I have master and slave setup.

> I was able to do the  LOAD DATA FROM MASTER;

> 

> to get the data but the data does not replicate after that. =20

> 

> Looking at the info below can you tell why replication is not taking =

> place.

> Can I provide you with any other information?



Look in the tail of .err file, which may contain some clue info. 



Are you sure that replication slave is running? 



See http://dev.mysql.com/doc/mysql/en/Replication.html, 

most issues are covered there. 



-- 



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Egor Egorov
 / /|_/ / // /\ \/ /_/ / /__   [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]

RE: Replication Issue

[Randy Johnson]

Here is what is in the error log:  looks awful  How do I determine if
slave is running correctly.  I though show Slave status \G did this...



041026  0:19:44  Slave I/O thread killed while reading event
041026  0:19:44  Slave I/O thread exiting, read up to log 'www-bin.001',
position 5685
041026  0:19:44  Error reading relay log event: slave SQL thread was killed
041026  0:20:09  Couldn't fix table with quick recovery: Found wrong number
of deleted records
041026  0:20:09  Run recovery again without -q
041026  0:20:09  Note: Retrying repair of: './dotproject/user_tasks' with
keycache
041026  0:20:09  Couldn't fix table with quick recovery: Found wrong number
of deleted records
041026  0:20:09  Run recovery again without -q
041026  0:20:09  Note: Retrying repair of: './openreports/REPORT' with
keycache
041026  0:20:09  Delete link points outside datafile at 180
041026  0:20:09  Note: Retrying repair of: './openreports/REPORT_CHART' with
keycache
041026  0:20:09  Delete link points outside datafile at 180
041026  0:20:10  Couldn't fix table with quick recovery: Found wrong number
of deleted records
041026  0:20:10  Run recovery again without -q
041026  0:20:10  Note: Retrying repair of: './psa/ClientsTraffic' with
keycache
041026  0:20:10  Couldn't fix table with quick recovery: Found wrong number
of deleted records
041026  0:20:10  Run recovery again without -q
041026  0:20:10  Note: Retrying repair of: './psa/DomainsTraffic' with
keycache
041026  0:20:10  Couldn't fix table with quick recovery: Found wrong number
of deleted records
041026  0:20:10  Run recovery again without -q
041026  0:20:10  Note: Retrying repair of: './psa/IP_Addresses' with
keycache
041026  0:20:11  Couldn't fix table with quick recovery: Found wrong number
of deleted records
041026  0:20:11  Run recovery again without -q
041026  0:20:11  Note: Retrying repair of: './psa/data_bases' with keycache
041026  0:20:11  Delete link points outside datafile at 136
041026  0:20:11  Note: Retrying repair of: './psa/domains' with keycache
041026  0:20:11  Delete link points outside datafile at 136
041026  0:20:11  Delete link points outside datafile at 0
041026  0:20:11  Note: Retrying repair of: './psa/lockout' with keycache
041026  0:20:11  Delete link points outside datafile at 0
041026  0:20:11  Delete link points outside datafile at 0
041026  0:20:11  Note: Retrying repair of: './psa/log_actions' with keycache
041026  0:20:11  Delete link points outside datafile at 0
041026  0:20:11  Delete link points outside datafile at 4700
041026  0:20:11  Delete link points outside datafile at 0
041026  0:20:11  Note: Retrying repair of: './psa/log_components' with
keycache
041026  0:20:11  Delete link points outside datafile at 0
041026  0:20:11  Delete link points outside datafile at 4112
041026  0:20:11  Delete link points outside datafile at 0
041026  0:20:11  Note: Retrying repair of: './psa/mail_redir' with keycache
041026  0:20:11  Delete link points outside datafile at 0
041026  0:20:11  Delete link points outside datafile at 0
041026  0:20:11  Note: Retrying repair of: './psa/sessions' with keycache
041026  0:20:11  Delete link points outside datafile at 0
041026  0:20:12  Couldn't fix table with quick recovery: Found wrong number
of deleted records
041026  0:20:12  Run recovery again without -q
041026  0:20:12  Note: Retrying repair of: './psa/smtp_poplocks' with
keycache
041026  0:20:12  Delete link points outside datafile at 480
041026  0:20:12  Note: Retrying repair of: './psa/sys_users' with keycache
041026  0:20:12  Delete link points outside datafile at 480
041026  0:20:12  Couldn't fix table with quick recovery: Found wrong number
of deleted records
041026  0:20:12  Run recovery again without -q
041026  0:20:12  Note: Retrying repair of: './psa/web_users' with keycache
041026  0:20:13  Delete link points outside datafile at 0
041026  0:20:13  Note: Retrying repair of: './winklink/msg_sent' with
keycache
041026  0:20:13  Delete link points outside datafile at 0
041026  0:20:20  Slave SQL thread initialized, starting replication in log
'www-bin.001' at position 4, relay log './www-relay-bin.01' position: 4
041026  0:20:20  Slave I/O thread: connected to master
'[EMAIL PROTECTED]:3306',  replication started in log 'www-bin.001' at position
4
[EMAIL PROTECTED] mysql5]# 

-Original Message-
From: Egor Egorov [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 27, 2004 12:21 PM
To: [EMAIL PROTECTED]
Subject: Re: Replication Issue


"Randy Johnson" <[EMAIL PROTECTED]> wrote:



> I have mysql master and mysql slave on same machine running 
> separately.

> I have master and slave setup.

> I was able to do the  LOAD DATA FROM MASTER;

>

Re: Replication Issue

[Egor Egorov]

"Randy Johnson" <[EMAIL PROTECTED]> wrote:



> I have mysql master and mysql slave on same machine running separately.

> I have master and slave setup.

> I was able to do the  LOAD DATA FROM MASTER;

> 

> to get the data but the data does not replicate after that. =20

> 

> Looking at the info below can you tell why replication is not taking =

> place.

> Can I provide you with any other information?



Look in the tail of .err file, which may contain some clue info. 



Are you sure that replication slave is running? 



See http://dev.mysql.com/doc/mysql/en/Replication.html, 

most issues are covered there. 



-- 



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Egor Egorov
 / /|_/ / // /\ \/ /_/ / /__   [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]

Replication Issue

[Randy Johnson]

I have mysql master and mysql slave on same machine running separately.

I have master and slave setup.

I was able to do the  LOAD DATA FROM MASTER;

to get the data but the data does not replicate after that.  

Looking at the info below can you tell why replication is not taking place.
Can I provide you with any other information?

Thanks!

Randy


Here is output from Show Slave Status \G

mysql> show slave status \G
*** 1. row ***
 Slave_IO_State: Waiting for master to send event
Master_Host: localhost
Master_User: repuser
Master_Port: 3306
  Connect_Retry: 10
Master_Log_File: www-bin.001
Read_Master_Log_Pos: 7413
 Relay_Log_File: www-relay-bin.02
  Relay_Log_Pos: 8092
  Relay_Master_Log_File: www-bin.001
   Slave_IO_Running: Yes
  Slave_SQL_Running: Yes
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: 7413
Relay_Log_Space: 8092
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: 


OS is redhat e 2.1

Master
3.23.58
--
[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
log-bin
server-id = 1
 
[mysql.server]
user=mysql
basedir=/var/lib

[safe_mysqld]
err-log=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid





Slave
5.0.1-alpha-standard

# Example MySQL config file for medium systems.
#
# This is for a system with little memory (32M - 64M) where MySQL plays
# an important part, or systems up to 128M where MySQL is used together with
# other programs (such as a web server)
#
# You can copy this file to
# /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is /usr/local/mysql/data) or
# ~/.my.cnf to set user-specific options.
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.

# The following options will be passed to all MySQL clients
[client]
#password   = your_password
port= 3310
socket  = /tmp/mysql5.sock

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port= 3310
socket  = /tmp/mysql5.sock
datadir = /usr/local/mysql5/data
skip-locking
key_buffer = 16M
max_allowed_packet = 1M
table_cache = 64
sort_buffer_size = 512K
net_buffer_length = 8K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 8M
server-id = 2


[mysql.server]
user = mysql
basedir = /usr/local/mysql5

[safe_mysqld]
err-log = /usr/local/mysql5/error.log
datadir = /usr/local/mysql5/data
pid-file = /var/run/mysqld/mysqld5.pid

# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
#
#skip-networking

# Replication Master Server (default)
# binary logging is required for replication
log-bin

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id   = 2

# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
#the syntax is:
#
#CHANGE MASTER TO MASTER_HOST=, MASTER_PORT=,
#MASTER_USER=, MASTER_PASSWORD= ;
#
#where you replace , ,  by quoted strings and
# by the master's port number (3306 by default).
#
#Example:
#
#CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
#MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
#start replication for the first time (even unsuccessfully, for example
#if you mistyped the password in master-password and the slave fails to
#connect), the slave will create a master.info file, and any later
#change in this file to the variables' values below will be ignored and
#overridden by the content of the master.info file, unless you shutdown
#the slave server, 

RE: Local Master replication issue

[Sanjeev Sagar]

--log-slave-updates did the job.

Regards,

-Original Message-
From: Sanjeev Sagar [mailto:[EMAIL PROTECTED]
Sent: Fri 9/10/2004 3:36 PM
To: [EMAIL PROTECTED]
Subject: Local Master replication issue
 
Hello All,

I am seeing a small problem in Ring replication where one slave is acting as Local 
Master. See below

M - Super Master
S1/LM1 - Slave of super Master and act as Local Master for S2
S2 - slave of LM1

I ran one Insert on M, it showd up on S1/LM1 but it did not showed up in S2.

What I can see that S1 I/O thread bring that transaction in relay log on S1 and apply 
it but it did not consider as write on s1/LM1 resulting that binlog do not have record 
of it. Since binlog do not hast it, so it did not replicate to S2.

Am I missing anything here?

As per our requirement that transaction should also showed up in S2 too?

It's obivious to think that make S2 as direct slave of M but it is not accepted 
because things r bit complicated here.

Is there any specific configuration thing to acheive a slave as local master for 
another slave.

Any help will be highly appreciable.

Regards,

Local Master replication issue

[Sanjeev Sagar]

Hello All,

I am seeing a small problem in Ring replication where one slave is acting as Local 
Master. See below

M - Super Master
S1/LM1 - Slave of super Master and act as Local Master for S2
S2 - slave of LM1

I ran one Insert on M, it showd up on S1/LM1 but it did not showed up in S2.

What I can see that S1 I/O thread bring that transaction in relay log on S1 and apply 
it but it did not consider as write on s1/LM1 resulting that binlog do not have record 
of it. Since binlog do not hast it, so it did not replicate to S2.

Am I missing anything here?

As per our requirement that transaction should also showed up in S2 too?

It's obivious to think that make S2 as direct slave of M but it is not accepted 
because things r bit complicated here.

Is there any specific configuration thing to acheive a slave as local master for 
another slave.

Any help will be highly appreciable.

Regards,

Re: Replication Issue

[Jeremy Zawodny]

On Wed, May 05, 2004 at 06:44:09PM +0200, Mechain Marc wrote:
> Hello,
> 
> Why such a SQL request running well on the master is not correctly replicated on the 
> slave, 
> 
> set @providerId='012345';
> insert into DATA_TYPE values (1,@providerId,'DATA_TYPE',1);
> 
> Here is an extract of the Slave Logfile:
> 
> MYBCK.log.1:ERROR: 1048  Column 'PROVIDER_ID' cannot be null
> MYBCK.log.1:040503 17:44:18  Slave: error 'Column 'PROVIDER_ID' cannot be null' on 
> query 'insert into DATA_TYPE values (1,@providerId,'DATA_TYPE',1)', error_code=1048
> 
> The question is: why is the value of @providerId not properly replicated ?
> 
> Is it a bug ?

Them manual says that "user variables" don't replicate properly.

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]

Replication Issue

[Mechain Marc]

Hello,

Why such a SQL request running well on the master is not correctly replicated on the 
slave, 

set @providerId='012345';
insert into DATA_TYPE values (1,@providerId,'DATA_TYPE',1);

Here is an extract of the Slave Logfile:

MYBCK.log.1:ERROR: 1048  Column 'PROVIDER_ID' cannot be null
MYBCK.log.1:040503 17:44:18  Slave: error 'Column 'PROVIDER_ID' cannot be null' on 
query 'insert into DATA_TYPE values (1,@providerId,'DATA_TYPE',1)', error_code=1048

The question is: why is the value of @providerId not properly replicated ?

Is it a bug ?

Regards,
Marc.

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Replication Issue?

[Roger Davis]

Hi all,
   My slave has been working fine up until now.  Here is the error message.

030730 11:32:28  Slave: connected to master '[EMAIL PROTECTED]:3306',
replication started in log 'SQLServer1-bin.034' at position 77571524
ERROR: 1062  Duplicate entry '120816' for key 1
030730 11:32:28  Slave:  error running query 'INSERT INTO Assignments (
.

Key 1 is CaseID

Database changed
mysql> select CaseID from Assignments Order by CaseID DESC Limit 3;
++
| CaseID |
++
| 120815 |
| 120814 |
| 120813 |
++
3 rows in set (0.02 sec)

mysql> DELETE FROM Assignments WHERE CaseID = 120816;
Query OK, 0 rows affected (0.04 sec)

If I try to restart the slave I get the error all over again.

Anyone have any Ideas


Roger
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.504 / Virus Database: 302 - Release Date: 7/24/2003


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Replication issue

[Michael T. Babcock]

I'm replicating over a local SSH tunnel to a remote machine ... both 
MySQL instances have been working fine in the past (and both have their 
own binary logs, and only one database is being replicated between the 
two).  I'm getting this in the error logs:

021030 13:13:25  Slave: connected to master '[EMAIL PROTECTED]:3303',  
replication started in log 'FIRST' at position 6281
021030 13:13:25  Slave: received 0 length packet from server, apparent 
master shutdown:
021030 13:13:25  Slave: Failed reading log event, reconnecting to retry, 
log 'FIRST' position 6281
021030 13:13:25  Slave: reconnected to master 
'[EMAIL PROTECTED]:3303',replication resumed in log 'FIRST' at position 6281
021030 13:13:25  Slave: received 0 length packet from server, apparent 
master shutdown:
021030 13:14:25  Slave: Failed reading log event, reconnecting to retry, 
log 'FIRST' position 6281

SSH is showing this:

debug1: Connection to port 3303 forwarding to 127.0.0.1 port 3306 requested.
debug1: fd 8 setting TCP_NODELAY
debug1: fd 8 setting O_NONBLOCK
debug1: channel 2: new [direct-tcpip]
debug1: channel 2: open confirm rwindow 131072 rmax 32768
debug1: channel 2: read<=0 rfd 8 len 0
debug1: channel 2: read failed
debug1: channel 2: close_read
debug1: channel 2: input open -> drain
debug1: channel 2: rcvd eof
debug1: channel 2: output open -> drain
debug1: channel 2: obuf empty
debug1: channel 2: close_write
debug1: channel 2: output drain -> closed
debug1: channel 2: ibuf empty
debug1: channel 2: send eof
debug1: channel 2: input drain -> closed
debug1: channel 2: send close
debug1: channel 2: rcvd close
debug1: channel 2: is dead
debug1: channel 2: garbage collecting
debug1: channel_free: channel 2: direct-tcpip: listening port 3303 for 
127.0.0.1 port 3306, connect from 127.0.0.1 port 1660, nchannels 3

--
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: Additional Information: Replication issue in 4.0.4

[Shane Allen]

On Sat, Oct 05, 2002 at 03:47:18PM +0300, Heikki Tuuri wrote:
> Shane,
> 
> > 021004 12:57:00  Slave: error 'Incorrect key file for table:
> 'listing_text'. Try to repair it' on query 'UPDATE sell.listing_text SET
> description='blah' WHERE listing_id=221112', error_code=1034
> >
> > So, I issued `mysqlcheck -r sell listing_text`, and eventually "Lost
> > connection to MySQL server during query". Inspection of the error log
> > yields the following:
> >
> > mysqld: mf_iocache.c:1106: _flush_io_cache: Assertion `info->end_of_file
> == my_tell(info->file,(myf) (0))' failed.
> >
> > Number of processes running now: 1
> > mysqld process hanging, pid 790 - killed
> 
> did you try to run the command line repair tool on a table while the mysqld
> server was up? The server must be shut down if you use the command line
> tool. Otherwise the indexes of the table may be cached in the key_buffer of
> the mysqld process.

Heikki,

If I attempt to run mysqlcheck -r   while the server is down,
I get:

mysqlcheck: Got error: 2002: Can't connect to local MySQL server through socket 
'/tmp/mysql.sock' (2) when trying to connect

It is my understanding that mysqlcheck's repair mechanism relies on
MySQL's built-in REPAIR statement, at least in the case of a MyISAM
table.

Thanks

-- 
Shane Allen <[EMAIL PROTECTED]>

interesting side-note: mutt's list-reply misses my send-hooks... :)

-
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: Additional Information: Replication issue in 4.0.4

[Heikki Tuuri]

Shane,

- Original Message -
From: "Shane Allen" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Friday, October 04, 2002 10:17 PM
Subject: Additional Information: Replication issue in 4.0.4


> On Thu, Oct 03, 2002 at 06:39:26PM -0500, Shane Allen wrote:
> > We have a 4.0.4-beta master and slave.
> >
> > The slaving process starts correctly, but randomly (and frequently) has
> > issues.
> >
> > When the server starts, it will slave, but eventually will hit one of
> > two conditions:
> >
> > - Duplicate key insert error (we re-sync'd the slave by hand during the
> >   install, copying databases by hand, etc, so they're known good)
> >
> > - Signal 8. The database will hit Signal 8, die, and be restarted.
> >   Immediately upon restarting, it dies, and restarts, ad naseum.
>
> I upgraded in testing to 4.0.4 again, built with debugging enabled, and
> got a slightly different result.
>
> This time, it eventually hit a query and the slaving stopped. This time
> the error was:
>
> 021004 12:57:00  Slave: error 'Incorrect key file for table:
'listing_text'. Try to repair it' on query 'UPDATE sell.listing_text SET
description='blah' WHERE listing_id=221112', error_code=1034
>
> So, I issued `mysqlcheck -r sell listing_text`, and eventually "Lost
> connection to MySQL server during query". Inspection of the error log
> yields the following:
>
> mysqld: mf_iocache.c:1106: _flush_io_cache: Assertion `info->end_of_file
== my_tell(info->file,(myf) (0))' failed.
>
> Number of processes running now: 1
> mysqld process hanging, pid 790 - killed
>
> presumably the debugging code that is built in is what is preventing the
> signal 8 behaviour that I experienced last night.
>
> On the master database I have been able to issue successful repair
> statements several timesi against this table, and the databases that I am
attempting to
> repair have been copied over from the master, so I'm not sure what is
> causing the repairs to fail...

did you try to run the command line repair tool on a table while the mysqld
server was up? The server must be shut down if you use the command line
tool. Otherwise the indexes of the table may be cached in the key_buffer of
the mysqld process.

> --
> Shane Allen <[EMAIL PROTECTED]>

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

sql query




-
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

Additional Information: Replication issue in 4.0.4

[Shane Allen]

On Thu, Oct 03, 2002 at 06:39:26PM -0500, Shane Allen wrote:
> We have a 4.0.4-beta master and slave.
> 
> The slaving process starts correctly, but randomly (and frequently) has
> issues.
> 
> When the server starts, it will slave, but eventually will hit one of
> two conditions:
> 
> - Duplicate key insert error (we re-sync'd the slave by hand during the
>   install, copying databases by hand, etc, so they're known good)
> 
> - Signal 8. The database will hit Signal 8, die, and be restarted.
>   Immediately upon restarting, it dies, and restarts, ad naseum.

I upgraded in testing to 4.0.4 again, built with debugging enabled, and
got a slightly different result.

This time, it eventually hit a query and the slaving stopped. This time
the error was:

021004 12:57:00  Slave: error 'Incorrect key file for table: 'listing_text'. Try to 
repair it' on query 'UPDATE sell.listing_text SET description='blah' WHERE 
listing_id=221112', error_code=1034

So, I issued `mysqlcheck -r sell listing_text`, and eventually "Lost
connection to MySQL server during query". Inspection of the error log
yields the following:

mysqld: mf_iocache.c:1106: _flush_io_cache: Assertion `info->end_of_file == 
my_tell(info->file,(myf) (0))' failed.

Number of processes running now: 1
mysqld process hanging, pid 790 - killed

presumably the debugging code that is built in is what is preventing the
signal 8 behaviour that I experienced last night.

On the master database I have been able to issue successful repair
statements several timesi against this table, and the databases that I am attempting to
repair have been copied over from the master, so I'm not sure what is
causing the repairs to fail...

-- 
Shane Allen <[EMAIL PROTECTED]>

sell.com : Buy & Sell Anything
http://www.sell.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

Replication issue in 4.0.4

[Shane Allen]

We have a 4.0.4-beta master and slave.

The slaving process starts correctly, but randomly (and frequently) has
issues.

When the server starts, it will slave, but eventually will hit one of
two conditions:

- Duplicate key insert error (we re-sync'd the slave by hand during the
  install, copying databases by hand, etc, so they're known good)

- Signal 8. The database will hit Signal 8, die, and be restarted.
  Immediately upon restarting, it dies, and restarts, ad naseum.

The Dupkicate Key insert doesn't have any decent or recognizable
accompanying errors, however the signal 8 leaves the following in the
logs:

021003 18:04:03  mysqld restarted
/usr/local/libexec/mysqld: ready for connections
021003 18:04:03  Slave I/O thread: connected to master
'[EMAIL PROTECTED]:3306',  replication started in log
'dbmaster1-bin.002' at position 110748
mysqld got signal 8;
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=402649088
read_buffer_size=1044480
sort_buffer_size=1048568
max_used_connections=0
max_connections=2500
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections
= 130 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x82d4d00
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=0x5c190f98, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80940d7
0x81798fb
0x8095aa5
0x8056129
0x8057109
0x804b7d2
0x80b513a
0x80cd4ad
0x809f16d
0x80a2d8c
0x80db5a5
0x81183c6
0x8117147
0x8177394
0x81aa79a
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 0x82d0ba6 = UPDATE /* sess_read:update timestamp */
admin.login SET login.last_modified = NOW(), login.mumbojumbo =
FLOOR(RAND()*) WHERE login.uid IN( 0, 27 ) AND login.session
= 'fb103efea43b37b049cb1d54f400724d'
thd->thread_id=2

Successfully dumped variables, if you ran with --log, take a look at the
details of what thread 2 did to cause the crash.  In some cases of
really
bad corruption, the values shown above may be invalid.

The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains
information that should help you find out what is causing the crash.

Number of processes running now: 0


I have run a backtrace, and came up with the following:

0x80940d7 _Z15handle_segfaulti + 503
0x81798fb sem_timedwait + 95
0x8095aa5 rnd + 53
0x8056129 _ZN13Item_func_mul3valEv + 41
0x8057109 _ZN15Item_func_floor7val_intEv + 41
0x804b7d2 _ZN4Item13save_in_fieldEP5Field + 226
0x80b513a _Z11fill_recordR4ListI4ItemES2_ + 106
0x80cd4ad 
_Z12mysql_updateP3THDP13st_table_listR4ListI4ItemES6_PS4_P8st_orderm15enum_duplicates13thr_lock_type
 + 2093
0x809f16d _Z21mysql_execute_commandv + 4829
0x80a2d8c _Z11mysql_parseP3THDPcj + 300
0x80db5a5 _ZN15Query_log_event10exec_eventEP17st_relay_log_info + 293
0x81183c6 _Z22process_io_create_fileP14st_master_infoP21Create_file_log_event + 166
0x8117147 _Z10next_eventP17st_relay_log_info + 423
0x8177394 pthread_handle_free + 72
0x81aa79a __nss_lookup_function + 686

Reverting the slave to 4.0.3 fixed the instability AFAICT (it's only
been reverted for a brief period). The master has remained at 4.0.4

Let me know if you need further info.

Thanks

-- 
Shane Allen <[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: replication issue (A _REAL_ ISSUE)

[Michael Douglass]

I was wrong.  My slave servers are STILL 'hanging' and not continuing
to replicate.  They give no errors, the slave appears to stay running,
it just lags behind the master.  Nothing I have done has fixed this.
Again I'm running 3.23.49.

To "fix" the problem I issue a slave stop, slave start command.  This
appears to kickstart the slave process and it catches back up to the
master.

Thoughts?

On Wed, Feb 27, 2002 at 01:29:31PM -0600, Michael Douglass said:
> 
> It would appear that the apparent lagging/slave processes not working
> (yet telling me they are up) was due to having two slaves set to the
> same server-id.  I will know as more time passes.
> 
> On Wed, Feb 27, 2002 at 09:27:04AM -0600, Michael Douglass said:
> > 
> > David,
> > 
> >   I am seeing the exact same thing on some Solaris boxen.  My database
> > sees a couple of updates every minute or two; and show slave status on
> > the slave always appears to lag behind the master.  The data in my
> > tables lag as well as I've done some rudimentary checksumming and have
> > found differences.  I've found that if I go to each slave and do a slave
> > stop and a slave start that it restarts the slave connection and then
> > runs through all of the new changes.
> > 
> > Mysql community,
> > 
> >   Thoughts as to what could be causing this?  I am using --replicate-do-
> > db command to replicate only a single database; that's about the only
> > thing I can think of that is special about my setup.
> > 
> > Thanks,
> > 
> > On Mon, Feb 11, 2002 at 10:24:46AM -0800, David Piasecki said:
> > > I've recently set up replication on one of my databases. Both master and
> > > slave are running MySQL 3.23.46 on FreeBSD 4.1. The only tables that get
> > > updated or inserted into hold approximately 140,000 records, growing at
> > > a rate of around 50-100 every day. The issue is it is currently taking
> > > approximately 20-30 minutes for an update/insert that occurs on the
> > > master to show up on the slave. An insert operation on the master
> > > usually only takes a second or so, so it doesn't make sense that it
> > > should take so long for the slave to update. There is nothing
> > > non-standard about either table - each contains approximately 20
> > > columns, one auto-increment field, and one index.
> > > 
> > > Hoping someone has some insight into this matter... BTW, both servers
> > > are on the same private network, literally being right next to each
> > > other, so I know it's not a network issue.
> > > 
> > > 
> > > David Piasecki
> > > 
> > > 
> > > 
> > > -
> > > 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
> > 
> > -- 
> > Michael Douglass
> > Chief System Engineer
> > Texas Networking, Inc.  (512-794-7123)
> > 
> > -
> > 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
> 
> -- 
> Michael Douglass
> Chief System Engineer
> Texas Networking, Inc.  (512-794-7123)
> 
> -
> 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

-- 
Michael Douglass
Chief System Engineer
Texas Networking, Inc.  (512-794-7123)

-
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: replication issue

[Michael Douglass]

It would appear that the apparent lagging/slave processes not working
(yet telling me they are up) was due to having two slaves set to the
same server-id.  I will know as more time passes.

On Wed, Feb 27, 2002 at 09:27:04AM -0600, Michael Douglass said:
> 
> David,
> 
>   I am seeing the exact same thing on some Solaris boxen.  My database
> sees a couple of updates every minute or two; and show slave status on
> the slave always appears to lag behind the master.  The data in my
> tables lag as well as I've done some rudimentary checksumming and have
> found differences.  I've found that if I go to each slave and do a slave
> stop and a slave start that it restarts the slave connection and then
> runs through all of the new changes.
> 
> Mysql community,
> 
>   Thoughts as to what could be causing this?  I am using --replicate-do-
> db command to replicate only a single database; that's about the only
> thing I can think of that is special about my setup.
> 
> Thanks,
> 
> On Mon, Feb 11, 2002 at 10:24:46AM -0800, David Piasecki said:
> > I've recently set up replication on one of my databases. Both master and
> > slave are running MySQL 3.23.46 on FreeBSD 4.1. The only tables that get
> > updated or inserted into hold approximately 140,000 records, growing at
> > a rate of around 50-100 every day. The issue is it is currently taking
> > approximately 20-30 minutes for an update/insert that occurs on the
> > master to show up on the slave. An insert operation on the master
> > usually only takes a second or so, so it doesn't make sense that it
> > should take so long for the slave to update. There is nothing
> > non-standard about either table - each contains approximately 20
> > columns, one auto-increment field, and one index.
> > 
> > Hoping someone has some insight into this matter... BTW, both servers
> > are on the same private network, literally being right next to each
> > other, so I know it's not a network issue.
> > 
> > 
> > David Piasecki
> > 
> > 
> > 
> > -
> > 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
> 
> -- 
> Michael Douglass
> Chief System Engineer
> Texas Networking, Inc.  (512-794-7123)
> 
> -
> 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

-- 
Michael Douglass
Chief System Engineer
Texas Networking, Inc.  (512-794-7123)

-
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: replication issue

[Michael Douglass]

David,

  I am seeing the exact same thing on some Solaris boxen.  My database
sees a couple of updates every minute or two; and show slave status on
the slave always appears to lag behind the master.  The data in my
tables lag as well as I've done some rudimentary checksumming and have
found differences.  I've found that if I go to each slave and do a slave
stop and a slave start that it restarts the slave connection and then
runs through all of the new changes.

Mysql community,

  Thoughts as to what could be causing this?  I am using --replicate-do-
db command to replicate only a single database; that's about the only
thing I can think of that is special about my setup.

Thanks,

On Mon, Feb 11, 2002 at 10:24:46AM -0800, David Piasecki said:
> I've recently set up replication on one of my databases. Both master and
> slave are running MySQL 3.23.46 on FreeBSD 4.1. The only tables that get
> updated or inserted into hold approximately 140,000 records, growing at
> a rate of around 50-100 every day. The issue is it is currently taking
> approximately 20-30 minutes for an update/insert that occurs on the
> master to show up on the slave. An insert operation on the master
> usually only takes a second or so, so it doesn't make sense that it
> should take so long for the slave to update. There is nothing
> non-standard about either table - each contains approximately 20
> columns, one auto-increment field, and one index.
> 
> Hoping someone has some insight into this matter... BTW, both servers
> are on the same private network, literally being right next to each
> other, so I know it's not a network issue.
> 
> 
> David Piasecki
> 
> 
> 
> -
> 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

-- 
Michael Douglass
Chief System Engineer
Texas Networking, Inc.  (512-794-7123)

-
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: replication issue

[David Piasecki]

I've recently set up replication on one of my databases. Both master and
slave are running MySQL 3.23.46 on FreeBSD 4.1. The only tables that get
updated or inserted into hold approximately 140,000 records, growing at
a rate of around 50-100 every day. The issue is it is currently taking
approximately 20-30 minutes for an update/insert that occurs on the
master to show up on the slave. An insert operation on the master
usually only takes a second or so, so it doesn't make sense that it
should take so long for the slave to update. There is nothing
non-standard about either table - each contains approximately 20
columns, one auto-increment field, and one index.

Hoping someone has some insight into this matter... BTW, both servers
are on the same private network, literally being right next to each
other, so I know it's not a network issue.


David Piasecki



-
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

(Sort of ) replication issue

[Victoria Reznichenko]

David,

Monday, January 28, 2002, 10:43:38 PM, you wrote:

DS> REALFROM: David Shields <[EMAIL PROTECTED]> 
DS> HOUR: 2002012901

DS> You wrote:
DS> What about mysqldump? See http://www.mysql.com/doc/m/y/mysqldump.html
DS> for more info about mysqldump.


DS> well, no, not really :

DS> site1 - has apache / php / mysql + database x

DS> site2 - has apache / php / mysql + database y

DS> site3 - has apache / php / mysql + database z

DS> at 9:00 am all databses (x,y,z) are same.

DS> during day, people at 1 update x, people at 2 update y, people at 3 update z.

DS> at (say) 23:00 , I want to put all x's changes into y and z, all y's 
DS> changes into x and z, all z's changes into x and y.

mysqldump x > x.dmp
mysqldump y > y.dmp
mysqldump z > z.dmp

DS> would require that i then do a diff of x, y and apply all < diffs to x, 
DS> all > diffs to y ... and so on - it looks like an over-engineered solution 
DS> to me. What I was asking is whether replication would ease my pain.

I think, replication in any form is not a solution for you in this case.
You have to think hard what you want from the database and which data and what changes 
should be done by various people on various databases.
That's a software design question, not MySQL's one.
Why don't you run all these sites using one MySQL server?






-- 
For technical support contracts, goto https://order.mysql.com/
This email is sponsored by Ensita.net http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Victoria Reznichenko
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.net
   <___/   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

(Sort of ) replication issue

[David Shields]

You wrote:
What about mysqldump? See http://www.mysql.com/doc/m/y/mysqldump.html
for more info about mysqldump.


well, no, not really :

site1 - has apache / php / mysql + database x

site2 - has apache / php / mysql + database y

site3 - has apache / php / mysql + database z

at 9:00 am all databses (x,y,z) are same.

during day, people at 1 update x, people at 2 update y, people at 3 update z.

at (say) 23:00 , I want to put all x's changes into y and z, all y's 
changes into x and z, all z's changes into x and y.

mysqldump x > x.dmp
mysqldump y > y.dmp
mysqldump z > z.dmp

would require that i then do a diff of x, y and apply all < diffs to x, 
all > diffs to y ... and so on - it looks like an over-engineered solution 
to me. What I was asking is whether replication would ease my pain.

David.

-
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

(Sort of ) replication issue

[Victoria Reznichenko]

David,

Monday, January 28, 2002, 10:39:12 AM, you wrote:

DS> Hi, I was wondering if any of you clever people out there can help me. I 
DS> have a client with a problem I'm sure some of you have fixed in the past ...

DS> Client has 3 geographically separate sites, running same application (mine, 
DS> of course) and generating data on MySQL database.
DS> Periodically (probably nightly), we want to push changes occurring on each 
DS> database into each of other 2 sites. Data volumes are low-ish (est max 5Meg 
DS> per database absolute worst case). Line cost is minimal (ADSL), and comms 
DS> issues I can work out just fine.

DS> This strikes me as a version of the multi-mysql-database replication 
DS> pattern, though sort of slow. Is replication setup acceptable, or are the 
DS> downtimes where databases are separate an issue, and is this using a 
DS> sledgehammer to crack a nut?

DS> The alternative that occurs to me (though it is a bit if a pain) is to 
DS> change my code slightly so each DB update query is written to a transaction 
DS> log at each site, and then manually apply each of these logs to the other 2 
DS> databases. I can do this fine, but it seems a bit, well, crude. Plus the 
DS> overhead of protecting the logs, and of clearing them on successful completion.

What about mysqldump? See http://www.mysql.com/doc/m/y/mysqldump.html
for more info about mysqldump.




-- 
For technical support contracts, goto https://order.mysql.com/
This email is sponsored by Ensita.net http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Victoria Reznichenko
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.net
   <___/   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: (Sort of ) replication issue

[admin]

Hi.

Not only that you also sent it to the wrong person:)
It was david that asked the question anyway i cc it to the list and him.

sometime i will experiment with that also but time is to short:)

Regards
/PM\

Ed Lazor wrote:
> 
> doh... I should go to bed... I just reread what I wrote and it dawned on me
> that I didn't really say anything you didn't already know...  I do know
> that replication is possible and it's built into MySQL... I don't remember
> how I did it... but it wasn't that difficult... had to do with establishing
> one server as a master and the other two as slaves to the master server and
> there was a place where you could specify how often replication
> occurs.  Between replication, the main server records logs and uses the
> logs to track what should be transferred to the clients...  so only changed
> data gets replicated, which is very cool.
> 
> Hope that helps.
> 
> -Ed
> 
> At 09:53 AM 1/28/2002 +0100, you wrote:
> >Hi.
> >
> >I would do a simple read file,search database,input record script in
> >perl
> >and transfer the files using scp (ofcourse i asume this is in
> >linux/unix)
> >
> >put it all under cronjob and it should work fine.
> >
> >On the other hand i am sure others have better ideas:)
> >
> >/PM\
> >
> >David Shields wrote:
> > >
> > > Hi, I was wondering if any of you clever people out there can help me. I
> > > have a client with a problem I'm sure some of you have fixed in the
> > past ...
> > >
> > > Client has 3 geographically separate sites, running same application (mine,
> > > of course) and generating data on MySQL database.
> > > Periodically (probably nightly), we want to push changes occurring on each
> > > database into each of other 2 sites. Data volumes are low-ish (est max 5Meg
> > > per database absolute worst case). Line cost is minimal (ADSL), and comms
> > > issues I can work out just fine.
> > >
> > > This strikes me as a version of the multi-mysql-database replication
> > > pattern, though sort of slow. Is replication setup acceptable, or are the
> > > downtimes where databases are separate an issue, and is this using a
> > > sledgehammer to crack a nut?
> > >
> > > The alternative that occurs to me (though it is a bit if a pain) is to
> > > change my code slightly so each DB update query is written to a transaction
> > > log at each site, and then manually apply each of these logs to the other 2
> > > databases. I can do this fine, but it seems a bit, well, crude. Plus the
> > > overhead of protecting the logs, and of clearing them on successful
> > completion.
> > >
> > > Am I missing something, or is there a better way ? Advice and
> > > recommendations solicited and welcomed.
> > >
> > > David.
> > >
> > > (By the way, Mysql 3.23.38, app in php 4.0.5)
> > >
> > > Magic words: sql, database, query, abracadabra, butterscotch, nibble,
> > > phong. (some of these are just *nice* words, you know ? )
> > >
> > > -
> > > 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

-
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: (Sort of ) replication issue

[admin]

Hi.

I would do a simple read file,search database,input record script in
perl
and transfer the files using scp (ofcourse i asume this is in
linux/unix)

put it all under cronjob and it should work fine. 

On the other hand i am sure others have better ideas:)

/PM\

David Shields wrote:
> 
> Hi, I was wondering if any of you clever people out there can help me. I
> have a client with a problem I'm sure some of you have fixed in the past ...
> 
> Client has 3 geographically separate sites, running same application (mine,
> of course) and generating data on MySQL database.
> Periodically (probably nightly), we want to push changes occurring on each
> database into each of other 2 sites. Data volumes are low-ish (est max 5Meg
> per database absolute worst case). Line cost is minimal (ADSL), and comms
> issues I can work out just fine.
> 
> This strikes me as a version of the multi-mysql-database replication
> pattern, though sort of slow. Is replication setup acceptable, or are the
> downtimes where databases are separate an issue, and is this using a
> sledgehammer to crack a nut?
> 
> The alternative that occurs to me (though it is a bit if a pain) is to
> change my code slightly so each DB update query is written to a transaction
> log at each site, and then manually apply each of these logs to the other 2
> databases. I can do this fine, but it seems a bit, well, crude. Plus the
> overhead of protecting the logs, and of clearing them on successful completion.
> 
> Am I missing something, or is there a better way ? Advice and
> recommendations solicited and welcomed.
> 
> David.
> 
> (By the way, Mysql 3.23.38, app in php 4.0.5)
> 
> Magic words: sql, database, query, abracadabra, butterscotch, nibble,
> phong. (some of these are just *nice* words, you know ? )
> 
> -
> 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

(Sort of ) replication issue

[David Shields]

Hi, I was wondering if any of you clever people out there can help me. I 
have a client with a problem I'm sure some of you have fixed in the past ...

Client has 3 geographically separate sites, running same application (mine, 
of course) and generating data on MySQL database.
Periodically (probably nightly), we want to push changes occurring on each 
database into each of other 2 sites. Data volumes are low-ish (est max 5Meg 
per database absolute worst case). Line cost is minimal (ADSL), and comms 
issues I can work out just fine.

This strikes me as a version of the multi-mysql-database replication 
pattern, though sort of slow. Is replication setup acceptable, or are the 
downtimes where databases are separate an issue, and is this using a 
sledgehammer to crack a nut?

The alternative that occurs to me (though it is a bit if a pain) is to 
change my code slightly so each DB update query is written to a transaction 
log at each site, and then manually apply each of these logs to the other 2 
databases. I can do this fine, but it seems a bit, well, crude. Plus the 
overhead of protecting the logs, and of clearing them on successful completion.

Am I missing something, or is there a better way ? Advice and 
recommendations solicited and welcomed.

David.

(By the way, Mysql 3.23.38, app in php 4.0.5)

Magic words: sql, database, query, abracadabra, butterscotch, nibble, 
phong. (some of these are just *nice* words, you know ? ) 

-
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

replication issue with FreeBSD 4.2-RELEASE

[Brian Reichert]

I'm exploring mysql replication under FreeBSD 4.2-RELEASE.

Two machines, named 'master' and 'slave', each running FreeBSD
4.2-RELEASE and MySQL 3.23.36-debug.

I've followed the instructions at

  

All very straight forward.

When I spin everything up, I see these errors on the slave server:

  /usr/local/libexec/mysqld: ready for connections

  010718 19:28:17  Slave: connected to master '[EMAIL PROTECTED]:3306',
  replication started in log 'FIRST' at position 4

  010718 19:29:22  Error reading packet from server: Lost connection
  to MySQL server during query (read_errno 35,server_errno=2013)

  010718 19:29:22  Slave: Failed reading log event, reconnecting
  to retry, log 'master-bin.001' position 803

  010718 19:29:22  Slave: reconnected to master
  '[EMAIL PROTECTED]:3306',replication resumed in log 'master-bin.001'
  at position 803

And the last two errors just keep repeating.  I can otherwise
connect just fine:

  slave% mysql -u repl -prepl -h master.xxx.xxx
  Welcome to the MySQL monitor.  Commands end with ; or \g.
  Your MySQL connection id is 58 to server version: 3.23.36-debug-log
  
  Type 'help;' or '\h' for help. Type '\c' to clear the buffer
  
  mysql> quit
  Bye

I presume 'read_errno 35' refers to:

   35 EAGAIN Resource temporarily unavailable. This is a
   temporary condition and later calls to the same routine may
   complete normally.

Does anyone have any insight?  Funky hardware?  The list has mentioned 
4.2-RELEASE having threading problems, fixed in 4.3.  Might this be the
case?  I don't want to have to upgrade the OS, out-of-hand.

Upgrade the version of MySQL on the master a/o slave?  I see some
changes WRT replication:

  F.2.1 Changes in release 3.23.40
   
 Added slave_wait_timeout for replication. 

  F.2.3 Changes in release 3.23.38

 Better error message when slave max_allowed_packet is too low
 to read a very long log event from the master.

  F.2.4 Changes in release 3.23.37

 Fixed bug that erroneously logged a drop of internal temporary
 table on thread termination to the binary log - bug affected
 replication.

Would any of these apply to the errors I'm seeing?

-- 
Brian 'you Bastard' Reichert<[EMAIL PROTECTED]>
37 Crystal Ave. #303Daytime number: (603) 434-6842
Derry NH 03038-1713 USA Intel architecture: the left-hand path

-
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

Replication issue

[Scott Vanderweyst]

Is it possible to define multiple masters for a specific server:
ie: Updates from different servers all update to a single backup server

I'd prefer not to need to set up a circular replication scheme, due to
geographical issues, and also data relavance issues.

Taking a quick look through the source makes it appear that there isn't
currently that functionality.

What are some other ways that I might be able to do this... Multiple
servers on the same machine using the same base directory/databases with
locking enabled(Is this even possible???)

Basically (bi-directional chain)
box0<-box1<->box2<->box3->box4
where arrows show direction of data transmission

Any advice would be appreciated
Scott V


-
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