FTP Timeout not honoured

Description

The WebUI setting for the FTP service has a "Timeout" value setting. This does not update "TimeoutNoTransfer" in the proftpd.conf file. This means that the FTP connection will be dropped after 300 seconds no matter what setting is chosen in the WebUI.

If you set Timeout 7200 in the GUI, the proftp will contain:

TimeoutIdle 7200
TimeoutLogin 300
TimeoutNoTransfer 300
TimeoutStalled 3600

The "TimeoutNoTransfer" still take presendence and kill the connecton with "No transfer timeout (300 seconds): closing control connection" .

It is possible to add "TimeoutNoTransfer 7200" to the Auxcilary parameters, in which case it is added to the bottom of the config file. The first entry still remains and takes precedense and the connection is still dropped.

We have a legacy backup application that goes through each target directory before uploading changed files. Since there are over a million filles this takes some time and 300 seconds is not enough, which means the system times out and aborts the backup process.

I think that the best solution is that the WebUI setting controls both "TimeoutIdle" and "TimeoutNoTransfer". An alternative solution is to add a second control in the WebUI for the "TimeoutNoTransfer" setting.

Problem/Justification

None

Impact

None

Activity

Show:

Vladimir Vinogradenko December 14, 2021 at 12:27 PM

sorry, we are reverting this for 13.0, only SCALE will include the fix

Bug Clerk December 13, 2021 at 2:50 PM

Bug Clerk December 10, 2021 at 1:43 PM

Vladimir Vinogradenko December 9, 2021 at 11:44 AM

yes, TrueNAS CORE 13.0 will include the fix

Forza December 9, 2021 at 7:33 AM

Hi. 

 

I see this problem on TrueNAS Core.  Is the proposed fix also applicable to TrueNAS Core? 

Complete

Details

Assignee

Reporter

Labels

Time remaining

0m

Components

Fix versions

Affects versions

Priority

Katalon Platform

Created October 26, 2021 at 5:42 AM
Updated July 1, 2022 at 5:52 PM
Resolved December 14, 2021 at 12:20 PM