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

Announcements
Join us to spark ideas for how to put the latest capabilities into action. Register here!
cancel
Showing results for 
Search instead for 
Did you mean: 
lguevara
Partner - Creator II
Partner - Creator II

Qlik Replicate directories change owner attunity to root

Hi,

I identified that in the qlik replicate data folder, some files are with the root owner and for I had the error "<data directory>/logs/metrics/metricsLog.txt. Error: Permission denied", then I changd to attunity owner and works fine.
But I don't know why change owner directory, because we don't manually change this.
If any process in replicate that do that?

lguevara_0-1747242840372.png

Thanks

 

Labels (2)
4 Replies
Dana_Baldwin
Support
Support

Hi @lguevara 

Was the software installed as Root and the owner & group specified during the installation?

Thanks,

Dana

lguevara
Partner - Creator II
Partner - Creator II
Author

Hi @Dana_Baldwin 

Was installed as root, and the owner and group was by default attunity.

"sudo verbose=true data=/Qlik/data iport=3550 rport=3552 pass=password rpm -ivh --prefix /opt areplicate-2024.11.0-177.x86_64.rpm".

thanks

 

Dana_Baldwin
Support
Support

Hi @lguevara 

As far as I know, all the correct permissions should be in place after the install and there would be no reason for the Attunity user to change ownership of a needed file to Root - and it sounds like it would not have had permission to change the ownership to root even if it tried.

But I don't have a definitive answer on how it got that way. Maybe someone else will reply as well with more info.

Is this a new install?

Thanks,

Dana

john_wang
Support
Support

Hello @lguevara , 

In addition to @Dana_Baldwin  comments, please note the following regarding process ownership and log file owners:

If the Qlik Replicate Service is started by the root account, some of the log files will be owned by root , while others may still be owned by attunity. This inconsistency typically arises due to different startup methods being used.

There are generally two ways to start the Replicate service:

    1- ./areplicate start

    2- systemctl start areplicate

  • If command #1 is executed by the root user, then the Replicate processes will run under the root account.

  • Similarly, if sudo is used , the process owner will also be root.

To maintain consistent file ownership (e.g., all under attunity), we recommend always starting Replicate using the same method and user account—preferably with the attunity user, unless root privileges are explicitly required.

Hope this helps.

John.

 

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