ubc / barman-docker

ubc math score form

barman-docker's Issues

BACKEND Error: "cannot execute SQL commands in WAL sender for physical replication"

Hello, I have an stack with two repmgr containers running and pgpool. If I connect barman directly to repmgr node 1 (running like primary) everything looks fine. However if I connect barman container with pgpool instead of repmgr directly this fails with this error:

Docker images in use:
ubcctlt/barman:v2.19
bitnami/postgresql-repmgr:13.6.0-debian-10-r78
bitnami/pgpool:4.3.1-debian-10-r68

Setting ownership/permissions on /var/lib/barman and /var/log/barman
Generating cron schedules
Generating Barman configurations
Checking/Creating replication slot
Creating physical replication slot 'barman' on server 'pgpool'
2022-05-11 19:53:18,625 [18] barman.server INFO: Creating physical replication slot 'barman' on server 'pgpool'
ERROR: Cannot create replication slot 'barman' on server 'pgpool': Backend throw an error message
DETAIL:  Exiting current session because of an error from backend
HINT:  BACKEND Error: "cannot execute SQL commands in WAL sender for physical replication"
server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.
2022-05-11 19:53:18,668 [18] barman.server ERROR: Cannot create replication slot 'barman' on server 'pgpool': Backend throw an error message
DETAIL:  Exiting current session because of an error from backend
HINT:  BACKEND Error: "cannot execute SQL commands in WAL sender for physical replication"
server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.
Nothing to do. Position of receive-wal is aligned.
2022-05-11 19:53:19,768 [21] barman.wal_archiver INFO: Nothing to do. Position of receive-wal is aligned.
Initializing done
Started Barman exporter on 0.0.0.0:9780
Exception in thread Thread-2:
sh.ErrorReturnCode_1: 

  RAN: /usr/local/bin/barman -f json status pgpool

  STDOUT:
{"_EXCEPTION": ["Backend throw an error message\nDETAIL:  Exiting current session because of an error from backend\nHINT:  BACKEND Error: \"cannot execute SQL commands in WAL sender for physical replication\"\nserver closed the connection unexpectedly\n\tThis probably means the server terminated abnormally\n\tbefore or while processing the request.\n\nSee log file for more details."], "pgpool": {"active": {"description": "Active", "message": "True"}, "description": {"description": "Description", "message": "PostgreSQL Database (Streaming-Only)"}, "disabled": {"description": "Disabled", "message": "False"}}}

  STDERR:
2022-05-11 19:53:21,124 [36] barman.cli ERROR: Backend throw an error message
DETAIL:  Exiting current session because of an error from backend
HINT:  BACKEND Error: "cannot execute SQL commands in WAL sender for physical replication"
server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.

See log file for more details.
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/dist-packages/barman/cli.py", line 1910, in main
    args.func(args)
  File "/usr/local/lib/python3.9/dist-packages/barman/cli.py", line 510, in status
    server.status()
  File "/usr/local/lib/python3.9/dist-packages/barman/server.py", line 1230, in status
    self.status_pos... (1107 more, please see e.stderr)

My app is connected successfully to pgpool container. Why barman no? What is the difference bewteen use directly barman w/ pgpool & barman w/ repmgr or postgres.

[update-request] Barman updates available

Barman 2.17 was recently released. Have you considered updating this image?

Since 2.10, the following things appear to have happened:

• barman migrated their repo to https://github.com/EnterpriseDB/barman/ (starting with 2.13)
• barman-cloud-wal-archive and barman-cloud-backup where moved into the new barman-cli-cloud package
• a few bugfixes have landed and there are some interesting new features like Azure blob support

FWIW their docs link to the 2.13 version so we might want to consider that "stable". If i look at pkgs.org it seems that most distros haven't made the switch to github hosted barman yet and are still using 2.12.

[Feature Request] Adding support for pgsql 15

Hi there,

Since you r not using barman anymore, I doubt you will add this but there s no harm in asking.

Would it be possible to add support for postgresql 15 client in your dockerfile ?

Should I make a pr for this ?

Regards,

DB_Port is not used for connection

Hi, the environment DB_PORT is not used to connect to the database. A connection is always established via port 5432.

Error "/tini: no such file or directory: unknown"

Hello, I'm using your image in Kubernetes and it gives me this error.

RunContainerError: failed to start container "c944dc805bc1b2c908ae069f70074eebf5b975c1574a4c012ea5973f8f9d6971": Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "/tini": stat /tini: no such file or directory: unknown

Do you know what it means? I had used your image before and no error was given. Can you help me?