Probably a silly question, but if I have my logs set to binary, how
can I read them and check on a query that's failing? I don't
necessarily want to switch to text logs because we'll want to do
replication soon here, so I want to keep it as a binary log. My problem
is I have a query
Ashley M. Kirchner wrote:
Probably a silly question, but if I have my logs set to binary, how
can I read them and check on a query that's failing? I don't
necessarily want to switch to text logs because we'll want to do
replication soon here, so I want to keep it as a binary log. My
On Fri, 2007-04-27 at 09:19 -0500, [EMAIL PROTECTED] wrote:
So if one is doing a full mysqldump every night, all bin-logs can be
deleted after this?
On the slave - Yes. In fact I would highly recommend it before
starting the slave processes again. This will reset the bin log's
'position
So if one is doing a full mysqldump every night, all bin-logs can be
deleted after this?
If bin-logging is disabled, will master/slave syncing still occur?
David
Issuing a 'reset master' will purge all of the logs as well. I wouldn't
just rm them, as they are being tracked in the index file
Running mysql 4, just poked into data and see I have gigs and gigs of
hostname-bin.xxx log files.
How does one maintain these, can someone point me to relevant data on what
to do about drive space being lost to these?
thanks
--
-
Scott
Hi,
Scott Haneda wrote:
Running mysql 4, just poked into data and see I have gigs and gigs of
hostname-bin.xxx log files.
How does one maintain these, can someone point me to relevant data on what
to do about drive space being lost to these?
thanks
See attached message I just sent to
In the short term, see the manual page for PURGE MASTER LOGS. In the
long term, write a cron job.
innotop (http://sourceforge.net/projects/innotop) also has a new
feature, unreleased because I just wrote it a few hours ago, which will
help you figure out which binlogs can be purged safely
Hi Scott,
Scott Haneda wrote:
In the short term, see the manual page for PURGE MASTER LOGS. In the
long term, write a cron job.
innotop (http://sourceforge.net/projects/innotop) also has a new
feature, unreleased because I just wrote it a few hours ago, which will
help you figure out which
Yes -- sorry for being so general. You can use the binlogs for a)
replication b) replaying changes since your last backup so you get
point-in-time recovery. If you have no replication slaves, just delete
everything older than your latest backup. You can just use 'rm'. If
you use PURGE
stress). You could restore the previous nights backup
and run these bin logs up to the point of the delete command - a little
bit of editing would be needed to do this, but you get the idea.
For this to work smoothly, you need to reset the logs after every
backup. If your using mysqldump, just add
So, I take it since I do not have a slave at all, I could safely just
disable this feature altogether?
If I do not need point in time recovery, and the once every 12 hour dump I
do across all databases is ok with me, I suppose I can just disable said
feature? Heck, some of these boogers are a
Hi All,
I have a question on purging some old bin-logs.
whats the best way to do it?
This is a fairly old version - 4.0.18-standard-log. I have 128 1 GB
files out there, going back 8 months.
I think the correct syntax is :
PURGE BINARY LOGS TO 'mysql-bin.010';
but from what
http://dev.mysql.com/doc/refman/5.0/en/purge-master-logs.html
DÆVID
-Original Message-
From: George Law [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 10, 2006 11:56 AM
To: mysql@lists.mysql.com
Subject: purging bin logs
Hi All,
I have a question on purging some old bin
I'm using MySQL 4.1 and the master runs on a Windows 2000 server. This
master replicates to several slaves.
While browsing the data directory on the master, there are a lot of
binary log files that are named:
MasterName-relay-bin.99 (where MasterName is the server-name and
99 is a
Those do indeed have something to do with replication - they're a
record of all data manipulation commands (inserts, updates, deletes,
table creates and alters, etc). The slaves basically read the
commands from those files in order to replicate what the master has
done.
You can purge them
(0.00 sec)
There are relay-bin files that correspond in the 6-digit number to the
mysql-bin logs above.
I was under the impression that the PURGE MASTER command would delete
the mysql-bin files, not the replay-bin files. I was looking at the
manual earlier and could not find a reference to deleting
;
+--+
| Log_name |
+--+
| mysql_bin.000344 |
| mysql_bin.000345 |
| mysql_bin.000346 |
+--+
3 rows in set (0.00 sec)
There are relay-bin files that correspond in the 6-digit number to the
mysql-bin logs above.
I was under the impression
Bremer
Sent: Wednesday, June 28, 2006 15:59
To: 'Dan Buettner'
Cc: mysql@lists.mysql.com
Subject: RE: Relay-bin logs
Dan,
Yes they are on the master. The master is not configured as a slave:
mysql show slave status;
Empty set (0.07 sec)
mysql show master status
PROTECTED]
www.nisc.coop
-Original Message-
From: Dan Buettner [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 28, 2006 15:47
To: Dirk Bremer
Cc: mysql@lists.mysql.com
Subject: Re: Relay-bin logs
My bad, Dirk, sorry. I missed that you were asking about relay-bin
files, thought you
is that
there were inserts into this table earlier in the binlog, and they did
not produce any error messages.
Eric
-Original Message-
From: Scott Tanner [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 08, 2006 3:46 PM
To: Goldblatt, Eric
Subject: Re: replication after editing bin logs
Do you have control over the DELETE queries? If so I would look into the
option of using 'SQL_LOG_BIN':
http://dev.mysql.com/doc/refman/5.0/en/set-option.html
SQL_LOG_BIN = {0 | 1}
If set to 0, no logging is done to the binary log for the client.
The client must have the SUPER
: mysql@lists.mysql.com
Subject: Re: replication after editing bin logs
Do you have control over the DELETE queries? If so I would look into the
option of using 'SQL_LOG_BIN':
http://dev.mysql.com/doc/refman/5.0/en/set-option.html
SQL_LOG_BIN = {0 | 1}
If set to 0, no logging is done
:38 AM
To: Goldblatt, Eric
Cc: Mysql User List
Subject: Re: replication after editing bin logs
Can you post the failed SQL statement from your altered bin log, and
maybe the preceding commands related to that table?
Scott Tanner
AMi Entertainment.net
On Thu, 2006-03-09 at 08:28, Goldblatt, Eric
. But I haven't done
this in a replication situation.
Dan.
-Original Message-
From: Goldblatt, Eric [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 09, 2006 2:45 PM
To: Atle Veka
Cc: mysql@lists.mysql.com
Subject: RE: replication after editing bin logs
Atle,
No, unfortunately we have
Hello,
Another division in my organization is maintaining a mysql database. For
various reasons, data is deleted from this database after it has aged
more than a month. My division has a need for long term storage of the
same data, so I am trying the following strategy:
1. Create a snapshot
to match the position on
the master on both servers, the data is NOT getting updated. The
position continues to increment up and up, but nothing is changed.
When I had successful replication in the past, I remeber the bin-logs
being transfered from the master to the slave for the updates
the bin-logs
being transfered from the master to the slave for the updates. This is
currently NOT happenning on both servers.
When I execute the 'LOAD DATA FROM MASTER' I ALWAYS get an error.
ERROR 1189: Net error reading from master
And I get the same error on both servers.
Now I know
Hi list, I have 2 MySQL servers ver. 3.23.58, one is the master and the
other one the slave, the slave was working until I modified the following
lines in the master my.cnf file:
log-bin = /mnt/binlogs/masterBinLogs/sauron-bin
the directory and files have the following attributes:
drwxr-xr-x
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am trying to prune some bin-logs and noticed:
mysql show master logs;
++
| Log_name |
++
| db-bin.001 |
| db-bin.002 |
| db-bin.003 |
| db-bin.004 |
| db-bin.005 |
| db-bin.006 |
| db-bin.007 |
| db-bin.008 |
| db-bin.009
to prune some bin-logs and noticed:
mysql show master logs;
++
| Log_name |
++
| db-bin.001 |
| db-bin.002 |
| db-bin.003 |
| db-bin.004 |
| db-bin.005 |
| db-bin.006 |
| db-bin.007 |
| db-bin.008 |
| db-bin.009 |
| db-bin.010 |
| db-bin.011 |
| db-bin.012 |
| db-bin.013
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 15 June 2004 01:29 pm, Eric Gunnett wrote:
You can do a reset master, and it will start the log over at 001 and
remove the old log files that are there.
Thanks,
I also had to restart the slaves (change master to command) to start
.
Hope it helps
Thierno 6C
- Original Message -
From: Christopher L. Everett [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, October 03, 2003 12:49 AM
Subject: ran out of space for bin logs
Aparrently my binlogs grew and grew and ate up all the space on their
partition
Aparrently my binlogs grew and grew and ate up all the space on their
partition.
At this point, I see this on the master
mysql show master status;
Empty set (0.00 sec)
and this on the slave:
mysql show slave status\G
*** 1. row ***
Occasionally I will notice that one of my slaves is not in sync. It
will be reading fine from the master's bin-log, but it gets hung up in
the relay log and stops. It seems there is corrupt data in the relay
log. When I use the mysqlbinlog utility, I get tons of mysqlbinlog:
Error writing file
as to a ultra-early stage 2 box test system in a
LAN which does 2-way replication.
One runs LINUX and the other one Win2K. I have MySQL 4.0.4 on both.
Now the bin-logs are piling up on both machines. Well, sort of ;)
If I eventually get the whole thing going, the boxes will be in two
different
Hi,
I'm trying to figure out a viable two site configuration.
Currently I got as far as to a ultra-early stage 2 box test system in a
LAN which does 2-way replication.
One runs LINUX and the other one Win2K. I have MySQL 4.0.4 on both.
Now the bin-logs are piling up on both machines. Well, sort
| |
| 0 | 0 | 0 | |
++-+-+---+
Fix:
Submitter-Id:
Originator:kai uwe tempel
Organization: university leipzig
MySQL support: none
Synopsis: slaves (bin
I'm having a difficult time synchronizing my Master and Slave Servers.
I've been doing this using MySQL Binary Logs, where the Master rotates the
logs at 1 hour times, and the slave downloads it and imports it.
What happens why I try to pipe the binlog into mysql is that it reports and
error
38 matches
Mail list logo
