-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Responses from FTP client are not properly read #3
Comments
It turns out that I had implemented this feature a while ago and my checkout on Hazel Hen was not up to date. The problem is that this check fails because the output of the While I was at it, I introduced the Python logging module and a This is the output that I have when trying to copy a large file:
The assertion fails because there is no output of
Since this broke without us changing something, I presume that somehow the FTP server or clients now does something slightly differently. I will have to figure out how that is. Perhaps it is because the connection broke? In the interactive session I can perform It seems that the wrapping of the FTP client does not properly work any more. |
The HLRS wiki for HPSS states that one can either use the For the users, nothing has changed except that the interactive mode is no longer offered. @pittlerf, could you please deploy the latest version of this to your Hazel Hen account and try whether it works as expected? It might have some minor mistakes in the path handling, so please be a bit careful. File sizes are gathered by API methods now, so the parsing of These changes also remove any guards for filenames with spaces that were in there before, filenames with spaces will now break the thing. But since we are used to brittle software, we haven't used those in the first place. I hope that this issue is then resolved and the performance is still acceptable if not unchanged. @pittlerf, please feel free to close this issue if it is resolved now. |
Hi Martin. Thanks for the update. I have actually a small problem. When I try to setup I got the following error message:
I actually tried to circumvent this by setting the old location of the pass file in the new code. Then by the copying I get the following error:
Could you help me to fix this? |
The first issue is fixed now. In Python 3 there is The second is harder. In the beginning of the traceback it says The file in question, This program here seems to be robust enough to catch such errors. I have started the same transfer in an interactive I noticed that I did not set the “class of service”, and now my script does this. With the correct class of service set, it is currently transferring the file and has not crashed. From the interactive session I see that it will take another 50 minutes for it to be transferred. The changes are already pushed, so you can pull down the latest version and try it for yourself. We will have to see how the performance is. Using the interactive |
The 660 GB file has been successfully transferred to the archive, both with an interactive |
@pittlerf has notified me that the files are not transmitted correctly using the
put
command. I now have reproduced it myself.I have a file
sWC_A2p1_Mpi270_L32T96-forward-logs-1161-1-2626.tar.gz
which is 291M of size (304938506). This got transferred to the archive with the this command:Looking at the
dir
output within an interactive FTP session shows a size of 33554432 where we would want 304938506. That only 11% of the original file. A test with a smaller file (size 7850) shows that the numbers fromls -l
on the normal file system anddir
in the FTP session are of the same units, namely bytes.The transfer of the large file was done almost instantly. I have checked a few minutes later and the file size has not been updated in the archive. Retrieving the file with
get
also gives a file which is much smaller than the original file. Therefore I conclude that the transfers get aborted at some point.The exact details of the breaking are very likely out of our control and have to be treated by the HLRS support. For our sanity it is important that the file sizes are verified after storing things into the archive. Similarly we should verify the file size after retrieving a file from the archive.
I will work on the wrapper script to make those additional checks.
The text was updated successfully, but these errors were encountered: