xTuple.com xTupleU Blog & News Customer Support

Login via client throws DB errors

Greetings xtuple developers.

Starting with the 5.0 client for windows I noticed that the login operation was throwing errors into the postgres log. Specifically the postgres log is reporting a syntax error. I had thought the error might have been fixed in the new 5.1.0 client but I see that it is still there. I just wanted to report it as a possible error in the qt client code. Below is a snippet of the db log that shows the error when logging in with the released 5.1.0 windows client to a postgres 9.6 database::

2020-03-16 14:32:02 CDT admin 511 172.20.0.78 - FATAL: password authentication failed for user “admin”
2020-03-16 14:32:02 CDT admin 511 172.20.0.78 - DETAIL: Password does not match for user “admin”.
Connection matched pg_hba.conf line 89: “host all admin 172.20.0.0/16 md5”
2020-03-16 14:32:02 CDT admin 511 172.20.0.78 - FATAL: password authentication failed for user “admin”
2020-03-16 14:32:02 CDT admin 511 172.20.0.78 - DETAIL: Password does not match for user “admin”.
Connection matched pg_hba.conf line 89: “host all admin 172.20.0.0/16 md5”
2020-03-16 14:32:02 CDT admin 511 172.20.0.78 - ERROR: syntax error at end of input at character 8
2020-03-16 14:32:02 CDT admin 511 172.20.0.78 - STATEMENT: LISTEN
2020-03-16 14:32:02 CDT admin 511 172.20.0.78 - ERROR: syntax error at end of input at character 8
2020-03-16 14:32:02 CDT admin 511 172.20.0.78 - STATEMENT: LISTEN
2020-03-16 14:32:02 CDT admin 511 172.20.0.78 - ERROR: syntax error at end of input at character 8
2020-03-16 14:32:02 CDT admin 511 172.20.0.78 - STATEMENT: LISTEN
2020-03-16 14:32:02 CDT admin 511 172.20.0.78 - ERROR: syntax error at end of input at character 8
2020-03-16 14:32:02 CDT admin 511 172.20.0.78 - STATEMENT: LISTEN

If I can help with any additional info just let me know. This is primarily a cosmetic error and causing no problems but it appears this behavior is not what you intended.

Just an after thought. The login from the “Xtuple Updater” version 2.5.2 does NOT produce the errors in the database log.

Thanks
Jim