Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.Join Us
FATAL: password authentication failed for user "qlogs_reader" DETAIL: Role "qlogs_reader" does not exist. Connection matched pg_hba.conf line 80: "host all all 127.0.0.1/32 md5"
FATAL: password authentication failed for user "qlogs_writer" DETAIL: Role "qlogs_writer" does not exist. Connection matched pg_hba.conf line 80: "host all all 127.0.0.1/32 md5"After set db_v_file_override = 1 for monitoring apps, the windows event logs still has the error for "qlogs_writer
This is the known issue reported in the bug 'QLIK-85837 Centralized Logging throws Windows Errors even when disabled'. It has been fixed in June 2018 release.
This error actually the administrator can ignore as monitoring apps keep reading logging database firstly before looking at the log files. It does not matter whether logging database service is running or stopped.
To stop this error, the solution can be to rename the data connection called QLogs.
Search Qlik's Support Knowledge database or request assisted support for highly complex issues.Submit a case
Experiencing a serious issue, please contact us by phone. View phone numbers and hours by region.