FATAL logged when starting

From: "Sahagian, David" <david(dot)sahagian(at)emc(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: FATAL logged when starting
Date: 2013-02-21 16:34:55
Message-ID: F3CBFBA88397EA498B22A05FFA9EC49D011B61C6D5@MX22A.corp.emc.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

We get this FATAL pg_log entry, just after Postgres startup.
(Postgres does start OK)
//9.1.3 on Linux

2013-02-20 10:15:46.637 EST 50eedb22.3602 0
LOG: database system is ready to accept connections
2013-02-20 10:15:46.637 EST 50eedb22.3607 0
LOG: autovacuum launcher started
2013-02-20 10:15:47.390 EST [unknown] rsaadmin 50eedb23.3609 2/1 0
FATAL: no pg_hba.conf entry for host "[local]", user "rsaadmin", database "postgres", SSL off

Postgres is run under the linux user account "rsaadmin", but we don't have a Postgres role by that name.
We use [-w] as an option for pg_ctl start.

As I read postgresql.org/docs/9.1/static/app-pg-ctl.html,

-w
. . . When waiting for startup, pg_ctl repeatedly attempts to connect to the server . . .

My question:
Is there a way for me to specify a DIFFERENT USER, that pg_ctl will use to determine postgres has started ?

If not, how do people work around getting this nasty FATAL log message ?

Thanks,
-dvs-

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2013-02-21 16:41:30 Re: FATAL logged when starting
Previous Message Tom Lane 2013-02-21 16:27:53 Re: Trigram (pg_trgm) GIN index not used