There was an incident on friday where one of our clients changed their data source from SFTP to HTTPS.
To accomodate, we changed the destination from SFTP to HTTPS in our v2 poll, however the v2 poll didn't post messages so we converted it to sr3 (this is a whole separate issue but worth noting for context).
So we have a v3 poll now posting to a v2 sarra.
For some reason still unknown, the v2 sarra would download corrupted files from the v3 poll. The fix to prevent this data corruption was to specify debug on inside of the v2 sarra configuration.
Additional info
The v3 poll doesn't post the file size because it isn't being listed remotely.
When the sarra didn't have debug on, a lot of the downloaded files had the same reported file size which was strange.
-rw-rw-r-- 1 sarra sarra 31709548 Oct 19 19:01 GW1AM2_202410191122_051A_L1SGBTBR_2220220.h5
-rw-rw-r-- 1 sarra sarra 31709548 Oct 19 19:02 GW1AM2_202410191212_067D_L1SGBTBR_2220220.h5
-rw-rw-r-- 1 sarra sarra 31709548 Oct 19 19:05 GW1AM2_202410191709_115D_L1SGBTBR_2220220.h5
-rw-rw-r-- 1 sarra sarra 32769288 Oct 19 19:34 GW1AM2_202410181715_108A_L1SGBTBR_2220220.h5
The next step in this saga is to try to port the v2 sarra to sr3. However, I've been testing an sr3 sarra on dev and the checksums we receive are different from what is on ops with the v2 sarra.
Unfortunately the stat stuff in the transfer class isn't available on OPS yet, and would likely help for this kind of problem.
Problem
There was an incident on friday where one of our clients changed their data source from SFTP to HTTPS.
To accomodate, we changed the
destination
from SFTP to HTTPS in our v2 poll, however the v2 poll didn't post messages so we converted it to sr3 (this is a whole separate issue but worth noting for context).So we have a v3 poll now posting to a v2 sarra.
For some reason still unknown, the v2 sarra would download corrupted files from the v3 poll. The fix to prevent this data corruption was to specify
debug on
inside of the v2 sarra configuration.Additional info
The v3 poll doesn't post the file size because it isn't being listed remotely.
The sarra (with debug on) then gets the file size (somehow), notices its different from what is available remotely, and then downloads it.
When the sarra didn't have debug on, a lot of the downloaded files had the same reported file size which was strange.
The next step in this saga is to try to port the v2 sarra to sr3. However, I've been testing an sr3 sarra on dev and the checksums we receive are different from what is on ops with the v2 sarra.
Unfortunately the
stat
stuff in the transfer class isn't available on OPS yet, and would likely help for this kind of problem.