Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fSERf-00063n-LV for pgadmin-hackers@arkaria.postgresql.org; Mon, 11 Jun 2018 04:28:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fSERe-0007Yr-GK for pgadmin-hackers@arkaria.postgresql.org; Mon, 11 Jun 2018 04:28:42 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fSERe-0007Yg-1T for pgadmin-hackers@lists.postgresql.org; Mon, 11 Jun 2018 04:28:42 +0000 Received: from mail-oi0-x244.google.com ([2607:f8b0:4003:c06::244]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fSERa-0005dB-U2 for pgadmin-hackers@postgresql.org; Mon, 11 Jun 2018 04:28:40 +0000 Received: by mail-oi0-x244.google.com with SMTP id f79-v6so16715959oib.7 for ; Sun, 10 Jun 2018 21:28:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ZFpzXpHP8oYwYv2r4rbGgMYWnOmKflJtUF4TySsiCmE=; b=fDcX1r8BV9miX7it7Egd1adxLJxdwgxi0rg7tJ1mh7SIIKbbTVvTeAlsel1QlfdazY rEKrzBYlHadoH5jkZ+gQDYspCZn5IxUm9LUPI3B9AV+uLmYbTUGyjuLr6hkNW9jxJuii sX3JRB0PTFv9y6sd8sVMUtV8KGB5KvayHkgLF4lXQMJtsEc3+tM6rDs9vUNNMDCcp/LA ahqGmmISENPUSqxomQIFSRGcPOFTCMQuP9W+1VgoYI13Xe91LvrdCVlXQgyi3GTl9SCk rIKRUoD3dhe74a+WKFxBFJV5kUsEhROOJ8p88LvBTpEl5By7Fdc13LFYC1k2IoJulWml 4SCg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ZFpzXpHP8oYwYv2r4rbGgMYWnOmKflJtUF4TySsiCmE=; b=Etr/t7qQGrgIcfrNz6+A3YRuwr2P+rYY/04jZxsWTxME6FHBgimtaJZ5I+HGmcvtwL pLBW3F8GciEZgkzdSC8DUksfN//GV/pCJW6A2Mp6PSwKvJbHKUoYIW9KGGCTE/5D0UyU ax5dVsnSM2DbP6oWwFwS03fbcUzfJK3r+OkH2EGXw5wbj1n5HhzMPxxcj111oFgnOfvT dCPr9dRHnyMJ2z2N+WAx38Qy4377nOIvvndDZWtKyU/xlX7NtVYnDXk8B5aKQ0MpjEXK xyEnYXQr8Ia6cLk/y8pSM0NPaaxMpLEHfX9q9Gd4antOdY3niOfbe0iS8ph477VGw/2Q f3bQ== X-Gm-Message-State: APt69E3qLFLtJNfRkYFPeJnlbqfz3MFVSOieKhji97Ll0UhO9tr/7kkl 6OP8N6mSo+DRaOhKDYHTGSJtcjgM4nj/mbqaGAfH8SEN X-Google-Smtp-Source: ADUXVKIO47nkq1RsyCS8LU0pkk1sW08fc4ph+OGLtOLpRQfwI3xPq8EyE+TYGrHCjdr6LJORUdd3wupCeH53efgk/hc= X-Received: by 2002:aca:907:: with SMTP id 7-v6mr8218815oij.300.1528691318131; Sun, 10 Jun 2018 21:28:38 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac9:7a54:0:0:0:0:0 with HTTP; Sun, 10 Jun 2018 21:28:17 -0700 (PDT) In-Reply-To: References: From: Ashesh Vashi Date: Mon, 11 Jun 2018 09:58:17 +0530 Message-ID: Subject: Re: PGAgent 4.0 error feedback To: Rob Emery Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="000000000000fd2068056e562ea0" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000fd2068056e562ea0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Rob, On Mon, Jun 11, 2018 at 9:13 AM, Ashesh Vashi wrote: > Hi Rob, > > On Sun, Jun 10, 2018 at 2:26 AM, Rob Emery > 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 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.linkedin.com/in/asheshvashi * > > -- > > Thanks & Regards, > > Ashesh Vashi > EnterpriseDB INDIA: Enterprise PostgreSQL Company > > > > *http://www.linkedin.com/in/asheshvashi* > > > > >> >> Thanks, >> Rob >> -- >> >> -- >> >> >> >> Codeweavers May Newsletter >> l Codeweavers >> April >> Finance Trends >> >> >> >> April=E2=80=99s Dealer Highlights >> >> > finance-trends> >> >> _ >> _ >> >> >> >> *Phone:* 0800 021 0888 Email: contactus@codeweavers.net >> >> Codeweavers Ltd | Barn 4 | Dunston >> Business Village | Dunston | ST18 9AB >> Registered in England and Wales No. >> 04092394 | VAT registration no. 974 9705 63 >> >> >> >> >> >> >> >> >> >> >> > --000000000000fd2068056e562ea0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Rob,

On Mon, Jun 11, 2018 at 9:13 AM, Ashesh Vash= i <ashesh.vashi@enterprisedb.com> wrote:
Hi Rob,

On Sun, Jun= 10, 2018 at 2:26 AM, Rob Emery <re-pgsql@codeweavers.net> 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,<= br> 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' - pl= ease
run pgagent_upgrade.sql.
`

whereas 3.4.1 tends to output from the pgconnection itself like:
`
Sat Jun=C2=A0 9 21:32:13 2018 : WARNING: Couldn't create the primary connection (attempt 1): FATAL:=C2=A0 no pg_hba.conf entry for host
"172.30.0.16", user "pgagent_login_role", database
"pgagent_login_role", SSL on
FATAL:=C2=A0 no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SS= L 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 sh= are the operating system details?

I've sent a patch to resolve the issue=C2=A0 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:=C2=A0= Enterprise PostgreSQL Company


http://www.linkedin.com/in/asheshvashi=C2=A0=C2=A0


<= span>--

Thanks & Regards,
=
Ashesh Va= shi
EnterpriseDB INDIA:=C2=A0Enterprise Pos= tgreSQL Company


http://www.linkedin.com/in/asheshvashi


=C2=A0

Thanks,
Rob
--

--
=C2=A0<https://codeweavers.net>


Codeweavers May Newsletter
<https://mailchi.mp/codeweavers/march-edi= tion-336883>=C2=A0=C2=A0l=C2=A0 Codeweavers April
Finance Trends
<https://codeweavers.net/com= pany-blog/codeweavers-april-finance-trends>


April=E2=80=99s Dealer Highlights
<https://codeweavers.net/compan= y-blog/aprils-dealer-highlights>
<https://codeweavers.net= /company-blog/codeweavers-march-car-finance-trends>

_
_



*Phone:*=C2=A00800 021 0888=C2=A0=C2=A0=C2=A0Email:=C2=A0contactus@codeweavers.net=
<mailto:c= ontactus@codeweavers.net>
Codeweavers Ltd=C2=A0| Barn 4 | Dunston
Business Village | Dunston | ST18 9AB
Registered in England and Wales No.
04092394 | VAT registration no. 974 9705 63=C2=A0




<https://www.linkedin.com/company/codewe= avers-limited>=C2=A0=C2=A0
<https://vimeo.com/codeweaversltd>=C2=A0=C2=A0
<https://plus.google.com/b/105942302039373248738/+CodeweaversNet>=C2=A0=C2=A0
<https://twitter.com/CodeweaversTeam>




--000000000000fd2068056e562ea0--