Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
Its posible in Qlik Replicate in Linuxchange the folder <datafolder>\data\logs to /VAR/LOG ?
Thanks,
Hello @lguevara ,
Yes, there are several options available. The most stable approach is outlined below.
Please stop the Qlik Replicate services first (eg systemctl stop areplicate). After completing all the necessary configurations, restart the services to apply the changes (eg systemctl start areplicate).
1. Create the actual log destination directory
sudo mkdir -p /var/log/replicate
sudo chown attunity:attunity /var/log/replicate
Replace attunity:attunity with the user/group you want the service runs as.
2. Create a tmpfiles.d config file by account "attunity"
Create a custom file for your configuration (e.g. replog.conf):
vi /etc/tmpfiles.d/replog.conf
And add this line:
L /opt/attunity/replicate/data/logs - attunity attunity - /var/log/replicate
3. Remove any existing directory
This is critical — the symlink cannot be created if the directory already exists.
Backup the folder "/opt/attunity/replicate/logs" then:
rm -rf /opt/attunity/replicate/logs
4. Apply the tmpfiles rules immediately
(by account "attunity")
systemd-tmpfiles --create /etc/tmpfiles.d/replog.conf
Now /opt/attunity/replicate/logs should be a symlink to /var/log/replicate.
You can verify:
ls -l /opt/attunity/replicate/logs
It Should show: logs -> /var/log/replicate as below:
5. Enable persistence at boot
The rule in /etc/tmpfiles.d/replog.conf will be processed on every boot (or when tmpfiles is triggered). No additional action needed.
Cleanup (Undo)
If you want to undo this later:
rm /etc/tmpfiles.d/replog.conf
rm /opt/attunity/replicate/logs
(the below are optional, the folders will be created when Replicate service restart)
mkdir -p /opt/attunity/replicate/logs
chown attunity:attunity /opt/attunity/replicate/logs
Please perform thorough acceptance testing in a lower environment before implementing the changes in the production system.
Hope this helps.
John.
Hello @lguevara ,
Yes, there are several options available. The most stable approach is outlined below.
Please stop the Qlik Replicate services first (eg systemctl stop areplicate). After completing all the necessary configurations, restart the services to apply the changes (eg systemctl start areplicate).
1. Create the actual log destination directory
sudo mkdir -p /var/log/replicate
sudo chown attunity:attunity /var/log/replicate
Replace attunity:attunity with the user/group you want the service runs as.
2. Create a tmpfiles.d config file by account "attunity"
Create a custom file for your configuration (e.g. replog.conf):
vi /etc/tmpfiles.d/replog.conf
And add this line:
L /opt/attunity/replicate/data/logs - attunity attunity - /var/log/replicate
3. Remove any existing directory
This is critical — the symlink cannot be created if the directory already exists.
Backup the folder "/opt/attunity/replicate/logs" then:
rm -rf /opt/attunity/replicate/logs
4. Apply the tmpfiles rules immediately
(by account "attunity")
systemd-tmpfiles --create /etc/tmpfiles.d/replog.conf
Now /opt/attunity/replicate/logs should be a symlink to /var/log/replicate.
You can verify:
ls -l /opt/attunity/replicate/logs
It Should show: logs -> /var/log/replicate as below:
5. Enable persistence at boot
The rule in /etc/tmpfiles.d/replog.conf will be processed on every boot (or when tmpfiles is triggered). No additional action needed.
Cleanup (Undo)
If you want to undo this later:
rm /etc/tmpfiles.d/replog.conf
rm /opt/attunity/replicate/logs
(the below are optional, the folders will be created when Replicate service restart)
mkdir -p /opt/attunity/replicate/logs
chown attunity:attunity /opt/attunity/replicate/logs
Please perform thorough acceptance testing in a lower environment before implementing the changes in the production system.
Hope this helps.
John.