Should duplicacy report "missing chunks" when the connection failed?

UX
,
#1

dublicacy is telling me in the web-ui that a scheduled check resulted in missing chunks. But when I check the logs, I find that what caused the check to fail was a connection problem.

2023-01-19 07:31:25.872 DEBUG CHUNK_CACHE Chunk 0cb3d912019848103eb98009b339d7cb6d8d437a188dc029015608d825a0fbb6 has been loaded from the snapshot cache
2023-01-19 07:31:26.013 WARN SFTP_RETRY Encountered an error (failed to send packet: EOF); retry after 1 second(s)
2023-01-19 07:31:27.128 WARN SFT_RECONNECT Failed to connect to 127.0.0.1:2022: dial tcp 127.0.0.1:2022: connect: connection refused; retrying
2023-01-19 07:31:27.129 WARN SFTP_RETRY Encountered an error (failed to send packet: EOF); retry after 2 second(s)
2023-01-19 07:31:29.130 WARN SFT_RECONNECT Failed to connect to 127.0.0.1:2022: dial tcp 127.0.0.1:2022: connect: connection refused; retrying
2023-01-19 07:31:29.130 WARN SFTP_RETRY Encountered an error (failed to send packet: EOF); retry after 4 second(s)
2023-01-19 07:31:33.131 WARN SFT_RECONNECT Failed to connect to 127.0.0.1:2022: dial tcp 127.0.0.1:2022: connect: connection refused; retrying
2023-01-19 07:31:33.131 WARN SFTP_RETRY Encountered an error (failed to send packet: EOF); retry after 8 second(s)
2023-01-19 07:31:41.138 WARN SFT_RECONNECT Failed to connect to 127.0.0.1:2022: dial tcp 127.0.0.1:2022: connect: connection refused; retrying
2023-01-19 07:31:41.138 WARN SFTP_RETRY Encountered an error (failed to send packet: EOF); retry after 16 second(s)
2023-01-19 07:31:57.141 WARN SFT_RECONNECT Failed to connect to 127.0.0.1:2022: dial tcp 127.0.0.1:2022: connect: connection refused; retrying
2023-01-19 07:31:57.141 WARN SFTP_RETRY Encountered an error (failed to send packet: EOF); retry after 32 second(s)
2023-01-19 07:32:29.147 WARN SFT_RECONNECT Failed to connect to 127.0.0.1:2022: dial tcp 127.0.0.1:2022: connect: connection refused; retrying
2023-01-19 07:32:29.147 WARN SFTP_RETRY Encountered an error (failed to send packet: EOF); retry after 64 second(s)
2023-01-19 07:33:33.185 WARN SFT_RECONNECT Failed to connect to 127.0.0.1:2022: dial tcp 127.0.0.1:2022: connect: connection refused; retrying
2023-01-19 07:33:33.186 WARN SFTP_RETRY Encountered an error (failed to send packet: EOF); retry after 128 second(s)
2023-01-19 07:35:41.250 WARN SFT_RECONNECT Failed to connect to 127.0.0.1:2022: dial tcp 127.0.0.1:2022: connect: connection refused; retrying
2023-01-19 07:35:41.259 WARN SFTP_RETRY Encountered an error (failed to send packet: EOF); retry after 1 second(s)
2023-01-19 07:35:42.265 WARN SFT_RECONNECT Failed to connect to 127.0.0.1:2022: dial tcp 127.0.0.1:2022: connect: connection refused; retrying
2023-01-19 07:35:42.268 WARN SFTP_RETRY Encountered an error (failed to send packet: EOF); retry after 2 second(s)
2023-01-19 07:35:44.269 WARN SFT_RECONNECT Failed to connect to 127.0.0.1:2022: dial tcp 127.0.0.1:2022: connect: connection refused; retrying
2023-01-19 07:35:44.269 WARN SFTP_RETRY Encountered an error (failed to send packet: EOF); retry after 4 second(s)
2023-01-19 07:35:48.270 WARN SFT_RECONNECT Failed to connect to 127.0.0.1:2022: dial tcp 127.0.0.1:2022: connect: connection refused; retrying
2023-01-19 07:35:48.270 WARN SFTP_RETRY Encountered an error (failed to send packet: EOF); retry after 8 second(s)
2023-01-19 07:35:56.271 WARN SFT_RECONNECT Failed to connect to 127.0.0.1:2022: dial tcp 127.0.0.1:2022: connect: connection refused; retrying
2023-01-19 07:35:56.271 WARN SFTP_RETRY Encountered an error (failed to send packet: EOF); retry after 16 second(s)
2023-01-19 07:36:12.272 WARN SFT_RECONNECT Failed to connect to 127.0.0.1:2022: dial tcp 127.0.0.1:2022: connect: connection refused; retrying
2023-01-19 07:36:12.272 WARN SFTP_RETRY Encountered an error (failed to send packet: EOF); retry after 32 second(s)
2023-01-19 07:36:44.273 WARN SFT_RECONNECT Failed to connect to 127.0.0.1:2022: dial tcp 127.0.0.1:2022: connect: connection refused; retrying
2023-01-19 07:36:44.273 WARN SFTP_RETRY Encountered an error (failed to send packet: EOF); retry after 64 second(s)
2023-01-19 07:37:48.273 WARN SFT_RECONNECT Failed to connect to 127.0.0.1:2022: dial tcp 127.0.0.1:2022: connect: connection refused; retrying
2023-01-19 07:37:48.273 WARN SFTP_RETRY Encountered an error (failed to send packet: EOF); retry after 128 second(s)
2023-01-19 07:39:56.273 WARN SFT_RECONNECT Failed to connect to 127.0.0.1:2022: dial tcp 127.0.0.1:2022: connect: connection refused; retrying
2023-01-19 07:39:56.274 ERROR DOWNLOAD_CHUNK Chunk d43554944e828b620436307920c026f90df14493d3e88843f32bc02b49b43c01 can't be found
Chunk d43554944e828b620436307920c026f90df14493d3e88843f32bc02b49b43c01 can't be found

Isn’t it missleading for duplicacy to announce “missing chunks” in this case?

#2

It is misleading. Network errors should be pass-through, i.e., reported as it is without adding another layer of encapsulation. Unfortunately this is not supported by the current error handling mechanism.

1 Like