421 Maximum session time exceeded

[Jean-Michel]

Hello

We have problems moving files from a FTPS server to our S3 bucket
Looks like the connection get closed after 10 minutes with the above error code

From the session log below, could you please confirm that the problem is on the FTPS server and not in our Syncovery configuration or access to our S3 ?

- Syncovery and S3 buckets are in AWS Dublin
- Remote FTPS server is in Austria. The location is a major TV broadcaster and should have bandwidth.

Thanks

Jean-Michel

Code: Select all

Syncovery v10.12.2, build 183 (64-bit)

Licensed to: newxxsbridge
Running on : parsec-ops.pamstagging.xxxxxxx.io
Running as : PARSEC-OPS\Administrator  (Admin)
System Info: Microsoft Windows Server 2019 Datacenter Build 17763
Using Backup Privilege

Log for profile XXXXX Media from XXX, started at 6:29:12 PM on 5/29/2024

LEFT: ftp://ftp.xxx.at/XXXXX
RIGHT: S3://xxxxxxxxx/watchfolder/xxxxxx

Continuous Sync Run Number 12
The profile is run by the scheduler in a separate thread.


Copying Direction : Left To Right

6:29:12 PM.495 Disconnecting from server in order to reconnect. Reason: Exception in CheckConnection: not connected
6:29:12 PM.495 Reconnecting to server
OpenSSL version info: 
Scanning Folders Started At 5/29/2024 6:29:13 PM
Getting S3 Listing (splitting after 2000000 entries)
S3 Listing Downloading Time: 0.24 seconds for 1 HTTP requests
S3 Listing Processing Time : 0.00 seconds for 0 directory entries


Total System Memory at 5/29/2024 6:29:14 PM: 16128 MB, Available: 9605 MB, Memory Load: 40%

Free Space on right side:  Not checked, needed:      57 GB

Main Copying Phase Started At 5/29/2024 6:29:14 PM

Connecting with ftp.xxx.at
OpenSSL version info: 
Working with folder emulation mode for S3.
6:39:17 PM.437 IP Exception (5): ETGFTPProtocolReplyError 421 Maximum session time exceeded - closing.
 @ 0000000002C138F5, CP:CorEX5:421 Maximum session time exceeded - closing.

6:39:17 PM.437 Disconnecting from server in order to reconnect. Reason: Exception in CheckConnection: not connected
6:39:17 PM.437 Reconnecting to server
OpenSSL version info: 
Exception 421 Maximum session time exceeded - closing.
 at 0000000002C138F5.
Filename: ftp://ftp.xxx.at/XXXXXX/xxxxxxxx.mxf
Checkpoints: TGGetOrPutEX:421 Maximum session time exceeded - closing.


Errors / Access problems with 1 File:

\xxxxxxxx.mxf (421 Maximum session time exceeded - closing. at 0000000002C138F5.CP: TGGetOrPutEX:421 Maximum session time exceeded - closing.)

Main Copying Phase Ended At 5/29/2024 6:39:19 PM And Took 00:10:05


SUMMARY
------------------------------------------------------------------
Short Results: INCOMPLETE: 0 copied of 1, Errors with 1 File(s)
Operation completed at 6:39:19 PM on 5/29/2024
Total duration: 00:10:07

Errors with 1 File(s).

[tobias]

Hello,
yes, the error "421 Maximum session time exceeded" is from the FTP server. You could ask them to allow unlimited connection times.

Or you can set up the Syncovery job differently. Currently it is configured to keep the FTP connection permanently and check for new files regularly.

You may need to remove the checkmark "Use a single never-ending profile run (to keep FTP connections)" from the "Monitoring" tab sheet in the Syncovery profile.

And instead, give the profile a regular schedule to run (for example) every 10 minutes.

If you run it too frequently, you will probably get locked out of the server.

You may need to live with larger delays in the file transfers than you originally intended.