-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
my replication slave crashed. Now, I am unable to restart with following
error message:
081021 21:34:21 [Note] Slave SQL thread initialized, starting
replication in log 'log.000129' at position 28457291, relay log
'/video/mysql/mysqld-relay-bin.0
Good issue, I totally had the same concerns, so we built our own
system. As a side note we run an admin server which we use to
generate reports, run backups and so on - it takes load off the
production servers, where speed is critical. Recovery from backup
however is a whole other issue, an
David Ulevitch wrote:
On Jul 12, 2005, at 6:15 AM, gerald_clark wrote:
Nightly backup and binlogs can take you to any point in the day.
I failed to make my entire point clear then. That's true.
But when someone does the "oh fsck, I think I just ran a catastrophic
query on our productio
On Jul 12, 2005, at 6:15 AM, gerald_clark wrote:
Nightly backup and binlogs can take you to any point in the day.
I failed to make my entire point clear then. That's true.
But when someone does the "oh fsck, I think I just ran a catastrophic
query on our production database" we would now h
ld be (more or less, I'd have more
checks/auditing):
1) lynx --source http://private.internal.server/operations/
replication-status [contents $master_log_file:$master_log_pos]
2a) if (values == previous_values || values == 'HALT'); do stop
slave; page_operations_team; sleep 30
, I'd have more
checks/auditing):
1) lynx --source http://private.internal.server/operations/
replication-status [contents $master_log_file:$master_log_pos]
2a) if (values == previous_values || values == 'HALT'); do stop
slave; page_operations_team; sleep 30 mins; done;
2b
>>>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
>>>sett
ation 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-test
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;
&g
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 sho
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 mas
Which version are you running? Try slave start;
-Original Message-
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: 6/16/04 2:53 AM
Subject: start slave;
I am running MySQL 2.23 and configuring replication.
When I execute "start slave;" to start replication from slave, mys
I am running MySQL 2.23 and configuring replication.
When I execute "start slave;" to start replication from slave, mysql
prompts...
"ERROR 1064: You have an error in your SQL syntex near 'start slave' at
line 1"
Any idea? Thanks.
Joseph
--
MySQL General
d. Fix the problem, and
re-start the slave thread with mysqladmin start-slave - log 'FIRST' position
1544
When I tried to restart the slave according to the syntax in the error, I
get the following:
mymach2:/usr/local/mysql/var $ mysqladmin start-slave - log 'FIRST'
posi
14 matches
Mail list logo
