Very slow windows server process/service start

[dpogorzelski]

Question

When running cloud_sql_proxy as a windows service the startup time is very slow, to the point where windows fails to start the service with message:
Error 1053 the service did not respond to the start or control request in a timely fashion

The service is created via:

New-Service -Name "test" -BinaryPathName "C:\cloud_sql_proxy.exe -verbose=false -instances=`"$env:SQL_INSTANCES`"" -StartupType Auto

When using a service wrapper such as nssm the service starts instantly from windows perspective but that's only because there is nssm in front, the actual cloud_sql_proxy executable takes 1-2min to be ready and receive connections.

[dpogorzelski]

Official Windows server 2012 image was used in this testing in GCE

[Carrotman42]

Back in the day the Proxy started up instantly, but now it does a bunch of network activity to verify the command line arguments before allowing connections. Still, 1-2 minutes sounds unexpected to me personally.

Do you have lots of instances in your list or something?

What logs come out of the Proxy process during this time?

[kurtisvg]

When running cloud_sql_proxy as a windows service the startup time is very slow, to the point where windows fails to start the service with message:

The binary doesn't work directly as a service on Windows. This is because Windows services require specific support which the proxy doesn't implement (yet: #277). Until then, you'll have to use a tool such as nssm to run it as as service.

I would agree that the 1-2 minutes on startup time is excessive. In addition to providing logs, can you run the proxy manually and see if you still see this start up time when just running the proxy manually?

[shubha-rajan]

Closing this stale issue. Feel free to reopen if you'd like to follow up.