# mk-table-checksum issue with mysql log tables

**URL:** <https://forums.percona.com/t/mk-table-checksum-issue-with-mysql-log-tables/2389>\
**Category:** Other Tools\
**Created:** [October 26, 2010, 3:44pm UTC](https://forums.percona.com/t/mk-table-checksum-issue-with-mysql-log-tables/2389 "2010-10-26T15:44:58Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![iberkner](https://avatars.discourse-cdn.com/v4/letter/i/c67d28/32.png) [@iberkner](https://forums.percona.com/u/iberkner)\
**Post date:** [October 26, 2010, 3:44pm UTC](https://forums.percona.com/t/mk-table-checksum-issue-with-mysql-log-tables/2389/1 "2010-10-26T15:44:58Z")

</div>

Running the checksum script and it says that the general\_log and slow\_log files are different even though they are not used and contain no records.

Any suggestions? I just ran “flush logs” maybe that will help.

Differences on h=192.168.1.1  
DB TBL CHUNK CNT\_DIFF CRC\_DIFF BOUNDARIES  
mysql general\_log 0 0 1 1=1  
mysql slow\_log 0 0 1 1=1

Differences on h=192.168.1.226  
DB TBL CHUNK CNT\_DIFF CRC\_DIFF BOUNDARIES  
mysql general\_log 0 0 1 1=1  
mysql slow\_log 0 0 1 1=1

---

<div class="post-metadata">

**Author:** ![iberkner](https://avatars.discourse-cdn.com/v4/letter/i/c67d28/32.png) [@iberkner](https://forums.percona.com/u/iberkner)\
**Post date:** [October 26, 2010, 4:14pm UTC](https://forums.percona.com/t/mk-table-checksum-issue-with-mysql-log-tables/2389/2 "2010-10-26T16:14:00Z")

</div>

I just realized that flush logs of course will not help with this issue. Specifically this issue is caused by the error generated with the mk-table-checksum process that I posted in a previous post:

$VAR1 = {Code =\> ‘1592’,Level =\> ‘Note’,Message =\> ‘Statement may not be safe to log in statement format.’}; at /root/bin/mk-table-checksum line 5066. while doing mysql.general\_log  
$VAR1 = {Code =\> ‘1592’,Level =\> ‘Note’,Message =\> ‘Statement may not be safe to log in statement format.’}; at /root/bin/mk-table-checksum line 5066. while doing mysql.slow\_log

These errors refer to the general\_log and slow\_log tables and these are the tables that are showing not synched up.

So now the question is really what is causing this error…

---

<div class="post-metadata">

**Author:** ![iberkner](https://avatars.discourse-cdn.com/v4/letter/i/c67d28/32.png) [@iberkner](https://forums.percona.com/u/iberkner)\
**Post date:** [October 26, 2010, 4:16pm UTC](https://forums.percona.com/t/mk-table-checksum-issue-with-mysql-log-tables/2389/3 "2010-10-26T16:16:47Z")

</div>

This article seems to be very related?

[URL][MySQL Bugs: #42851: Spurious "Statement is not safe to log in statement format." warnings](http://bugs.mysql.com/bug.php?id=42851%5B/URL%5D)

---

<div class="post-metadata">

**Author:** ![iberkner](https://avatars.discourse-cdn.com/v4/letter/i/c67d28/32.png) [@iberkner](https://forums.percona.com/u/iberkner)\
**Post date:** [October 27, 2010, 3:50pm UTC](https://forums.percona.com/t/mk-table-checksum-issue-with-mysql-log-tables/2389/4 "2010-10-27T15:50:05Z")

</div>

Its fun replying to myself ). Alas, hopefully someone will find this useful.

My understanding is that these tables are essentially independent on each system, so testing replication on them is unnecessary. I initially prevented replication from checking these tables by using the --table-ignore option and then switched to the --ignore-databases option and am now only checksumming the databases that I care about.