Qlik Community

Ask a Question

Qlik Sense Deployment & Management

Discussion board where members learn more about Qlik Sense Installation, Deployment and Management.

Announcements
Qlik Highlights 2020 Giveaway! Watch, reply and have a chance to win a $200 Amazon Gift Card! Watch Video
cancel
Showing results for 
Search instead for 
Did you mean: 
Partner
Partner

enable centralized logging for sense system performance analyzer

Hi,

I am trying to use the sense system performance analyzer. It's requirement is to enabe the centralized logging. I tried reading few articles. One of the articles asks me to go to C:\Program Files\Qlik\Sense\Logging\ in QMC or centralized node

However, the logging folder does not even exist there. Is there any other way to enable centralized logging so that we can start using the sense system performance analyzer

 

Regards

12 Replies
Partner
Partner

Goodmorning @AarizShah ,

are you following this kb article? https://support.qlik.com/articles/000059077
The mentioned folder C:\Program Files\Qlik\Sense is the default folder for installing QS. If you have installed QS in a different folder you should check for <Disk>:\<QS installation folder>\Logging.

I hope this helps,
Riccardo

Partner
Partner

Hi @rzenere ,

Many thanks for the reply. You were right. It was at another location. However, when I try to execute the command

 Qlik.Logging.Service.exe validate, I get an error Failed to Validate logging database

Do you have any suggestions on how to fix this?

Regards

Aariz

Partner
Partner

Hm, could you check another could of things?

  1. did you run the command from an elevated prompt (so with Administrator rights)?
  2. is the Qlik Sense Logging Service running? Usually I set it to 'Manual' run when I don't have the centralized logging configured

Riccardo

Partner
Partner

You are actually right. The service was stopped and set to manual. However, it is not starting. Windows event log viewer shows this error

The description for Event ID 0 from source PostgreSQL cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

FATAL: password authentication failed for user "senselog_writer"
DETAIL: Role "qlogs_writer" does not exist.
Connection matched pg_hba.conf line 82: "host all all ::1/128 md5"

Partner
Partner

Where can I set this user role, password etc? The user that starts the service is a different one than mentioned here
Partner
Partner

I'm not sure why it is reported 'senselog_writer'. 'qlogs_writer' is a user that exists only in the repository, just like 'postgres' or 'qliksenserepository'.
Did you change anything in the file C:\ProgramData\Qlik\Sense\Log\QlikCentralizedLogging.config ?
Also, on which version of QS are you working?
Partner
Partner

I only changed one entry in the QlikCentralizedLogging to enable CentralizedLoggingLogEnabled
Partner
Partner

Ok... So I'm still not sure why you get that 'qsenselog_writer'. Could you check the file C:\ProgramData\Qlik\Sense\Log\QlikCentralizedLogging.config and look if, for some reasons, it is mentioned qsenselog_writer?
Also, another question that I should have asked you before: in your environment has ever been configured the centralized logging? The kb article I mentioned earlier is used to enable/disable the centralized logging when you have already configured it. If during your installation you haven't selected the possibility to use it, then the QLogs database (which is the one used by this configuration) hasn't been created and neither the users. In this case, the kb article to follow should be this: https://support.qlik.com/articles/Basic/How-to-set-up-the-Qlik-Sense-Logging-Service?articleId=How-t...
Partner
Partner

Yes, it was never configured. This is the first time I have to configure it. regarding the error, I pasted a wrong event. For the logging error, the correct event error is

FATAL:  password authentication failed for user "qlogs_reader"
DETAIL:  Role "qlogs_reader" does not exist.
 Connection matched pg_hba.conf line 82: "host    all             all             ::1/128                 md5"