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 socket
localallall md5
# TYPE DATABASE USER ADDRESS METHOD
# "local" isfor Unix domain socket connections onlylocalallall scram-sha-256
# IPv4 local connections:
hostssl allall0.0.0.0/0 scram-sha-256
local/sockets authentication is, by default, peer authentication. PG knows the user is authenticated because Linux has already authenticated the account.