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.
*Phone:* 0800 021 0888 Email: contactus@codeweavers.net <mailto: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
