[chef] Re: Re: nodes not showing up in `knife status`


Chronological Thread 
  • From: Adam Ochonicki < >
  • To:
  • Subject: [chef] Re: Re: nodes not showing up in `knife status`
  • Date: Tue, 29 Jan 2013 09:14:31 -0500

Your best bet is probably to build chef server using chef solo so you don't run into these manual config problems


That's why we're using chef :)

On Jan 29, 2013, at 9:00 AM, Spike Grobstein < "> > wrote:

ahhh. ok. This is all starting to make sense now. I didn't fully understand how all the components of chef worked together, so I didn't know where to look.

the nodes were not coming up in searches, so it definitely looked like my new nodes weren't being indexed in solr. I tried to run `knife index rebuild -y`, but got:

$ knife index rebuild -y
ERROR: Server returned error for http://localhost:4000//search/reindex, retrying 1/5 in 4s

(I have an ssh tunnel to access the private network of our infrastructure)

so I took a look at /var/log/chef/solr.log and saw:

Jan 29, 2013 1:52:04 PM org.apache.solr.core.SolrCore execute
INFO: [] webapp=/solr path=/update params={} status=500 QTime=6 
Jan 29, 2013 1:52:04 PM org.apache.solr.common.SolrException log
SEVERE: java.io.FileNotFoundException: /var/cache/chef/solr/data/index/_6xjj.fdt (Permission denied)

I'd had a problem in early january when upgrading my chef-server system and inadvertently deleted the `chef` user, so I recreated it and went around and had to re-`chown` everything. I missed the /var/cache/chef directory, so after fixing that, this worked:

$ knife index rebuild -y
Chef::ApiClient:    success
Chef::DataBag:      success
Chef::Environment:  success
Chef::Node:         success
Chef::Role:         success

now `knife status` shows all of my nodes, including the new ones.

Thanks for all the help!



...spike

On Jan 29, 2013, at 2:07 AM, Chirag Jog wrote:

Hi Spike,
Another thing to try is that - are those nodes showing up in knife search ? 
You could try knife search node 'platform:ubuntu' or knife search node 'name:<name-of-the-node> or name:*. This help identify if they are being indexed at all.



Regards,
Chirag Jog
Chief Technology Officer, 
Clogeny Technologies | http://clogeny.com 
(M) 0091-9766619440 | Skype: chirag.jog



On Tue, Jan 29, 2013 at 8:19 AM, Spike Grobstein < " target="_blank"> > wrote:
Hi Chirag,

I'm just running:

knife status

no additional options or anything.



...spike


Hello Spike,
Knife status uses the solr based search mechanism to find all the nodes . It seems the nodes that are missing don't meet that search criteria . 

Can you share the entire knife status command ?

--
Regards, Chirag 

On Tuesday, January 29, 2013, Spike Grobstein wrote:
Hi Chefs,

I've recently added some new nodes to our chef-server, but when I run `knife status`, I don't see these nodes in the list.

`knife node edit $NODE` works
`knife client edit $NODE` works

the nodes show up in the webui.

the name in /etc/chef/client.rb is correct on the nodes.

Is there anything else I should look at?

75 total nodes show up when I run `knife status`. We're missing about 6 nodes from the list that I can see so far. I have a full range of last-run-at times; from minutes to over 6000 hours (some nodes I haven't upgraded the client on for quite a while), so I don't think it's just truncating the list.

Thanks in advance!


...spike


--
Regards,
Chirag Jog
Chief Technology Officer, 
Clogeny Technologies | http://clogeny.com 
(M) 0091-9766619440 | Skype: chirag.jog









Archive powered by MHonArc 2.6.16.

§