Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
Mika_2000
Contributor III
Contributor III

Qlik Sense hub and QMC not reachable after installing a Windows Server update

Hello everyone reading this!

Over the past few days, we've noticed something related to Qlik Sense environments. Four of our clients have reported an incident where the Qlik Sense Hub and QMC are not reachable, this is something uncommon and happens rarely. Once logged into their servers we tried the usual stuff.

  1. Restarting the Qlik Sense services.
  2. Rebuilding the Qlik Sense service certificates.
  3. Rebooted the server.
  4. Checked the firewall

Etc etc, for these four clients these fixes did not work. We went to take a look at the Event Viewer and noticed that PostgreSQL kept logging the following error.

FATAL: no pg_hba.conf entry for host <Ipv6 address of the server> iser “qliksenserepository”, database “QSMQ”, SSL off.

Mika_2000_0-1668523669898.png

 

Investigating this event on the internet we saw that we needed to change this pg_hba.conf file to accept the server’s ipv6 address which seems logical. However, this ipv6 address is already registered in this .conf file.

Looking further on our client’s server we noticed that this issue occurred after upgrading their Windows server.

Mika_2000_1-1668523685640.png

It seems that this update has triggered this issue to all four clients affected by this issue. They all installed this update, rebooted the server and tried to start Qlik Sense but their browser just says “This webpage is not avaible” also when trying to reach https://localhost:443/qmc or /hub.

We have told our clients to restore a backup from 08-11-2022 and 09-11-2022 but this did not have any affect, once we rebuild the certificates, their environments did work again.

We think this issue is triggered by the Windows update because all clients affected by this issue run on a different Qlik Sense release. Has anyone else come across this issue? How did you fix it? Is this issue known by the Qlik Team or is it just coincidence that all four clients ran across the same issue after updating their environment? We would like to hear what you think about this issue :D. Once we find out what really happened we will of course update this ticket.

If you have any questions feel free to ask me!

 

Labels (1)
3 Solutions

Accepted Solutions
jonas_brorstad
Partner - Contributor
Partner - Contributor

jonas_brorstad_0-1668669868928.png

I have solved it by adding this entry (marked in blue) in the pg_hba.conf file and restarted the services.

 

View solution in original post

Rakesh_HB
Support
Support

Hello All,

If you see the below KB Article from Microsoft, there are a few changes Microsoft had made for DNS and HNS with this Windows Patch. Please read it carefully.

 

Thank you!

Rakesh

 

Rakesh HB

View solution in original post

maxime_belanger_UQ
Contributor
Contributor

We had the same issue, on Qliksense February 2022, Windows Server 2019.

Our achitecture has 4 Qliksense nodes, with the primary node having the problem with the postgresql service not starting after the November 8, 2022—KB5019966 (OS Build 17763.3650) WIndows Patch that was installed on November 11th in our case.

Adding the ipv6 ::0/0 address in the pg_hba.conf as stated in the solution fixed the problem after restarting the server. For other people having a hard time finding the file, it is in a hidden folder by default; for us it was here:  C:\ProgramData\Qlik\Sense\Repository\PostgreSQL\12.5\pg_hba.conf  )

View solution in original post

15 Replies
Alan_Slaughter
Support
Support

Hi Mika_2000

If your IPv6 is not static and is DHCP?  I would recommend applying this article:

PostgreSQL: postgresql.conf and pg_hba.conf explained

Mika_2000
Contributor III
Contributor III
Author

We have indeed seen the article you mentioned, however to test some things we even turned off IPv6 entirely and the error still got logged. Before we turned off IPv6 we indeed checked this and the IPv6 is not static and is DHCP.

When applying the changes in this article and rebooting the server, we were not able to start the Qlik Sense services after applying this fix.

In some cases the pg_hba.conf file did not contain the right IPv6 address, it did not match the server's IPv6 address. Like mentioned above, changing this value and rebooting the server will lead to the issue that the services are unable to start, really weird.

Maria_Halley
Support
Support

@Mika_2000 

Since you mention Windows update, can you take a look at this article. The symptoms are not the same, but there have been issues with Windows updates.

https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Enterprise-on-Windows-Internal-Er...

Alan_Slaughter
Support
Support

Hi Mika_2000, could you please attach the pg_hba.conf file before you made the changes and after you made the changes?

Mika_2000
Contributor III
Contributor III
Author

Hi @Maria_Halley,

Thanks for the suggestion! We have tried to roll back the windows update using https://learn.microsoft.com/en-us/troubleshoot/windows-client/group-policy/use-group-policy-to-deplo...

We haven't yet seen the link you mentioned! Thanks for the suggestion, tomorrow we have an appointment with another client who runs into the same problem as mentioned in my original post and we will take this into account.

Mika_2000
Contributor III
Contributor III
Author

Thanks for you response @Alan_Slaughter,

Yet another customer has ran into the problem as mentioned in my original post.

Tomorrow we have an appointment with him to fix this issue, we will try to save the pg_hba.conf file to show you the contents.

jonas_brorstad
Partner - Contributor
Partner - Contributor

I have hade the same issue with 5 customers this week. Just reported this issue via the chat to the support. Hopefully it will reach RnD for a fix!

Mika_2000
Contributor III
Contributor III
Author

Hopefully they will! Just out of curiosity, how did you manage to get the hub and qmc up and running again?

jonas_brorstad
Partner - Contributor
Partner - Contributor

jonas_brorstad_0-1668669868928.png

I have solved it by adding this entry (marked in blue) in the pg_hba.conf file and restarted the services.