Sandbox checksum unable to be generated


#1

I can’t seem to find anything online related to this error I am getting
when attempting to upload a new version of a cookbook. Does this trace make
sense to anyone?

INFO: Validating ruby files
INFO: Validating templates
INFO: Syntax OK
INFO: Generating Metadata
WARN: HTTP Request Returned 500 Internal Server Error: Named route
sandbox_checksum could not be generated with
{:sandbox_id=>“fb314161f0e547039636c9f64e850f02”, :checksum=>""}
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/http.rb:2097:in
error!': 500 "Internal Server Error" (Net::HTTPFatalError) from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:229:inapi_request’
from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:280:in
retriable_rest_request' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:210:inapi_request’
from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:121:in
post_rest' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/cookbook_uploader.rb:26:inupload_cookbook’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:67:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:65:ineach’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:65:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:80:inhumanize_auth_exceptions’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:53:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife.rb:127:inrun’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/application/knife.rb:118:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/bin/knife:25 from /usr/bin/knife:19:inload’
from /usr/bin/knife:19

Thanks,
Tristan


#2

Hi Tristan,

Sandboxes are the mechanism by which files for cookbooks get onto the chef
server. The files are checksummed to avoid forcing you to upload the same
file multiple times; basically, we’re optimizing for the “tweak one file,
upload, test, repeat” use case. The first step in uploading a cookbook is to
create a sandbox, indicating the checksums of the files that you want to
upload to the server. The server then checks to see which checksums it
already has and returns the list of unknown checksums and where they can be
uploaded.

This error indicates that the server is receiving a request to create a
sandbox that includes an empty string for a checksum. I’m still
investigating how this is possible. You’re using knife from the command line
to perform this operation, right?

-chris

On Tue, Dec 7, 2010 at 9:03 AM, Tristan Sloughter <
tristan.sloughter@gmail.com> wrote:

I can’t seem to find anything online related to this error I am getting
when attempting to upload a new version of a cookbook. Does this trace make
sense to anyone?

INFO: Validating ruby files
INFO: Validating templates
INFO: Syntax OK
INFO: Generating Metadata
WARN: HTTP Request Returned 500 Internal Server Error: Named route
sandbox_checksum could not be generated with
{:sandbox_id=>“fb314161f0e547039636c9f64e850f02”, :checksum=>""}
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/http.rb:2097:in
error!': 500 "Internal Server Error" (Net::HTTPFatalError) from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:229:inapi_request’
from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:280:in
retriable_rest_request' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:210:inapi_request’
from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:121:in
post_rest' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/cookbook_uploader.rb:26:inupload_cookbook’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:67:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:65:ineach’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:65:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:80:inhumanize_auth_exceptions’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:53:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife.rb:127:inrun’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/application/knife.rb:118:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/bin/knife:25 from /usr/bin/knife:19:inload’
from /usr/bin/knife:19

Thanks,
Tristan


#3

Makes sense.

Correct, I’m using knife upload. I’ve been using it this way for weeks.

Thanks,
Tristan

On Tue, Dec 7, 2010 at 11:48 AM, Chris Walters cw@opscode.com wrote:

Hi Tristan,

Sandboxes are the mechanism by which files for cookbooks get onto the chef
server. The files are checksummed to avoid forcing you to upload the same
file multiple times; basically, we’re optimizing for the “tweak one file,
upload, test, repeat” use case. The first step in uploading a cookbook is to
create a sandbox, indicating the checksums of the files that you want to
upload to the server. The server then checks to see which checksums it
already has and returns the list of unknown checksums and where they can be
uploaded.

This error indicates that the server is receiving a request to create a
sandbox that includes an empty string for a checksum. I’m still
investigating how this is possible. You’re using knife from the command line
to perform this operation, right?

-chris

On Tue, Dec 7, 2010 at 9:03 AM, Tristan Sloughter <
tristan.sloughter@gmail.com> wrote:

I can’t seem to find anything online related to this error I am getting
when attempting to upload a new version of a cookbook. Does this trace make
sense to anyone?

INFO: Validating ruby files
INFO: Validating templates
INFO: Syntax OK
INFO: Generating Metadata
WARN: HTTP Request Returned 500 Internal Server Error: Named route
sandbox_checksum could not be generated with
{:sandbox_id=>“fb314161f0e547039636c9f64e850f02”, :checksum=>""}
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/http.rb:2097:in
error!': 500 "Internal Server Error" (Net::HTTPFatalError) from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:229:inapi_request’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:280:in
retriable_rest_request' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:210:inapi_request’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:121:in post_rest' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/cookbook_uploader.rb:26:inupload_cookbook’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:67:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:65:ineach’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:65:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:80:inhumanize_auth_exceptions’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:53:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife.rb:127:inrun’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/application/knife.rb:118:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/bin/knife:25 from /usr/bin/knife:19:inload’
from /usr/bin/knife:19

Thanks,
Tristan


#4

It it happening consistently on a particular cookbook? If so, are you
willing to send me a tarball so I can try it myself?

Thanks,
Chris

On Tue, Dec 7, 2010 at 9:52 AM, Tristan Sloughter <
tristan.sloughter@gmail.com> wrote:

Makes sense.

Correct, I’m using knife upload. I’ve been using it this way for weeks.

Thanks,
Tristan

On Tue, Dec 7, 2010 at 11:48 AM, Chris Walters cw@opscode.com wrote:

Hi Tristan,

Sandboxes are the mechanism by which files for cookbooks get onto the chef
server. The files are checksummed to avoid forcing you to upload the same
file multiple times; basically, we’re optimizing for the “tweak one file,
upload, test, repeat” use case. The first step in uploading a cookbook is to
create a sandbox, indicating the checksums of the files that you want to
upload to the server. The server then checks to see which checksums it
already has and returns the list of unknown checksums and where they can be
uploaded.

This error indicates that the server is receiving a request to create a
sandbox that includes an empty string for a checksum. I’m still
investigating how this is possible. You’re using knife from the command line
to perform this operation, right?

-chris

On Tue, Dec 7, 2010 at 9:03 AM, Tristan Sloughter <
tristan.sloughter@gmail.com> wrote:

I can’t seem to find anything online related to this error I am getting
when attempting to upload a new version of a cookbook. Does this trace make
sense to anyone?

INFO: Validating ruby files
INFO: Validating templates
INFO: Syntax OK
INFO: Generating Metadata
WARN: HTTP Request Returned 500 Internal Server Error: Named route
sandbox_checksum could not be generated with
{:sandbox_id=>“fb314161f0e547039636c9f64e850f02”, :checksum=>""}
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/http.rb:2097:in
error!': 500 "Internal Server Error" (Net::HTTPFatalError) from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:229:inapi_request’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:280:in
retriable_rest_request' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:210:inapi_request’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:121:in post_rest' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/cookbook_uploader.rb:26:inupload_cookbook’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:67:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:65:ineach’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:65:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:80:inhumanize_auth_exceptions’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:53:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife.rb:127:inrun’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/application/knife.rb:118:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/bin/knife:25 from /usr/bin/knife:19:inload’
from /usr/bin/knife:19

Thanks,
Tristan


#5

Its consistent, I can not get my current changes to upload.

I’ll check if I can send out a tarball to you.

Tristan

On Tue, Dec 7, 2010 at 11:56 AM, Chris Walters cw@opscode.com wrote:

It it happening consistently on a particular cookbook? If so, are you
willing to send me a tarball so I can try it myself?

Thanks,
Chris

On Tue, Dec 7, 2010 at 9:52 AM, Tristan Sloughter <
tristan.sloughter@gmail.com> wrote:

Makes sense.

Correct, I’m using knife upload. I’ve been using it this way for weeks.

Thanks,
Tristan

On Tue, Dec 7, 2010 at 11:48 AM, Chris Walters cw@opscode.com wrote:

Hi Tristan,

Sandboxes are the mechanism by which files for cookbooks get onto the
chef server. The files are checksummed to avoid forcing you to upload the
same file multiple times; basically, we’re optimizing for the “tweak one
file, upload, test, repeat” use case. The first step in uploading a cookbook
is to create a sandbox, indicating the checksums of the files that you want
to upload to the server. The server then checks to see which checksums it
already has and returns the list of unknown checksums and where they can be
uploaded.

This error indicates that the server is receiving a request to create a
sandbox that includes an empty string for a checksum. I’m still
investigating how this is possible. You’re using knife from the command line
to perform this operation, right?

-chris

On Tue, Dec 7, 2010 at 9:03 AM, Tristan Sloughter <
tristan.sloughter@gmail.com> wrote:

I can’t seem to find anything online related to this error I am getting
when attempting to upload a new version of a cookbook. Does this trace make
sense to anyone?

INFO: Validating ruby files
INFO: Validating templates
INFO: Syntax OK
INFO: Generating Metadata
WARN: HTTP Request Returned 500 Internal Server Error: Named route
sandbox_checksum could not be generated with
{:sandbox_id=>“fb314161f0e547039636c9f64e850f02”, :checksum=>""}
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/http.rb:2097:in
error!': 500 "Internal Server Error" (Net::HTTPFatalError) from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:229:inapi_request’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:280:in
retriable_rest_request' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:210:inapi_request’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:121:in post_rest' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/cookbook_uploader.rb:26:inupload_cookbook’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:67:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:65:ineach’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:65:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:80:inhumanize_auth_exceptions’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:53:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife.rb:127:inrun’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/application/knife.rb:118:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/bin/knife:25 from /usr/bin/knife:19:inload’
from /usr/bin/knife:19

Thanks,
Tristan


#6

So I realized I “could”, but it would have to be modified, so not sure
that’ll be good enough. And I wouldn’t want to not remove everything…

Tristan

On Tue, Dec 7, 2010 at 11:58 AM, Tristan Sloughter <
tristan.sloughter@gmail.com> wrote:

Its consistent, I can not get my current changes to upload.

I’ll check if I can send out a tarball to you.

Tristan

On Tue, Dec 7, 2010 at 11:56 AM, Chris Walters cw@opscode.com wrote:

It it happening consistently on a particular cookbook? If so, are you
willing to send me a tarball so I can try it myself?

Thanks,
Chris

On Tue, Dec 7, 2010 at 9:52 AM, Tristan Sloughter <
tristan.sloughter@gmail.com> wrote:

Makes sense.

Correct, I’m using knife upload. I’ve been using it this way for weeks.

Thanks,
Tristan

On Tue, Dec 7, 2010 at 11:48 AM, Chris Walters cw@opscode.com wrote:

Hi Tristan,

Sandboxes are the mechanism by which files for cookbooks get onto the
chef server. The files are checksummed to avoid forcing you to upload the
same file multiple times; basically, we’re optimizing for the “tweak one
file, upload, test, repeat” use case. The first step in uploading a cookbook
is to create a sandbox, indicating the checksums of the files that you want
to upload to the server. The server then checks to see which checksums it
already has and returns the list of unknown checksums and where they can be
uploaded.

This error indicates that the server is receiving a request to create a
sandbox that includes an empty string for a checksum. I’m still
investigating how this is possible. You’re using knife from the command line
to perform this operation, right?

-chris

On Tue, Dec 7, 2010 at 9:03 AM, Tristan Sloughter <
tristan.sloughter@gmail.com> wrote:

I can’t seem to find anything online related to this error I am getting
when attempting to upload a new version of a cookbook. Does this trace make
sense to anyone?

INFO: Validating ruby files
INFO: Validating templates
INFO: Syntax OK
INFO: Generating Metadata
WARN: HTTP Request Returned 500 Internal Server Error: Named route
sandbox_checksum could not be generated with
{:sandbox_id=>“fb314161f0e547039636c9f64e850f02”, :checksum=>""}
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/http.rb:2097:in
error!': 500 "Internal Server Error" (Net::HTTPFatalError) from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:229:inapi_request’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:280:in
retriable_rest_request' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:210:inapi_request’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:121:in post_rest' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/cookbook_uploader.rb:26:inupload_cookbook’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:67:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:65:ineach’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:65:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:80:inhumanize_auth_exceptions’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:53:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife.rb:127:inrun’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/application/knife.rb:118:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/bin/knife:25 from /usr/bin/knife:19:inload’
from /usr/bin/knife:19

Thanks,
Tristan


#7

Wait wait… I “fixed” it.

So I decided to ensure all changes were saved and I started closing all my
emacs buffers to make sure of that. I got to a template that hadn’t been
saved. After saving it upload worked fine… But the file did exist in its
former state on disk, and already existed in the repo.

I hope that helps explain why the checksum would be empty.

Tristan

On Tue, Dec 7, 2010 at 12:03 PM, Tristan Sloughter <
tristan.sloughter@gmail.com> wrote:

So I realized I “could”, but it would have to be modified, so not sure
that’ll be good enough. And I wouldn’t want to not remove everything…

Tristan

On Tue, Dec 7, 2010 at 11:58 AM, Tristan Sloughter <
tristan.sloughter@gmail.com> wrote:

Its consistent, I can not get my current changes to upload.

I’ll check if I can send out a tarball to you.

Tristan

On Tue, Dec 7, 2010 at 11:56 AM, Chris Walters cw@opscode.com wrote:

It it happening consistently on a particular cookbook? If so, are you
willing to send me a tarball so I can try it myself?

Thanks,
Chris

On Tue, Dec 7, 2010 at 9:52 AM, Tristan Sloughter <
tristan.sloughter@gmail.com> wrote:

Makes sense.

Correct, I’m using knife upload. I’ve been using it this way for weeks.

Thanks,
Tristan

On Tue, Dec 7, 2010 at 11:48 AM, Chris Walters cw@opscode.com wrote:

Hi Tristan,

Sandboxes are the mechanism by which files for cookbooks get onto the
chef server. The files are checksummed to avoid forcing you to upload the
same file multiple times; basically, we’re optimizing for the “tweak one
file, upload, test, repeat” use case. The first step in uploading a cookbook
is to create a sandbox, indicating the checksums of the files that you want
to upload to the server. The server then checks to see which checksums it
already has and returns the list of unknown checksums and where they can be
uploaded.

This error indicates that the server is receiving a request to create a
sandbox that includes an empty string for a checksum. I’m still
investigating how this is possible. You’re using knife from the command line
to perform this operation, right?

-chris

On Tue, Dec 7, 2010 at 9:03 AM, Tristan Sloughter <
tristan.sloughter@gmail.com> wrote:

I can’t seem to find anything online related to this error I am
getting when attempting to upload a new version of a cookbook. Does this
trace make sense to anyone?

INFO: Validating ruby files
INFO: Validating templates
INFO: Syntax OK
INFO: Generating Metadata
WARN: HTTP Request Returned 500 Internal Server Error: Named route
sandbox_checksum could not be generated with
{:sandbox_id=>“fb314161f0e547039636c9f64e850f02”, :checksum=>""}
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/http.rb:2097:in
error!': 500 "Internal Server Error" (Net::HTTPFatalError) from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:229:inapi_request’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:280:in
retriable_rest_request' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:210:inapi_request’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:121:in post_rest' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/cookbook_uploader.rb:26:inupload_cookbook’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:67:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:65:ineach’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:65:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:80:inhumanize_auth_exceptions’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:53:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife.rb:127:inrun’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/application/knife.rb:118:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/bin/knife:25 from /usr/bin/knife:19:inload’
from /usr/bin/knife:19

Thanks,
Tristan


#8

Ok, I’ll keep digging at the code. If I construct a patch to add some
logging, will you be able to apply it to your client and server?

On Tue, Dec 7, 2010 at 10:03 AM, Tristan Sloughter <
tristan.sloughter@gmail.com> wrote:

So I realized I “could”, but it would have to be modified, so not sure
that’ll be good enough. And I wouldn’t want to not remove everything…

Tristan

On Tue, Dec 7, 2010 at 11:58 AM, Tristan Sloughter <
tristan.sloughter@gmail.com> wrote:

Its consistent, I can not get my current changes to upload.

I’ll check if I can send out a tarball to you.

Tristan

On Tue, Dec 7, 2010 at 11:56 AM, Chris Walters cw@opscode.com wrote:

It it happening consistently on a particular cookbook? If so, are you
willing to send me a tarball so I can try it myself?

Thanks,
Chris

On Tue, Dec 7, 2010 at 9:52 AM, Tristan Sloughter <
tristan.sloughter@gmail.com> wrote:

Makes sense.

Correct, I’m using knife upload. I’ve been using it this way for weeks.

Thanks,
Tristan

On Tue, Dec 7, 2010 at 11:48 AM, Chris Walters cw@opscode.com wrote:

Hi Tristan,

Sandboxes are the mechanism by which files for cookbooks get onto the
chef server. The files are checksummed to avoid forcing you to upload the
same file multiple times; basically, we’re optimizing for the “tweak one
file, upload, test, repeat” use case. The first step in uploading a cookbook
is to create a sandbox, indicating the checksums of the files that you want
to upload to the server. The server then checks to see which checksums it
already has and returns the list of unknown checksums and where they can be
uploaded.

This error indicates that the server is receiving a request to create a
sandbox that includes an empty string for a checksum. I’m still
investigating how this is possible. You’re using knife from the command line
to perform this operation, right?

-chris

On Tue, Dec 7, 2010 at 9:03 AM, Tristan Sloughter <
tristan.sloughter@gmail.com> wrote:

I can’t seem to find anything online related to this error I am
getting when attempting to upload a new version of a cookbook. Does this
trace make sense to anyone?

INFO: Validating ruby files
INFO: Validating templates
INFO: Syntax OK
INFO: Generating Metadata
WARN: HTTP Request Returned 500 Internal Server Error: Named route
sandbox_checksum could not be generated with
{:sandbox_id=>“fb314161f0e547039636c9f64e850f02”, :checksum=>""}
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/http.rb:2097:in
error!': 500 "Internal Server Error" (Net::HTTPFatalError) from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:229:inapi_request’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:280:in
retriable_rest_request' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:210:inapi_request’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:121:in post_rest' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/cookbook_uploader.rb:26:inupload_cookbook’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:67:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:65:ineach’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:65:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:80:inhumanize_auth_exceptions’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:53:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife.rb:127:inrun’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/application/knife.rb:118:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/bin/knife:25 from /usr/bin/knife:19:inload’
from /usr/bin/knife:19

Thanks,
Tristan


#9

Glad to hear it’s working now. I guess the tests missed that case :slight_smile:

I’ve created http://tickets.opscode.com/browse/CHEF-1922 to track the fix.

-chris

On Tue, Dec 7, 2010 at 10:05 AM, Tristan Sloughter <
tristan.sloughter@gmail.com> wrote:

Wait wait… I “fixed” it.

So I decided to ensure all changes were saved and I started closing all my
emacs buffers to make sure of that. I got to a template that hadn’t been
saved. After saving it upload worked fine… But the file did exist in its
former state on disk, and already existed in the repo.

I hope that helps explain why the checksum would be empty.

Tristan

On Tue, Dec 7, 2010 at 12:03 PM, Tristan Sloughter <
tristan.sloughter@gmail.com> wrote:

So I realized I “could”, but it would have to be modified, so not sure
that’ll be good enough. And I wouldn’t want to not remove everything…

Tristan

On Tue, Dec 7, 2010 at 11:58 AM, Tristan Sloughter <
tristan.sloughter@gmail.com> wrote:

Its consistent, I can not get my current changes to upload.

I’ll check if I can send out a tarball to you.

Tristan

On Tue, Dec 7, 2010 at 11:56 AM, Chris Walters cw@opscode.com wrote:

It it happening consistently on a particular cookbook? If so, are you
willing to send me a tarball so I can try it myself?

Thanks,
Chris

On Tue, Dec 7, 2010 at 9:52 AM, Tristan Sloughter <
tristan.sloughter@gmail.com> wrote:

Makes sense.

Correct, I’m using knife upload. I’ve been using it this way for weeks.

Thanks,
Tristan

On Tue, Dec 7, 2010 at 11:48 AM, Chris Walters cw@opscode.com wrote:

Hi Tristan,

Sandboxes are the mechanism by which files for cookbooks get onto the
chef server. The files are checksummed to avoid forcing you to upload the
same file multiple times; basically, we’re optimizing for the “tweak one
file, upload, test, repeat” use case. The first step in uploading a cookbook
is to create a sandbox, indicating the checksums of the files that you want
to upload to the server. The server then checks to see which checksums it
already has and returns the list of unknown checksums and where they can be
uploaded.

This error indicates that the server is receiving a request to create
a sandbox that includes an empty string for a checksum. I’m still
investigating how this is possible. You’re using knife from the command line
to perform this operation, right?

-chris

On Tue, Dec 7, 2010 at 9:03 AM, Tristan Sloughter <
tristan.sloughter@gmail.com> wrote:

I can’t seem to find anything online related to this error I am
getting when attempting to upload a new version of a cookbook. Does this
trace make sense to anyone?

INFO: Validating ruby files
INFO: Validating templates
INFO: Syntax OK
INFO: Generating Metadata
WARN: HTTP Request Returned 500 Internal Server Error: Named route
sandbox_checksum could not be generated with
{:sandbox_id=>“fb314161f0e547039636c9f64e850f02”, :checksum=>""}
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/http.rb:2097:in
error!': 500 "Internal Server Error" (Net::HTTPFatalError) from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:229:inapi_request’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:280:in
retriable_rest_request' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:210:inapi_request’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:121:in post_rest' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/cookbook_uploader.rb:26:inupload_cookbook’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:67:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:65:ineach’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:65:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:80:inhumanize_auth_exceptions’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:53:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife.rb:127:inrun’
from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/application/knife.rb:118:in
run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/bin/knife:25 from /usr/bin/knife:19:inload’
from /usr/bin/knife:19

Thanks,
Tristan


#10

I’ve seen this when I have an unsaved buffer and temporary emacs files
configured to drop in the same folder e.g
#default#.rb

You can customize the temp file location.

Regards,

AJ
On 8/12/2010 8:08 AM, “Chris Walters” cw@opscode.com wrote:

Glad to hear it’s working now. I guess the tests missed that case :slight_smile:

I’ve created http://tickets.opscode.com/browse/CHEF-1922 to track the fix.

-chris

On Tue, Dec 7, 2010 at 10:05 AM, Tristan Sloughter <
tristan.sloughter@gmail.com> wrote:

Wait wait… I “fixed” it.

So I decided to ensure all changes were saved and I started closing all
my

emacs buffers to make sure of that. I got to a template that hadn’t been
saved. After saving it upload worked fine… But the file did exist in
its

former state on disk, and already existed in the repo.

I hope that helps explain why the checksum would be empty.

Tristan

On Tue, Dec 7, 2010 at 12:03 PM, Tristan Sloughter <
tristan.sloughter@gmail.com> wrote:

So I realized I “could”, but it would have to be modified, so not sure
that’ll be good enough. And I wouldn’t want to not remove everything…

Tristan

On Tue, Dec 7, 2010 at 11:58 AM, Tristan Sloughter <
tristan.sloughter@gmail.com> wrote:

Its consistent, I can not get my current changes to upload.

I’ll check if I can send out a tarball to you.

Tristan

On Tue, Dec 7, 2010 at 11:56 AM, Chris Walters cw@opscode.com wrote:

It it happening consistently on a particular cookbook? If so, are you
willing to send me a tarball so I can try it myself?

Thanks,
Chris

On Tue, Dec 7, 2010 at 9:52 AM, Tristan Sloughter <
tristan.sloughter@gmail.com> wrote:

Makes sense.

Correct, I’m using knife upload. I’ve been using it this way for
weeks.

Thanks,
Tristan

On Tue, Dec 7, 2010 at 11:48 AM, Chris Walters cw@opscode.com
wrote:

Hi Tristan,

Sandboxes are the mechanism by which files for cookbooks get onto
the

chef server. The files are checksummed to avoid forcing you to
upload the

same file multiple times; basically, we’re optimizing for the "tweak
one

file, upload, test, repeat" use case. The first step in uploading a
cookbook

is to create a sandbox, indicating the checksums of the files that
you want

to upload to the server. The server then checks to see which
checksums it

already has and returns the list of unknown checksums and where they
can be

uploaded.

This error indicates that the server is receiving a request to
create

a sandbox that includes an empty string for a checksum. I’m still
investigating how this is possible. You’re using knife from the
command line

to perform this operation, right?

-chris

On Tue, Dec 7, 2010 at 9:03 AM, Tristan Sloughter <
tristan.sloughter@gmail.com> wrote:

I can’t seem to find anything online related to this error I am
getting when attempting to upload a new version of a cookbook. Does
this

trace make sense to anyone?

INFO: Validating ruby files
INFO: Validating templates
INFO: Syntax OK
INFO: Generating Metadata
WARN: HTTP Request Returned 500 Internal Server Error: Named route
sandbox_checksum could not be generated with
{:sandbox_id=>“fb314161f0e547039636c9f64e850f02”, :checksum=>""}

/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/http.rb:2097:in

error!': 500 "Internal Server Error" (Net::HTTPFatalError) from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:229:inapi_request’

from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:280:in
retriable_rest_request' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:210:inapi_request’

from
/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/rest.rb:121:in
`post_rest’

from

/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/cookbook_uploader.rb:26:in

`upload_cookbook’
from

/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:67:in

`run’
from

/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:65:in

`each’
from

/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:65:in

`run’
from

/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:80:in

`humanize_auth_exceptions’
from

/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife/cookbook_upload.rb:53:in

run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/knife.rb:127:inrun’

from

/Library/Ruby/Gems/1.8/gems/chef-0.9.8/lib/chef/application/knife.rb:118:in

run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.8/bin/knife:25 from /usr/bin/knife:19:inload’
from /usr/bin/knife:19

Thanks,
Tristan