Dear Alexander!
I tested the previously reported case (concerning 3.5.13) of a connection loss
during directory upload (mirror) with 3.5.15 and still have the same trouble:
the timeout detection doesn't seem to work in certain situations. Should I
test this scenario with 3.6 also, or will the newest release act the same way?
Thanks in advance
Michael
---> TYPE I
<--- 200 Type set to I
---> MDTM 4_0_2
<--- 213 20071101083515
---> MDTM 5_1_0
<--- 213 20071101083515
---> MDTM 5_2_0
<--- 213 20071101083515
---> MDTM 5_2_2
<--- 213 20071101083515
---> MDTM 5_2_6
<--- 213 20071101083635
Mirroring directory `common.external.runtime-23.0/libs/swiftmq/4_0_2'
---> CWD /hhla/releases/Release_vc_client_2.5/common.external.runtime-23.0/libs/
swiftmq/4_0_2
<--- 250 CWD successful. "/hhla/releases/Release_vc_client_2.5/common.external.r
untime-23.0/libs/swiftmq/4_0_2" is current directory.
---> TYPE A
<--- 200 Type set to A
---> PASV
<--- 227 Entering Passive Mode (172,15,2,183,4,211)
---- Connecting data socket to (172.15.2.183) port 1235
---- Data connection established
---> LIST
<--- 150 Connection accepted
---- Got EOF on data connection
---- Closing data socket
<--- 226 Transfer OK
Mirroring directory `common.external.runtime-23.0/libs/swiftmq/5_1_0'
---> CWD /hhla/releases/Release_vc_client_2.5/common.external.runtime-23.0/libs/
swiftmq/5_1_0
<--- 250 CWD successful. "/hhla/releases/Release_vc_client_2.5/common.external.r
untime-23.0/libs/swiftmq/5_1_0" is current directory.
---> PASV
...5_1_0: Getting directory contents (0) [Waiting for response...]
BASH-Script:
/usr/bin/lftp << !FTP_TRANSFER
set ftp:list-empty-ok true
set net:timeout 10
set net:max-retries 2
set net:reconnect-interval-base 5
set net:reconnect-interval-multiplier 1
debug
open ${FTPHOST}
user ${FTPUSR} ${FTPPW}
mirror -vvv -R --delete-first -L -e --max-errors=1 -p ${sourceDir}
${targetDir}
bye
!FTP_TRANSFER
