-
-
Notifications
You must be signed in to change notification settings - Fork 906
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
Problem: IndexError: list index out of range #1088
Comments
@jbrandru You have a very interesting issue. It looks like that something in the bucket_list reply is not normal in your case.
Also, it could be interesting for you to have look at the files causing the crash to see if they don't have special characters. |
We are targeting an internal Dell EMC ECS Object Storage The below output has been slightly modifyed for privacy reasons (directories/hostnames) [root@servername ~]# /bin/s3cmd -v -d -c /XXXX/.s3cfg sync /XXXX/projects/XXXX/people/XXXX/get_duration.sh s3://gm-archive/XXXX/people/XXXX/get_duration.sh
|
The file in the example is a simple shell script
|
I could be wrong, but I think that there is an issue with the EMC ECS implementation.
There is key I'm thinking if I can change the code to be able to handle such an abnormal case. But, in the meantime, is it possible for you to do the following command:
(So, same s3 path without the get_duration.sh at the end). Then, you can try to same sync operation with the same file, but to another destination "folder" on s3 that will not have a lot of files (ie < 1000). This is only a supposition, but I think that there is a chance that ECS is calculating the isTruncated flag with the whole folder, before noticing that it has only to send the info for 1. |
The du command produces the same error but I am able to put the effected files in other "directories" I have also found that the put commands also produce the error though very rarely |
I just pushed to MASTER a fix to handle your case. Even if it works correctly with that, it would still be better that you report the issue to Dell EMC as their behavior is not correct, and I'm afraid that it would have a side effect any day or hide something else. |
From my limited tests this seems to have resolved the issue for us |
sync fails on random files (everytime) if I use put instead of sync it works fine but that not really usable for us
The text was updated successfully, but these errors were encountered: