On Thu, Mar 01, 2012 at 06:10:56PM -0800, Choi, Jimmy@CIO wrote: > ---> sending a packet, length=22, type=5(READ), id=65560
This is the last request with a response. > ---> sending a packet, length=22, type=5(READ), id=65561 > ---> sending a packet, length=22, type=5(READ), id=65562 > ---> sending a packet, length=22, type=5(READ), id=65563 > ---> sending a packet, length=22, type=5(READ), id=65564 > ---> sending a packet, length=22, type=5(READ), id=65565 > ---> sending a packet, length=22, type=5(READ), id=65566 > ---> sending a packet, length=22, type=5(READ), id=65567 > ---> sending a packet, length=22, type=5(READ), id=65568 > ---> sending a packet, length=22, type=5(READ), id=65569 > ---> sending a packet, length=22, type=5(READ), id=65570 > ---> sending a packet, length=22, type=5(READ), id=65571 > ---> sending a packet, length=22, type=5(READ), id=65572 > ---> sending a packet, length=22, type=5(READ), id=65573 > ---> sending a packet, length=22, type=5(READ), id=65574 > <--- got a packet, length=32777, type=103(DATA), id=65559 > ---- data packet: pos=2147418112, size=32768 > ---> sending a packet, length=22, type=5(READ), id=65575 > <--- got a packet, length=32777, type=103(DATA), id=65560 > ---- data packet: pos=2147450880, size=32768 This is the last response. > ---> sending a packet, length=22, type=5(READ), id=65576 > **** Timeout - reconnecting As you see, the server does not respond anymore. 2147450880+32768 = 0x80000000, just the signed int overflow. I think it is a bug on the server, but it can also be caused by incorrectly formed requests. You can try to download a large file from annother sftp server to find the actual reason for this misbehavior. -- Alexander. _______________________________________________ lftp mailing list lftp@uniyar.ac.ru http://univ.uniyar.ac.ru/mailman/listinfo/lftp
