Skip to content
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

Error doing multipart upload #2

Closed
lmars opened this issue Oct 9, 2014 · 2 comments · Fixed by #28
Closed

Error doing multipart upload #2

lmars opened this issue Oct 9, 2014 · 2 comments · Fixed by #28

Comments

@lmars
Copy link
Owner

lmars commented Oct 9, 2014

I am getting the following error trying to upload a large (~1GB) box:

==> virtualbox-iso: Running post-processor: vagrant-s3
==> virtualbox-iso (vagrant-s3): Preparing to upload box for 'virtualbox' provider to S3 bucket 'vagrant.lmars.net'
    virtualbox-iso (vagrant-s3): Box to upload: packer_virtualbox-iso_virtualbox.box (1060157666 bytes)
    virtualbox-iso (vagrant-s3): Fetching latest manifest
    virtualbox-iso (vagrant-s3): Generating checksum
    virtualbox-iso (vagrant-s3): Checksum is fe24c05d9aac09a1d2f81965a3c25e01519192091c6f233a3f160a0a898dae48
    virtualbox-iso (vagrant-s3): Adding virtualbox 20141008.0 box to manifest
    virtualbox-iso (vagrant-s3): Uploading box to S3: vagrant/boxes/20141008.0/packer_virtualbox-iso_virtualbox.box
    virtualbox-iso (vagrant-s3): File size > 100MB. Initiating multipart upload
Build 'virtualbox-iso' errored: 1 error(s) occurred:

* Post-processor failed: Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.
@lmars
Copy link
Owner Author

lmars commented Oct 11, 2014

The underlying error response from S3 has code RequestTimeout, so I tried making that a retriable error (i.e. here) which worked 90% of the time, but then the other 10% I got another error:

Put [URL]: http: Request.ContentLength=5242880 with Body length 5238784

AFAICS when retrying in putPart, the reader is seeked back to the start here so I'm not sure why it is getting the content length wrong in a small number of cases.

@Jalle19
Copy link
Collaborator

Jalle19 commented Jun 2, 2016

Would probably be fixed if #25 gets fixed, I had a quick look at the docs and it seems the SDK has a built-in fairly sophisticated file uploader.

Jalle19 pushed a commit to Jalle19/packer-post-processor-vagrant-s3 that referenced this issue Jun 4, 2016
Jalle19 pushed a commit to Jalle19/packer-post-processor-vagrant-s3 that referenced this issue Jun 5, 2016
Jalle19 pushed a commit to Jalle19/packer-post-processor-vagrant-s3 that referenced this issue Jun 8, 2016
@lmars lmars closed this as completed in #28 Jun 16, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants