fedora-infrastructure

#3649 about Jan 18, m,irror syncs to our S3 buckets stopped
Closed: Fixed Opened by mdomsch.

Closed: Fixed
Reopen Issue

= bug description =
S3 buckets in us-east-1, us-west-2, maybe more, stopped receiving updates about January 18, 2013. Need to figure out why. This will prevent our users in EC2 from getting updates and other content from S3, instead pulling from other external public mirrors.

logs say:
Problem: MemoryError:
S3cmd: 1.1.0-beta3

Traceback (most recent call last):
File "/usr/bin/s3cmd", line 1927, in
main()
File "/usr/bin/s3cmd", line 1868, in main
cmd_func(args)
File "/usr/bin/s3cmd", line 1085, in cmd_sync
return cmd_sync_local2remote(args)
File "/usr/bin/s3cmd", line 950, in cmd_sync_local2remote
remote_list = fetch_remote_list(destination_base, recursive = True, require_attribs = True)
File "/usr/lib/python2.6/site-packages/S3/FileLists.py", line 317, in fetch_remote_list
remote_list[key] = objectlist[key]
MemoryError

This has been temporarily worked around by excluding /development/18/ from the list of synced directories. But that is purely a workaround that lets syncs complete today. I'll file a bug in the s3cmd bugtracker about it.
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.