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

[bitnami/pgbouncer] auth file is corrupted on boot #48264

Closed
penguincoder opened this issue Sep 12, 2023 · 5 comments
Closed

[bitnami/pgbouncer] auth file is corrupted on boot #48264

penguincoder opened this issue Sep 12, 2023 · 5 comments
Assignees
Labels
pgbouncer solved tech-issues The user has a technical issue about an application

Comments

@penguincoder
Copy link

Name and Version

bitnami/pgbouncer:1.20.1

What architecture are you using?

amd64

What steps will reproduce the bug?

  1. When using the container in docker-compose
  2. I set the following environment variables POSTGRESQL_USERNAME=postgres and POSTGRESQL_PASSWORD=password
  3. The container fails to start with the following error: ERROR broken auth file

What is the expected behavior?

I expect pgbouncer to initialize with the provided authorization information.

What do you see instead?

2023-09-12T16:49:28.514407599Z pgbouncer 16:49:28.51
2023-09-12T16:49:28.515651272Z pgbouncer 16:49:28.51 Welcome to the Bitnami pgbouncer container
2023-09-12T16:49:28.516655859Z pgbouncer 16:49:28.51 Subscribe to project updates by watching https://github.com/bitnami/containers
2023-09-12T16:49:28.517886012Z pgbouncer 16:49:28.51 Submit issues and feature requests at https://github.com/bitnami/containers/issues
2023-09-12T16:49:28.518852758Z pgbouncer 16:49:28.51
2023-09-12T16:49:28.530062429Z pgbouncer 16:49:28.52 INFO  ==> ** Starting PgBouncer setup **
2023-09-12T16:49:28.539993766Z pgbouncer 16:49:28.53 INFO  ==> Validating settings in PGBOUNCER_* env vars...
2023-09-12T16:49:28.543535411Z pgbouncer 16:49:28.54 INFO  ==> Initializing PgBouncer...
2023-09-12T16:49:28.548429493Z pgbouncer 16:49:28.54 INFO  ==> Waiting for PostgreSQL backend to be accessible
2023-09-12T16:49:28.563105347Z pgbouncer 16:49:28.56 INFO  ==> Backend postgres:5432 accessible
2023-09-12T16:49:28.564676249Z pgbouncer 16:49:28.56 INFO  ==> Configuring credentials
2023-09-12T16:49:28.566219051Z pgbouncer 16:49:28.56 INFO  ==> Creating configuration file
2023-09-12T16:49:28.769117012Z pgbouncer 16:49:28.76 INFO  ==> Loading custom scripts...
2023-09-12T16:49:28.772171024Z pgbouncer 16:49:28.77 INFO  ==> ** PgBouncer setup finished! **
2023-09-12T16:49:28.772209125Z
2023-09-12T16:49:28.784015751Z pgbouncer 16:49:28.78 INFO  ==> ** Starting PgBouncer **
2023-09-12T16:49:28.786849638Z 2023-09-12 16:49:28.786 UTC [1] ERROR broken auth file
2023-09-12T16:49:28.787897166Z 2023-09-12 16:49:28.787 UTC [1] LOG kernel file descriptor limit: 1048576 (hard: 1048576); max_client_conn: 500, max expected fd use: 532
2023-09-12T16:49:28.788222715Z 2023-09-12 16:49:28.788 UTC [1] LOG listening on 0.0.0.0:6432
2023-09-12T16:49:28.788257805Z 2023-09-12 16:49:28.788 UTC [1] LOG listening on unix:/tmp//.s.PGSQL.6432
2023-09-12T16:49:28.788336087Z 2023-09-12 16:49:28.788 UTC [1] LOG process up: PgBouncer 1.20.1, libevent 2.1.12-stable (epoll), adns: c-ares 1.17.1, tls: OpenSSL 1.1.1n  15 Mar 2022
2023-09-12T16:50:28.789473247Z 2023-09-12 16:50:28.789 UTC [1] LOG stats: 0 xacts/s, 0 queries/s, in 0 B/s, out 0 B/s, xact 0 us, query 0 us, wait 0 us
2023-09-12T16:51:28.788811145Z 2023-09-12 16:51:28.788 UTC [1] LOG stats: 0 xacts/s, 0 queries/s, in 0 B/s, out 0 B/s, xact 0 us, query 0 us, wait 0 us
2023-09-12T16:52:25.442891494Z 2023-09-12 16:52:25.442 UTC [1] LOG C-0x563e63134d60: (nodb)/(nouser)@172.18.0.18:52778 no such user: postgres

Additional information

I believe that the change was introduced in #46094 via commit d384b3e

I was able to downgrade to container version 1.20.1-debian-11-r27 and continue working as expected.

I suspect that once Bitnami CI published a new version of the container this morning, we started seeing intermittent failures in our CI while our nodes slowly downloaded the new container until such time that all of the nodes had the updated image.

@penguincoder penguincoder added the tech-issues The user has a technical issue about an application label Sep 12, 2023
@bitnami-bot bitnami-bot added this to Triage in Support Sep 12, 2023
@github-actions github-actions bot added the triage Triage is needed label Sep 12, 2023
@javsalgar javsalgar changed the title pgbouncer auth file is corrupted on boot [bitnami/pgbouncer] auth file is corrupted on boot Sep 13, 2023
@javsalgar javsalgar moved this from Triage to In progress in Support Sep 13, 2023
@github-actions github-actions bot added in-progress and removed triage Triage is needed labels Sep 13, 2023
@bitnami-bot bitnami-bot assigned CeliaGMqrz and unassigned javsalgar Sep 13, 2023
@CeliaGMqrz
Copy link
Contributor

Hi @penguincoder

Thanks for reporting this issue. Is right. I was able to reproduce the error. I have created an internal task to resolve this. We'll leave this issue on hold until we have updates. Sorry for the inconvenience.

@github-actions github-actions bot moved this from In progress to Pending in Support Sep 18, 2023
@CeliaGMqrz CeliaGMqrz moved this from Pending to On hold in Support Sep 18, 2023
@github-actions github-actions bot added on-hold Issues or Pull Requests with this label will never be considered stale and removed in-progress labels Sep 18, 2023
@ruudschilders
Copy link

I see something I guess is related. I use pgbouncer on https://mastodon.world, and when upgrading the pgbouncer container to :latest, I see that userlist.txt is overwritten every time I start the container. It replaces the syntax
"user" "password"
by
pgbouncer_escape_auth user pgbouncer_escape_auth password

I reverted to version 1.20.0 as a workaround.

@bitnami-bot bitnami-bot moved this from On hold to Triage in Support Sep 19, 2023
@github-actions github-actions bot added triage Triage is needed and removed on-hold Issues or Pull Requests with this label will never be considered stale labels Sep 19, 2023
@carrodher carrodher moved this from Triage to In progress in Support Sep 20, 2023
@github-actions github-actions bot added in-progress and removed triage Triage is needed labels Sep 20, 2023
@bitnami-bot bitnami-bot assigned jotamartos and unassigned CeliaGMqrz Sep 20, 2023
@carrodher carrodher assigned CeliaGMqrz and unassigned jotamartos Sep 20, 2023
@CeliaGMqrz
Copy link
Contributor

Hi @penguincoder,

Could you confirm if the problem has been solved after the latest changes? Thanks for your feedback.

@github-actions github-actions bot moved this from In progress to Pending in Support Sep 20, 2023
@highemerly
Copy link

I have same issues, but I have confirmed that latest bitnami/pgbouncer:1.20.1 image fixes my issues.

@github-actions github-actions bot moved this from Pending to In progress in Support Sep 23, 2023
@CeliaGMqrz
Copy link
Contributor

Hi @highemerly, thanks for your feedback!

@github-actions github-actions bot moved this from In progress to Pending in Support Sep 25, 2023
@bitnami-bot bitnami-bot moved this from Pending to Solved in Support Sep 25, 2023
@github-actions github-actions bot removed this from Solved in Support Sep 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pgbouncer solved tech-issues The user has a technical issue about an application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants