What may cause - Connection rejected: FATAL: Ident authentication failed for user?

Started by Emi Lualmost 17 years ago6 messagesgeneral
Jump to latest
#1Emi Lu
emilu@encs.concordia.ca

Good morning,

My daily data population cronjob(around 1 hour) terminated at the middle
and raised the following error this morning:

Connection rejected: FATAL: Ident authentication failed for user
"schema_owner_name".

Could anyone tell me what might cause the problem please?

Thanks a lot!
--
Lu Ying

#2Grzegorz Jaśkiewicz
gryzman@gmail.com
In reply to: Emi Lu (#1)
Re: What may cause - Connection rejected: FATAL: Ident authentication failed for user?

On Wed, Apr 22, 2009 at 2:36 PM, Emi Lu <emilu@encs.concordia.ca> wrote:

Good morning,

My daily data population cronjob(around 1 hour) terminated at the middle and
raised the following error this morning:

Connection rejected: FATAL: Ident authentication failed for user
"schema_owner_name".

Could anyone tell me what might cause the problem please?

password isn't specified for user, and indent rule doesn't apply to
his origin (host it is logging from) . Check hba conf

--
GJ

#3John Cheng
jlcheng@ymail.com
In reply to: Emi Lu (#1)
Re: What may cause - Connection rejected: FATAL: Ident authentication failed for user?

Check your pg_hba.conf file. What does it look like? The message suggests that your job is trying to connect to the database as the user "schema_owner_name" (or whatever the real user name is), but is actually running as a different unix user. Also, did anyone change the unix user running this particular data population job?

----
John L. Cheng

----- Original Message ----

Show quoted text

From: Emi Lu <emilu@encs.concordia.ca>
To: pgsql-general@postgresql.org
Sent: Wednesday, April 22, 2009 6:36:44 AM
Subject: [GENERAL] What may cause - Connection rejected: FATAL: Ident authentication failed for user?

Good morning,

My daily data population cronjob(around 1 hour) terminated at the middle and
raised the following error this morning:

Connection rejected: FATAL: Ident authentication failed for user
"schema_owner_name".

Could anyone tell me what might cause the problem please?

Thanks a lot!
-- Lu Ying

-- Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

#4Scott Marlowe
scott.marlowe@gmail.com
In reply to: Emi Lu (#1)
Re: What may cause - Connection rejected: FATAL: Ident authentication failed for user?

On Wed, Apr 22, 2009 at 7:36 AM, Emi Lu <emilu@encs.concordia.ca> wrote:

Good morning,

My daily data population cronjob(around 1 hour) terminated at the middle and
raised the following error this morning:

Connection rejected: FATAL: Ident authentication failed for user
"schema_owner_name".

Could anyone tell me what might cause the problem please?

This does not seem logical. ident authentication doesn't just
suddenly get turned on by accident. Are you sure these two things are
related?

#5Emi Lu
emilu@encs.concordia.ca
In reply to: Scott Marlowe (#4)
Re: What may cause - Connection rejected: FATAL: Ident authentication failed for user?

My daily data population cronjob(around 1 hour) terminated at the middle and
raised the following error this morning:

Connection rejected: FATAL: Ident authentication failed for user
"schema_owner_name".
Could anyone tell me what might cause the problem please?

This does not seem logical. ident authentication doesn't just
suddenly get turned on by accident. Are you sure these two things are
related?

The problem still did not resolve:( It happened again this morning.

No changes for the script and postgresql configuration. But when I
re-run the script, it succeeded.

The "Ident authentication" failure happened when "pg_dump" data to one
directory.

If it is not because of pg configuration, what other possible reasons
could cause this exception message???

--
Lu Ying

In reply to: Emi Lu (#5)
Re: What may cause - Connection rejected: FATAL: Ident authentication failed for user?

On 28/04/2009 15:52, Emi Lu wrote:

The problem still did not resolve:( It happened again this morning.

No changes for the script and postgresql configuration. But when I
re-run the script, it succeeded.

Is there something interrupting network connectivity?

Ray.

------------------------------------------------------------------
Raymond O'Donnell, Director of Music, Galway Cathedral, Ireland
rod@iol.ie
Galway Cathedral Recitals: http://www.galwaycathedral.org/recitals
------------------------------------------------------------------