topic Re: Replicate task stops abrutly without any error in log in Qlik Replicate

Replicate task stops abrutly without any error in log

gkaur — Fri, 27 Oct 2023 11:40:33 GMT

I am running Qlik replicate version(May 2023 (2023.5.0.322)) and trying to replicate data from Postgresql to snowflake.

My replicate task stops on its own after running full load and now resuming the task, same behavior there is nothing in the log files indicating any warning or error.

No failed queries on snowflake side either. Where do i check what is wrong with this CDC capture. I have other task running perfectly on the same PG and snowflake instance.

Re: Replicate task stops abrutly without any error in log

Heinvandenheuvel — Fri, 27 Oct 2023 12:00:19 GMT

Does the process go away, or does it stop doing any visible action?

What where the last lines in the log? Did it do any useful work (target apply verbose)

How quickly after startup does it stop? Minutes? If so, start with enabling DEBUG or even VERBOSE logging for all categories to see more details on the last actions.

Finally, have you checked out the REPSRV.LOG file for 'high level' runtime information?

Hein.

Re: Replicate task stops abrutly without any error in log

Dana_Baldwin — Mon, 30 Oct 2023 18:48:10 GMT

Hi @gkaur

If you see a message in the user interface or the repsrv.log that the task "stopped abnormally" it means the process abended. Please open a support case and provide the information requested here: Collecting Replicate Process Dumps - Qlik Community - 1746840

Thanks,

Dana

Re: Replicate task stops abrutly without any error in log

brain83 — Thu, 02 Nov 2023 13:30:44 GMT

The server is installed as a client, but the device I would like to apply the task sequence on is not a client. I have tried to push out the client installation but it has not worked.

Re: Replicate task stops abrutly without any error in log

IanM — Wed, 08 Nov 2023 11:21:54 GMT

I had something very similar to this running Replicate on a Windows server VM.

Turns out the VM ran out of memory due to a monitoring process building a report.

If you are using windows, check your system logs with event viewer and look for errors about the time it happened.