I'm trying to resolve a frustrating replication problem with my databases.
The master contains a number of schema, only using Innodb tables.
Updates happen regularly, usually using bulk inserts of the form
INSERT ... ON DUPLICATE UPDATE. Data is mostly numbers. The missing
queries contain no
I have a simple master-slave replication setup. Nothing very interesting
as far as I know, both running identically configured 5.1.31 using
'mixed' replication.
I have a couple of issues which I assume are related, although I suppose
they might not be:
1) When the monitoring showed that
Hi,
I keep getting the below in the error log. I can't see any problems (no
other errors and replication is working) and the master DB is available
the whole time.
070928 12:07:31 [Note] Slave: received end packet from server, apparent
master shutdown:
070928 12:07:31 [Note] Slave I/O thread:
My master has two databases: channel and hardware. I'm only interested
in replicating hardware, so I set up replicate-do-db=hardware on the slaves.
However, I am having problems because of giant LOAD DATA operations
performed nightly on channel. Replication blows up with max packet
exceeded
i probably should have mentioned: both master slave are running 4.0.20
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jon Drukman wrote:
My master has two databases: channel and hardware. I'm only interested
in replicating hardware, so I set up replicate-do-db=hardware on the slaves.
However, I am having problems because of giant LOAD DATA operations
On Tuesday 09 November 2004 11:49 am, ian douglas wrote:
My bad, I wasn't running START SLAVE to get them going. Seems odd that
this has to be done manually.
I never do.. once its started, it should be fine.. Your just getting errors
making it stop.
Also, overnight, my slaves reported this
If a slave dies, is there any way to determine that state from an
external point of view (ie: via Perl/DBD) so we can write a script of
some kind to either connect to the slave and issue a START SLAVE or
send the last xx lines of the .err log file to our tech staff?
I tried writing a Perl
On Tuesday 09 November 2004 03:23 pm, ian douglas wrote:
GRANT SUPER,REPLICATION CLIENT to 'syscheck'@'mywebserver.domain.org'
IDENTIFIED BY 'mypasswd' ;
I have no idea how this script is gonna help, but your having permission
problems. The last message you wrote was permission problems as
At 9:49 -0800 11/9/04, ian douglas wrote:
Except that changes made on the master are not automatically picked
up by the slaves.
My bad, I wasn't running START SLAVE to get them going. Seems odd
that this has to be done manually.
Perhaps you have the --skip-slave-start option in an option file?
One master, two slaves, mysql 4.1.7 installed via compiled source code,
on RedHat 8.0
On the master system I did this:
grant SUPER,REPLICATION CLIENT on *.* to 'repl_user'@'known.hostname1'
identified by 'repl_passwd' ;
grant SUPER,REPLICATION CLIENT on *.* to 'repl_user'@'known.hostname2'
Answered my own question, sorry for the quick posting...
When I was trying to do the LOAD DATA FROM MASTER, with the master set
as GRANT ALL ON *.* TO 'repl_user'@ ... the slaves were reporting an
error that stated I needed to GRANT SUPER,REPLICATION CLIENT on the
master, which didn't work.
After a little more RTFM-surfing, I found the GRANT REPLICATION SLAVE
for the master, and a LOAD DATA worked just fine.
Except that changes made on the master are not automatically picked up
by the slaves.
Am I missing something?
-id
--
MySQL General Mailing List
For list archives:
Has anyone ever encountered a problem where replication stops due to a
partially completed query on the master?
I am currently encountering this problem on my server and was wondering if I
need to resync the slave server to the master by copying all the data files
to the slave and then restarting
I'm not sure what's going on with our replication. Everything was
working fine, then all of a sudden it stopped. I did STOP SLAVE; RESET
SLAVE; LOAD DATA FROM MASTER and it completed after a few minutes, but
when I checked SHOW SLAVE STATUS it no longer had any information about
the master. I
Gabriel Ricard wrote:
I'm not sure what's going on with our replication. Everything was
working fine, then all of a sudden it stopped. I did STOP SLAVE; RESET
SLAVE; LOAD DATA FROM MASTER and it completed after a few minutes, but
when I checked SHOW SLAVE STATUS it no longer had any information
The replication between two servers works. But I tried to disable
replication on one table. According to the MYSQL Documentation. I did the
following:
#1 stop Slave
#2 Modified my.cnf on slave
[mysqld]
server-id=3
master-host=192.168.1.129
master-user=aert12
master-password=password
mysql-max-3.23.57-pc-linux-i686
I notice that slaves which never went out of sync are now doing so
regularly with the same traffic pattern. Since upgrading to 3.23.57 I've
notice a large increase in CPU utilization with the same configuration
as the previous version in production 3.23.54. Anyone
That got me greping through my Master's log and I came accross the
following :
Error reading packet from server: log event entry exceeded
max_allowed_packet - increase max_allowed_packet on master
(server_errno=65535)
This seems to have happened in the date ranges where replication was
On Wed, Jun 11, 2003 at 05:22:50PM +0530, Mithun Bhattacharya wrote:
I am frequently getting errors as given below on my slave server.
-
030605 3:27:19 Slave: did not get the expected error running query
from master - expected: 'Got error %d
Hello,
I'm running MySQL Ver 12.18 Distrib 4.0.12 I had replication set up and
working perfectly between two machines in a round robin fashion. (Serv 1
updates Serv 2 and Serv 2 updates Serv 1.)
Recently serv 2 locked up, upon restarting, it automatically began to
update with the files
Hi Calvin,
I am not sure which table format you use, but somehow I assume you use innodb.
If I remember correctly than Innodb will need all log files. If only one is
missing than thats it, you get the error described.
- anybody please correct me if I talk rubbish here
Best regards
Nils
Nils,
I agree with you, you do have to have all the log files, which is why I
reset the master.
According to the manual:
4.10.7.5 RESET MASTER (master)
Deletes all binary logs listed in the index file, resetting the binlog index
file to be empty. Previously
I've got 3 databases running DB1, DB2, DB3.
DB1 version 3.23.41
DB2 version 3.23.41
DB3 version 3.12.51
DB1 is the master for DB2 in replication
I'm trying now to set up DB3 to replicate from DB2
So in essence DB1 - DB2 - DB3
I ran through the instructions for setting up replication of DB2 to
Hi,
I'm having a bit of a nightmare getting replication working.
Both slave and master are 4.0.10-gamma
If I install fresh copies on two clean machines, and follow the
instructions in manual.txt, everything works fine.
The problem is that I need to do this in a production environment,
so I
Hi All
I am trying to make a replication for my database.
The master and the slave both in version 3.23.41 and i am working on windows
2000.
I create user with FILE privilege and I flush all the tables and block write
queries.
Now I run the query SHOW MASTER STATUS and I get null in all the
On Tuesday 18 February 2003 15:36, Harald Fuchs wrote:
In article [EMAIL PROTECTED],
John Taylor [EMAIL PROTECTED] writes:
I get the error:
ERROR 1227: Access denied. You need the REPLICATION SLAVE privilege for this
operation
I've tried setting the grants again, but it doesn't seem
I am using MySQL version 4.0.10 on both Slave and Master. I am running a
Visual Basic front end connected to MySQL via MySQL ODBC v3.51.04. When
using MySQLCC, adding records to the master database will work fine, the
server shows the additional record added. When using our app in VB, a
record
-Ursprngliche Nachricht-
Von: Guddack Thorsten ICM MP SCM GO 21
Gesendet: Freitag, 31. Januar 2003 20:51
An: 'Gelu Gogancea'; '[EMAIL PROTECTED]'
Betreff: Re: Replication Problems/Questions
Hi,
thank you for you're response,
but in the mysql-manual version 4.0 they said
Hi List
I'm using 2 WinNT-Servers, Sp6 with mysql 4.0.5. max-nt.
I ve setup a replication between these two servers as discribed in the
manual and some small problems comes up.
Maybe someone can give me some help.
1.) On the Master I create a user repl with the rights 'replication slave'.
Hi,
- Original Message -
From: Guddack Thorsten ICM MP SCM GO 21 [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, January 30, 2003 3:44 PM
Subject: Replication Problems/Questions
Hi List
I'm using 2 WinNT-Servers, Sp6 with mysql 4.0.5. max-nt.
I ve setup a replication between
So I have been reading a lot lately about replication but I can't find a
good summary/explanation of MySQL's replication features regarding InnoDB
tables and how their transactional properties may cause problems in
replication.
I have seen suggestions that InnoDB tables should be converted to
Kris,
- Original Message -
From: Krzysztof Karski [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Tuesday, January 21, 2003 11:35 AM
Subject: replication problems with InnoDB tables...?
So I have been reading a lot lately about replication but I can't find a
good summary
I have been having a lot of trouble configuring mysql to do just the
simplest replication. Its a standard RedHat 8.0 install, I have followed
the directions on http://www.mysql.com/doc/en/Replication_HOWTO.html to the
letter half a dozen times now and still, the slave server crashes repeatedly
as
We have two users, lets call them test and test2.
When we log in as test from our front end web servers, we can execute queries and they
replicate.
When we log in as test from our back end db servers (say to run a cleanup script by
hand), the queries replicate.
When we log in as test2 from
I am getting this error while trying to Replicate to a second MySQL server.
021124 23:40:25 Slave: reconnected to master
'[EMAIL PROTECTED]:3306',replication resumed in log 'FIRST' at position
4
021124 23:40:25 Error reading packet from server: Binary log is not open
(server_errno=2000)
I have
dear everybody,
I have tree linux 7.3 machines on which MySQL-3.23.51-1.i386.rpm,
MySQL-client-3.23.51-1.i386.rpm and MySQL-shared-3.23.51-1.i386.rpm is
installed. the intrusion detection system snort loggs to these machines.
Every machine is set up the same way and contains the same table. The
Thanks a lot. I've fixed my problems with this.
Best regards.
- Original Message -
From: Gerald Clark [EMAIL PROTECTED]
To: Santiago Alba [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Friday, July 12, 2002 3:53 PM
Subject: Re: Replication problems
Did you copy the master.info file
Hi,
That wasn't the problem. The problem was in master.info file.
Thanks a lot.
- Original Message -
From: Ralf Narozny [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, July 12, 2002 4:39 PM
Subject: Re: Replication problems
Hello!
You will get problems when you set the 2nd
Hi All,
I had a system replication on Linux consisting of MASTER and only one SLAVE.
I stopped replication, I did a backup on my slave and it recreated in
another machine so now I have two SLAVES connected to database MASTER.
But I found problems. I show you the output on my database MASTER and
Did you copy the master.info file over too?
Santiago Alba wrote:
Hi All,
I had a system replication on Linux consisting of MASTER and only one SLAVE.
I stopped replication, I did a backup on my slave and it recreated in
another machine so now I have two SLAVES connected to database MASTER.
Subject: Re: Replication problems
From: Jared Richardson [EMAIL PROTECTED]
===
Did you change the slave number in the second slave's config file? I forget
the exact syntax, but if memory serves, there is a number in the my.ini (or
my.cnf) that must be unique. If you just copied, you may have
Both my slave server say they are replicating correctly in the
mysqld.log but they arn't. Any change made to the master is not
reflected to the slaves. I have tried reseting the master and slaves but
didn't change anything. Also tried redumping the databases to the slaves
but that didn't effect
I'm having the same problems, but I've noticed that the reported error
doesn't seem to be a real failure. The databases seem to be updated correctly.
When I look at my slave error log, I can see that the at position is
a number that always matches the size of the log file on the master.
Just to let you know that when I installed 3.23.51 binary on both Debian
Linux boxes, same problem, but when I re-installed the 3.23.49a binary on
both boxes the problem went away. Uncertain why.
Regards,
Jeff Hill
At 08:25 AM 18/06/2002 -0400, Jeff Hill wrote:
I'm having the same problems,
Hi,
On 13 Feb 2002, at 12:44, Henning Sprang wrote:
Was something wrong with this post or is it really such a weird
problem that there is neither a solution nor anything i could do to
solve it, nor anything i could do to find out more about it?
Well. Replication is somewhat weird. ;-)
Hy,
Was something wrong with this post or is it really such a weird problem
that there is neither a solution nor anything i could do to solve it,
nor anything i could do to find out more about it?
that was the message:
I get some Errors when doing Replication on MySQL 3.23.47. And can't get
Hy All,
I get some Errors when doing Replication on MySQL 3.23.47. (I did not
upgrade because in Changelog there is no Replication-Related Bugfix
mentioned)
the Messages in error-log are:
020208 17:43:20 mysqld started
/usr/local/mysql/3.23.47/libexec/mysqld: ready for connections
020208
Hy all,
I just try to set up Replication with two mysql databases,
i did everything like described in the Replication-Howto.
Now i get the following errors when starting the slave:
020117 18:37:55 mysqld started
Can't initialize InnoDB as 'innodb_data_file_path' is not set
Hy, sorry for the trouble!
i tried to do a
chown mysql:daemon -R *
in the data dir, and after that it worked.
I didn't try that before because somehow i couldn't see a connection
between differing ownerships and disfunctional tables when looking at this.
sorry,
henning
Henning Sprang wrote:
chown -R mysql:mysql /var/lib/mysql
( or whatever the data directory is ).
Henning Sprang wrote:
Hy all,
I just try to set up Replication with two mysql databases,
i did everything like described in the Replication-Howto.
Now i get the following errors when starting the slave:
020117
Hello Heikki,
Saturday, January 05, 2002, 11:55:02 PM, you wrote:
Hello mysql,
I'm using mysql 3.23.47 with Innodb and trying to play around with
replication. The replication options are default.
I got one table content occasionally deleted on slave, and note what
HT Who deleted the
Hello mysql,
I'm using mysql 3.23.47 with Innodb and trying to play around with
replication. The replication options are default.
I got one table content occasionally deleted on slave, and note what
this did not stop the replication: The inserts are successfully
passed, therefore the
Hi!
-Original Message-
From: Peter Zaitsev [EMAIL PROTECTED]
To: [EMAIL PROTECTED] [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: Saturday, January 05, 2002 10:35 PM
Subject: Innodb/Replication problems.
Hello mysql,
I'm using mysql 3.23.47 with Innodb and trying
Hi.
My first guess would be that somehow the slave got out of sync. I
would try to update the slave by hand and see what happens after
restart.
Sorry, I don't see what could be the cause.
Bye,
Benjamin.
On Tue, Oct 02, 2001 at 06:07:29PM +0200, [EMAIL PROTECTED] wrote:
[...]
I have
Benjamin Pflugmann writes:
Hi. My first guess would be that somehow the slave got out of
sync. I would try to update the slave by hand and see what happens
after restart.
Sorry, I don't see what could be the cause.
I tried the following:
on master:
reset master
on all slaves:
slave stop
Benjamin Pflugmann writes:
Hi. Does the error log of the master contain any error?
Nothing at all in the master logs.
Does the new log position make sense?
Yes, the position is ok, and the slave gets the updates. Its just that
strange error messages about dropped connections and 0-byte
Description:
Hi,
I have 28 linux boxes configured identically, 27 as slaves, one as
master. On all 27 slaves, everything works fine, but only on one I have strange
errors in the logs:
011002 17:49:49 Slave: received 0 length packet from server, apparent master
shutdown: (0)
011002
Also my master.info ends up being wrong whenever the
server is
rebooted. (binlog.100 becomes binlog.100\n).
Can you expand on that problem a bit?
When I do a show slave status before a reboot I have this:
On Wed, Aug 29, 2001 at 12:18:02PM -0400, Michael Eklund wrote:
Am I the only one that thinks that mysql ought to replicate NOW,
CURRENT_DATE, etc. as the time when those actual inserts happened
not as NOW,CURRENT_DATE,etc.
Probably not.
If you are replicating accross a distance (12,15,20
Am I the only one that thinks that mysql ought to replicate
NOW, CURRENT_DATE, etc. as the time when those actual
inserts happened not as NOW,CURRENT_DATE,etc. If you are
replicating accross a distance (12,15,20 hops) and there is
a connectivity problem, then you end up with data that is
out of
Hello,
I'm very new to MySQL and have posted a few mails regarding replication in
mySQL. I'm still having problems ! Can someone please send me a step by
step guide on how I can setup replication between my ISPs MySQL database and
one I wish to have and use locally. I have already a database
15, 2001 10:55 PM
Subject: replication problems questions
Hello,
I'm very new to MySQL and have posted a few mails regarding replication in
mySQL. I'm still having problems ! Can someone please send me a step by
step guide on how I can setup replication between my ISPs MySQL database
On Wed, Aug 15, 2001 at 10:55:53PM +0100, Neil Tompkins wrote:
Hello,
I'm very new to MySQL and have posted a few mails regarding
replication in mySQL. I'm still having problems ! Can someone
please send me a step by step guide on how I can setup replication
between my ISPs MySQL
Luc Foisy wrote:
We are looking for a solution to backing up a remote database, without using
mysqldump, and replication seemed to offer the solution required.
I set up the master/slave configurations on both the master and the slave
exactly the way it was shown in the MySQL documentation
We are looking for a solution to backing up a remote database, without using
mysqldump, and replication seemed to offer the solution required.
I set up the master/slave configurations on both the master and the slave
exactly the way it was shown in the MySQL documentation (4.10.3 How To Set
Up
Hi
Before enabling replication between two live machines, I've been doing some tests in
the office
between two similar machines.
Everything appears to work well, as expected, except the command
LOAD TABLE x FROM MASTER;
This records an error on the screen
ERROR 1188: Error From master:
Hi
Problem solved.
After adding select permission (now file+select) to the replication user the command
LOAD TABLE x FROM MASTER
works perfectly.
The only question is, why does this command need SELECT permission, whilst the rest
of replication does not ?
Simon
On Tuesday 29 May 2001
-List: contact [EMAIL PROTECTED]; run by ezmlm (http://www.ezmlm.org)
List-ID: mysql.mysql.com
List-Help: mailto:[EMAIL PROTECTED]
List-Unsubscribe: mailto:[EMAIL PROTECTED]
List-Post: mailto:[EMAIL PROTECTED]
List-Subscribe: mailto:[EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: replication
mysql sql db
I am unable to get replication running. I have set up both master and slave
systems with version 3.23.33-log of musql. I can do a "load table from
master" but when I start the slave, all I get in the slave log is:
010410 16:37:24 Slave: Failed reading log event, reconnecting to
Hi,
we use mysql with replication, all works fine.
Now we wan't exclude some tables from the replication.
I enter in my.cnf the line
binlog-ignore-db = news
(stop the master and restart the master after the change in my.cnf)
After this, the master don't repliacted any databases,
only the
My Replication-Slave crashed a few days ago with an error in the error-log
saying something like "duplicate primary key processing query "INSERT INTO
testtable (time,name,number) VALUES (NOW(),'Hello',10)"
testtable's primary key was (time,name)
time: datetime
name: varchar
number: int
What
"JK" == Jan Kirchhoff [EMAIL PROTECTED] writes:
JK If the Slave gets out of sync (loses the connection to the server), connects
JK again and tries to catch up, it processes those two queries *within one
JK second* which would result in an duplicate primary key on the slave. The
JK Slave
73 matches
Mail list logo
