-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
> pe
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]
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?
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 w
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 scri
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
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.
Also, overnight, my slaves reported this error:
041108 19:06:42 [Note] Slave I/O thread: connected to maste
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: http://li
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
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
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
failin
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 erro
Nils,
(B
(BI agree with you, you do have to have all the log files, which is why I
(Breset the master.
(B
(BAccording to the manual:
(B
(B4.10.7.5 RESET MASTER (master)
(B
(BDeletes all binary logs listed in the index file, resetting the binlog index
(Bfile to be empty. Previously na
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 Valent
-Ursprüngliche 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 > ve
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 replicati
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 sum
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 whe
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 y
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
Hello!
You will get problems when you set the 2nd slaves server-id the same as
other one. server-ids MUST be unique...once made that mistake too...
Greetings
Ralf
Gerald Clark wrote:
> Did you copy the master.info file over too?
>
>
> Santiago Alba wrote:
>
>> Hi All,
>>
>> I had a system re
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
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,
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.
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:
>
> 020
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:
> > 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
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 da
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 documentati
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 10:06,
31 matches
Mail list logo
