[chef] RE: Re: RE: Re: Re: Re: Service statement bug in recipe when running on SuSe..?

["Bamberger, David" < >]

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 

 
Sent: Friday, September 16, 2011 9:17 AM
To: 

 
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>