Unable to finish the upgrade to QS Windows Enterprise Feb 2022 SR1 release

[VladKomarov]

Hello all!

I would like to check if anyone has experienced issues upgrading to the latest Feb 2022 SR1 release.

We have a client with QS Nov 2020 SR3 version installed on their server (single node).
The plan was to upgrade them to the latest release and we have picked Feb 2022 SR1 for that. Plus, we need to update PostgreSQL to the 12.5 release.
Here was the sequence of events:

The system was upgraded, uninstalled and installed again to update the PostgreSQL DB to 12.5 version.
Certificates were exported and imported back after the upgrade. No issues during the upgrade,  but after repository was restored from backup, and certificataes imported, the Qlik was not starting up.

All services were running, but QMC was not coming up.

Logs were collected and sent to support, and they have pointed out to this error:

From Windows events logs:
,{"Level":"Error","Logged":"2022-02-23T00:39:36-06:00","Source":"PostgreSQL","InstanceId":0,"Message":"The description for Event ID '0' in Source 'PostgreSQL' cannot be found. The local computer may not have the necessary registry information or message DLL files to display the message, or you may not have permission to access them. The following information is part of the event:'FATAL: password authentication failed for user \"qlogs_reader\"\nDETAIL: Password does not match for user \"qlogs_reader\".\n\tConnection matched pg_hba.conf line 82: \"host all all ::1/128 md5\"\n'","LogName":"Application","User":null}

Based on the error above, it looks like the issues is related to "Centralized Logging". As far I understand this feature is no longer present in Qlik Sense.
It was anounced that it will be removed "by the end of 2021" (https://community.qlik.com/t5/Support-Updates-Blog/Deprecation-of-Centralized-Logging-in-Qlik-Sense-...)

Since we have upgraded to Feb 2022 release, is it possible that the error we've got in the logs and the whole issue is related to the fact that we have restored a repository from the system that did have the Centralized Logging configured onto the system that is no longer supporting that functionality?

We end up re-creating all certificates from scratch and system is up and running after that. 

We need to run similar upgrade soon, so I am checking if we could avoid the certificates recreationg part the next time.

Looking forward to your comments and suggestions.

Best regards,

Vladimir 

[Sebastian_Linser · Accepted solution]

This issue you got 

\"qlogs_reader\"\nDETAIL: Password does not match for user \"qlogs_reader\".\n\tConnection matched pg_hba.conf line 82: \"host all all ::1/128 md5\"\n'","LogName":"Application","User":null}

has nothing todo with the QMC not comming up. 

In the old version of the upgrade article it mentioned the deleting of the certs and appdata.

I rewrote it a bit to get all this frictions of, please check it out again. Why the QMC is not comming up is most likley hidden in the repository, license or proxy logs.

Here the link once more:

https://community.qlik.com/t5/Knowledge/Qlik-Sense-May-2021-Upgrade-bundled-PostgreSQL-to-12-5-versi...

The error you see above is coming from reloading the monitoring apps which still point to the Qlogs database. 

To change that duplicate the monitoring apps, then edit the line

SET db_v_file_override = 0;

and set it to 

SET db_v_file_override = 1;

• 0 means auto (check qlogs first, then files)
• 1 files only
• 2 only Qlogs

Then republish the app and reload, the error in the event logs should be gone.

best regards

Sebastian