Unmanaged Postgres, single node, repmgr fails on boot

[mayailurus]

Hm… Is 48ed1eeb303078 definitely the Machine’s own ID? Possibly you had multiple nodes in the past, and this is a remnant of that older configuration, .

If this persists, then I would try the volume-forking technique (with explicit volume ID) and see whether that new Machine boots successfully…

---

Aside: This might be a good time to reassess whether single-Machine Legacy Postgres is really the right fit for the data you have in there. The next glitch like this could very well wipe out the data itself, …

@john-fly

But many users use single-machine Fly PG for production! Please don’t do this – it’s not a supported configuration! I’ve had to break the news to several users recently that their data was lost/may be lost when a host goes offline for a (suspected) hardware failure, taking the data with it. Always run a Fly PG cluster with 3 or more nodes in production.