Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
Qlik replicate service i.e.. areplicate in dead state. I am not sure why it is going to this state.
Below is the status received while checking status of service.
● areplicate.service - SYSV: Attunity Replicate service management
Loaded: loaded (/etc/rc.d/init.d/areplicate; generated)
Active: inactive (dead)
Docs: man:systemd-sysv-generator(8)
Can you please help to understand and resolve the issue.
Thanks,
Rajeshwari
Hi Rajeshwari,
I was able to reproduce this on my end, even thought the service was running.
[root@replicate2 ~]# service areplicate status
running: /opt/attunity/replicate/bin/repctl -d /opt/attunity/replicate/data service start port=3550 rest_port=3552
[root@replicate2 ~]# systemctl status areplicate
● areplicate.service - SYSV: Attunity Replicate service management
Loaded: loaded (/etc/rc.d/init.d/areplicate; generated)
Active: failed (Result: exit-code) since Tue 2023-01-10 09:15:44 CET; 1 months 19 days ago
Docs: man:systemd-sysv-generator(8)
After rebooting the linux box, everything was working as expected.
[root@replicate2 ~]# reboot now
[root@replicate2 ~]# systemctl status areplicate
● areplicate.service - SYSV: Attunity Replicate service management
Loaded: loaded (/etc/rc.d/init.d/areplicate; generated)
Active: active (running) since Wed 2023-03-01 09:26:04 CET; 28s ago
Docs: man:systemd-sysv-generator(8)
Process: 988 ExecStart=/etc/rc.d/init.d/areplicate start (code=exited, status=0/SUCCESS)
To avoid any issues, I'd encourage you to follow our public doc [1].
Therefore, in this case, you should run:
/opt/attunity/replicate/bin/areplicate status
or
service areplicate status
In both cases, I am assuming that you are running the commands as root.
I hope it helps.
Kind Regards,
Martin
Hi Rajeshwari,
I was able to reproduce this on my end, even thought the service was running.
[root@replicate2 ~]# service areplicate status
running: /opt/attunity/replicate/bin/repctl -d /opt/attunity/replicate/data service start port=3550 rest_port=3552
[root@replicate2 ~]# systemctl status areplicate
● areplicate.service - SYSV: Attunity Replicate service management
Loaded: loaded (/etc/rc.d/init.d/areplicate; generated)
Active: failed (Result: exit-code) since Tue 2023-01-10 09:15:44 CET; 1 months 19 days ago
Docs: man:systemd-sysv-generator(8)
After rebooting the linux box, everything was working as expected.
[root@replicate2 ~]# reboot now
[root@replicate2 ~]# systemctl status areplicate
● areplicate.service - SYSV: Attunity Replicate service management
Loaded: loaded (/etc/rc.d/init.d/areplicate; generated)
Active: active (running) since Wed 2023-03-01 09:26:04 CET; 28s ago
Docs: man:systemd-sysv-generator(8)
Process: 988 ExecStart=/etc/rc.d/init.d/areplicate start (code=exited, status=0/SUCCESS)
To avoid any issues, I'd encourage you to follow our public doc [1].
Therefore, in this case, you should run:
/opt/attunity/replicate/bin/areplicate status
or
service areplicate status
In both cases, I am assuming that you are running the commands as root.
I hope it helps.
Kind Regards,
Martin
I made a small mistake in my previous comment Rajeshwari,
When the service is stopped, you'll get the same output as you did.
[root@replicate2 ~]# systemctl stop areplicate
[root@replicate2 ~]# systemctl status areplicate
● areplicate.service - SYSV: Attunity Replicate service management
Loaded: loaded (/etc/rc.d/init.d/areplicate; generated)
Active: inactive (dead) since Wed 2023-03-01 09:27:41 CET; 2s ago
Docs: man:systemd-sysv-generator(8)
However, after you start the service, you should be able to see it up and running.
[root@replicate2 ~]# systemctl start areplicate
[root@replicate2 ~]# systemctl status areplicate
● areplicate.service - SYSV: Attunity Replicate service management
Loaded: loaded (/etc/rc.d/init.d/areplicate; generated)
Active: active (running) since Wed 2023-03-01 09:28:02 CET; 2s ago
Docs: man:systemd-sysv-generator(8)
Hope this clarifies your inquiry!
Kind Regards,
Martin
Hi Martin,
Thanks for your response.
I tried to start the service but no luck, Getting same inactive message.
Below are the command ran from my end (in my case have to run from "replicate" user).
325 systemctl status areplicate
326 /opt/attunity/replicate/installation/bin/repctl.sh -d /opt/attunity/replicate/data service stop
327 systemctl status areplicate
328 /opt/attunity/replicate/installation/bin/repctl.sh -d /opt/attunity/replicate/data service start port=3550 rest_port=355
329 systemctl status areplicate
330 /opt/attunity/replicate/bin/areplicate status
331 history
[replicate@replicate-QLIK-dev-2 ~]$ systemctl status areplicate
● areplicate.service - SYSV: Attunity Replicate service management
Loaded: loaded (/etc/rc.d/init.d/areplicate; generated)
Active: inactive (dead)
Docs: man:systemd-sysv-generator(8)
1.is this a new install and service can not start or exist and now having issue ?
2. what version of replicate are you running ?
3. did you try to run the service as root ?
4. check the ~\data\logs for any repcmd or repsrv log for more info.
Hey @rchinthalapalli67 ,
I agree with @Steve_Nguyen , you need to try these commands as root user rather than "in my case have to run from "replicate" user".
From the user guide:
As mentioned before, we also recommend start/stop/status with the below command rather than systemctl
/opt/attunity/replicate/bin/areplicate start
Thanks,
Kelly
@KellyHobson and @Steve_Nguyen Thanks for all your suggestions.
1. From replicate user , I try to start service using below cmd
/opt/attunity/replicate/installation/bin/repctl.sh -d /opt/attunity/replicate/data service start port=3550 rest_port=3552
-- it is working now.
Issue with my end. System configurations are disabled due to that when I used systemctl status cmd to check status of replicate service it is showing as inactive but in actual case it is running.
2. When I use root user, not worked for me. May be configurations are diffrent.