ProxySG appliance FTP upload fails but test upload is successful


Article ID: 166816


Updated On:


ProxySG Software - SGOS


The ProxySG appliance can establish a successful connection with the FTP server and a test test upload works but main upload fails.


The appliance generates event log alerts for failed FTP uploads. Event log details might show events such as the following (this in an example of FTP upload used in streaming access log):

 220 Microsoft FTP Service"   
 USER bcftpupload"     
 331 Password required for bcftpupload." 
 PASS *****"  
 230 User bcftpupload logged in." 
 CWD HHCMain"   
 250 CWD command successful." 
 TYPE I"  
 200 Type set to I." 
 227 Entering Passive Mode (172,23,45,101,173,239)
 Creating data socket to"
 STOR SG_BC-Proxy1_streaming__11_20130316095932.log.gz" 
 125 Data connection already open; Transfer starting."  
 426 Connection closed; transfer aborted."   
Client received bad transfer response - 426."   
 Log uploading failed. 

In this example, FTP response code 426 means “Transient Negative Completion reply” from FTP server. A successful upload should display 226, meaning “Transfer complete”. If the status code is in 4XX format, most likely the FTP server does not have sufficient disk space to write the log file. In case of test upload, the appliance uploads a dummy file 1KB in size and shows response code 220. The original log file is larger than that.

To solve this problem, delete older log files from the directory/disk used for storing logs on the FTP server.

For information on FTP response codes, refer to