Error while syncing device data with CloudSQL

[Jannik Zgraggen]

I am looking at Google Cloud SQL as an alternative to  AWS SQL to store data gathered with different measuring devices for my company. We use the software GridVis to use access the internal storage of the devices (Janitza UMG605) via TCP/IP and GridVis then syncs the data stored on the device with the mySQL data base.

The syncing procedure works with an internal company server and with the relational database tool of AWS but it has often problems syncing with Google Cloud SQL (error message displayed in image below)

Anyone an idea what the issue could be?

I am thankful for any help.

[Digil (Google Cloud Platform Support)]

It looks like a connectivity issue. You can verify this with a network trace between your server and Cloud SQL instance.You can also check this help center article for known issues with Cloud SQL for MySQL. 

Furthermore, I'll also suggest you to post this concern in 'StackoverFlow' community. There, you will also get much more attention from a larger technical support community(which also includes Google Support members) as well.  

[Jannik Zgraggen]

Thanks. I posted the question in 'StackoverFlow' : https://stackoverflow.com/questions/49666755/syncing-with-google-cloud-sql-fails-aws-connection-works

I am neither using SSL nor Proxy.

Could it be that my connection to the google instance is slower than to the AWS-instance?

[Jannik Zgraggen]

I tried to access the AWS instance and the Google Cloud Instance through the IP traceroute tool. (Results attached)
The both instances are in Frankfurt Germany.

The aws-instance-trace ends up in Germany but google-instance-trace ends up in the us.

Can you recommend another tool for Network tracing?

On Thursday, April 5, 2018 at 2:32:12 AM UTC+2, Digil (Google Cloud Platform Support) wrote:

[Digil (Google Cloud Platform Support)]

Using SSL or Cloud SQL Proxy, should not have an impact on speed. However, it is always highly recommended to use an SSL certificate or Cloud SQL Proxy connection as it provides secure access to your database instance. If you are using the Cloud SQL Proxy, you do not need to use an SSL certificate, because the proxy connection is encrypted by default.

 

Geographically, your instance will be located in the zone which you selected. The reason, Google IP shows registered to the US location is because most of the Google Cloud IPs are SWIP’ed to Mountain View, CA location. For more information, you can read the Stackoverflow thread, where one of our Engineer had provided more details.

 

There is already a feature request in place to reflect the appropriate Geo-information about the IP-addresses as well.

 

There are several third party 'traceroute' tools available which you can use. For example:  ‘traceroute.org’ is one of the online tools.

 

It seems like you have posted your issue regarding SQL syncing on 'StackOverflow.com' and one of our Google Engineer had provided explanation and possible work around towards the fix.

 

 

 

[Jannik Zgraggen]

Hi I talked as well to employees of Gridwis, apparently FTP is used to access the device. I am now using HTTP to access the device and everything works fine.

 

Thanks again for your help!