Receiving connection timeouts to SQL Server from app running in staging deployment slot

Question

Receiving connection timeouts to SQL Server from app running in staging deployment slot

Jacob Page 0

For some reason, I'm receiving new connection timeout issues in a deployment slot for my Azure app service. This is despite me having not changed anything network-wise, the primary deployment slot not having a connection issue, and me being able to connect to the database from my workstation just fine. I am not using any vnets.

Any idea how this could be happening?

 ConnectionError: Failed to connect to <mydb>.database.windows.net:1433 in 15000ms
 at /home/site/wwwroot/node_modules/mssql/lib/tedious/connection-pool.js:85:17
 at Connection.onConnect (/home/site/wwwroot/node_modules/tedious/lib/connection.js:1012:9)
 at Object.onceWrapper (node:events:629:26)
 at Connection.emit (node:events:514:28)
 at Connection.emit (/home/site/wwwroot/node_modules/tedious/lib/connection.js:1040:18)
 at Connection.connectTimeout (/home/site/wwwroot/node_modules/tedious/lib/connection.js:1254:10)
 at Timeout._onTimeout (/home/site/wwwroot/node_modules/tedious/lib/connection.js:1199:12)
 at listOnTimeout (node:internal/timers:569:17)
 at process.processTimers (node:internal/timers:512:7) {
 code: 'ETIMEOUT',
 originalError: ConnectionError: Failed to connect to ifhc.database.windows.net:1433 in 15000ms
 at Connection.connectTimeout (/home/site/wwwroot/node_modules/tedious/lib/connection.js:1254:26)
 at Timeout._onTimeout (/home/site/wwwroot/node_modules/tedious/lib/connection.js:1199:12)
 at listOnTimeout (node:internal/timers:569:17)
 at process.processTimers (node:internal/timers:512:7) {
 code: 'ETIMEOUT',
 isTransient: undefined
 }
 }

Konstantinos Passadis 13,766 Reputation points

2023-10-30T12:57:11.3166667+00:00

Hello @Jacob Page !

Do you have any feedback on your issue?

Kindly mark any answer that helped you as Accepted and Upvote or post your feedback to provide additional help!

Regards

Konstantinos Passadis 13,766 Reputation points

2023-10-30T12:57:11.3166667+00:00

Hello @Jacob Page !

Do you have any feedback on your issue?

Kindly mark any answer that helped you as Accepted and Upvote or post your feedback to provide additional help!

Regards

Answer 1

Konstantinos Passadis 13,766

Hello @Jacob Page !

Welcome to Microsoft QnA!

Facing some issues on WebApp connectivity considering nothing has changed could have a lot of reasons.

First of all examine all your logs and try to activate Application Insights for a period of time to drill better into logging

Use the "Diagnose and solve problems" , https://learn.microsoft.com/en-us/azure/app-service/overview-diagnostics

Check Service Status for you region might be something else on Azure not your fault

Check Service Limits , it could be a limit you reached , highy unlikely but worth checking https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits

Upgrade your Plan to another Tier and check the behavior , you can do that easily !

https://learn.microsoft.com/en-us/azure/app-service/app-service-plan-manage#move

If nothing comes up , check with Azure Support !

I hope this helps!

Kindly mark the answer as Accepted and Upvote in case it helped!

Regards

Jacob H Page 0 Reputation points

2023-10-30T16:24:30.6666667+00:00

Thanks for your post.

I had tried running diagnostics, and the only feedback I got is that my app service is not using a vNet; it never was before either, and I don't need a vNet to reach the database from the other slot or from my workstation, so it seems like the diagnostic tool is pretty limited.

I saw there was some kind of maintenance going on for the region, but there were no links for details, just some ticket numbers with no instructions on how to see more info, so I have no idea if that could be related. Still, it's odd that the primary slot for my app, which runs in the same region, is not having the same issue.

I highly doubt this is a plan limit; if so I would expect an error message rather than a connection failure, and this is not a high-activity site that I'd expect to exceed limits. I'm already paying way too much, especially now that I'm adding support to my plan to get to the bottom of this issue which has prevented me from being able to deploy new versions of my app.
Konstantinos Passadis 13,766 Reputation points

2023-10-31T23:47:40.7966667+00:00
Hello @Jacob Page !

Thank you for your message!

yes highly unlikely a Limit agree , i just want to have a 360 view on issues , you never know what may come up from searching!

So , have you doubled checked Metrics and Logs ?

Could you kindly share some info on the code and the deployment details?

The more info we have the better help we can provide !

What are your Frameworks ?

If i understand correctly maybe i am wrong , is this a MSSQL backend ?

What does it do ?

Any particular info on the Front end ? Again , the more you can provide , the better we can assist !

I hope this helps!

Kindly mark the answer as Accepted and Upvote in case it helped!

Regards
Jacob H Page 0 Reputation points

2023-10-31T23:53:30.27+00:00

This is a nodejs application using the mssql package to connect to an MSSQL server.

Receiving connection timeouts to SQL Server from app running in staging deployment slot

1 answer

Activity