Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello everyone,
I set up a replication pipeline with PostgreSQL CDC, using a test table and a 6-hour schedule. Everything worked fine for the first three runs, during which data changes were detected and QVDs were historized. After that, the PostgreSQL log reported the following error:
Could not send data to client: Connection reset by peer
There are no complex firewalls between Qlik and PostgreSQL.
See the attached file for one Qlik log reporting the error: Termination signal intercepted
Has anyone else had the same issue?
Thanks
Marco
Hello @marcocim ,
Thanks for the update.
It appears the main issue is that the task stops after ~30 seconds during each run, likely due to a schedule that triggers the stop.
Since the client (QCDI) is paused, the PostgreSQL server returns the error:
could not send data to client: Connection reset by peer
Could you please stop or disable the schedule to check if this resolves the issue?
Alternatively, could you share with our support team how the schedule is currently defined? Seems I cannot reproduce the behavior in my labs.
thanks,
John.
Hi @john_wang ,
the schedule is set to run every hour
I stopped the schedule and re-run the pipeline manually, it seems to work on the same wal processed from august 8th at 15:00, but in the meantime Postgre produced many other wals.
Below you can see the last lines of the log of the last manual run:
Obviously Postgre data changes are not receipted by Qlik replicate CDC.
I showed schedule configuration to Qlik support, during a meeting held last Friday.
Thanks for your support
Marco