non-retryable error - invalid socket for PostgreSQL

[chris_s]

Hi

We have a Task which is replicating data from a LogStream into a PostgreSQL. After a couple of Minutes or even after an hour the task fails with the following error.

00256316: 2024-04-09T13:28:57 [TARGET_LOAD ]E: Command failed to load data with exit error code 1, Command output: invalid socket [1020417] (csv_target.c:1012)

00256316: 2024-04-09T13:28:57 [TARGET_LOAD ]E: Failed to wait for previous run [1020417] (csv_target.c:1123)

00256316: 2024-04-09T13:28:57 [TARGET_LOAD ]E: Failed to start load process for file '22' [1020417] (csv_target.c:1793)

00256316: 2024-04-09T13:28:57 [TARGET_LOAD ]E: Failed to load file '22' [1020417] (csv_target.c:1892)

00256303: 2024-04-09T13:28:57 [TASK_MANAGER ]E: Table error occurred. Based on error behavior policy, task will stop. [1021705] (replicationtask.c:3166)

We expect that the underlying Infrstructure is not 100% available, but I would expect that there would be some kind of retry mechanism. 

We configured the following Error Handlers: Environmental Errors Handling Policy, Data Errors Handling Policy and Table Errors Handling Policy

Is it possible to configure a retry for this kind of error (invalid socket)

Best Regards

Christoph

[john_wang]

Hello Christoph @chris_s ,

Thanks for reaching out to Qlik Community!

We might set the error handling to attempt given number of retry or  infinite retry as below example:

However I strongly suggest to solve the "invalid socket" rather than rely on the retry as the error and retry may introduce latency issues.

There are many factors may lead the same "invalid socket" error, eg connection error, PostgreSQL server crash, firewall killed connections, server closed the connection unexpectedly, timeout occurs, or even data error etc. Please set TARGET_LOAD to Verbose, recreate the error and check the task log file to understand the root cause. Maybe you also need to decrypt the task log.

Hope this helps.

John.