Mysql Forgets Info After Sync?! Help! :(

[gh0st]

Hello all,

I have been using SQLyog for quite some time now. Just recently, I have been noticing that my databases are behaving very strangely after a sync, and cant seem to figure out why. First let me explain my topology.

I/we use mysql for our mail servers, (postfix, courier-imap) to store usernames, passwords, alias/virtual mailboxes, auto responders, activity info, the whole 9 yards. Each mail server in the cluster runs its own mysql database, which is then synchronized from a standalone mysql server. Our customer management system writes to the standalone sql server, and then pushes the updates (be it usernames, passwords, new accounts, forwards, whatever) via SQLyog to the mail servers mysql databases.

I have noticed, that after a sync data that is not being updated, dissapears! I can do a select on data that should not have been updated by SQLyog and it returns 0 rows, after a few secconds, its there again. This has been causing intermittent login problems for the pop/imap users. I am using SQLyog Job Agent Version 4.0 with mysql version: 4.1.10a-standard-log across the board. Please HELP!!

-joshua

[Ritesh]

SQLyog Job Agent 4.0 is pretty old and we have had lot of bug fixes after that.

Did you try the sync using the latest SJA v5.x?

If it is still giving errors then can you send me sample data so that we can reproduce the problem?

[peterlaursen]

Code:

data that is not being updated, dissapears!

Could you explain what is precisely 'disappears' ? Is it (only) this:

I can do a select on data that should not have been updated by SQLyog and it returns 0 rows, after a few secconds, its there again.

And after that there are no problems?

I think it looks mostly like a MySQL issue of some kind. Like MySQL operates some temporary tables internally. Or does it lock access? What is the MySQL version? On what platform?

[gh0st]

What dissapears:

entire rows of data

I am using SQLyog Job Agent Version 4.0 with mysql version: 4.1.10a-standard-log across the board, on fedora core 2 linux. I have not tried sja 5.0 yet, ill give that a try

It could very well be a sql problem, if so it is one that I have been unable to figure out. I have tried running the myisamchk and isamchk utilities, to no avail

[peterlaursen]

But if I understand you right, they don't disappear permanently?

[gh0st]

peterlaursen wrote on Apr 5 2006, 06:40 AM:

But if I understand you right, they don't disappear permanently?

correct, i am almost certain that this is an issue with mysql and not with sja

I have tried running myisamchk and isamchk with the repair options on all sql servers, both source and destination servers, I've even gone as far as droping the database, recreating it, and resync'ing it, still no luck.

I've used sja for quite some time, and have updated to the latest version with still no change. This same schema has been in place for a while, and never have had any problems with it until now.

baffled.

[Author]

Posts