Disable chef-client?

Douglas_Garstang · October 22, 2014, 3:49pm

All,

When the chef-client is running as a daemon, is there a way to keep the
client running as a daemon, but temporarily put it into NOOP mode?

Doug

Peter_Burkholder1 · October 22, 2014, 7:18pm

Lockfile? See

and

In client.rb or solo.rb

lockfile "/not-nfs/chef-lockfile.pid"

On Wed, Oct 22, 2014 at 11:49 AM, Douglas Garstang doug.garstang@gmail.com
wrote:

All,

When the chef-client is running as a daemon, is there a way to keep the
client running as a daemon, but temporarily put it into NOOP mode?

Doug

kallistec · October 22, 2014, 10:13pm

On Wednesday, October 22, 2014 at 12:18 PM, Peter Burkholder wrote:

Lockfile? See Chef 11 In-Depth: Client Improvements - Chef Blog | Chef and

In client.rb or solo.rb

lockfile "/not-nfs/chef-lockfile.pid"

Chef uses flocks to ensure that there is a live “owner” of this lockfile, and depending on configuration, the default behavior if the lock isn’t available is for chef to wait, so this isn’t really a good option.

On Wed, Oct 22, 2014 at 11:49 AM, Douglas Garstang <doug.garstang@gmail.com (mailto:doug.garstang@gmail.com)> wrote:

All,

When the chef-client is running as a daemon, is there a way to keep the client running as a daemon, but temporarily put it into NOOP mode?

Doug
Doug,

There’s nothing built-in to do this. You could maybe experiment with using a data bag item to drive recipe code that would set Chef::Config[:why_run] to true, but I’m not sure it will work. Though we do something similar with a “suicide” cookbook that makes chef-client abort early if a certain data bag item contains a specific value (and we added some scripts to change the data bag item easily from the command line.

HTH,

--
Daniel DeLeo

Tensibai · October 22, 2014, 10:22pm

My point of view: I would use a tag or an attribute and a top level (in run list) recipe aborting (gracefully if possible, can't remember this) the chef run if the tag is present.

---- Douglas Garstang a écrit ----

All,

When the chef-client is running as a daemon, is there a way to keep the client running as a daemon, but temporarily put it into NOOP mode?

Doug

Tensibai · October 23, 2014, 8:28am

you may even use the resource "omnibus chef killer" from

github.com

chef-boneyard/omnibus_updater/blob/master/recipes/installer.rb

#
# Cookbook:: omnibus_updater
# Recipe:: installer
#
# Copyright:: 2014-2017, Heavy Water Ops, LLC
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#

include_recipe 'omnibus_updater'

This file has been truncated. show original

as a starting point for yours.

Le 2014-10-23 00:22, Tensibai Zhaoying a écrit :

My point of view: I would use a tag or an attribute and a top level (in run list) recipe aborting (gracefully if possible, can't remember this) the chef run if the tag is present.

---- Douglas Garstang a écrit ----

All,

When the chef-client is running as a daemon, is there a way to keep the client running as a daemon, but temporarily put it into NOOP mode?

Doug

Topic		Replies	Views
Client locking Chef Infra (archive)	2	305	August 12, 2014
Chef Client runs twice Chef Infra (archive)	1	737	June 18, 2015
Chef-3854 Chef Infra (archive)	2	271	May 30, 2013
Chef client multithreading Chef Infra (archive)	2	1596	December 20, 2015
Simultaneous chef run handling on linux/windows Chef Infra (archive)	2	657	August 20, 2013

Disable chef-client?

In client.rb or solo.rb

In client.rb or solo.rb

Related Topics