github/databasus
1
1
Fork 0
mirror of https://github.com/databasus/databasus.git synced 2026-04-06 00:32:03 +02:00
Code Issues 3 Packages Projects Releases Wiki Activity

PostgreSQL restore fails with fe_sendauth: no password supplied despite pgpass file being present #270

New Issue
Closed
opened 2026-04-05 16:16:05 +02:00 by MrUnknownDE · 0 comments
MrUnknownDE commented 2026-04-05 16:16:05 +02:00
Owner
Copy Link

Originally created by @paowuh on 1/8/2026

Description

During a PostgreSQL restore operation performed with Databasus, the process fails due to an authentication error, even though a .pgpass file is automatically generated by the tool.

The backup is created from a PostgreSQL 14 server and restored to a PostgreSQL 14 identical (mirror) server.
The backup storage is a S3-compatible object storage.

Environment

  • Tool: Databasus 2.21.1
  • Source database: PostgreSQL 14
  • Target database: PostgreSQL 14
  • Backup storage: S3-compatible object storage
  • Authentication method: password

Steps to Reproduce

  1. Configure Databasus to back up a PostgreSQL 14 database.
  2. Store the backup on an S3-compatible object storage (scality).
  3. Start a restore operation to a PostgreSQL 14 mirror server.
  4. The restore fails at the beginning of the restore process.

Actual Result

The restore process fails with the following error:

PostgreSQL authentication failed - no password supplied. stderr: pg_restore: connecting to database for restore
WARNING: password file "/databasus-data/temp/pgpass_8dd95546-6a40-400f-aa9c-7435c52321db992840413/.pgpass" has group or world access; permissions should be u=rw (0600) or less
pg_restore: error: connection to server at "dbtracetest.steri.wh.com" (10.20.53.102), port 5432 failed: fe_sendauth: no password supplied
*Originally created by @paowuh on 1/8/2026* ## Description During a **PostgreSQL restore** operation performed with **Databasus**, the process fails due to an authentication error, even though a `.pgpass` file is automatically generated by the tool. The backup is created from a **PostgreSQL 14** server and restored to a **PostgreSQL 14 identical (mirror) server**. The backup storage is a **S3-compatible object storage**. --- ## Environment - Tool: **Databasus 2.21.1** - Source database: PostgreSQL 14 - Target database: PostgreSQL 14 - Backup storage: S3-compatible object storage - Authentication method: password --- ## Steps to Reproduce 1. Configure Databasus to back up a PostgreSQL 14 database. 2. Store the backup on an S3-compatible object storage (scality). 3. Start a restore operation to a PostgreSQL 14 mirror server. 4. The restore fails at the beginning of the restore process. --- ## Actual Result The restore process fails with the following error: ```text PostgreSQL authentication failed - no password supplied. stderr: pg_restore: connecting to database for restore WARNING: password file "/databasus-data/temp/pgpass_8dd95546-6a40-400f-aa9c-7435c52321db992840413/.pgpass" has group or world access; permissions should be u=rw (0600) or less pg_restore: error: connection to server at "dbtracetest.steri.wh.com" (10.20.53.102), port 5432 failed: fe_sendauth: no password supplied
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
bug
bug
bug
bug
bug
bug
bug
bug
bug
bug
bug
bug
bug
bug
bug
bug
bug
bug
bug
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
MrUnknownDE
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/databasus#270
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?