Skip to main content
Announcements
UPGRADE ADVISORY for Qlik Replicate 2024.5: Read More
cancel
Showing results for 
Search instead for 
Did you mean: 
Pradeep099
Contributor
Contributor

While setup Qlik getting error

Hi Team,

While setup Qlik, seeing below service failed to start. Please check below error and also see attachment for more details. Please check and help me with the solution.

 

Hi Team,

We were trying to setup Qlik,  seeing below service failed . Please check the attachment for more details. Please help me how to resolve this?

Service Name – areplicate

 

 

[/apps/attunity/replicate/bin]# systemctl status areplicate.service● areplicate.service - SYSV: Attunity Replicate service managementLoaded: loaded (/etc/rc.d/init.d/areplicate; generated)Active: failed (Result: exit-code) since Wed 2022-02-23 01:28:25 EST; 45min agoDocs: man:systemd-sysv-generator(8)Process: 228579 ExecStart=/etc/rc.d/init.d/areplicate start (code=exited, status=126)

 

Feb 23 01:28:25 ip-10-45-123-190.us.aegon.com systemd[1]: Starting SYSV: Attunity Replicate service management...Feb 23 01:28:25 ip-10-45-123-190.us.aegon.com areplicate[228579]: /etc/rc.d/init.d/areplicate: line 207: /apps/attunity/replicate/bin/arep_login.sh:>Feb 23 01:28:25 ip-10-45-123-190.us.aegon.com areplicate[228579]: Failed to start serviceFeb 23 01:28:25 ip-10-45-123-190.us.aegon.com systemd[1]: areplicate.service: Control process exited, code=exited status=126Feb 23 01:28:25 ip-10-45-123-190.us.aegon.com systemd[1]: areplicate.service: Failed with result 'exit-code'.Feb 23 01:28:25 ip-10-45-123-190.us.aegon.com systemd[1]: Failed to start SYSV: Attunity Replicate service management.

Labels (1)
2 Replies
john_wang
Support
Support

Hello @Pradeep099 ,

What's the Linux OS platform type and version? please let me know what's the operations you used to startup the Replicate Service, include the account name (is it root?), and even the command how you installed (and account name).
please obfuscate sensitive information as needed if you want to paste screen copy , or piece of logs etc.

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!
Heinvandenheuvel
Specialist III
Specialist III

@Pradeep099 Thanks for creating a fresh topic for this fresh problem.

That's good. At the same time I am extremely disappointed in your reading, communicating, and troubleshooting abilities. Let's try again to just answer some basic question and follow up on suggestions. We can only help if you put in the appropriate efforts.

From an earlier reply I made:

"Clearly indicate the server type used, the OS and its version, the Replicate version, and the most detailed error message you can find. The attached picture means little or nothing - just showing it once was there, and a partial version with failure to connect.

Since it appears to have worked before, what changed? File/(data) directory locations?File protections? Username locked? The details will be on the Replicate server, perhaps in <replicatedata>/logs/repsrv.log"