uot; <[EMAIL PROTECTED]>; "Krishna Chandra Prajapati" <[EMAIL
PROTECTED]>; "MYSQL General List"
Sent: Monday, May 26, 2008 1:03 PM
Subject: Re: error while starting replication for the first time
> Hi All,
> The issue has been solved, we removed relay-log.index fil
Hi All,
The issue has been solved, we removed relay-log.index files which was
refering to the old relay-log file. After this the CHANGE MASTER worked and
replication is going on fine.
regards
anandkl
On 5/24/08, Moon's Father <[EMAIL PROTECTED]> wrote:
>
> I think you should check the error wit
I think you should check the error with perror at first.
On Sat, May 24, 2008 at 12:46 AM, Mike <[EMAIL PROTECTED]> wrote:
> On Fri, May 23, 2008 at 12:08 PM, Ananda Kumar <[EMAIL PROTECTED]> wrote:
>
> > Hi Mike,
> > Since i have done a fresh backup from master (with master db down), and
> > cop
On Fri, May 23, 2008 at 12:08 PM, Ananda Kumar <[EMAIL PROTECTED]> wrote:
> Hi Mike,
> Since i have done a fresh backup from master (with master db down), and
> copied over the same to slave. Then why is the slaving looking for old
> relay-log. I also did the "RESET SLAVE", bit still getting error
Hi Mike,
Since i have done a fresh backup from master (with master db down), and
copied over the same to slave. Then why is the slaving looking for old
relay-log. I also did the "RESET SLAVE", bit still getting error.
I am wondering, why is the slave looking for old relay-logs
On 5/23/08, Mike <
Ok, since you do not have the bin log you need to start over again with the
replication and do either a
mysqldump or get the rawdata. then once you have the data then you can
start replication again.
http://dev.mysql.com/doc/refman/5.0/en/replication-solutions-backups-mysqldump.html
http://dev.my
RESET MASTER...delete all the bin logs. Infact i tried this on the slave as
it also a MASTER to itself, but the error kept on coming.
regards
anandkl
On 5/23/08, Mike <[EMAIL PROTECTED]> wrote:
>
>
>
> On Fri, May 23, 2008 at 8:13 AM, Ananda Kumar <[EMAIL PROTECTED]> wrote:
>
>> Files is owned b
On Fri, May 23, 2008 at 8:13 AM, Ananda Kumar <[EMAIL PROTECTED]> wrote:
> Files is owned by mysql, but the point is, these relay-log files are not
> present.
> Before setting up the slave, i cleaned up all files.
>
If you want the logs back you could use RESET MASTER maybe.
http://dev.mysql
Files is owned by mysql, but the point is, these relay-log files are not
present.
Before setting up the slave, i cleaned up all files.
regards
anandkl
On 5/23/08, Krishna Chandra Prajapati <[EMAIL PROTECTED]> wrote:
>
> Please check the ownership of the files copied on the slave.
>
> Give permis
Please check the ownership of the files copied on the slave.
Give permissions by chown -R mysql:mysql
On Fri, May 23, 2008 at 2:47 PM, Ananda Kumar <[EMAIL PROTECTED]> wrote:
> Hi Krishna,
> As i said, this is a complete copy from master db to slave.
> I have deleted all old files from slave and
Hi Krishna,
As i said, this is a complete copy from master db to slave.
I have deleted all old files from slave and setting up from scratch, by
taking a complete backup from master, copying over to slave and using the
change master command with BIN LOG and POSITION taken before taking a backup
copy
check permissions
On Fri, May 23, 2008 at 12:33 PM, Ananda Kumar <[EMAIL PROTECTED]> wrote:
> Hi All,
> I shutdown my master, took a db files backup. Copied it over to slave
> machine.
> I executed "change master" command, then when i start slave "slave start",
> i
> get the below error. I did "r
Hi All,
I shutdown my master, took a db files backup. Copied it over to slave
machine.
I executed "change master" command, then when i start slave "slave start", i
get the below error. I did "reset slave", but still getting same error, what
could be the reason, and how to fix it.
080522 23:04:05 [
13 matches
Mail list logo
