Ian Barwick

The warning you mention: ``` # sudo -u postgres repmgr -f /etc/postgresql/14/requestlog/repmgr.conf cluster show -LDEBUG --verbose Warning: No existing cluster is suitable as a default target. Please see man pg_wrapper(1)...

At this point we haven't made any particular provision for `repmgr` to run in Docker, so it's possible there may be issues of one kind or another. > I also...

Also I see from the Stackoverflow post you're using repmgr 5.0; we strongly recommend using repmgr 5.1, the latest version.

In that case I'm not sure what can be done. As stated before, we haven't tested this on Docker at all, so it's hard to see what the issue might...

Aha, if you start it like that, it's probably not daemonizing properly. Try something like: ``` repmgrd -f /etc/repmgr.conf --daemonize --pid-file=/tmp/repmgrd.pid >> /tmp/repmgrd.log 2>&1 ```

Can you provide the output of: `SELECT * FROM repmgr.nodes` (in database `repmgr`)? Thanks.

Per the [documentation](https://repmgr.org/docs/current/repmgr-standby-unregister.html): > Unregisters a standby with repmgr. This command does not affect the actual replication, just removes the standby's entry from the repmgr metadata. so working as specified....

It looks like something went wrong during the switchover; from the available output it looks like `node1` somehow started as a primary (which is why you are seeing the original...

> Hi > > I want to configure failover cluster my environment for automatic failover while master postgresql is down. That won't work.

Thanks for the report; we have confirmed/reproduced the issue and provided a fix. If you'd like to test, we can provide snapshot packages.