[Aidan]

peterlaursen wrote on Jul 22 2009, 08:06 PM:

If you will let us try from our end we can see that if we run from inside our debugging environment (Visual Studio). If so please create a private ticket for exchanging server details.

Thank you Peter, I have submitted a ticket. It will be great if you can at least determine if there is a specific problem with configurations, etc. at either one of the hosting services so that I can address the issue with them.

I'm wondering if the size of the db could be a problem, since it was working with only occasional failure when the db was smaller, then failures became more frequent until now it not working at all?

Thanks,

Aidan

[Aidan]

some additional info that may shed more light:

I have been trying some sync operations direct from the wizard. It now seems like I am getting more of the 2006 error whereas before (from scheduled sync), I was getting more of the 2013 errors. It also just hangs sometimes and does nothing so I have to click Terminate.

I have tried it in 'generate script' mode instead of direct sync. It also fails in this case. Looking at the output SQL, there are a few update statements in it after it fails.

[Aidan]

Thank you for replying Navya.

The 2013 error is the one I get mostly, and just occasionally I get 2006.

The fact that 2013 means “Lost connection to MySQL server during query” doesn't help me much – I need to figure out why and how to rectify. In the document you linked, it mentions this error in the context of SSH tunnelling but I am not using SSH tunnelling so I do not think that is applicable in my case.

Is there a way to determine which MySQL server it lost the connection to, the source or the target?

I do not have direct access to the servers, they are both on shared hosting. I have Plesk access to the source and Cpanel access to the target (with phpMyAdmin on both).

I can try requesting server config changes through support if that is what is needed but I would need to know exactly what to request.

I've checked the max_allowed_packet for both source and target and it is similar on both – 16777216 on the target and 16776192 on the source.

When I run a sync directly from the wizard, it seems to work for updating a few rows initially as I can see the Updating row: messages in the output area. I just tried it again not and it got to about 25 rows before it fails. When I run it again, it does the same thing, updates a few rows and then fails after a minute or a few (varies).

Is there a way to set SQLyog sync to try again if the connection fails so that if it is only able to do a few updates at a time it can keep reconnecting until it eventually gets them all?

[Author]

Posts