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 M
t"
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 -
!
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.m
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
t: 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
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
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 dad
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://list
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
Subje
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
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 consis
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:
>
>
> 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'
(11
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 runn
[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 C
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
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? Doe
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 usin
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
set
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 lik
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/mys
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
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
"
e 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', r
"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
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 Sla
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 comm
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 s
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 dif
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
approxima
30 matches
Mail list logo
