Re: Re: Service statement bug in recipe when running on SuSe..?


#1

Yes, there is an /etc/init.d/chef-client is there. A service chef-client start issued at the client works fine.

Sent from my Verizon Wireless 4GLTE smartphone

----- Reply message -----
From: “Allan Wind” allan_wind@lifeintegrity.com
To: "chef@lists.opscode.com" chef@lists.opscode.com
Subject: [chef] Re: Service statement bug in recipe when running on SuSe…?
Date: Thu, Sep 15, 2011 5:43 pm

On 2011-09-15 16:32:42, Van Fossan,Randy wrote:

service “chef-client” do

service_name node[:ravchef][:service]

action [:enable, :start]

end

Looks right to me. Do you have a /etc/init.d/chef-client? What
happens when you start chef-client manually?

/Allan

Allan Wind
Life Integrity, LLC
http://lifeintegrity.com


#2

On 2011-09-15 16:24:34, Van Fossan,Randy wrote:

Yes, there is an /etc/init.d/chef-client is there. A service
chef-client start issued at the client works fine.

The next thing I would do (and I have not used chef-solo) would
be to run this with debug logging to see what happens.

/Allan

Allan Wind
Life Integrity, LLC
http://lifeintegrity.com


#3

Running the cookbook via chef-solo to start the chef-client service
works like a champ. Just cannot do it via chef-client running on the
command line on SuSe…

node.json
{
“run_list”: [ “recipe[ravchef::default]” ]
}

-----Original Message-----
From: Allan Wind [mailto:allan_wind@lifeintegrity.com]
Sent: Friday, September 16, 2011 3:36 AM
To: chef@lists.opscode.com
Subject: [chef] Re: Re: Re: Service statement bug in recipe when running
on SuSe…?

On 2011-09-15 16:24:34, Van Fossan,Randy wrote:

Yes, there is an /etc/init.d/chef-client is there. A service
chef-client start issued at the client works fine.

The next thing I would do (and I have not used chef-solo) would be to
run this with debug logging to see what happens.

/Allan

Allan Wind
Life Integrity, LLC
http://lifeintegrity.com


#4

On 2011-09-16 09:24:19, Van Fossan,Randy wrote:

Running the cookbook via chef-solo to start the chef-client service
works like a champ. Just cannot do it via chef-client running on the
command line on SuSe…

node.json
{
“run_list”: [ “recipe[ravchef::default]” ]
}

Sorry, I am will not be a further help then. Btw, I meant to say
that I only used chef-solo.

/Allan

Allan Wind
Life Integrity, LLC
http://lifeintegrity.com


#5

Allan,

We’ve found that if an init script status function returns a “0” for some reason for during chef-client runs chef assumes it’s running.

So, some debug output from a chef-client run:

[Fri, 16 Sep 2011 09:51:08 -0700] DEBUG: ---- Begin output of /sbin/service splunk status ----
[Fri, 16 Sep 2011 09:51:08 -0700] DEBUG: STDOUT: Splunk status:
splunkd is not running.
[Fri, 16 Sep 2011 09:51:08 -0700] DEBUG: STDERR:
[Fri, 16 Sep 2011 09:51:08 -0700] DEBUG: ---- End output of /sbin/service splunk status ----
[Fri, 16 Sep 2011 09:51:08 -0700] DEBUG: Ran /sbin/service splunk status returned 0
[Fri, 16 Sep 2011 09:51:08 -0700] DEBUG: service[splunk] is running

In this case the splunk binary presents us a readable notice but doesn’t push an exit code 3. Could this be your issue?

Regards.
dbam

David Bamberger
DevOps

Infogroup
office: 503.419.0564
cell: 510.759.4360
www.infogroup.com
Find us here: Twitter | Facebook | Community


From: Allan Wind [allan_wind@lifeintegrity.com]
Sent: Friday, September 16, 2011 9:17 AM
To: chef@lists.opscode.com
Subject: [chef] Re: RE: Re: Re: Re: Service statement bug in recipe when running on SuSe…?

On 2011-09-16 09:24:19, Van Fossan,Randy wrote:

Running the cookbook via chef-solo to start the chef-client service
works like a champ. Just cannot do it via chef-client running on the
command line on SuSe…

node.json
{
“run_list”: [ “recipe[ravchef::default]” ]
}

Sorry, I am will not be a further help then. Btw, I meant to say
that I only used chef-solo.

/Allan

Allan Wind
Life Integrity, LLC
http://lifeintegrity.com