Replication Master Not Logging Changes?

[Lukas Bradley]

It appears as if my master is not logging changes to any databases. When I
use mysqlbinlog against the current (and previous) logs, I get the
following:

dollars@nat451:/var/log/mysql$ mysqlbinlog mysql-bin.003
# at 4
#031201 18:57:25 server id 154 Start: binlog v 4, server v created
691231 19:00:00
dollars@nat451:/var/log/mysql$ mysqlbinlog mysql-bin.004
# at 4
#031201 19:28:54 server id 154 Rotate to mysql-bin.005

In those time periods, I added a table named "Lukas" to the "dollars"
database. I also added three rows. Nothing was output to the logs.

Here is the my.cnf lines regarding replication.

server-id = 154
log-bin = /var/log/mysql/mysql-bin.log
binlog-do-db = dollars,epoch
When running "show master status" I get the following:

File Position Binlog_do_db Binlog_ignore_d b
mysql-bin.005 4 dollars,epoch

The slave connects correctly, and waits patiently for updates. The master
logs the slave connecting, but gives it nothing.

Any ideas?

Lukas

[Lukas Bradley]

The preceding setup is on MySQL 4.0.16 on Debian LINUX.
"Lukas Bradley" <lu***@REMOVE-IT-somnia.com> wrote in message
news:Xv******** ************@sp eakeasy.net...

It appears as if my master is not logging changes to any databases. When I use mysqlbinlog against the current (and previous) logs, I get the
following:

dollars@nat451:/var/log/mysql$ mysqlbinlog mysql-bin.003
# at 4
#031201 18:57:25 server id 154 Start: binlog v 4, server v created 691231 19:00:00
dollars@nat451:/var/log/mysql$ mysqlbinlog mysql-bin.004
# at 4
#031201 19:28:54 server id 154 Rotate to mysql-bin.005

In those time periods, I added a table named "Lukas" to the "dollars"
database. I also added three rows. Nothing was output to the logs.

Here is the my.cnf lines regarding replication.

server-id = 154
log-bin = /var/log/mysql/mysql-bin.log
binlog-do-db = dollars,epoch
When running "show master status" I get the following:

File Position Binlog_do_db Binlog_ignore_d b
mysql-bin.005 4 dollars,epoch

The slave connects correctly, and waits patiently for updates. The master
logs the slave connecting, but gives it nothing.

Any ideas?

Lukas

[Lukas Bradley]

The preceding setup is on MySQL 4.0.16 on Debian LINUX.
"Lukas Bradley" <lu***@REMOVE-IT-somnia.com> wrote in message
news:Xv******** ************@sp eakeasy.net...

It appears as if my master is not logging changes to any databases. When I use mysqlbinlog against the current (and previous) logs, I get the
following:

dollars@nat451:/var/log/mysql$ mysqlbinlog mysql-bin.003
# at 4
#031201 18:57:25 server id 154 Start: binlog v 4, server v created 691231 19:00:00
dollars@nat451:/var/log/mysql$ mysqlbinlog mysql-bin.004
# at 4
#031201 19:28:54 server id 154 Rotate to mysql-bin.005

In those time periods, I added a table named "Lukas" to the "dollars"
database. I also added three rows. Nothing was output to the logs.

Here is the my.cnf lines regarding replication.

server-id = 154
log-bin = /var/log/mysql/mysql-bin.log
binlog-do-db = dollars,epoch
When running "show master status" I get the following:

File Position Binlog_do_db Binlog_ignore_d b
mysql-bin.005 4 dollars,epoch

The slave connects correctly, and waits patiently for updates. The master
logs the slave connecting, but gives it nothing.

Any ideas?

Lukas

[Lukas Bradley]

I'm still trying to make this work, so I'm just going to keep posting what I
find.

I'm certainly using the correct database, and my transactions are being
commited. I've tried MyISAM and InnoDB tables, and neither are shown.

Here is a sample query:

use dollars ;
create table Bobby
(
id int unsigned primary key auto_increment,
ssn int
) type=InnoDB ;
insert into Bobby (ssn) values (12312),(123125 44),(1231231);
commit ;
Now, the binlogs before the query are as follows:

lukas@localhost :/var/log/mysql$ dir
total 28
drwxrwxrwx 2 dollars mysql 4096 Dec 1 21:53 ./
drwxr-xr-x 9 root root 4096 Dec 1 06:52 ../
-rw-rw---- 1 dollars users 1271 Dec 1 21:36 mysql-bin.001
-rw-rw---- 1 dollars users 655 Dec 1 21:59 mysql-bin.002
-rw-rw---- 1 dollars users 58 Dec 1 21:49 mysql-bin.index
-rw-rw---- 1 dollars users 348 Dec 1 21:49 mysql-slow.log

After the preceding code block, the binlogs have increased.

lukas@localhost :/var/log/mysql$ dir
total 24
drwxrwxrwx 2 dollars mysql 4096 Dec 1 21:59 ./
drwxr-xr-x 9 root root 4096 Dec 1 06:52 ../
-rw-rw---- 1 dollars users 1271 Dec 1 21:36 mysql-bin.001
-rw-rw---- 1 dollars users 904 Dec 1 22:02 mysql-bin.002
-rw-rw---- 1 dollars users 58 Dec 1 21:49 mysql-bin.index
-rw-rw---- 1 dollars users 348 Dec 1 21:49 mysql-slow.log

As you can see, the bin.002 log increased from 655 bytes to 904 bytes.
However, running mysqlbinlog on the 002 file STILL produces nothing:

lukas@localhost :/var/log/mysql$ mysqlbinlog mysql-bin.002
# at 4
#031201 21:49:39 server id 154 Start: binlog v 4, server v created
691231 19:00:00

There are two things I notice about this output. First, the last part
"created 691231 19:00:00" is 7pm on New Years Eve 1969. Is this
coincidentally near the epoch, or was this a missed compiled time? I don't
think this should be the time of the binlog creation....

The second thing I notice..... well.... the second thing I notice is the
damn thing isn't working. So someone help me.... please?

Lukas

[Lukas Bradley]

I'm still trying to make this work, so I'm just going to keep posting what I
find.

I'm certainly using the correct database, and my transactions are being
commited. I've tried MyISAM and InnoDB tables, and neither are shown.

Here is a sample query:

use dollars ;
create table Bobby
(
id int unsigned primary key auto_increment,
ssn int
) type=InnoDB ;
insert into Bobby (ssn) values (12312),(123125 44),(1231231);
commit ;
Now, the binlogs before the query are as follows:

lukas@localhost :/var/log/mysql$ dir
total 28
drwxrwxrwx 2 dollars mysql 4096 Dec 1 21:53 ./
drwxr-xr-x 9 root root 4096 Dec 1 06:52 ../
-rw-rw---- 1 dollars users 1271 Dec 1 21:36 mysql-bin.001
-rw-rw---- 1 dollars users 655 Dec 1 21:59 mysql-bin.002
-rw-rw---- 1 dollars users 58 Dec 1 21:49 mysql-bin.index
-rw-rw---- 1 dollars users 348 Dec 1 21:49 mysql-slow.log

After the preceding code block, the binlogs have increased.

lukas@localhost :/var/log/mysql$ dir
total 24
drwxrwxrwx 2 dollars mysql 4096 Dec 1 21:59 ./
drwxr-xr-x 9 root root 4096 Dec 1 06:52 ../
-rw-rw---- 1 dollars users 1271 Dec 1 21:36 mysql-bin.001
-rw-rw---- 1 dollars users 904 Dec 1 22:02 mysql-bin.002
-rw-rw---- 1 dollars users 58 Dec 1 21:49 mysql-bin.index
-rw-rw---- 1 dollars users 348 Dec 1 21:49 mysql-slow.log

As you can see, the bin.002 log increased from 655 bytes to 904 bytes.
However, running mysqlbinlog on the 002 file STILL produces nothing:

lukas@localhost :/var/log/mysql$ mysqlbinlog mysql-bin.002
# at 4
#031201 21:49:39 server id 154 Start: binlog v 4, server v created
691231 19:00:00

There are two things I notice about this output. First, the last part
"created 691231 19:00:00" is 7pm on New Years Eve 1969. Is this
coincidentally near the epoch, or was this a missed compiled time? I don't
think this should be the time of the binlog creation....

The second thing I notice..... well.... the second thing I notice is the
damn thing isn't working. So someone help me.... please?

Lukas