Closed GoogleCodeExporter closed 9 years ago
Hi acotto,
with the attached patch (devs: see
http://code.google.com/p/maatkit/issues/detail?id=99#c1) you should be able to
ignore
the user-table so you can at least sync the other ones.
Regards
Pascal
Original comment by m...@pascalhofmann.de
on 30 Oct 2008 at 1:35
Attachments:
s/sync/checksum/ :)
Original comment by m...@pascalhofmann.de
on 30 Oct 2008 at 1:36
acotto,
mk-table-checksum has recently undergone some work. Could you please download
the
newest rev and tell me if this problem still happens? (I bet it still will, but
it's
best to check.)
And what is max_allowed_packet set to on your server?
And if possible, could you provide the full SHOW CREATE TABLE cs_core.user (you
could
email it to my Google Code username by changing the .n@ part to .nichter@)?
Thanks.
Original comment by dan...@percona.com
on 12 Nov 2008 at 4:04
Target these for release end of January 2009.
Original comment by baron.schwartz
on 4 Jan 2009 at 5:04
acotto, can you create a trivial Perl program that just connects and runs the
command, and see if it breaks? Something like
perl -MDBI -MData::Dumper -e'$dbh=DBI->connect(....); print Dumper
$dbh->selectall_arrayref("show create table....")'
Original comment by baron.schwartz
on 10 Jan 2009 at 9:22
K, I ran this:
perl -MDBI -MData::Dumper -e'$dbh = DBI->connect(...); print Dumper;
@result = $dbh->selectall_arrayref("show create table user"); print
$result[0][0][1];'
And it finished just fine and printed out the user table schema.
Original comment by aco...@gmail.com
on 10 Jan 2009 at 10:14
Is this still an issue? I'm at a loss for how to reproduce that kind of dbi
error.
Original comment by dan...@percona.com
on 5 Jun 2009 at 2:51
Original comment by dan...@percona.com
on 11 Jun 2009 at 8:43
I'm going to close this issue for now since there hasn't been an
update/response in
quite awhile. Please respond and help me reproduce this error if this is still
an issue.
Original comment by dan...@percona.com
on 8 Jul 2009 at 9:44
Sorry for not replying in so long, I hadn't had a chance to try this again.
Another sysadmin on my team ran a
checksum on just our user table, and had no problems. The problem might have
fixed itself, or it might have
something to do with our database + user table + maatkit. We have not upgraded
maatkit since I first submitted
that bug, so I cannot confirm if any changes will have fixed the problem.
In summary, all is well. If we have any further related problems I will update
this bug report. Thanks guys!
Original comment by aco...@gmail.com
on 8 Jul 2009 at 9:50
No problem; thanks for replying. Glad to hear it's now working. :-)
Original comment by dan...@percona.com
on 8 Jul 2009 at 9:56
Original issue reported on code.google.com by
aco...@gmail.com
on 28 Oct 2008 at 7:05Attachments: