- From: Tomasz Chmielewski <
>
- To:
- Cc:
- Subject: [chef] Re: Re: 403 "Forbidden" when uploading cookbooks with large files
- Date: Tue, 22 Apr 2014 02:00:08 +0100
- Domainkey-signature: a=rsa-sha1; c=nofws; d=wpkg.org; h=date:from:to:cc :subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; q=dns; s=default; b=rnU xYGrCplxQZHH2pOMQCXrmzlYA0wdWBpN4NY+OZECUl8zxCEzx85/PwX/h8B35q6p Kikwb93XA/0A+ysEu5i1Ym82gm/X7TSRt7xgiT3gzj+XuByMrQGjksiiX9LahpYE HcsB1D7UOWuim3KxcsXDwDmqrm3fQkryfsM8zjvw=
Hi,
I've followed some hints found via google, and changed this from 900
to 1800:
:/etc/chef-server#
grep -r s3_url_ttl *
chef-server-running.json: "s3_url_ttl": 1800,
Now I'm getting:
$ time knife cookbook upload --all
(...)
Uploading mmaww-staging [1.0.0] <---- the only large recipe
(...)
ERROR: Chef::Exceptions::ContentLengthMismatch: Response body length 0 does
not match HTTP Content-Length header 206.
real 28m27.768s
user 0m7.113s
sys 0m2.634s
The file I'm uploading is a static file and is unlikely to change in the
future.
--
Tomasz Chmielewski
http://wpkg.org
On Mon, 21 Apr 2014 17:46:37 -0700
Stephen Delano
<
>
wrote:
>
How long is the cookbook upload taking? The upload URLs for each file
>
are pre-signed with an expiry time, usually set at 15 mins. With that
>
large file, you may be exceeding that time.
>
>
Have you tried uploading just that cookbook?
>
>
Also, you might want to think about storing that file somewhere else.
>
It's a bad practice to store large artifacts in your cookbooks. Is
>
your cookbook in source control? What happens when that artifact
>
changes? You'll run into repo bloat pretty quickly that way.
>
>
On Monday, April 21, 2014, Tomasz Chmielewski
>
<
>
>
wrote:
>
>
> I'm unable to upload a cookbook with a large file (~160 MB):
>
>
>
> $ knife cookbook upload --all
>
>
>
> Uploading mmaww-staging [1.0.0]
>
> (...)
>
> ERROR: Failed to upload
>
> /home/tch/Desktop/chef-repo/cookbooks/mmaww-staging/files/default/mongo-db.tar.xz
>
> (95d55edf3a75d5358a424d843c3e8463) to
>
> https://chef01.sys:443/bookshelf/organization-00000000000000000000000000000000/checksum-95d55edf3a75d5358a424d843c3e8463?AWSAccessKeyId=...&Expires=1398124259&Signature=...Unk%3D:
>
> 403 "Forbidden" <?xml version="1.0"
>
> encoding="UTF-8"?><Error><Code>AccessDenied</Code><Message>Access
>
> Denied</Message><RequestId>g2gCZAATYm9va3NoZWxmQDEyNy4wLjAuMWgDYgAABXZiAAHoHmIAAf01</RequestId><HostId></HostId></Error>
>
> ERROR: You authenticated successfully to https://192.168.11.34 as
>
> tch but you are not authorized for this action
>
> Response: <?xml version="1.0"
>
> encoding="UTF-8"?><Error><Code>AccessDenied</Code><Message>Access
>
> Denied</Message><RequestId>g2gCZAATYm9va3NoZWxmQDEyNy4wLjAuMWgDYgAABXZiAAHoHmIAAf01</RequestId><HostId></HostId></Error>
>
>
>
> $ echo $?
>
> 100
>
>
>
> Any advice?
>
>
>
> # dpkg -l|grep chef
>
> ii chef-server
>
> 11.0.12-1.ubuntu.12.04 The full stack of chef-server
>
>
>
> --
>
> Tomasz Chmielewski
>
> http://wpkg.org
>
>
>
>
--
Tomasz Chmielewski
Archive powered by MHonArc 2.6.16.