New deployment is not starting

Troubleshooting and help
,
1

image
image738Ă—396 18 KB

Hi,

My deployment is not starting. Image attached 33aaf52e.

Is there any way for me to debug?

I deleted the service and recreated with the same result. Is there a workaround?

Is there something I can avoid to stop this happening?

Kyle

2

if it’s stuck on Starting and not on Provisioning it means that your service is probably already running, but something in your health check is going wrong.
Could you send the logs in your deployment section?

image
image709Ă—251 10.3 KB

Edit: if the deployment takes as long as yours does, it can also be that there was an error during the build or the deployment is just stuck (happened to me multiple times), in that case it’s better to change a few files in your instance (nothing significant, just so that it’s not exactly the same as before) and after the new commits redeploy.

3

The logs in the deployment pane are blank - just says “No logs available in the last 30 days”. I assume that you have access to logs that I don’t have access to.

4

I’m sorry, but I don’t have access to Koyeb’s internal logs. What are you trying to deploy? Sometimes an issue during the build can block the instance from actually starting.

5

So for anyone who stumbles onto this thread I fumbled around blindly trying this and that since there were no logs visible to me. Eventually the service would not build either.

What fixed it was to pause the service and then redeploy. I assume the service gets itself into a weird state and pausing the service and restarting gets it out of the weird state.

I wish I had tried this approach earlier - seems obvious now - but by definition it is always the last thing you try that works :slight_smile:

1 Like
6

Marking an answer as solution helps everyone find their answer faster :wink: