Comment by ~sschwarzer on ~sschwarzer/ftputil
Hi ~lfkdev, thanks for your feedback.
The feature is designed so that ftputil shouldn't send the
OPTS UTF8 ONcommand if theFEATcommand doesn't return the feature as supported (see https://git.sr.ht/~sschwarzer/ftputil/tree/main/item/ftputil/session.py#L18 ).Can you please use a command line FTP client to send the
FEATcommand to the server yourself and paste in a ticket comment what you get?
Comment by ~sschwarzer on ~sschwarzer/ftputil
Ok, thanks for the update. :-)
REPORTED RESOLVED NOT_OUR_BUG
Comment by ~sschwarzer on ~sschwarzer/ftputil
This is the python code I use to upload the cwd.
Thanks for the code! However, it looks like this code does not use FTPS. Do you also get errors with FTP, not just FTPS? If yes, does the error situation differ?
If you see the problems only with FTPS but not FTP, how do you define the FTPS session for use with ftputil?
The FileZilla server version is part of the title of this ticket.
Indeed. :-) Actually, it happened to me a bit ago that someone asked for information that was already in the subject of an email I had written. My conclusion from this: Always put important information also in the main text, not only the subject or title. :-)
I bet you will be able to reproduce this problem easily. If need be, with a Windows VM, or if that is against your principles, I could give you a temporary account on my FileZilla server.
I plan to try the script against my local test server (PureFTPd) first. If I can't reproduce the error, I'd appreciate if you could give me the FileZilla account. But please wait until I tried with my server here (after the clarification about the FTPS session).
Comment by ~sschwarzer on ~sschwarzer/ftputil
Thanks for the info!
Does it change anything if you transfer the large file first? If the transfer fails as well, is it at around the same amount of transferred data?
Can you paste a small self-contained example script here that reproduces the error if you run it (even if I can't run the script)? Please obfuscate the password and, if it's important, the host and user name. I'm especially interested in any custom setup you do in a session factory or otherwise.
Did you have a chance to test against a FileZilla server running under Linux, and if yes, do you see the error there, too?
If I want to try to reproduce the problem with a FileZilla server under Linux, is there anything I should be aware of, i.e. non-default server settings? What's the version of the FileZilla server?
That said, at the moment I don't really have an idea how I'd debug this problem, even if I could reproduce it.
Comment by ~sschwarzer on ~sschwarzer/ftputil
Regarding the "Connection reset by peer" errors you're seeing: These don't look like timeout errors, at least not on the FTP level, but rather on the socket level.
Sorry for any potential confusion. You didn't say that you suspect a timeout issue, but usually I suspect a timeout issue if smaller files can be transferred, but larger files can't be. ;-) But again, the problem you're seeing could have a totally different reason or reasons.
Comment by ~sschwarzer on ~sschwarzer/ftputil
First of all, ftputil uses ftplib under the hood. Also, as far as I remember, ftputil doesn't do anything special regarding FTPS that ftplib can't do. On the other hand, what ftputil does differently is that it doesn't use the initial FTP session for file transfers. Instead, ftputil creates dedicated FTP connections for remote files.
Regarding the "Connection reset by peer" errors you're seeing: These don't look like timeout errors, at least not on the FTP level, but rather on the socket level. That said, "Connection reset by peer" errors can have many different reasons.
The machine using ftputil to upload files is also under a high CPU load.
I think this could have an influence. Can you try the transfers with a less loaded client? What about the server? Is it also possibly overloaded?
By the way, can you please paste a stacktrace from the error into this ticket? You can use Markdown, i.e. put three backticks each above and below the stacktrace to make the stacktrace readable.
documentation added by ~sschwarzer on ~sschwarzer/ftputil
tests added by ~sschwarzer on ~sschwarzer/ftputil