MySql error

  • 265Views
  • Last Post 17 November 2020
0
votes
pablo.lopez posted this 06 October 2020

Estamos teniendo un error esporadicamente de coneccion a la db MySql

Ya tenemos en whitelist las ip [13.86.253.112 | 40.118.246.204]

RunId = 44820050 Error:

An error occurred with the following error message: "Can't connect to MySQL server on '52.201.126.7' (10061): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 52.201.126.7306"

Podrán confirmarnos la IP desde la cual se intento realizar la conexión.

 

mysql-connection
Order By: Standard | Newest | Votes
0
votes
Dmitriy Muzurov posted this 07 October 2020

Hello Pablo,

Thank you for submitting a ticket with us.

Since this message appeared only on one run and next run is successful, we tend to think that the issue is caused by something temporary on your server side.

We are looking forward to hearing from you, should you have any questions.

0
votes
pablo.lopez posted this 16 October 2020

Hi, is it not really one time error.

It is recurrent, but not too commun.

For eg: from 10 connections it failed one time, for tis reason it looks like a Connection IP problem

We have two IP's on whitelisting [13.86.253.112 | 40.118.246.204] and probably it failed when Skyvia try to connect from another IP.

0
votes
pablo.lopez posted this 16 October 2020

 

Is it possible to check which IP is using to connect when failed???

 

Rgds

0
votes
Dmitriy Muzurov posted this 19 October 2020

Hi Pablo,

Thank you for getting back to us.

We tend to think that the issue is related to your server rather than IP address.

Please set both Command and Connection Timeouts to 0 in the MySQL connection details in your Skyvia account.

We are looking forward to hearing from you, should you have any questions.

0
votes
pablo.lopez posted this 23 October 2020

Hi Dmity, thanks for your return.

We hav already changed, and the error persist.

Also is sporadic, then today failed again on one package

RunId = 45819313

An error occurred with the following error message: "Can't connect to MySQL server on '52.201.126.7' (10061): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 52.201.126.7306"

 

Do you have another option??

 

We have already set up on whitelist [13.86.253.112 | 40.118.246.204]

We remove connection timeout to 0 and it continue failing.

Is it possible to  check wich IP is trying to connect both RunId failed????

Rgds

 

0
votes
pablo.lopez posted this 27 October 2020

Any news??

-1
votes
Dmitriy Muzurov posted this 28 October 2020

Dear Pablo,

Thank you for your reply.

Please try to Increase the values of the following parameters in the configuration of your MySQL Server:

- max_allowed_packet

- net_read_timeout

- net_write_timeout

- wait_timeout

For more information, please refer to these links: 1, 2.

We are looking forward to hearing from you, should you have any questions.

0
votes
pablo.lopez posted this 29 October 2020

Hi Paul, Dimitry, Thanks for your return.

  We have already checked with Server Admins and they reply the values set up on our Server.

  • max_allowed_packet..... 1073741824 (MAX value, 1GB)
  • net_read_timeout..... 3600 (el default es 30 sec, set up time 1 h)
  • net_write_timeout..... 3600 (el default es 60 sec, set up time 1 h ) 
  • wait_timeout..... 28800 (default value 8hs)

This definition looks right.   Could you please check why failed the following Run_Id's [44820050 | 45819313]

0
votes
pablo.lopez posted this 30 October 2020

Any return??

-1
votes
Dmitriy Muzurov posted this 30 October 2020

Dear Pablo,

Thank you for reply.

The run ID 45819313 failed due to the error "Can't connect to MySQL server...".

Please enable new runtime in the package and let us know the result.

We are looking forward to hearing from you.

0
votes
pablo.lopez posted this 30 October 2020

Hi,

When we retry, it works OK.

It failed when packages are schedulled, then we need more specific information for your side

Ej:

Also, you can see:

+ is it not a timeout problem, because it failed before 2 minutes

+ is is not a weight problem, because it failed on queries wo returned 18 results eg: 45819312.

Could you please review wich IP tried to connect???

Rgds

0
votes
pablo.lopez posted this 02 November 2020

Hi Paul, Ditry.

  We continue waiting response from this ticket.   Send you another runId Error It is a realy light view and it failed currently. It runs daily at 10:00 ARTZ Could you please help us??

0
votes
Dmitriy Muzurov posted this 03 November 2020

Hello Pablo,

Thank you for getting back to us.

Requests are sent from one IP address - 40.118.135.83 from the same instance that has both successful and failed runs.

The issue might be connected to the stage of connecting to your host.

We would recommend doing the following:

1) switch schedule to some other time

2) enable 'Use new runtime' option. Make sure to replace double quotes to single quotes in the expressions.

We are looking forward to hearing from you.

0
votes
pablo.lopez posted this 03 November 2020

Hi Dmitriy,

Is not possible to connect from this IP.

 

Whe have only on whitelisting:  [13.86.253.112 | 40.118.246.204] as doccumentation says

Is it really important to set up as whitelisitn ALL IP's used because databases are not public.

 

Please send me whole ip used by Skyvia.

Rgds

0
votes
pablo.lopez posted this 04 November 2020

Any return??

0
votes
Dmitriy Muzurov posted this 05 November 2020

Hi Pablo,

Sorry for confusion, that IP is not public.

There are two public IP addresses used by Skyvia - 40.118.246.204 and 13.86.253.112.

The request to your instance was made from the first one. Still the recommendation is the same as in our previous reply.

We are looking forward to hearing from you, should you have any questions.

0
votes
pablo.lopez posted this 05 November 2020

Hi, We have already re-schedulle last week and it continue fails.

We just marked all packages as "Use new Runtime".

We will wait the next few days to see what happens.

0
votes
pablo.lopez posted this 05 November 2020

Hi, we update Use New Runtime and it failled with another error.

Could you please help us??

Rgds

0
votes
pablo.lopez posted this 05 November 2020

Hi Paul. 

Using New Runtime package failed by  Index was out of range

Run Id

46417411

Date: Nov 5, 2020 10:44:00 AM

State: Failed

Error: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index

The Success run was when i unchecked  New Runtime package.

  Could someone plase help us right now??   Rgds

-1
votes
Dmitriy Muzurov posted this 06 November 2020

Dear Pablo,

Thank you for screenshots.

This issue is known and our developers already implemented a fix for it.

It will be applied with new Skyvia version within next 2-3 weeks.

Should you have any questions, do not hesitate to contact us back.

0
votes
pablo.lopez posted this 06 November 2020

Hi All

  We begin this trouble since 5 weeks.   Also you propose a new resolution and this proposal doesnt works and will be available on 2-3 weeks..  Is it a Joke??     Dimitry, could you please give us a response for appalling support experience. 

 

 

 

[email protected]">@Paul Crane , @[email protected]   Please scalate it to Dmitry's Manager

0
votes
Dmitriy Muzurov posted this 09 November 2020

Dear Pablo,

We would like to sincerely apologize that solution of the issue takes much more time than you had probably expected. Thank you very much for your patience. 

We offerred you to migrate to new runtime in order to check whether this helps, however the same day an issue occurred with new runtime and that affected many Skyvia clients.

Our Sales Development Representative will get in touch with you to provide fair compensation.

We will let you know once the fix for the issue with new runtime is rolled out to prodution.

0
votes
pablo.lopez posted this 09 November 2020

No, i need to solved it after this workarround.

 

Any other option??

 

Rgds

0
votes
Dmitriy Muzurov posted this 10 November 2020

Dear Pablo,

It seems we tried all options and switching to new runtime is a kind of last resort.

So, once a fix is applied and new runtime is working without issues, you can try whether connection errors appear again on your packages.

Should you have any questions, do not hesitate to contact us back.

0
votes
Dmitriy Muzurov posted this 17 November 2020

Dear Pablo,

The issue with "Index was out of range" error was fixed and new runtime should work without issues currently.

Feel free to contact us back, should you have any questions.

New Ticket
Categories
Popular Tags
Close