I upgraded lftp from 3.4.6 to 3.5.10 when the newer version had its ~x86 keyword removed. Subsequently I noticed on several occasions, after logging into a server which uses lftp nightly to back-up its file system to an FTP server, that the lftp process was consuming 100% CPU and had been running for tens of hours. I am currently downgrading to 3.4.6 by manually masking 3.5.10 on my servers. I don't know for sure what causes this endless loop. I'll put the lftp script I'm using in the additional information box. Reproducible: Sometimes Steps to Reproduce: 1. upload large file overnight to FTP server on the LAN 2. at some point, lftp may go into an endless loop Actual Results: lftp is using 99-100% CPU and never terminates. Expected Results: should either terminate with an error or after successfully uploading the file set net:timeout 360 set net:max-retries 5 set net:reconnect-interval-base 1 set net:reconnect-interval-max 1 set cmd:fail-exit true open -u 'redacted-username-password' redacted-server cd "/Backup/redacted-dir" put /dev/stdin -o "redacted-filename"
added 3.5.11. sorry haven't got around to testing this yet.
has it reoccured in 3.5.11? a backtrace from the running program would be useful too if it reoccurs. http://www.gentoo.org/proj/en/qa/backtraces.xml
I installed 3.5.12, yes, it is still happening. lftp runs nightly to ftp a backup to another machine, and a significant fraction of the time, it is still running the next morning and using up 100% CPU. The ebuild for the versions which don't have this problem all seem to have disappeared! I don't know how I can downgrade to a non-buggy version now.
hoping this was fixed in later version. I really did loose many months last year just doing other stuff so apologizes for the delay.
It may be fixed - I am not sure. I ended up adding a kill script to my crontab so that if lftp runs for more than a few hours it will be killed. I could disabled that and see if it's still happening, if you want. I think it must be some particular feature I am using - or the flakiness of the FTP server I am uploading to - which is triggering this. Otherwise I imagine you would have more similar bug reports. The FTP server is a "Snap" server and I definitely find it to be flaky, which is why I am using lftp. Perhaps it drops the connection in some particular way while I am uploading which sends lftp in an endless loop. I certainly don't think it should be using 100% CPU time. I suppose the best solution would be for me to build it with debugging and enable core dump or some such, but I too have been busy and haven't gotten around to that. I may have time for it at some point.
