public inbox for [email protected]
help / color / mirror / Atom feedPGAgent 4.0 error feedback
8+ messages / 3 participants
[nested] [flat]
* PGAgent 4.0 error feedback
@ 2018-06-09 20:56 Rob Emery <[email protected]>
2018-06-11 03:43 ` Re: PGAgent 4.0 error feedback Ashesh Vashi <[email protected]>
0 siblings, 1 reply; 8+ messages in thread
From: Rob Emery @ 2018-06-09 20:56 UTC (permalink / raw)
To: pgadmin-hackers
Hi Guys,
I've been testing out PGAgent 4 (build today from master at commit
86ca5c5ed1ad572075ba27e05e4680ebdf5b9feb) to check the connection
handling on error is still fixed with the boost reimplementation
(which it is!)
and noticed a few issues compared to PGAgent 3 around feedback to the
user if the connection string is incorrect.
I've tested with incorrect username and password, user not in the hba,
db doesn't exist, postgresql not running on the host (or incorrect
hostaddr) and 4 seems to always returns the error :
`
ERROR: Couldn't find the function 'pgagent_schema_version' - please
run pgagent_upgrade.sql.
`
whereas 3.4.1 tends to output from the pgconnection itself like:
`
Sat Jun 9 21:32:13 2018 : WARNING: Couldn't create the primary
connection (attempt 1): FATAL: no pg_hba.conf entry for host
"172.30.0.16", user "pgagent_login_role", database
"pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user
"pgagent_login_role", database "pgagent_login_role", SSL off
`
which at least points the user towards the actual error!
Not sure if this is known already, but I thought I'd raise it prior to release.
Thanks,
Rob
--
--
<https://codeweavers.net;
Codeweavers May Newsletter
<https://mailchi.mp/codeweavers/march-edition-336883> l Codeweavers April
Finance Trends
<https://codeweavers.net/company-blog/codeweavers-april-finance-trends;
April’s Dealer Highlights
<https://codeweavers.net/company-blog/aprils-dealer-highlights;
<https://codeweavers.net/company-blog/codeweavers-march-car-finance-trends;
_
_
*Phone:* 0800 021 0888 Email: [email protected]
<mailto:[email protected]>
Codeweavers Ltd | Barn 4 | Dunston
Business Village | Dunston | ST18 9AB
Registered in England and Wales No.
04092394 | VAT registration no. 974 9705 63
<https://www.linkedin.com/company/codeweavers-limited>
<https://vimeo.com/codeweaversltd>
<https://plus.google.com/b/105942302039373248738/+CodeweaversNet>
<https://twitter.com/CodeweaversTeam;
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: PGAgent 4.0 error feedback
2018-06-09 20:56 PGAgent 4.0 error feedback Rob Emery <[email protected]>
@ 2018-06-11 03:43 ` Ashesh Vashi <[email protected]>
2018-06-11 04:28 ` Re: PGAgent 4.0 error feedback Ashesh Vashi <[email protected]>
2018-06-11 07:20 ` Re: PGAgent 4.0 error feedback Rob Emery <[email protected]>
0 siblings, 2 replies; 8+ messages in thread
From: Ashesh Vashi @ 2018-06-11 03:43 UTC (permalink / raw)
To: Rob Emery <[email protected]>; +Cc: pgadmin-hackers
Hi Rob,
On Sun, Jun 10, 2018 at 2:26 AM, Rob Emery <[email protected]> wrote:
> Hi Guys,
>
> I've been testing out PGAgent 4 (build today from master at commit
> 86ca5c5ed1ad572075ba27e05e4680ebdf5b9feb) to check the connection
> handling on error is still fixed with the boost reimplementation
> (which it is!)
> and noticed a few issues compared to PGAgent 3 around feedback to the
> user if the connection string is incorrect.
>
> I've tested with incorrect username and password, user not in the hba,
> db doesn't exist, postgresql not running on the host (or incorrect
> hostaddr) and 4 seems to always returns the error :
> `
> ERROR: Couldn't find the function 'pgagent_schema_version' - please
> run pgagent_upgrade.sql.
> `
>
> whereas 3.4.1 tends to output from the pgconnection itself like:
> `
> Sat Jun 9 21:32:13 2018 : WARNING: Couldn't create the primary
> connection (attempt 1): FATAL: no pg_hba.conf entry for host
> "172.30.0.16", user "pgagent_login_role", database
> "pgagent_login_role", SSL on
> FATAL: no pg_hba.conf entry for host "172.30.0.16", user
> "pgagent_login_role", database "pgagent_login_role", SSL off
> `
>
> which at least points the user towards the actual error!
>
> Not sure if this is known already, but I thought I'd raise it prior to
> release.
>
Thanks for sharing the information.
Is it possible for you to share the logs with log level set to debug?
Also - please share the operating system details?
--
Thanks & Regards,
Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company
<http://www.enterprisedb.com/;
*http://www.linkedin.com/in/asheshvashi*
<http://www.linkedin.com/in/asheshvashi;
>
> Thanks,
> Rob
> --
>
> --
> <https://codeweavers.net;
>
>
> Codeweavers May Newsletter
> <https://mailchi.mp/codeweavers/march-edition-336883; l Codeweavers
> April
> Finance Trends
> <https://codeweavers.net/company-blog/codeweavers-april-finance-trends;
>
>
> April’s Dealer Highlights
> <https://codeweavers.net/company-blog/aprils-dealer-highlights;
> <https://codeweavers.net/company-blog/codeweavers-march-car-finance-trends
> >
>
> _
> _
>
>
>
> *Phone:* 0800 021 0888 Email: [email protected]
> <mailto:[email protected]>
> Codeweavers Ltd | Barn 4 | Dunston
> Business Village | Dunston | ST18 9AB
> Registered in England and Wales No.
> 04092394 | VAT registration no. 974 9705 63
>
>
>
>
> <https://www.linkedin.com/company/codeweavers-limited;
> <https://vimeo.com/codeweaversltd;
> <https://plus.google.com/b/105942302039373248738/+CodeweaversNet;
> <https://twitter.com/CodeweaversTeam;
>
>
>
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: PGAgent 4.0 error feedback
2018-06-09 20:56 PGAgent 4.0 error feedback Rob Emery <[email protected]>
2018-06-11 03:43 ` Re: PGAgent 4.0 error feedback Ashesh Vashi <[email protected]>
@ 2018-06-11 04:28 ` Ashesh Vashi <[email protected]>
1 sibling, 0 replies; 8+ messages in thread
From: Ashesh Vashi @ 2018-06-11 04:28 UTC (permalink / raw)
To: Rob Emery <[email protected]>; +Cc: pgadmin-hackers
Hi Rob,
On Mon, Jun 11, 2018 at 9:13 AM, Ashesh Vashi <[email protected]
> wrote:
> Hi Rob,
>
> On Sun, Jun 10, 2018 at 2:26 AM, Rob Emery <[email protected]>
> wrote:
>
>> Hi Guys,
>>
>> I've been testing out PGAgent 4 (build today from master at commit
>> 86ca5c5ed1ad572075ba27e05e4680ebdf5b9feb) to check the connection
>> handling on error is still fixed with the boost reimplementation
>> (which it is!)
>> and noticed a few issues compared to PGAgent 3 around feedback to the
>> user if the connection string is incorrect.
>>
>> I've tested with incorrect username and password, user not in the hba,
>> db doesn't exist, postgresql not running on the host (or incorrect
>> hostaddr) and 4 seems to always returns the error :
>> `
>> ERROR: Couldn't find the function 'pgagent_schema_version' - please
>> run pgagent_upgrade.sql.
>> `
>>
>> whereas 3.4.1 tends to output from the pgconnection itself like:
>> `
>> Sat Jun 9 21:32:13 2018 : WARNING: Couldn't create the primary
>> connection (attempt 1): FATAL: no pg_hba.conf entry for host
>> "172.30.0.16", user "pgagent_login_role", database
>> "pgagent_login_role", SSL on
>> FATAL: no pg_hba.conf entry for host "172.30.0.16", user
>> "pgagent_login_role", database "pgagent_login_role", SSL off
>> `
>>
>> which at least points the user towards the actual error!
>>
>> Not sure if this is known already, but I thought I'd raise it prior to
>> release.
>>
> Thanks for sharing the information.
>
> Is it possible for you to share the logs with log level set to debug?
> Also - please share the operating system details?
>
I've sent a patch
<https://www.postgresql.org/message-id/CAG7mmoy7ruK%3DHZGOt5GTFsuSF5e4%2BzHnagU0hJfuMUhqjZs%3Dmw%40ma...;
to resolve the issue based on some assumptions, to verify those
assumptions I would still like to see the logs (if you can provide), and
operating system information.
--
Thanks & Regards,
Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company
<http://www.enterprisedb.com/;
*http://www.linkedin.com/in/asheshvashi
<http://www.linkedin.com/in/asheshvashi>*
>
> --
>
> Thanks & Regards,
>
> Ashesh Vashi
> EnterpriseDB INDIA: Enterprise PostgreSQL Company
> <http://www.enterprisedb.com/;
>
>
> *http://www.linkedin.com/in/asheshvashi*
> <http://www.linkedin.com/in/asheshvashi;
>
>
>
>>
>> Thanks,
>> Rob
>> --
>>
>> --
>> <https://codeweavers.net;
>>
>>
>> Codeweavers May Newsletter
>> <https://mailchi.mp/codeweavers/march-edition-336883; l Codeweavers
>> April
>> Finance Trends
>> <https://codeweavers.net/company-blog/codeweavers-april-finance-trends;
>>
>>
>> April’s Dealer Highlights
>> <https://codeweavers.net/company-blog/aprils-dealer-highlights;
>> <https://codeweavers.net/company-blog/codeweavers-march-car-
>> finance-trends>
>>
>> _
>> _
>>
>>
>>
>> *Phone:* 0800 021 0888 Email: [email protected]
>> <mailto:[email protected]>
>> Codeweavers Ltd | Barn 4 | Dunston
>> Business Village | Dunston | ST18 9AB
>> Registered in England and Wales No.
>> 04092394 | VAT registration no. 974 9705 63
>>
>>
>>
>>
>> <https://www.linkedin.com/company/codeweavers-limited;
>> <https://vimeo.com/codeweaversltd;
>> <https://plus.google.com/b/105942302039373248738/+CodeweaversNet;
>> <https://twitter.com/CodeweaversTeam;
>>
>>
>>
>
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: PGAgent 4.0 error feedback
2018-06-09 20:56 PGAgent 4.0 error feedback Rob Emery <[email protected]>
2018-06-11 03:43 ` Re: PGAgent 4.0 error feedback Ashesh Vashi <[email protected]>
@ 2018-06-11 07:20 ` Rob Emery <[email protected]>
2018-06-11 07:28 ` Re: PGAgent 4.0 error feedback Ashesh Vashi <[email protected]>
1 sibling, 1 reply; 8+ messages in thread
From: Rob Emery @ 2018-06-11 07:20 UTC (permalink / raw)
To: Ashesh Vashi <[email protected]>; +Cc: pgadmin-hackers
Hi Ashesh,
Log-level wise I was using the same command for both versions:
./pgagent -f -l 2 -t 1 -r 1 'hostaddr=server user=username
password=password dbname=postgres'
and messing up the connection string in various ways (missing dbname,
incorrect password, incorrect hostaddr)
This was built and tested on Debian GNU/Linux 9.4 (stretch).
I've attached an example of the differing output when the dbname is missing
from the connectionstring; basically it's the same for all errors.
Many Thanks,
Rob
On 11/06/2018, Ashesh Vashi <[email protected]> wrote:
> Hi Rob,
>
> On Sun, Jun 10, 2018 at 2:26 AM, Rob Emery <[email protected]>
> wrote:
>
>> Hi Guys,
>>
>> I've been testing out PGAgent 4 (build today from master at commit
>> 86ca5c5ed1ad572075ba27e05e4680ebdf5b9feb) to check the connection
>> handling on error is still fixed with the boost reimplementation
>> (which it is!)
>> and noticed a few issues compared to PGAgent 3 around feedback to the
>> user if the connection string is incorrect.
>>
>> I've tested with incorrect username and password, user not in the hba,
>> db doesn't exist, postgresql not running on the host (or incorrect
>> hostaddr) and 4 seems to always returns the error :
>> `
>> ERROR: Couldn't find the function 'pgagent_schema_version' - please
>> run pgagent_upgrade.sql.
>> `
>>
>> whereas 3.4.1 tends to output from the pgconnection itself like:
>> `
>> Sat Jun 9 21:32:13 2018 : WARNING: Couldn't create the primary
>> connection (attempt 1): FATAL: no pg_hba.conf entry for host
>> "172.30.0.16", user "pgagent_login_role", database
>> "pgagent_login_role", SSL on
>> FATAL: no pg_hba.conf entry for host "172.30.0.16", user
>> "pgagent_login_role", database "pgagent_login_role", SSL off
>> `
>>
>> which at least points the user towards the actual error!
>>
>> Not sure if this is known already, but I thought I'd raise it prior to
>> release.
>>
> Thanks for sharing the information.
>
> Is it possible for you to share the logs with log level set to debug?
> Also - please share the operating system details?
>
> --
>
> Thanks & Regards,
>
> Ashesh Vashi
> EnterpriseDB INDIA: Enterprise PostgreSQL Company
> <http://www.enterprisedb.com/;
>
>
> *http://www.linkedin.com/in/asheshvashi*
> <http://www.linkedin.com/in/asheshvashi;
>
>
>
>>
>> Thanks,
>> Rob
>> --
>>
>> --
>> <https://codeweavers.net;
>>
>>
>> Codeweavers May Newsletter
>> <https://mailchi.mp/codeweavers/march-edition-336883; l Codeweavers
>> April
>> Finance Trends
>> <https://codeweavers.net/company-blog/codeweavers-april-finance-trends;
>>
>>
>> April’s Dealer Highlights
>> <https://codeweavers.net/company-blog/aprils-dealer-highlights;
>> <https://codeweavers.net/company-blog/codeweavers-march-car-finance-trends
>> >
>>
>> _
>> _
>>
>>
>>
>> *Phone:* 0800 021 0888 Email: [email protected]
>> <mailto:[email protected]>
>> Codeweavers Ltd | Barn 4 | Dunston
>> Business Village | Dunston | ST18 9AB
>> Registered in England and Wales No.
>> 04092394 | VAT registration no. 974 9705 63
>>
>>
>>
>>
>> <https://www.linkedin.com/company/codeweavers-limited;
>> <https://vimeo.com/codeweaversltd;
>> <https://plus.google.com/b/105942302039373248738/+CodeweaversNet;
>> <https://twitter.com/CodeweaversTeam;
>>
>>
>>
>
--
<https://codeweavers.net;
Codeweavers May Newsletter
<https://mailchi.mp/codeweavers/march-edition-336883> l Codeweavers April
Finance Trends
<https://codeweavers.net/company-blog/codeweavers-april-finance-trends;
April’s Dealer Highlights
<https://codeweavers.net/company-blog/aprils-dealer-highlights;
<https://codeweavers.net/company-blog/codeweavers-march-car-finance-trends;
_
_
*Phone:* 0800 021 0888 Email: [email protected]
<mailto:[email protected]>
Codeweavers Ltd | Barn 4 | Dunston
Business Village | Dunston | ST18 9AB
Registered in England and Wales No.
04092394 | VAT registration no. 974 9705 63
<https://www.linkedin.com/company/codeweavers-limited>
<https://vimeo.com/codeweaversltd>
<https://plus.google.com/b/105942302039373248738/+CodeweaversNet>
<https://twitter.com/CodeweaversTeam;
rob@ISIS:~/pgagent-git-build$ ./pgagent -f 'hostaddr=172.30.0.16 user=pgagent_login_role password=password'
Mon Jun 11 08:17:49 2018 ERROR: Couldn't find the function 'pgagent_schema_version' - please run pgagent_upgrade.sql.
rob@ISIS:~/pgagent-3.4.1-build$ ./pgagent -f 'hostaddr=172.30.0.16 user=pgagent_login_role password=password'
Mon Jun 11 08:18:01 2018 : WARNING: Couldn't create the primary connection (attempt 1): could not connect to server: Connection refused
Is the server running on host "172.30.0.16" and accepting
TCP/IP connections on port 5432?
Attachments:
[text/plain] PGagent-BrokenConnectionString.txt (587B, 2-PGagent-BrokenConnectionString.txt)
download | inline:
rob@ISIS:~/pgagent-git-build$ ./pgagent -f 'hostaddr=172.30.0.16 user=pgagent_login_role password=password'
Mon Jun 11 08:17:49 2018 ERROR: Couldn't find the function 'pgagent_schema_version' - please run pgagent_upgrade.sql.
rob@ISIS:~/pgagent-3.4.1-build$ ./pgagent -f 'hostaddr=172.30.0.16 user=pgagent_login_role password=password'
Mon Jun 11 08:18:01 2018 : WARNING: Couldn't create the primary connection (attempt 1): could not connect to server: Connection refused
Is the server running on host "172.30.0.16" and accepting
TCP/IP connections on port 5432?
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: PGAgent 4.0 error feedback
2018-06-09 20:56 PGAgent 4.0 error feedback Rob Emery <[email protected]>
2018-06-11 03:43 ` Re: PGAgent 4.0 error feedback Ashesh Vashi <[email protected]>
2018-06-11 07:20 ` Re: PGAgent 4.0 error feedback Rob Emery <[email protected]>
@ 2018-06-11 07:28 ` Ashesh Vashi <[email protected]>
2018-06-11 08:08 ` Re: PGAgent 4.0 error feedback Robert Emery <[email protected]>
0 siblings, 1 reply; 8+ messages in thread
From: Ashesh Vashi @ 2018-06-11 07:28 UTC (permalink / raw)
To: Rob Emery <[email protected]>; +Cc: pgadmin-hackers
Hi Rob,
On Mon, Jun 11, 2018 at 12:50 PM, Rob Emery <[email protected]>
wrote:
> Hi Ashesh,
>
> Log-level wise I was using the same command for both versions:
>
> ./pgagent -f -l 2 -t 1 -r 1 'hostaddr=server user=username
> password=password dbname=postgres'
>
> and messing up the connection string in various ways (missing dbname,
> incorrect password, incorrect hostaddr)
>
> This was built and tested on Debian GNU/Linux 9.4 (stretch).
>
If you're working on the source, would please test the patch sent by me?
>
> I've attached an example of the differing output when the dbname is missing
> from the connectionstring; basically it's the same for all errors.
>
Thanks a lot for the information.
-- Thanks, Ashesh
>
> Many Thanks,
> Rob
>
> On 11/06/2018, Ashesh Vashi <[email protected]> wrote:
> > Hi Rob,
> >
> > On Sun, Jun 10, 2018 at 2:26 AM, Rob Emery <[email protected]>
> > wrote:
> >
> >> Hi Guys,
> >>
> >> I've been testing out PGAgent 4 (build today from master at commit
> >> 86ca5c5ed1ad572075ba27e05e4680ebdf5b9feb) to check the connection
> >> handling on error is still fixed with the boost reimplementation
> >> (which it is!)
> >> and noticed a few issues compared to PGAgent 3 around feedback to the
> >> user if the connection string is incorrect.
> >>
> >> I've tested with incorrect username and password, user not in the hba,
> >> db doesn't exist, postgresql not running on the host (or incorrect
> >> hostaddr) and 4 seems to always returns the error :
> >> `
> >> ERROR: Couldn't find the function 'pgagent_schema_version' - please
> >> run pgagent_upgrade.sql.
> >> `
> >>
> >> whereas 3.4.1 tends to output from the pgconnection itself like:
> >> `
> >> Sat Jun 9 21:32:13 2018 : WARNING: Couldn't create the primary
> >> connection (attempt 1): FATAL: no pg_hba.conf entry for host
> >> "172.30.0.16", user "pgagent_login_role", database
> >> "pgagent_login_role", SSL on
> >> FATAL: no pg_hba.conf entry for host "172.30.0.16", user
> >> "pgagent_login_role", database "pgagent_login_role", SSL off
> >> `
> >>
> >> which at least points the user towards the actual error!
> >>
> >> Not sure if this is known already, but I thought I'd raise it prior to
> >> release.
> >>
> > Thanks for sharing the information.
> >
> > Is it possible for you to share the logs with log level set to debug?
> > Also - please share the operating system details?
> >
> > --
> >
> > Thanks & Regards,
> >
> > Ashesh Vashi
> > EnterpriseDB INDIA: Enterprise PostgreSQL Company
> > <http://www.enterprisedb.com/;
> >
> >
> > *http://www.linkedin.com/in/asheshvashi*
> > <http://www.linkedin.com/in/asheshvashi;
> >
> >
> >
> >>
> >> Thanks,
> >> Rob
> >> --
> >>
> >> --
> >> <https://codeweavers.net;
> >>
> >>
> >> Codeweavers May Newsletter
> >> <https://mailchi.mp/codeweavers/march-edition-336883; l Codeweavers
> >> April
> >> Finance Trends
> >> <https://codeweavers.net/company-blog/codeweavers-april-finance-trends;
> >>
> >>
> >> April’s Dealer Highlights
> >> <https://codeweavers.net/company-blog/aprils-dealer-highlights;
> >> <https://codeweavers.net/company-blog/codeweavers-
> march-car-finance-trends
> >> >
> >>
> >> _
> >> _
> >>
> >>
> >>
> >> *Phone:* 0800 021 0888 Email: [email protected]
> >> <mailto:[email protected]>
> >> Codeweavers Ltd | Barn 4 | Dunston
> >> Business Village | Dunston | ST18 9AB
> >> Registered in England and Wales No.
> >> 04092394 | VAT registration no. 974 9705 63
> >>
> >>
> >>
> >>
> >> <https://www.linkedin.com/company/codeweavers-limited;
> >> <https://vimeo.com/codeweaversltd;
> >> <https://plus.google.com/b/105942302039373248738/+CodeweaversNet;
> >> <https://twitter.com/CodeweaversTeam;
> >>
> >>
> >>
> >
>
> --
> <https://codeweavers.net;
>
>
> Codeweavers May Newsletter
> <https://mailchi.mp/codeweavers/march-edition-336883; l Codeweavers
> April
> Finance Trends
> <https://codeweavers.net/company-blog/codeweavers-april-finance-trends;
>
>
> April’s Dealer Highlights
> <https://codeweavers.net/company-blog/aprils-dealer-highlights;
> <https://codeweavers.net/company-blog/codeweavers-march-car-finance-trends
> >
>
> _
> _
>
>
>
> *Phone:* 0800 021 0888 Email: [email protected]
> <mailto:[email protected]>
> Codeweavers Ltd | Barn 4 | Dunston
> Business Village | Dunston | ST18 9AB
> Registered in England and Wales No.
> 04092394 | VAT registration no. 974 9705 63
>
>
>
>
> <https://www.linkedin.com/company/codeweavers-limited;
> <https://vimeo.com/codeweaversltd;
> <https://plus.google.com/b/105942302039373248738/+CodeweaversNet;
> <https://twitter.com/CodeweaversTeam;
>
>
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: PGAgent 4.0 error feedback
2018-06-09 20:56 PGAgent 4.0 error feedback Rob Emery <[email protected]>
2018-06-11 03:43 ` Re: PGAgent 4.0 error feedback Ashesh Vashi <[email protected]>
2018-06-11 07:20 ` Re: PGAgent 4.0 error feedback Rob Emery <[email protected]>
2018-06-11 07:28 ` Re: PGAgent 4.0 error feedback Ashesh Vashi <[email protected]>
@ 2018-06-11 08:08 ` Robert Emery <[email protected]>
2018-06-11 08:10 ` Fwd: PGAgent 4.0 error feedback Rob Emery <[email protected]>
2018-06-11 09:43 ` Re: PGAgent 4.0 error feedback Ashesh Vashi <[email protected]>
0 siblings, 2 replies; 8+ messages in thread
From: Robert Emery @ 2018-06-11 08:08 UTC (permalink / raw)
To: Ashesh Vashi <[email protected]>; +Cc: pgadmin-hackers
Hello Again,
I've just tested the patch and the output is *much* more verbose with the same
set of flags now, even more so than the old version (see attached).
Thanks,
Rob
On 11/06/2018, Ashesh Vashi <[email protected]> wrote:
> Hi Rob,
>
>
> On Mon, Jun 11, 2018 at 12:50 PM, Rob Emery <[email protected]>
> wrote:
>
>> Hi Ashesh,
>>
>> Log-level wise I was using the same command for both versions:
>>
>> ./pgagent -f -l 2 -t 1 -r 1 'hostaddr=server user=username
>> password=password dbname=postgres'
>>
>> and messing up the connection string in various ways (missing dbname,
>> incorrect password, incorrect hostaddr)
>>
>> This was built and tested on Debian GNU/Linux 9.4 (stretch).
>>
> If you're working on the source, would please test the patch sent by me?
>
>>
>> I've attached an example of the differing output when the dbname is
>> missing
>> from the connectionstring; basically it's the same for all errors.
>>
>
> Thanks a lot for the information.
>
> -- Thanks, Ashesh
>
>>
>> Many Thanks,
>> Rob
>>
>> On 11/06/2018, Ashesh Vashi <[email protected]> wrote:
>> > Hi Rob,
>> >
>> > On Sun, Jun 10, 2018 at 2:26 AM, Rob Emery <[email protected]>
>> > wrote:
>> >
>> >> Hi Guys,
>> >>
>> >> I've been testing out PGAgent 4 (build today from master at commit
>> >> 86ca5c5ed1ad572075ba27e05e4680ebdf5b9feb) to check the connection
>> >> handling on error is still fixed with the boost reimplementation
>> >> (which it is!)
>> >> and noticed a few issues compared to PGAgent 3 around feedback to the
>> >> user if the connection string is incorrect.
>> >>
>> >> I've tested with incorrect username and password, user not in the hba,
>> >> db doesn't exist, postgresql not running on the host (or incorrect
>> >> hostaddr) and 4 seems to always returns the error :
>> >> `
>> >> ERROR: Couldn't find the function 'pgagent_schema_version' - please
>> >> run pgagent_upgrade.sql.
>> >> `
>> >>
>> >> whereas 3.4.1 tends to output from the pgconnection itself like:
>> >> `
>> >> Sat Jun 9 21:32:13 2018 : WARNING: Couldn't create the primary
>> >> connection (attempt 1): FATAL: no pg_hba.conf entry for host
>> >> "172.30.0.16", user "pgagent_login_role", database
>> >> "pgagent_login_role", SSL on
>> >> FATAL: no pg_hba.conf entry for host "172.30.0.16", user
>> >> "pgagent_login_role", database "pgagent_login_role", SSL off
>> >> `
>> >>
>> >> which at least points the user towards the actual error!
>> >>
>> >> Not sure if this is known already, but I thought I'd raise it prior to
>> >> release.
>> >>
>> > Thanks for sharing the information.
>> >
>> > Is it possible for you to share the logs with log level set to debug?
>> > Also - please share the operating system details?
>> >
>> > --
>> >
>> > Thanks & Regards,
>> >
>> > Ashesh Vashi
>> > EnterpriseDB INDIA: Enterprise PostgreSQL Company
>> > <http://www.enterprisedb.com/;
>> >
>> >
>> > *http://www.linkedin.com/in/asheshvashi*
>> > <http://www.linkedin.com/in/asheshvashi;
>> >
>> >
>> >
>> >>
>> >> Thanks,
>> >> Rob
>> >> --
>> >>
>> >> --
>> >> <https://codeweavers.net;
>> >>
>> >>
>> >> Codeweavers May Newsletter
>> >> <https://mailchi.mp/codeweavers/march-edition-336883; l Codeweavers
>> >> April
>> >> Finance Trends
>> >> <https://codeweavers.net/company-blog/codeweavers-april-finance-trends;
>> >>
>> >>
>> >> April’s Dealer Highlights
>> >> <https://codeweavers.net/company-blog/aprils-dealer-highlights;
>> >> <https://codeweavers.net/company-blog/codeweavers-
>> march-car-finance-trends
>> >> >
>> >>
>> >> _
>> >> _
>> >>
>> >>
>> >>
>> >> *Phone:* 0800 021 0888 Email: [email protected]
>> >> <mailto:[email protected]>
>> >> Codeweavers Ltd | Barn 4 | Dunston
>> >> Business Village | Dunston | ST18 9AB
>> >> Registered in England and Wales No.
>> >> 04092394 | VAT registration no. 974 9705 63
>> >>
>> >>
>> >>
>> >>
>> >> <https://www.linkedin.com/company/codeweavers-limited;
>> >> <https://vimeo.com/codeweaversltd;
>> >> <https://plus.google.com/b/105942302039373248738/+CodeweaversNet;
>> >> <https://twitter.com/CodeweaversTeam;
>> >>
>> >>
>> >>
>> >
>>
>> --
>> <https://codeweavers.net;
>>
>>
>> Codeweavers May Newsletter
>> <https://mailchi.mp/codeweavers/march-edition-336883; l Codeweavers
>> April
>> Finance Trends
>> <https://codeweavers.net/company-blog/codeweavers-april-finance-trends;
>>
>>
>> April’s Dealer Highlights
>> <https://codeweavers.net/company-blog/aprils-dealer-highlights;
>> <https://codeweavers.net/company-blog/codeweavers-march-car-finance-trends
>> >
>>
>> _
>> _
>>
>>
>>
>> *Phone:* 0800 021 0888 Email: [email protected]
>> <mailto:[email protected]>
>> Codeweavers Ltd | Barn 4 | Dunston
>> Business Village | Dunston | ST18 9AB
>> Registered in England and Wales No.
>> 04092394 | VAT registration no. 974 9705 63
>>
>>
>>
>>
>> <https://www.linkedin.com/company/codeweavers-limited;
>> <https://vimeo.com/codeweaversltd;
>> <https://plus.google.com/b/105942302039373248738/+CodeweaversNet;
>> <https://twitter.com/CodeweaversTeam;
>>
>>
>
--
Robert Emery
Infrastructure Director
E: [email protected] | T: 01785 711633 | W: www.codeweavers.net
--
<https://codeweavers.net;
Codeweavers May Newsletter
<https://mailchi.mp/codeweavers/march-edition-336883> l Codeweavers April
Finance Trends
<https://codeweavers.net/company-blog/codeweavers-april-finance-trends;
April’s Dealer Highlights
<https://codeweavers.net/company-blog/aprils-dealer-highlights;
<https://codeweavers.net/company-blog/codeweavers-march-car-finance-trends;
_
_
*Phone:* 0800 021 0888 Email: [email protected]
<mailto:[email protected]>
Codeweavers Ltd | Barn 4 | Dunston
Business Village | Dunston | ST18 9AB
Registered in England and Wales No.
04092394 | VAT registration no. 974 9705 63
<https://www.linkedin.com/company/codeweavers-limited>
<https://vimeo.com/codeweaversltd>
<https://plus.google.com/b/105942302039373248738/+CodeweaversNet>
<https://twitter.com/CodeweaversTeam;
./pgagent -f -l 2 -t 1 -r 1 'hostaddr=172.30.0.2 user=pgagent_login_role password=password'
Mon Jun 11 09:06:05 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:05 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:05 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:05 2018 DEBUG: password: *****
Mon Jun 11 09:06:05 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:05 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:05 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:05 2018 WARNING: Couldn't create the primary connection [Attempt #1]
Mon Jun 11 09:06:05 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:05 2018 DEBUG: No connections found!
Mon Jun 11 09:06:06 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:06 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:06 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:06 2018 DEBUG: password: *****
Mon Jun 11 09:06:06 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:06 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:06 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:06 2018 WARNING: Couldn't create the primary connection [Attempt #2]
Mon Jun 11 09:06:06 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:06 2018 DEBUG: No connections found!
Mon Jun 11 09:06:07 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:07 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:07 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:07 2018 DEBUG: password: *****
Mon Jun 11 09:06:07 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:07 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:07 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:07 2018 WARNING: Couldn't create the primary connection [Attempt #3]
Mon Jun 11 09:06:07 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:07 2018 DEBUG: No connections found!
Mon Jun 11 09:06:08 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:08 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:08 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:08 2018 DEBUG: password: *****
Mon Jun 11 09:06:08 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:08 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:08 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:08 2018 WARNING: Couldn't create the primary connection [Attempt #4]
Mon Jun 11 09:06:08 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:08 2018 DEBUG: No connections found!
Mon Jun 11 09:06:09 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:09 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:09 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:09 2018 DEBUG: password: *****
Mon Jun 11 09:06:09 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:09 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:09 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:09 2018 WARNING: Couldn't create the primary connection [Attempt #5]
Mon Jun 11 09:06:09 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:09 2018 DEBUG: No connections found!
Mon Jun 11 09:06:10 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:10 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:10 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:10 2018 DEBUG: password: *****
Mon Jun 11 09:06:10 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:10 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:10 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:10 2018 WARNING: Couldn't create the primary connection [Attempt #6]
Mon Jun 11 09:06:10 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:10 2018 DEBUG: No connections found!
Mon Jun 11 09:06:11 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:11 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:11 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:11 2018 DEBUG: password: *****
Mon Jun 11 09:06:11 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:11 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:11 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:11 2018 WARNING: Couldn't create the primary connection [Attempt #7]
Mon Jun 11 09:06:11 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:11 2018 DEBUG: No connections found!
Mon Jun 11 09:06:12 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:12 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:12 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:12 2018 DEBUG: password: *****
Mon Jun 11 09:06:12 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:12 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:12 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:12 2018 WARNING: Couldn't create the primary connection [Attempt #8]
Mon Jun 11 09:06:12 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:12 2018 DEBUG: No connections found!
Mon Jun 11 09:06:13 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:13 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:13 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:13 2018 DEBUG: password: *****
Mon Jun 11 09:06:13 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:13 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:13 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:13 2018 WARNING: Couldn't create the primary connection [Attempt #9]
Mon Jun 11 09:06:13 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:13 2018 DEBUG: No connections found!
Mon Jun 11 09:06:14 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:14 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:14 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:14 2018 DEBUG: password: *****
Mon Jun 11 09:06:14 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:14 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:14 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:14 2018 WARNING: Couldn't create the primary connection [Attempt #10]
Mon Jun 11 09:06:14 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:14 2018 DEBUG: No connections found!
Mon Jun 11 09:06:14 2018 ERROR: Stopping pgAgent: Couldn't establish the primary connection with the database server.
Attachments:
[text/plain] Output.txt (9.3K, 2-Output.txt)
download | inline:
./pgagent -f -l 2 -t 1 -r 1 'hostaddr=172.30.0.2 user=pgagent_login_role password=password'
Mon Jun 11 09:06:05 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:05 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:05 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:05 2018 DEBUG: password: *****
Mon Jun 11 09:06:05 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:05 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:05 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:05 2018 WARNING: Couldn't create the primary connection [Attempt #1]
Mon Jun 11 09:06:05 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:05 2018 DEBUG: No connections found!
Mon Jun 11 09:06:06 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:06 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:06 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:06 2018 DEBUG: password: *****
Mon Jun 11 09:06:06 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:06 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:06 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:06 2018 WARNING: Couldn't create the primary connection [Attempt #2]
Mon Jun 11 09:06:06 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:06 2018 DEBUG: No connections found!
Mon Jun 11 09:06:07 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:07 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:07 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:07 2018 DEBUG: password: *****
Mon Jun 11 09:06:07 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:07 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:07 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:07 2018 WARNING: Couldn't create the primary connection [Attempt #3]
Mon Jun 11 09:06:07 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:07 2018 DEBUG: No connections found!
Mon Jun 11 09:06:08 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:08 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:08 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:08 2018 DEBUG: password: *****
Mon Jun 11 09:06:08 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:08 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:08 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:08 2018 WARNING: Couldn't create the primary connection [Attempt #4]
Mon Jun 11 09:06:08 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:08 2018 DEBUG: No connections found!
Mon Jun 11 09:06:09 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:09 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:09 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:09 2018 DEBUG: password: *****
Mon Jun 11 09:06:09 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:09 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:09 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:09 2018 WARNING: Couldn't create the primary connection [Attempt #5]
Mon Jun 11 09:06:09 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:09 2018 DEBUG: No connections found!
Mon Jun 11 09:06:10 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:10 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:10 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:10 2018 DEBUG: password: *****
Mon Jun 11 09:06:10 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:10 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:10 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:10 2018 WARNING: Couldn't create the primary connection [Attempt #6]
Mon Jun 11 09:06:10 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:10 2018 DEBUG: No connections found!
Mon Jun 11 09:06:11 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:11 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:11 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:11 2018 DEBUG: password: *****
Mon Jun 11 09:06:11 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:11 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:11 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:11 2018 WARNING: Couldn't create the primary connection [Attempt #7]
Mon Jun 11 09:06:11 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:11 2018 DEBUG: No connections found!
Mon Jun 11 09:06:12 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:12 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:12 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:12 2018 DEBUG: password: *****
Mon Jun 11 09:06:12 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:12 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:12 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:12 2018 WARNING: Couldn't create the primary connection [Attempt #8]
Mon Jun 11 09:06:12 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:12 2018 DEBUG: No connections found!
Mon Jun 11 09:06:13 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:13 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:13 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:13 2018 DEBUG: password: *****
Mon Jun 11 09:06:13 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:13 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:13 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:13 2018 WARNING: Couldn't create the primary connection [Attempt #9]
Mon Jun 11 09:06:13 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:13 2018 DEBUG: No connections found!
Mon Jun 11 09:06:14 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:14 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:14 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:14 2018 DEBUG: password: *****
Mon Jun 11 09:06:14 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:14 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:14 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:14 2018 WARNING: Couldn't create the primary connection [Attempt #10]
Mon Jun 11 09:06:14 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:14 2018 DEBUG: No connections found!
Mon Jun 11 09:06:14 2018 ERROR: Stopping pgAgent: Couldn't establish the primary connection with the database server.
^ permalink raw reply [nested|flat] 8+ messages in thread
* Fwd: PGAgent 4.0 error feedback
2018-06-09 20:56 PGAgent 4.0 error feedback Rob Emery <[email protected]>
2018-06-11 03:43 ` Re: PGAgent 4.0 error feedback Ashesh Vashi <[email protected]>
2018-06-11 07:20 ` Re: PGAgent 4.0 error feedback Rob Emery <[email protected]>
2018-06-11 07:28 ` Re: PGAgent 4.0 error feedback Ashesh Vashi <[email protected]>
2018-06-11 08:08 ` Re: PGAgent 4.0 error feedback Robert Emery <[email protected]>
@ 2018-06-11 08:10 ` Rob Emery <[email protected]>
1 sibling, 0 replies; 8+ messages in thread
From: Rob Emery @ 2018-06-11 08:10 UTC (permalink / raw)
To: pgadmin-hackers
Hello Again,
I've just tested the patch and the output is *much* more verbose with the same
set of flags now, even more so than the old version (see attached).
Thanks,
Rob
On 11/06/2018, Ashesh Vashi <[email protected]> wrote:
> Hi Rob,
>
>
> On Mon, Jun 11, 2018 at 12:50 PM, Rob Emery <[email protected]>
> wrote:
>
>> Hi Ashesh,
>>
>> Log-level wise I was using the same command for both versions:
>>
>> ./pgagent -f -l 2 -t 1 -r 1 'hostaddr=server user=username
>> password=password dbname=postgres'
>>
>> and messing up the connection string in various ways (missing dbname,
>> incorrect password, incorrect hostaddr)
>>
>> This was built and tested on Debian GNU/Linux 9.4 (stretch).
>>
> If you're working on the source, would please test the patch sent by me?
>
>>
>> I've attached an example of the differing output when the dbname is
>> missing
>> from the connectionstring; basically it's the same for all errors.
>>
>
> Thanks a lot for the information.
>
> -- Thanks, Ashesh
>
>>
>> Many Thanks,
>> Rob
>>
>> On 11/06/2018, Ashesh Vashi <[email protected]> wrote:
>> > Hi Rob,
>> >
>> > On Sun, Jun 10, 2018 at 2:26 AM, Rob Emery <[email protected]>
>> > wrote:
>> >
>> >> Hi Guys,
>> >>
>> >> I've been testing out PGAgent 4 (build today from master at commit
>> >> 86ca5c5ed1ad572075ba27e05e4680ebdf5b9feb) to check the connection
>> >> handling on error is still fixed with the boost reimplementation
>> >> (which it is!)
>> >> and noticed a few issues compared to PGAgent 3 around feedback to the
>> >> user if the connection string is incorrect.
>> >>
>> >> I've tested with incorrect username and password, user not in the hba,
>> >> db doesn't exist, postgresql not running on the host (or incorrect
>> >> hostaddr) and 4 seems to always returns the error :
>> >> `
>> >> ERROR: Couldn't find the function 'pgagent_schema_version' - please
>> >> run pgagent_upgrade.sql.
>> >> `
>> >>
>> >> whereas 3.4.1 tends to output from the pgconnection itself like:
>> >> `
>> >> Sat Jun 9 21:32:13 2018 : WARNING: Couldn't create the primary
>> >> connection (attempt 1): FATAL: no pg_hba.conf entry for host
>> >> "172.30.0.16", user "pgagent_login_role", database
>> >> "pgagent_login_role", SSL on
>> >> FATAL: no pg_hba.conf entry for host "172.30.0.16", user
>> >> "pgagent_login_role", database "pgagent_login_role", SSL off
>> >> `
>> >>
>> >> which at least points the user towards the actual error!
>> >>
>> >> Not sure if this is known already, but I thought I'd raise it prior to
>> >> release.
>> >>
>> > Thanks for sharing the information.
>> >
>> > Is it possible for you to share the logs with log level set to debug?
>> > Also - please share the operating system details?
>> >
>> > --
>> >
>> > Thanks & Regards,
>> >
>> > Ashesh Vashi
>> > EnterpriseDB INDIA: Enterprise PostgreSQL Company
>> > <http://www.enterprisedb.com/;
>> >
>> >
>> > *http://www.linkedin.com/in/asheshvashi*
>> > <http://www.linkedin.com/in/asheshvashi;
>> >
>> >
>> >
>> >>
>> >> Thanks,
>> >> Rob
>> >> --
>> >>
>> >> --
>> >> <https://codeweavers.net;
>> >>
>> >>
>> >> Codeweavers May Newsletter
>> >> <https://mailchi.mp/codeweavers/march-edition-336883; l Codeweavers
>> >> April
>> >> Finance Trends
>> >> <https://codeweavers.net/company-blog/codeweavers-april-finance-trends;
>> >>
>> >>
>> >> April’s Dealer Highlights
>> >> <https://codeweavers.net/company-blog/aprils-dealer-highlights;
>> >> <https://codeweavers.net/company-blog/codeweavers-
>> march-car-finance-trends
>> >> >
>> >>
>> >> _
>> >> _
>> >>
>> >>
>> >>
>> >> *Phone:* 0800 021 0888 Email: [email protected]
>> >> <mailto:[email protected]>
>> >> Codeweavers Ltd | Barn 4 | Dunston
>> >> Business Village | Dunston | ST18 9AB
>> >> Registered in England and Wales No.
>> >> 04092394 | VAT registration no. 974 9705 63
>> >>
>> >>
>> >>
>> >>
>> >> <https://www.linkedin.com/company/codeweavers-limited;
>> >> <https://vimeo.com/codeweaversltd;
>> >> <https://plus.google.com/b/105942302039373248738/+CodeweaversNet;
>> >> <https://twitter.com/CodeweaversTeam;
>> >>
>> >>
>> >>
>> >
>>
>> --
>> <https://codeweavers.net;
>>
>>
>> Codeweavers May Newsletter
>> <https://mailchi.mp/codeweavers/march-edition-336883; l Codeweavers
>> April
>> Finance Trends
>> <https://codeweavers.net/company-blog/codeweavers-april-finance-trends;
>>
>>
>> April’s Dealer Highlights
>> <https://codeweavers.net/company-blog/aprils-dealer-highlights;
>> <https://codeweavers.net/company-blog/codeweavers-march-car-finance-trends
>> >
>>
>> _
>> _
>>
>>
>>
>> *Phone:* 0800 021 0888 Email: [email protected]
>> <mailto:[email protected]>
>> Codeweavers Ltd | Barn 4 | Dunston
>> Business Village | Dunston | ST18 9AB
>> Registered in England and Wales No.
>> 04092394 | VAT registration no. 974 9705 63
>>
>>
>>
>>
>> <https://www.linkedin.com/company/codeweavers-limited;
>> <https://vimeo.com/codeweaversltd;
>> <https://plus.google.com/b/105942302039373248738/+CodeweaversNet;
>> <https://twitter.com/CodeweaversTeam;
>>
>>
>
--
Robert Emery
Infrastructure Director
E: [email protected] | T: 01785 711633 | W: www.codeweavers.net
--
Robert Emery
Infrastructure Director
E: [email protected] | T: 01785 711633 | W: www.codeweavers.net
--
<https://codeweavers.net;
Codeweavers May Newsletter
<https://mailchi.mp/codeweavers/march-edition-336883> l Codeweavers April
Finance Trends
<https://codeweavers.net/company-blog/codeweavers-april-finance-trends;
April’s Dealer Highlights
<https://codeweavers.net/company-blog/aprils-dealer-highlights;
<https://codeweavers.net/company-blog/codeweavers-march-car-finance-trends;
_
_
*Phone:* 0800 021 0888 Email: [email protected]
<mailto:[email protected]>
Codeweavers Ltd | Barn 4 | Dunston
Business Village | Dunston | ST18 9AB
Registered in England and Wales No.
04092394 | VAT registration no. 974 9705 63
<https://www.linkedin.com/company/codeweavers-limited>
<https://vimeo.com/codeweaversltd>
<https://plus.google.com/b/105942302039373248738/+CodeweaversNet>
<https://twitter.com/CodeweaversTeam;
./pgagent -f -l 2 -t 1 -r 1 'hostaddr=172.30.0.2 user=pgagent_login_role password=password'
Mon Jun 11 09:06:05 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:05 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:05 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:05 2018 DEBUG: password: *****
Mon Jun 11 09:06:05 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:05 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:05 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:05 2018 WARNING: Couldn't create the primary connection [Attempt #1]
Mon Jun 11 09:06:05 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:05 2018 DEBUG: No connections found!
Mon Jun 11 09:06:06 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:06 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:06 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:06 2018 DEBUG: password: *****
Mon Jun 11 09:06:06 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:06 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:06 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:06 2018 WARNING: Couldn't create the primary connection [Attempt #2]
Mon Jun 11 09:06:06 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:06 2018 DEBUG: No connections found!
Mon Jun 11 09:06:07 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:07 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:07 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:07 2018 DEBUG: password: *****
Mon Jun 11 09:06:07 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:07 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:07 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:07 2018 WARNING: Couldn't create the primary connection [Attempt #3]
Mon Jun 11 09:06:07 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:07 2018 DEBUG: No connections found!
Mon Jun 11 09:06:08 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:08 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:08 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:08 2018 DEBUG: password: *****
Mon Jun 11 09:06:08 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:08 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:08 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:08 2018 WARNING: Couldn't create the primary connection [Attempt #4]
Mon Jun 11 09:06:08 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:08 2018 DEBUG: No connections found!
Mon Jun 11 09:06:09 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:09 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:09 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:09 2018 DEBUG: password: *****
Mon Jun 11 09:06:09 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:09 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:09 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:09 2018 WARNING: Couldn't create the primary connection [Attempt #5]
Mon Jun 11 09:06:09 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:09 2018 DEBUG: No connections found!
Mon Jun 11 09:06:10 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:10 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:10 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:10 2018 DEBUG: password: *****
Mon Jun 11 09:06:10 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:10 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:10 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:10 2018 WARNING: Couldn't create the primary connection [Attempt #6]
Mon Jun 11 09:06:10 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:10 2018 DEBUG: No connections found!
Mon Jun 11 09:06:11 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:11 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:11 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:11 2018 DEBUG: password: *****
Mon Jun 11 09:06:11 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:11 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:11 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:11 2018 WARNING: Couldn't create the primary connection [Attempt #7]
Mon Jun 11 09:06:11 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:11 2018 DEBUG: No connections found!
Mon Jun 11 09:06:12 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:12 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:12 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:12 2018 DEBUG: password: *****
Mon Jun 11 09:06:12 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:12 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:12 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:12 2018 WARNING: Couldn't create the primary connection [Attempt #8]
Mon Jun 11 09:06:12 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:12 2018 DEBUG: No connections found!
Mon Jun 11 09:06:13 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:13 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:13 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:13 2018 DEBUG: password: *****
Mon Jun 11 09:06:13 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:13 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:13 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:13 2018 WARNING: Couldn't create the primary connection [Attempt #9]
Mon Jun 11 09:06:13 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:13 2018 DEBUG: No connections found!
Mon Jun 11 09:06:14 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:14 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:14 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:14 2018 DEBUG: password: *****
Mon Jun 11 09:06:14 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:14 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:14 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:14 2018 WARNING: Couldn't create the primary connection [Attempt #10]
Mon Jun 11 09:06:14 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:14 2018 DEBUG: No connections found!
Mon Jun 11 09:06:14 2018 ERROR: Stopping pgAgent: Couldn't establish the primary connection with the database server.
Attachments:
[text/plain] Output.txt (9.3K, 2-Output.txt)
download | inline:
./pgagent -f -l 2 -t 1 -r 1 'hostaddr=172.30.0.2 user=pgagent_login_role password=password'
Mon Jun 11 09:06:05 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:05 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:05 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:05 2018 DEBUG: password: *****
Mon Jun 11 09:06:05 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:05 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:05 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:05 2018 WARNING: Couldn't create the primary connection [Attempt #1]
Mon Jun 11 09:06:05 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:05 2018 DEBUG: No connections found!
Mon Jun 11 09:06:06 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:06 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:06 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:06 2018 DEBUG: password: *****
Mon Jun 11 09:06:06 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:06 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:06 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:06 2018 WARNING: Couldn't create the primary connection [Attempt #2]
Mon Jun 11 09:06:06 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:06 2018 DEBUG: No connections found!
Mon Jun 11 09:06:07 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:07 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:07 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:07 2018 DEBUG: password: *****
Mon Jun 11 09:06:07 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:07 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:07 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:07 2018 WARNING: Couldn't create the primary connection [Attempt #3]
Mon Jun 11 09:06:07 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:07 2018 DEBUG: No connections found!
Mon Jun 11 09:06:08 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:08 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:08 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:08 2018 DEBUG: password: *****
Mon Jun 11 09:06:08 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:08 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:08 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:08 2018 WARNING: Couldn't create the primary connection [Attempt #4]
Mon Jun 11 09:06:08 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:08 2018 DEBUG: No connections found!
Mon Jun 11 09:06:09 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:09 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:09 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:09 2018 DEBUG: password: *****
Mon Jun 11 09:06:09 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:09 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:09 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:09 2018 WARNING: Couldn't create the primary connection [Attempt #5]
Mon Jun 11 09:06:09 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:09 2018 DEBUG: No connections found!
Mon Jun 11 09:06:10 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:10 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:10 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:10 2018 DEBUG: password: *****
Mon Jun 11 09:06:10 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:10 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:10 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:10 2018 WARNING: Couldn't create the primary connection [Attempt #6]
Mon Jun 11 09:06:10 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:10 2018 DEBUG: No connections found!
Mon Jun 11 09:06:11 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:11 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:11 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:11 2018 DEBUG: password: *****
Mon Jun 11 09:06:11 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:11 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:11 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:11 2018 WARNING: Couldn't create the primary connection [Attempt #7]
Mon Jun 11 09:06:11 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:11 2018 DEBUG: No connections found!
Mon Jun 11 09:06:12 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:12 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:12 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:12 2018 DEBUG: password: *****
Mon Jun 11 09:06:12 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:12 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:12 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:12 2018 WARNING: Couldn't create the primary connection [Attempt #8]
Mon Jun 11 09:06:12 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:12 2018 DEBUG: No connections found!
Mon Jun 11 09:06:13 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:13 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:13 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:13 2018 DEBUG: password: *****
Mon Jun 11 09:06:13 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:13 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:13 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:13 2018 WARNING: Couldn't create the primary connection [Attempt #9]
Mon Jun 11 09:06:13 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:13 2018 DEBUG: No connections found!
Mon Jun 11 09:06:14 2018 DEBUG: Creating primary connection
Mon Jun 11 09:06:14 2018 DEBUG: Parsing connection information...
Mon Jun 11 09:06:14 2018 DEBUG: user: pgagent_login_role
Mon Jun 11 09:06:14 2018 DEBUG: password: *****
Mon Jun 11 09:06:14 2018 DEBUG: hostaddr: 172.30.0.2
Mon Jun 11 09:06:14 2018 DEBUG: Creating DB connection: user=pgagent_login_role password=password hostaddr=172.30.0.2 dbname=
Mon Jun 11 09:06:14 2018 WARNING: Failed to create primary connection: FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on
FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off
Mon Jun 11 09:06:14 2018 WARNING: Couldn't create the primary connection [Attempt #10]
Mon Jun 11 09:06:14 2018 DEBUG: Clearing all connections
Mon Jun 11 09:06:14 2018 DEBUG: No connections found!
Mon Jun 11 09:06:14 2018 ERROR: Stopping pgAgent: Couldn't establish the primary connection with the database server.
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: PGAgent 4.0 error feedback
2018-06-09 20:56 PGAgent 4.0 error feedback Rob Emery <[email protected]>
2018-06-11 03:43 ` Re: PGAgent 4.0 error feedback Ashesh Vashi <[email protected]>
2018-06-11 07:20 ` Re: PGAgent 4.0 error feedback Rob Emery <[email protected]>
2018-06-11 07:28 ` Re: PGAgent 4.0 error feedback Ashesh Vashi <[email protected]>
2018-06-11 08:08 ` Re: PGAgent 4.0 error feedback Robert Emery <[email protected]>
@ 2018-06-11 09:43 ` Ashesh Vashi <[email protected]>
1 sibling, 0 replies; 8+ messages in thread
From: Ashesh Vashi @ 2018-06-11 09:43 UTC (permalink / raw)
To: Robert Emery <[email protected]>; +Cc: pgadmin-hackers
On Mon, Jun 11, 2018 at 1:38 PM, Robert Emery <[email protected]>
wrote:
> Hello Again,
>
> I've just tested the patch and the output is *much* more verbose with the
> same
> set of flags now, even more so than the old version (see attached).
>
Yes.
A many systems, pgAgent service starts before the database service file on
opearting system start.
Hence - instead of quitting on first connection failure, we attempt to
connect the database server at least 10 time before quitting, and that
would give the database server to start.
-- Thanks, Ashesh
>
> Thanks,
> Rob
>
> On 11/06/2018, Ashesh Vashi <[email protected]> wrote:
> > Hi Rob,
> >
> >
> > On Mon, Jun 11, 2018 at 12:50 PM, Rob Emery <[email protected]>
> > wrote:
> >
> >> Hi Ashesh,
> >>
> >> Log-level wise I was using the same command for both versions:
> >>
> >> ./pgagent -f -l 2 -t 1 -r 1 'hostaddr=server user=username
> >> password=password dbname=postgres'
> >>
> >> and messing up the connection string in various ways (missing dbname,
> >> incorrect password, incorrect hostaddr)
> >>
> >> This was built and tested on Debian GNU/Linux 9.4 (stretch).
> >>
> > If you're working on the source, would please test the patch sent by me?
> >
> >>
> >> I've attached an example of the differing output when the dbname is
> >> missing
> >> from the connectionstring; basically it's the same for all errors.
> >>
> >
> > Thanks a lot for the information.
> >
> > -- Thanks, Ashesh
> >
> >>
> >> Many Thanks,
> >> Rob
> >>
> >> On 11/06/2018, Ashesh Vashi <[email protected]> wrote:
> >> > Hi Rob,
> >> >
> >> > On Sun, Jun 10, 2018 at 2:26 AM, Rob Emery <[email protected]>
> >> > wrote:
> >> >
> >> >> Hi Guys,
> >> >>
> >> >> I've been testing out PGAgent 4 (build today from master at commit
> >> >> 86ca5c5ed1ad572075ba27e05e4680ebdf5b9feb) to check the connection
> >> >> handling on error is still fixed with the boost reimplementation
> >> >> (which it is!)
> >> >> and noticed a few issues compared to PGAgent 3 around feedback to the
> >> >> user if the connection string is incorrect.
> >> >>
> >> >> I've tested with incorrect username and password, user not in the
> hba,
> >> >> db doesn't exist, postgresql not running on the host (or incorrect
> >> >> hostaddr) and 4 seems to always returns the error :
> >> >> `
> >> >> ERROR: Couldn't find the function 'pgagent_schema_version' - please
> >> >> run pgagent_upgrade.sql.
> >> >> `
> >> >>
> >> >> whereas 3.4.1 tends to output from the pgconnection itself like:
> >> >> `
> >> >> Sat Jun 9 21:32:13 2018 : WARNING: Couldn't create the primary
> >> >> connection (attempt 1): FATAL: no pg_hba.conf entry for host
> >> >> "172.30.0.16", user "pgagent_login_role", database
> >> >> "pgagent_login_role", SSL on
> >> >> FATAL: no pg_hba.conf entry for host "172.30.0.16", user
> >> >> "pgagent_login_role", database "pgagent_login_role", SSL off
> >> >> `
> >> >>
> >> >> which at least points the user towards the actual error!
> >> >>
> >> >> Not sure if this is known already, but I thought I'd raise it prior
> to
> >> >> release.
> >> >>
> >> > Thanks for sharing the information.
> >> >
> >> > Is it possible for you to share the logs with log level set to debug?
> >> > Also - please share the operating system details?
> >> >
> >> > --
> >> >
> >> > Thanks & Regards,
> >> >
> >> > Ashesh Vashi
> >> > EnterpriseDB INDIA: Enterprise PostgreSQL Company
> >> > <http://www.enterprisedb.com/;
> >> >
> >> >
> >> > *http://www.linkedin.com/in/asheshvashi*
> >> > <http://www.linkedin.com/in/asheshvashi;
> >> >
> >> >
> >> >
> >> >>
> >> >> Thanks,
> >> >> Rob
> >> >> --
> >> >>
> >> >> --
> >> >> <https://codeweavers.net;
> >> >>
> >> >>
> >> >> Codeweavers May Newsletter
> >> >> <https://mailchi.mp/codeweavers/march-edition-336883; l
> Codeweavers
> >> >> April
> >> >> Finance Trends
> >> >> <https://codeweavers.net/company-blog/codeweavers-
> april-finance-trends>
> >> >>
> >> >>
> >> >> April’s Dealer Highlights
> >> >> <https://codeweavers.net/company-blog/aprils-dealer-highlights;
> >> >> <https://codeweavers.net/company-blog/codeweavers-
> >> march-car-finance-trends
> >> >> >
> >> >>
> >> >> _
> >> >> _
> >> >>
> >> >>
> >> >>
> >> >> *Phone:* 0800 021 0888 Email: [email protected]
> >> >> <mailto:[email protected]>
> >> >> Codeweavers Ltd | Barn 4 | Dunston
> >> >> Business Village | Dunston | ST18 9AB
> >> >> Registered in England and Wales No.
> >> >> 04092394 | VAT registration no. 974 9705 63
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> <https://www.linkedin.com/company/codeweavers-limited;
> >> >> <https://vimeo.com/codeweaversltd;
> >> >> <https://plus.google.com/b/105942302039373248738/+CodeweaversNet;
> >> >> <https://twitter.com/CodeweaversTeam;
> >> >>
> >> >>
> >> >>
> >> >
> >>
> >> --
> >> <https://codeweavers.net;
> >>
> >>
> >> Codeweavers May Newsletter
> >> <https://mailchi.mp/codeweavers/march-edition-336883; l Codeweavers
> >> April
> >> Finance Trends
> >> <https://codeweavers.net/company-blog/codeweavers-april-finance-trends;
> >>
> >>
> >> April’s Dealer Highlights
> >> <https://codeweavers.net/company-blog/aprils-dealer-highlights;
> >> <https://codeweavers.net/company-blog/codeweavers-
> march-car-finance-trends
> >> >
> >>
> >> _
> >> _
> >>
> >>
> >>
> >> *Phone:* 0800 021 0888 Email: [email protected]
> >> <mailto:[email protected]>
> >> Codeweavers Ltd | Barn 4 | Dunston
> >> Business Village | Dunston | ST18 9AB
> >> Registered in England and Wales No.
> >> 04092394 | VAT registration no. 974 9705 63
> >>
> >>
> >>
> >>
> >> <https://www.linkedin.com/company/codeweavers-limited;
> >> <https://vimeo.com/codeweaversltd;
> >> <https://plus.google.com/b/105942302039373248738/+CodeweaversNet;
> >> <https://twitter.com/CodeweaversTeam;
> >>
> >>
> >
>
>
> --
> Robert Emery
> Infrastructure Director
>
> E: [email protected] | T: 01785 711633 | W: www.codeweavers.net
>
> --
> <https://codeweavers.net;
>
>
> Codeweavers May Newsletter
> <https://mailchi.mp/codeweavers/march-edition-336883; l Codeweavers
> April
> Finance Trends
> <https://codeweavers.net/company-blog/codeweavers-april-finance-trends;
>
>
> April’s Dealer Highlights
> <https://codeweavers.net/company-blog/aprils-dealer-highlights;
> <https://codeweavers.net/company-blog/codeweavers-march-car-finance-trends
> >
>
> _
> _
>
>
>
> *Phone:* 0800 021 0888 Email: [email protected]
> <mailto:[email protected]>
> Codeweavers Ltd | Barn 4 | Dunston
> Business Village | Dunston | ST18 9AB
> Registered in England and Wales No.
> 04092394 | VAT registration no. 974 9705 63
>
>
>
>
> <https://www.linkedin.com/company/codeweavers-limited;
> <https://vimeo.com/codeweaversltd;
> <https://plus.google.com/b/105942302039373248738/+CodeweaversNet;
> <https://twitter.com/CodeweaversTeam;
>
>
^ permalink raw reply [nested|flat] 8+ messages in thread
end of thread, other threads:[~2018-06-11 09:43 UTC | newest]
Thread overview: 8+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2018-06-09 20:56 PGAgent 4.0 error feedback Rob Emery <[email protected]>
2018-06-11 03:43 ` Ashesh Vashi <[email protected]>
2018-06-11 04:28 ` Ashesh Vashi <[email protected]>
2018-06-11 07:20 ` Rob Emery <[email protected]>
2018-06-11 07:28 ` Ashesh Vashi <[email protected]>
2018-06-11 08:08 ` Robert Emery <[email protected]>
2018-06-11 08:10 ` Rob Emery <[email protected]>
2018-06-11 09:43 ` Ashesh Vashi <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox