Manual Start and Stop order of Qlik Sense services

[Sonja_Bauernfeind]

Manually restarting Qlik Sense services in the correct order is important to prevent errors in case of service dependencies. You can find more information about service dependencies in Services | help.qlik.com.

In a Multi-node environment, always start the central node first and stop the rim nodes first.

Content:

• Correct Start Order:
• Central node
• Rim node
• Correct Stop Order:
• Central node
• Rim node
• Sample PS Script below for stopping and starting the Qlik Sense services:
• Optional monitoring of start process:

Correct Start Order:

Central node

1. Qlik Sense Repository Database

   If PostgreSQL has been unbundled, look for postgresql-x64-X

2. Qlik Sense Service Dispatcher
3. Qlik Sense Repository Service

   Delay for up to five seconds before starting the Qlik Sense Repository Service to allow the Dispatcher time to start its microservices.

4. Qlik Sense Proxy Service, Qlik Sense Engine Service, Qlik Sense Scheduler Service, Qlik Sense Printing Service

Rim node

We are unable to provide a comprehensive start or stop order as rim nodes can have a number of different combinations of services installed. Please skip any services you do not have installed.

1. Qlik Sense Service Dispatcher
2. Qlik Sense Repository Service

   Delay for up to five seconds before starting the Qlik Sense Repository Service to allow the Dispatcher time to start its microservices.

3. Qlik Sense Proxy Service, Qlik Sense Engine Service, Qlik Sense Scheduler Service, Qlik Sense Printing Service

Correct Stop Order:

Central node

1. Qlik Sense Repository Service
   
   This is expected to terminate most services with a dependency on the Repository Service.
   
   
2. If not stopped by step one: Qlik Sense Proxy Service (QPS), Qlik Sense Engine Service (QES), Qlik Sense Scheduler Service (QSS), and Qlik Sense Printing Service (QPR) in no specific order
   
   
3. Qlik Sense Service Dispatcher (QSD)
   
   
4. Qlik Sense Repository Database (QRD)

   If PostgreSQL has been unbundled, look for postgresql-x64-X

Rim node

We are unable to provide a comprehensive start or stop order, as rim nodes can have a number of different combinations of services installed. Please skip any services you do not have installed.

1. Qlik Sense Repository Service
2. If not stopped by step one: Qlik Sense Proxy Service, Qlik Sense Engine Service, Qlik Sense Scheduler Service, Qlik Sense Printing Service
3. Qlik Sense Service Dispatcher (QSD)

Sample PS Script below for stopping and starting the Qlik Sense services:

Get-Service "Qlik*" | Where-Object {($_.Name -like "QlikSense*" -and $_.Name -notlike "QlikSenseRepositoryDatabase") -or ($_.Name -eq "QlikLoggingService")} | Stop-Service -Force 
Start-Service -Name "Qlik Sense Service Dispatcher" 
Start-Service -Name "QlikSenseServiceDispatcher" 
Start-Service "Qlik*"

 

Optional monitoring of start process:

Open the following location: C:\ProgramData\Qlik\Sense\Log\Repository\Trace
Monitor the folder after starting the Qlik Sense Repository Service (QRS). Files with appended time/date will disappear.
 

[howdash]

Question about the dependency and proper stopping order of Qlik Sense Service Dispatcher.

I noticed that when starting the services, Qlik Sense Service Dispatcher is listed as third in the list of services to start.

I would think that when stopping services, it would also be third from last to be stopped, but that's not the case. Qlik Sense Service Dispatcher is listed as the last service that should be stopped.

That implies, but I can't find anywhere that would confirm that Service Dispatcher is not dependent on Repository Database service.

@Sonja_Bauernfeind do you know if Qlik Sense Service Dispatcher is, in fact, not dependent on Qlik Sense Repository Database service?

[aathi33]

Hi @Sonja_Bauernfeind ,

I have updated my qlik postgresql from 9.6 to 14.8 manually. 
On that process my repository database service is removed,
Currently we are having the postgresql 14 service. 

What will be my start and stop order for services.

[Sonja_Bauernfeind]

Hello @aathi33 

Consider the new postgresql 14 service in place of the repository database service as noted in: Qlik Sense Repository Database (may also be called postgresql-x64-12)

I noticed this was not reflected in the stop order and have now edited the article.

All the best,
Sonja 

[aathi33]

Hi @Sonja_Bauernfeind

I appreciate your response.

After the postgresql update, I'm getting this error.
I tried to give permission to qlikrepository also but it is not working.

If I start the service of postgresql-x64-12 
I'm able to upgrade.

[Sonja_Bauernfeind]

Hello, @aathi33 I recommend you post about the issue in the appropriate forum: Deployment and Management.

Our active Support agents and your knowledgeable Qlik peers can better assist you there.

When posting, including as much detail as possible: What versions you upgraded from to, the process you used, etc.

All the best,
Sonja