Skip to main content
Announcements
See what Drew Clarke has to say about the Qlik Talend Cloud launch! READ THE BLOG
cancel
Showing results for 
Search instead for 
Did you mean: 
has35526
Contributor III
Contributor III

Qlik Logging service not running after changing the host name.

Qlik Logging service is not running. Below is the error. Any help would be appreciative. 

2023-09-06 15:17:29,874 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [INFO ] - Running as a service... 
2023-09-06 15:17:29,894 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [INFO ] - QLService::OnStart called! 
2023-09-06 15:17:30,016 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [ERROR] - DevartLogDatabase::Connect failed!
Exception:
    No such host is known

2023-09-06 15:17:30,126 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [ERROR] - Failed to retrieve settings from database QLogs. Error: ["DevartLogDatabase::Connect failed!\nException:\n\tNo such host is known\n"] 
2023-09-06 15:17:30,129 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [ERROR] - Failed to create the logging database schema. ["DevartLogDatabase::Connect failed!\nException:\n\tNo such host is known\n"] 
2023-09-06 15:17:30,129 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [ERROR] - QLService::SetupService failed to initialized required database! 
2023-09-06 15:17:30,129 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [ERROR] - QLService::OnStart failed to setup service for execution! 
2023-09-06 15:17:30,130 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [INFO ] - QLService::OnStop called! 
2023-09-06 18:30:07,485 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [INFO ] - QLService running update command 
2023-09-06 18:30:07,506 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [INFO ] - Updating host name in connection settings. 
2023-09-06 18:30:07,530 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [INFO ] - Successfully updated the connection settings. 
2023-09-06 18:33:05,024 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [INFO ] - QLService running update command 
2023-09-06 18:33:05,044 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [INFO ] - Updating host name in connection settings. 
2023-09-06 18:33:05,067 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [INFO ] - Successfully updated the connection settings. 
2023-09-06 18:33:52,068 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [INFO ] - Running as a service... 
2023-09-06 18:33:52,085 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [INFO ] - QLService::OnStart called! 
2023-09-06 18:33:52,234 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [ERROR] - DevartLogDatabase::Connect failed!
Exception:
    no pg_hba.conf entry for host " ", user "qlogs_writer", database "QLogs", SSL off

2023-09-06 18:33:52,338 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [ERROR] - Failed to retrieve settings from database QLogs. Error: ["DevartLogDatabase::Connect failed!\nException:\n\tno pg_hba.conf entry for host \" \", user \"qlogs_writer\", database \"QLogs\", SSL off\n"] 
2023-09-06 18:33:52,341 ip-382[Qlik.Logging.Service.exe] Qlik.Logging.Service [ERROR] - Failed to create the logging database schema. ["DevartLogDatabase::Connect failed!\nException:\n\tno pg_hba.conf entry for host \" \", user \"qlogs_writer\", database \"QLogs\", SSL off\n"] 
2023-09-06 18:33:52,341 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [ERROR] - QLService::SetupService failed to initialized required database! 
2023-09-06 18:33:52,341 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [ERROR] - QLService::OnStart failed to setup service for execution! 
2023-09-06 18:33:52,342 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [INFO ] - QLService::OnStop called! 
2023-09-06 18:35:27,153 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [INFO ] - Running as a service... 
2023-09-06 18:35:27,169 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [INFO ] - QLService::OnStart called! 
2023-09-06 18:35:27,315 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [ERROR] - DevartLogDatabase::Connect failed!
Exception:
    no pg_hba.conf entry for host " ", user "qlogs_writer", database "QLogs", SSL off

2023-09-06 18:35:27,418 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [ERROR] - Failed to retrieve settings from database QLogs. Error: ["DevartLogDatabase::Connect failed!\nException:\n\tno pg_hba.conf entry for host \" \", user \"qlogs_writer\", database \"QLogs\", SSL off\n"] 
2023-09-06 18:35:27,421 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [ERROR] - Failed to create the logging database schema. ["DevartLogDatabase::Connect failed!\nException:\n\tno pg_hba.conf entry for host \" \", user \"qlogs_writer\", database \"QLogs\", SSL off\n"] 
2023-09-06 18:35:27,421 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [ERROR] - QLService::SetupService failed to initialized required database! 
2023-09-06 18:35:27,421 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [ERROR] - QLService::OnStart failed to setup service for execution! 
2023-09-06 18:35:27,422 ip-382 [Qlik.Logging.Service.exe] Qlik.Logging.Service [INFO ] - QLService::OnStop called!

 

 

Labels (2)
1 Solution

Accepted Solutions
Sebastian_Linser

https://help.qlik.com/en-US/sense-admin/May2021/Subsystems/DeployAdministerQSE/Content/Sense_DeployA...

First you want to update the service to the new databasehostname, then in the pg_hba.conf file from the database there should be an entry for the QLogs database with the user mentioned above.

 

That was your inital error which ment you didn't had a line for user qlogs_reader and writer present.

d!\nException:\n\tno pg_hba.conf entry for host \" \", user \"qlogs_writer\", database \"QLogs\", SSL off\n"] 

host all all 0.0.0.0/0 md5 

would be the line to add to allow all connections from any ipv4 regardless of user and database. You can change md5 to scram-sha-256 if you used that one for the newer installation.

 

Think also about the fact that Qlogs is obsolete and will not work with any Postgresql DB beyond version 9.6.

This means in the future you need to plan to have the system without the Qlik Logging Service. You can still have the old Qlogs database for audit purposes.

Help users find answers! Don't forget to mark a solution that worked for you! 🙂

View solution in original post

4 Replies
RafaelBarrios
Partner - Specialist
Partner - Specialist

hi @has35526 

Keep in mind that there are several steps that you must perform with some commands to execute in the windows prompt console when you make a change of this type.

https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Change-hostname-and-certificates-...

Also, I think that from what I see it is not the case, but if you have made a recent update, this service has been deprecated and the Qlogs database is no longer used

 

hope this helps,

help users find answers! Don't forget to mark a solution that worked for you & to smash the like button!  😉

has35526
Contributor III
Contributor III
Author

@RafaelBarrios thanks for your response. We restored Qlik sense in a different host. Any idea how can I go about this Failed to retrieve settings from database QLogs. Error: ["DevartLogDatabase::Connect failed!\nException:\n\tNo such host is known\n"] 

Sebastian_Linser

https://help.qlik.com/en-US/sense-admin/May2021/Subsystems/DeployAdministerQSE/Content/Sense_DeployA...

First you want to update the service to the new databasehostname, then in the pg_hba.conf file from the database there should be an entry for the QLogs database with the user mentioned above.

 

That was your inital error which ment you didn't had a line for user qlogs_reader and writer present.

d!\nException:\n\tno pg_hba.conf entry for host \" \", user \"qlogs_writer\", database \"QLogs\", SSL off\n"] 

host all all 0.0.0.0/0 md5 

would be the line to add to allow all connections from any ipv4 regardless of user and database. You can change md5 to scram-sha-256 if you used that one for the newer installation.

 

Think also about the fact that Qlogs is obsolete and will not work with any Postgresql DB beyond version 9.6.

This means in the future you need to plan to have the system without the Qlik Logging Service. You can still have the old Qlogs database for audit purposes.

Help users find answers! Don't forget to mark a solution that worked for you! 🙂
RafaelBarrios
Partner - Specialist
Partner - Specialist

Hi @has35526 

this migration process is very well documented, did you followed the necessary steps ?

https://help.qlik.com/en-US/sense-admin/May2022/Subsystems/DeployAdministerQSE/Content/Sense_DeployA...

RafaelBarrios_0-1694038198506.png

backing up all databases, certificates and shared folder ?

 

I see two possible causes here.:

a) you tried to restore your current version in a much newer one

b)  maybe you didnt backup Qlogs database and/or restore it.

 

in any case, you can try

1. Make a new clean installation (Same version you had in the original environment) and select not to start services after setup.

 

From the previous link

Restoring a Qlik Sense site to a machine with a different hostname

Follow steps from 3 to the end

 

help users find answers! Don't forget to mark a solution that worked for you & to smash the like button!  😁