Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

zammad-backup not working with postgres 17 #440

Closed
krombel opened this issue Nov 15, 2024 · 2 comments · Fixed by #441
Closed

zammad-backup not working with postgres 17 #440

krombel opened this issue Nov 15, 2024 · 2 comments · Fixed by #441
Assignees

Comments

@krombel
Copy link

krombel commented Nov 15, 2024

After upgrading to the latest release backups are not working anymore.

These are the logs of the zammad-backup container:

zammad-backup-1  | 20241115163509 - backing up zammad...
zammad-backup-1  | tar: Removing leading `/' from member names
zammad-backup-1  | pg_dump: error: aborting because of server version mismatch
zammad-backup-1  | pg_dump: detail: server version: 17.1; pg_dump version: 15.8 (Debian 15.8-0+deb12u1)
zammad-backup-1  | backup finished :)
zammad-backup-1  | sleeping 37490 seconds until the next backup run...

It seems, this issue is coming from the ruby base image:
https://github.com/zammad/zammad/blob/6.4.0/Dockerfile#L20
where then the postgres-client package is installed
https://github.com/zammad/zammad/blob/6.4.0/contrib/docker/setup.sh#L7

This is currently based on bookworm - which does not have postgres-client for postgres 17 yet.
https://packages.debian.org/search?keywords=postgresql-client

@krombel krombel changed the title zammad-backup not working with postgres 17.0 zammad-backup not working with postgres 17 Nov 15, 2024
@mgruner mgruner self-assigned this Nov 18, 2024
@mgruner
Copy link
Collaborator

mgruner commented Nov 18, 2024

Confirmed, fix is in the works: zammad/zammad#5416

@mgruner
Copy link
Collaborator

mgruner commented Nov 20, 2024

@skyscooby our upgrading instructions for docker advise to check the release notes for zammad-docker-compose. I assume you didn't read these?

I have to admit that we need to improve our workflows and CI coverage, but it's not true that operational concerns are discarded.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants