Corrupted Cookbook on Server

Chef Infra (archive)
1

I have one cookbook on my Chef server that is in an odd state. I can get information on it with knife cookbook show and I can upload the same or new version to it. However, I cannot download it, nor can I delete it. It is only one of a number of test cookbooks, so it is not important that I save it. I have the most recent version on a client.

I have tried multiple variations of knife cookbook delete to get rid of it, any version of it or even all of it. I have even tried the -p (purge) option. Is there some brute force way to get rid of it so I can start over? I am still learning Chef, so I am very interested in learning to fix things when they go wrong.

Thanks,
-Dave

2

Hi,
I think you need to provide some more information here:

  • What output do you get when you try and delete it?

  • What does knife cookbook show <name> <version> give you?

  • If you run knife cookbook delete -VV <name> <version>, please copy the relevant debug output.

  • What logs are there on the chef server? (Use chef-server-ctl tail opscode-erchef to gather those logs).

thanks,
-Thom

3

From the client, using knife, there is no output. The command (on PowerShell Windows Console) never returns. Ctrl+C does end the attempt.

However, the logs on the server turned up something. (Thanks for helping me understand how to get that)

These seem to be the most relevant entries, but I am still looking at it:

==> /var/log/opscode/opscode-erchef/current <==
2017-03-28_15:32:15.46024 [info] Negotiated maximums: (Channel = 0, Frame = 131072, Heartbeat = 580)
2017-03-28_15:32:15.46026
2017-03-28_15:32:15.46352 [info] chef_keygen_cache configured size: 10 start_size: 0 max_workers: 1
2017-03-28_15:32:15.46518 [info] chef_keygen_cache starting with 0 keys in cache
2017-03-28_15:32:15.46519
2017-03-28_15:32:15.46873 [info] Application oc_chef_wm started on node 'erchef@127.0.0.1’
2017-03-28_15:32:15.46879 [info] Application oc_erchef started on node 'erchef@127.0.0.1’
2017-03-28_15:32:15.46921 [info] Application eper started on node 'erchef@127.0.0.1’
2017-03-28_15:32:15.46964 [info] Application efast_xs started on node 'erchef@127.0.0.1’
2017-03-28_16:11:39.48283 [error] {<<"method=GET; path=/organizations/coatelab/cookbooks/learn_chef_iis/cookbook; status=400; ">>,“Bad Request”}

==> /var/log/opscode/opscode-erchef/erchef.log <==
2017-03-28 08:32:15.460 [info] Negotiated maximums: (Channel = 0, Frame = 131072, Heartbeat = 580)

2017-03-28 08:32:15.463 [info] chef_keygen_cache configured size: 10 start_size: 0 max_workers: 1
2017-03-28 08:32:15.463 [info] chef_keygen_cache starting with 0 keys in cache

2017-03-28 08:32:15.468 [info] Application oc_chef_wm started on node 'erchef@127.0.0.1’
2017-03-28 08:32:15.468 [info] Application oc_erchef started on node 'erchef@127.0.0.1’
2017-03-28 08:32:15.469 [info] Application eper started on node 'erchef@127.0.0.1’
2017-03-28 08:32:15.469 [info] Application efast_xs started on node 'erchef@127.0.0.1’
2017-03-28 09:11:39.471 [error] {<<"method=GET; path=/organizations/coatelab/cookbooks/learn_chef_iis/cookbook; status=400; ">>,“Bad Request”}

==> /var/log/opscode/opscode-erchef/crash.log <==
2017-03-28 09:11:39 =ERROR REPORT====
{<<"method=GET; path=/organizations/coatelab/cookbooks/learn_chef_iis/cookbook; status=400; ">>,“Bad Request”}