Fly FLAME failing with timeout about flame HOT 1 CLOSED

Attempted to debug this issue.

PCI: Fatal: No config space access function found
...
WARN could not unmount /rootfs: EINVAL: Invalid argument

PCI Fatal is harmless Linux kernel chatter complaining of no PCI port found.
According to: https://community.fly.io/t/error-after-deploy-warn-could-not-unmount-rootfs-einval-invalid-argument/19624/6 the unmount is also harmless.

I tried checking if my clustering wasn't setup correctly:

{:dns_cluster, "~> 0.1.3"},

but I can see the other node (in a 2 node cluster) when doing list:

iex > Nodes.list()
[...]

This project has been upgraded since 1.12. I noticed the fly.toml tcp checks were quite short, but it had never been an issue bfore:

 [[services.tcp_checks]]
-grace_period = "1s"
-interval = "15s"
+grace_period = "10s"
+interval = "20s"
 restart_limit = 0
-timeout = "2s"
+timeout = "60s"

And now it works! Yay! 🎉

from flame.