New instances unable to start (no logs)

Troubleshooting and help
, , ,
1

New instances are failing to start.

I only changed the value of an existing plaintext environmental variable so it had the exact same code as the previous instance.

It logged Instance created. Preparing to start... and then ~15 min later Instance stopped and nothing more.

I made a small change to HTML, confirmed tests pass locally, the app runs locally, and CI passes on GitHub. That deployment is currently “Erroring” with the following as logs:

Instance created. Preparing to start...
Network configuration propagated
Instance is starting. Propagating network configuration...
Instance is stopping

My gut says this problem is not specific to my application and likely an infrastructure problem. Please let me know what else I can do to debug, get logs, or explore the problem so we can get to a solution.

2

Hey!

First, sorry for the inconvenience.

It’s indeed looking like an infra issue. I quickly checked and there is an issue with the machine where your latest deployment has been scheduled; thing is, we automatically try to allocate on different machines in case of internal failures, so there is definitely something wrong.

I’m looking deeper into it, we will get back to you here when we have more details.

1 Like
3

We moved the machine out of the pool, so if you redeploy your service, it should end up healthy.

As I stated earlier, it is not normal that your service ended up always scheduled on that machine; we will investigate.

Let me know if you have others issues!

1 Like
4

Thank you for getting to this quickly and confirming my hunch!

I triggered a redeploy from the settings page and can confirm it worked :+1:

5

Hello, i have the same issue on my project :
Instance created. Preparing to start...
Instance is starting. Propagating network configuration...
Network configuration propagated

and about 15minutes later :
Instance is stopping

with no further logs…
This is not the first time it happened to me, do you have more details on this issue ?

6

The same error happened to me

7

I changed the region from German to Washington and the deployment was successful

8

I have done the same thing and it worked thanks!
I hope this problem will be solved, I don’t want to have to change regions often :smiley:

9

Now i return to German region and the deployment was successful

1 Like