Login Timeout

[MitchellW-DWL]

Have been running this without any major issues for a while now on most of our actions, within the last couple of weeks or so though I've been noticing it fails a fair amount:

Details

``` Run Particular/install-sql-server-action@v1.0.0 with: connection-string-env-var: SQL_SERVER_CONNECTION_STRING extra-params: TrustServerCertificate=true; catalog: nservicebus env: AZURE_ARTIFACTS_FEED_URL: https://ojosolutions.pkgs.visualstudio.com/_packaging/DWL-Nuget/nuget/v3/index.json Run # Linux SQL install via Docker # Linux SQL install via Docker # If the password generator needs to be changed, make sure the resulting password meets SQL Server password requirements sa_pw=$(uuidgen) echo "::add-mask::$sa_pw" echo "Starting SQL Server in a Docker container..." docker run -e "ACCEPT_EULA=Y" -e "SA_PASSWORD=$sa_pw" -e "MSSQL_PID=Developer" -e "MSSQL_COLLATION=SQL_Latin1_General_CP1_CS_AS" -p 1433:1433 --name sqlserver -d mcr.microsoft.com/mssql/server:[2](https://github.com/dwlgit/Silvey/actions/runs/11037176868/job/30692799081?pr=244#step:3:2)017-latest echo "Setting environment variables for sqlcmd..." echo "SQLCMDPASSWORD=$sa_pw" >> $GITHUB_ENV echo "SQLCMDUSER=sa" >> $GITHUB_ENV echo "SQLCMDSERVER=localhost,14[3](https://github.com/dwlgit/Silvey/actions/runs/11037176868/job/30692799081?pr=244#step:3:3)3" >> $GITHUB_ENV echo "Setting environment variable SQL_SERVER_CONNECTION_STRING to SQL connection string..." echo "SQL_SERVER_CONNECTION_STRING=Server=localhost;Database=nservicebus;User Id=sa;***;TrustServerCertificate=true;" >> $GITHUB_ENV shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0} env: AZURE_ARTIFACTS_FEED_URL: https://ojosolutions.pkgs.visualstudio.com/_packaging/DWL-Nuget/nuget/v3/index.json Starting SQL Server in a Docker container... Unable to find image 'mcr.microsoft.com/mssql/server:2017-latest' locally 2017-latest: Pulling from mssql/server 699[4](https://github.com/dwlgit/Silvey/actions/runs/11037176868/job/30692799081?pr=244#step:3:4)51820735: Pulling fs layer 7c9d5ddcf18b: Pulling fs layer a4b3ddcdae79: Pulling fs layer 6994[5](https://github.com/dwlgit/Silvey/actions/runs/11037176868/job/30692799081?pr=244#step:3:5)1820735: Verifying Checksum [6](https://github.com/dwlgit/Silvey/actions/runs/11037176868/job/30692799081?pr=244#step:3:6)99451820[7](https://github.com/dwlgit/Silvey/actions/runs/11037176868/job/30692799081?pr=244#step:3:7)35: Download complete a4b3ddcdae79: Verifying Checksum a4b3ddcdae79: Download complete 699451[8](https://github.com/dwlgit/Silvey/actions/runs/11037176868/job/30692799081?pr=244#step:3:9)20735: Pull complete 7c9d5ddcf18b: Verifying Checksum 7c[9](https://github.com/dwlgit/Silvey/actions/runs/11037176868/job/30692799081?pr=244#step:3:10)d5ddcf18b: Download complete 7c9d5ddcf18b: Pull complete a4b3ddcdae79: Pull complete Digest: sha256:716c9b8028e69aa11db5800e31af7311c5242a31cc59209a6e82299b1cdcae41 Status: Downloaded newer image for mcr.microsoft.com/mssql/server:2017-latest 863de5c3ebd770c3568cbbee[10](https://github.com/dwlgit/Silvey/actions/runs/11037176868/job/30692799081?pr=244#step:3:11)3c5[11](https://github.com/dwlgit/Silvey/actions/runs/11037176868/job/30692799081?pr=244#step:3:12)2fab3c0443b20d9640936c36e0b2c4ecd Setting environment variables for sqlcmd... Setting environment variable SQL_SERVER_CONNECTION_STRING to SQL connection string... Run # Wait for availability then create initial catalog Attempt 1/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt 2/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt 3/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt 4/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt 5/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt 6/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt 7/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt 8/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt 9/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt 10/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt 11/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt [12](https://github.com/dwlgit/Silvey/actions/runs/11037176868/job/30692799081?pr=244#step:3:13)/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt [13](https://github.com/dwlgit/Silvey/actions/runs/11037176868/job/30692799081?pr=244#step:3:14)/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt [14](https://github.com/dwlgit/Silvey/actions/runs/11037176868/job/30692799081?pr=244#step:3:15)/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt [15](https://github.com/dwlgit/Silvey/actions/runs/11037176868/job/30692799081?pr=244#step:3:16)/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt [16](https://github.com/dwlgit/Silvey/actions/runs/11037176868/job/30692799081?pr=244#step:3:17)/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt 17/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt 18/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt 19/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt 20/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt 21/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt 22/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt 23/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt 24/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt 25/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt 26/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt 27/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt 28/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt 29/30 to connect to SQL Server... - Not ready, sleeping for 5s Attempt 30/30 to connect to SQL Server... - Not ready, sleeping for 5s Creating initial catalog 'nservicebus' Sqlcmd: Error: Microsoft ODBC Driver [17](https://github.com/dwlgit/Silvey/actions/runs/11037176868/job/30692799081?pr=244#step:3:18) for SQL Server : Login timeout expired. Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : TCP Provider: Error code 0x2749. Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.. Error: Process completed with exit code 1.

It seems somewhat intermittent but is now failing more often than it's not

[DavidBoike]

Interesting, we don't seem to be having this problem, it's been pretty reliable for us lately.

Curious, what is AZURE_ARTIFACTS_FEED_URL about? Just something from the wider workflow?

[matte]

I've see this error in our GitHub actions, hitting re-run the error frequently goes away. I'm chocking it up to slow Azure VMs running the action

[MitchellW-DWL]

Interesting, we don't seem to be having this problem, it's been pretty reliable for us lately.

Curious, what is AZURE_ARTIFACTS_FEED_URL about? Just something from the wider workflow?

Yeah that's just a var used in some of the other steps so its global to the action

[DavidBoike]

Yeah, we usually chock these sorts of things up to slow Azure VMs as well.

Though I will note that it looks like you're using v1.0.0 of the action, and we have v1.2.0 now, and looking at the diff there have been quite a few changes to the action logic itself, along with the ability to specify SQL Server version. Maybe try an upgrade and see if things improve?

[matte]

Though I will note that it looks like you're using v1.0.0

👆🏼 this, we just had to upgrade 1.2 come to think of it

[MitchellW-DWL]

Yeah, we usually chock these sorts of things up to slow Azure VMs as well.

Though I will note that it looks like you're using v1.0.0 of the action, and we have v1.2.0 now, and looking at the diff there have been quite a few changes to the action logic itself, along with the ability to specify SQL Server version. Maybe try an upgrade and see if things improve?

Apologies shoulda tried a new version before putting up issue 😆 I'll upgrade and see how it goes :)

[MitchellW-DWL]

Well have upgraded all the workflows we have using this and no seen it again since so I'll accept that as a fix - thanks all