From: Casey S. <cas...@ba...> - 2017-05-11 17:08:38
|
If the "—cf-invalidate" command line option is used, and there are files to upload, s3cmd will crash with a “ TypeError: 'module' object is not callable” error. This does not happen if the flag is removed, or if there are no files to sync. This is on FreeBSD 11.0, with Python 2.7 and s3cmd 1.6.1. Log: > [atlassian@bamboo-2 /data/data/bamboo/xml-data/build-dir/S3SYN-ROESCATALOGS3-JOB1]$ /home/atlassian/s3cmd/s3cmd sync --exclude '.svn/*' -r -P /data/data/bamboo/xml-data/build-dir/S3SYN-ROESCATALOGS3-JOB1/ s3://roes-catalog-us01 -v --acl-public --cf-invalidate > INFO: Compiling list of local files... > INFO: Running stat() and reading/calculating MD5 values on 421 files, this may take some time... > INFO: Retrieving list of remote files for s3://roes-catalog-us01/ ... > INFO: Found 421 local files, 478 remote files > INFO: Verifying attributes... > INFO: Summary: 1 local files to upload, 0 files to remote copy, 58 remote files to delete > upload: '/data/data/bamboo/xml-data/build-dir/S3SYN-ROESCATALOGS3-JOB1/testing5' -> 's3://roes-catalog-us01/testing5' [1 of 1] > 0 of 0 0% in 0s 0.00 B/s done > INFO: Done. Uploaded 0 bytes in 1.0 seconds, 0.00 B/s. > > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > An unexpected error has occurred. > Please try reproducing the error using > the latest s3cmd code from the git master > branch found at: > https://github.com/s3tools/s3cmd > and have a look at the known issues list: > https://github.com/s3tools/s3cmd/wiki/Common-known-issues-and-their-solutions > If the error persists, please report the > following lines (removing any private > info as necessary) to: > s3t...@li... > > > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > > Invoked as: /home/atlassian/s3cmd/s3cmd sync --exclude .svn/* -r -P /data/data/bamboo/xml-data/build-dir/S3SYN-ROESCATALOGS3-JOB1/ s3://roes-catalog-us01 -v --acl-public --cf-invalidate > Problem: TypeError: 'module' object is not callable > S3cmd: 1.6.1 > python: 2.7.13 (default, Apr 13 2017, 01:15:23) > [GCC 4.2.1 Compatible FreeBSD Clang 3.8.0 (tags/RELEASE_380/final 262564)] > environment LANG=None > > Traceback (most recent call last): > File "/home/atlassian/s3cmd/s3cmd", line 2994, in <module> > rc = main() > File "/home/atlassian/s3cmd/s3cmd", line 2913, in main > rc = cmd_func(args) > File "/home/atlassian/s3cmd/s3cmd", line 1835, in cmd_sync > return cmd_sync_local2remote(args) > File "/home/atlassian/s3cmd/s3cmd", line 1815, in cmd_sync_local2remote > _invalidate_on_cf(destination_base_uri) > File "/home/atlassian/s3cmd/s3cmd", line 1784, in _invalidate_on_cf > results = cf.InvalidateObjects(destination_base_uri, uploaded_objects_list, default_index_file, cfg.invalidate_default_index_on_cf, cfg.invalidate_default_index_root_on_cf) > File "/home/atlassian/s3cmd/S3/CloudFront.py", line 468, in InvalidateObjects > debug("InvalidateObjects(): request_body: %s" % invalbatch) > File "/home/atlassian/s3cmd/S3/CloudFront.py", line 289, in __str__ > s3 = S3(Config()) > TypeError: 'module' object is not callable > > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > An unexpected error has occurred. > Please try reproducing the error using > the latest s3cmd code from the git master > branch found at: > https://github.com/s3tools/s3cmd > and have a look at the known issues list: > https://github.com/s3tools/s3cmd/wiki/Common-known-issues-and-their-solutions > If the error persists, please report the > above lines (removing any private > info as necessary) to: > s3t...@li... > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |