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 1fSDjy-00020P-8g for pgadmin-hackers@arkaria.postgresql.org; Mon, 11 Jun 2018 03:43:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fSDjw-00079D-A9 for pgadmin-hackers@arkaria.postgresql.org; Mon, 11 Jun 2018 03:43:32 +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 1fSDjv-000793-H7 for pgadmin-hackers@lists.postgresql.org; Mon, 11 Jun 2018 03:43:32 +0000 Received: from mail-oi0-x22a.google.com ([2607:f8b0:4003:c06::22a]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fSDjn-0004dZ-IB for pgadmin-hackers@postgresql.org; Mon, 11 Jun 2018 03:43:29 +0000 Received: by mail-oi0-x22a.google.com with SMTP id t22-v6so16659598oih.6 for ; Sun, 10 Jun 2018 20:43:23 -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=/VKl1PE+acGtPyj2/tbQQR5+CICFbfPIrGsD5K39ZmQ=; b=rVxGq+rZqJ5uKZq1cHWhSdXf7IzRtdHd0qHa1Hdi4ext0RCEQuv3Nz6Bc0VX09p0u7 52GkmEQZqGNo3ocOSb2fqW1GpZtEnhcdm+/0nnA2xxS3aLB01Z6ThF16EJKHHKtVq9y/ 5kggyCl767kYY895vbMYTO8F4Fkfk4oS3w+G3WpjOefzxLL32uU7cqhbv0x88sPegqQo A2nP3EXVS7weetIvwEiAZ8tqVY21G/5h+B6rTEoNzkp+NUHTi2Pp5ycGjHF/sXxezds9 rgufmObrKuzhB87e/ZLVR6B/9GmBBUnNRd6yFHuctu4TedOG9QeNlRHMvO7kZMlj9nG1 kF+Q== 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=/VKl1PE+acGtPyj2/tbQQR5+CICFbfPIrGsD5K39ZmQ=; b=lssvzfmlnoFWWEzNbDwuGsKH942LatRQLQABSPid2Hwr5zE+3G3H66QrE5SACnhK1I hRR1NQ9e8FKUlqxqVqQvNdtqnEajshq8r1y0Vyv3WbGEIFu/b+fD7TgjbEEgKx8KlFQi elEAyP6DAujiB71gstUYZNL92VTQwNRrB4BPz3P4P7kT0rt2RaDe5lmUrDPWoEJh7Dz9 BjXk947X01SgCfd5vKsp6GlPbqhcIfWgEE3UihTrrcBr/QxDuhedbNN/GvXWFWignYeq +KAQR3v7KIalnUy/QFNXWhFY9PLD05BAUSww03qwdWIZmPbSLbbWkKz2i5sm/b2r3MiG C+8Q== X-Gm-Message-State: APt69E08cu8m735W4pmlfBRXOeF9iM7yqM3ZPYa5jBTDCQXlALw31V7O /E6DLXLAEiNfSoLwirBJpIeY+BXqOUdOhezW9x3yqx3Y X-Google-Smtp-Source: ADUXVKIGprw5QlHhKiuXBKp7DYFDrNmSwgSMcpICVo6Mj4nHTfS/nl1kvxSs0rocD5l7HYwdgHpqH6ooZ8lePFTVMbg= X-Received: by 2002:aca:c2d4:: with SMTP id s203-v6mr6553456oif.108.1528688601869; Sun, 10 Jun 2018 20:43:21 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac9:7a54:0:0:0:0:0 with HTTP; Sun, 10 Jun 2018 20:43:01 -0700 (PDT) In-Reply-To: References: From: Ashesh Vashi Date: Mon, 11 Jun 2018 09:13:01 +0530 Message-ID: Subject: Re: PGAgent 4.0 error feedback To: Rob Emery Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="000000000000165dab056e558dba" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000165dab056e558dba Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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? -- 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 > > > > > _ > _ > > > > *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 > > > > > > > > > > > --000000000000165dab056e558dba Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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 log= s with log level set to debug?
Also - please share the= operating system details?=C2=A0

--

Thanks & Re= gards,

Ashesh Vashi
EnterpriseDB INDIA:=C2=A0Enterprise PostgreSQL Company


htt= p://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>



--000000000000165dab056e558dba--