Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
Sukanya2
Contributor II
Contributor II

Services user got changed

Hello Team,

In earlier versions we used to start/view the Qlik services with ./areplicate start|stop|restart|status.

Recently we upgraded our replicate to version 2025.5.0.308 after that we are not able to use ./areplicate and we used systemctl status/stop/start.

 Is this a new update in the version 2025.5, is the older method deprecated or removed.

Can you please confirm.

Labels (2)
3 Replies
john_wang
Support
Support

Hello @Sukanya2 ,

You’re absolutely right — Replicate 2025.5 uses systemctl to start and stop services. The older startup method has been deprecated.

Regards,

John.

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!
Sukanya2
Contributor II
Contributor II
Author

Hi @john_wang 

 

In our environment we used to start services with QLIK_ADMIN user instead of ROOT user. But now systemctl is only workinh with ROOT but not QLIK_ADMIN user. Can you please comment on this

john_wang
Support
Support

Hello @Sukanya2 ,

There are several ways for a regular user (instead of "root") to run systemctl commands:

  1. Let the system automatically prompt for authentication.

  2. Use sudo systemctl directly.

In the examples below, I log in to Linux using the apac account, which is responsible for starting and stopping the Qlik Replicate services. The service itself runs under the default account attunity.

john_wang_0-1764390719503.png

Regards,

John.

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!