:80 address already in use

1

As of today, I’m unable to create new deployments:

2022-05-21T11:50:23Z   [info]Preparing to run: `soc-server` as root
2022-05-21T11:50:23Z   [info]2022/05/21 13:50:23 listening on [fdaa:0:30b1:a7b:23c5:0:848c:2]:22 (DNS: [fdaa::3]:53)
2022-05-21T11:50:23Z   [info]2022/05/21 13:50:23 soc-server ()
2022-05-21T11:50:23Z   [info]2022/05/21 13:50:23 grpc: :8080
2022-05-21T11:50:23Z   [info]2022/05/21 13:50:23 ssl hosts: fly.evcc.io,evcc.fly.dev,cloud.evcc.io
2022-05-21T11:50:23Z   [info]2022/05/21 13:50:23 ssl certdir: /data
2022-05-21T11:50:23Z   [info]2022/05/21 13:50:23 ssl hosts: fly.evcc.io,evcc.fly.dev,cloud.evcc.io
2022-05-21T11:50:23Z   [info]2022/05/21 13:50:23 ssl certdir: /data
2022-05-21T11:50:23Z   [info]2022/05/21 13:50:23 listen tcp :80: bind: address already in use
2022-05-21T11:50:24Z   [info]Stin child exited normally with code: 1
2022-05-21T11:50:24Z   [info]Starting clean up.
2022-05-21T11:50:24Z   [info]Umounting /dev/vdc from /data
--> v153 failed - Failed due to unhealthy allocations - not rolling back to stable job version 153 as current job has same specification and deploying as v154

--> Troubleshooting guide at https://fly.io/docs/getting-started/troubleshooting/
Error abort


make: *** [fly] Error 1

Application startup has not changed, but it looks as if fly is trying to start the application twice and waits for both??

2

Unfortunately, the deployment is also not rolled back, hence my application is not offline :frowning:

Any help welcome!

3

Update: I was able to rollback using Manual rollback to earlier version?. Still, new deployments don’t work.

I will investigate application side, maybe I’ve overlooked something…

4

Did you figure it out?

If not, is it a Dockerfile or builder app? If you can post its fly.toml and Dockerfile someone may be able to spot an issue. It seems unlikely Fly would start it twice unless told to. There is a possibility there is a duplicate log line too, given the times are the same.

5

Finally found it. Nicely hidden Application error. Sorry for the noise!

2 Likes