Postgres Service active with errors

From: nikhil raj <nikhilraj474(at)gmail(dot)com>
To: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Postgres Service active with errors
Date: 2024-05-23 22:52:27
Message-ID: CAG1ps1yzebmgdZXty+VVBszZszW_=iCfft87iOgJWy7=mFJ6mQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi All,

I can connect to Postgres, but when checking the status of the services, I
am getting the following error:

May 23 18:23:13 PG2433 systemd[1]: Starting PostgreSQL Cluster
13-main...*May 23 18:23:21 PG2433 postgresql(at)13-main[39428]: Warning:
connection to the database failed, disabling startup checks:
May 23 18:23:21 PG2433 postgresql(at)13-main[39428]: psql: error:
connection to server on socket "/var/run/postgresql/.s.PGSQL.5432"
failed: fe_sendauth: no password supplied*May 23 18:23:21 PG2433
systemd[1]: Started PostgreSQL Cluster 13-main.

When I set the database administrative login by Unix domain socket
authentication to md5 or scram-sha-256, it gives the above error in status,
but setting it to trust is a compliance issue.

Here is the relevant configuration in the pg_hba.conf file:

# Database administrative login by Unix domain socketlocal all
all md5

# TYPE DATABASE USER ADDRESS METHOD

# "local" is for Unix domain socket connections onlylocal all
all scram-sha-256
# IPv4 local connections:
hostssl all all 0.0.0.0/0 scram-sha-256

# IPv6 local connections:
host all all ::1/128 scram-sha-256
# Allow replication connections from localhost, by a user with the
# replication privilege.local replication all
peer
host replication all 127.0.0.1/32 md5
host replication all ::1/128 md5

And here is the relevant part of the postgresql.conf file:

listen_addresses = '*'
password_encryption = scram-sha-256

*.*

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message David G. Johnston 2024-05-23 23:46:43 Re: Postgres Service active with errors
Previous Message Rui DeSousa 2024-05-23 22:15:59 Re: AFTER INSERT trigger INSERT into another table-B are ignoring Table-B constraints