Re: pgAgent Job never starts - Mailing list pgadmin-support

From Dave Page
Subject Re: pgAgent Job never starts
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E40176CF06@ratbert.vale-housing.co.uk
Whole thread Raw
In response to pgAgent Job never starts  ("Vincent CORDIER - LOGIXEN" <v.cordier@logixen.com>)
List pgadmin-support
Oh, sorry - spotted something else - 127.0.0.1 is not the same as localhost as far as pgpass.conf is concerned. The easiest test is pribably to add the following to the pgpass.conf:

127.0.0.1:5432:solofamily:postgres:XXXXXX

127.0.0.1:5432:postgres:postgres:XXXXX
 
In production though, I would standardise your pgAgent config and everything else to use one or the other.
 
Regards, Dave
 


From: Vincent CORDIER - LOGIXEN [mailto:v.cordier@logixen.com]
Sent: 20 September 2006 13:51
To: Dave Page
Subject: Re: [pgadmin-support] pgAgent Job never starts

It's the same error message :

"Couldn't create connection: fe_sendauth: no password supplied" :-(

----- Original Message -----
From: Dave Page
Sent: Wednesday, September 20, 2006 2:41 PM
Subject: Re: [pgadmin-support] pgAgent Job never starts

 


From: Vincent CORDIER - LOGIXEN [mailto:v.cordier@logixen.com]
Sent: 20 September 2006 15:08
To: Dave Page
Subject: Re: [pgadmin-support] pgAgent Job never starts

Here is the the pgAgent command line :
 
"D:\Program Files\PostgreSQL\8.1\bin\pgAgent" INSTALL pgAgent -l 2 -u postgres -p XXXXX
 
hostaddr=127.0.0.1 dbname=postgres user=postgres
 
and the pgpass.conf file  
 
OK, this modified pgpass.conf should do the job:
 
# This entry is required to connect and run the job step
localhost:5432:solofamily:postgres:XXXXXX
 
# This entry is required to access the pgAgent configuration
localhost:5432:postgres:postgres:XXXXX
 
Install that, restart pgAgent and the errors in the event log should vanish and the job should run.
 
Regards, Dave 

pgadmin-support by date:

Previous
From: "Dave Page"
Date:
Subject: Re: pgAgent Job never starts
Next
From: Sim Zacks
Date:
Subject: bug report