[chef] Re: Re: Re: Re: Re: Re: Re: Problems with Search?

[Paul Paradise < >]

I've had similar problems in the past where the nagios would fail to restart because a client saved its node[:ipaddress] as nil, and the next chef-client run on my nagios server broke it. Anecdotally, it only happens when I reboot a node. I suspect there's a race condition at startup where chef-client starts running (and collects the ohai attributes) before the node gets a DHCP lease, and ends up writing a nil node[:ipaddress] when the run completes.

Perhaps you have the same problem, but with the node[:ipaddress] disappearing from your nagios node rather than the monitored nodes?

-Paul

On Thu, Jan 27, 2011 at 9:18 AM, Ash Berlin < "> > wrote:

This could be it yes - basically i'm searching on nrpe client machines for the host running nagois to allow nrpe connections from just this host, and all my clients are still on 0.9.8.

-ash

On 27 Jan 2011, at 17:11, Daniel DeLeo wrote:
> On Thu, Jan 27, 2011 at 8:54 AM, Gilles Devaux < "> > wrote:
>> I reported the same issue under the title "search sometimes returns no
>> result", I pasted my logs in the email.
>
> Is this a search for one specific host? Do the bad searches coincide
> with chef client runs on the searched-for system?  If so, I think this
> is a resolved bug on the client, and you can fix it by upgrading the
> client on the searched-for box to 0.9.12.
>
> The issue I'm thinking of is that the node is saved at the beginning
> of the run so that it has the correct run list when the client asks
> the server for the list of cookbooks to sync. However, some of the
> attributes have been wiped and not yet rebuilt when this node save
> occurs. Sound like your issue?
>
> Thanks,
> Dan