Chef-client daemon on RedHat, was: Chef 0.10.10.beta.1


#1

On Fri, Apr 20, 2012 at 1:30 PM, Arthur Kalmenson arthur.kalm@gmail.com wrote:

Not sure if this would be the best thread to ask, but it’d be nice if knife
bootstrap on a Red Hat server would create an init.d entry.

I’m also finding that when chef-client is installed on Red Hat boxes, it
doesn’t continue to check in with the chef server.

You’ll need to be specific about your installation, such as the
version of Redhat, version of Chef, how Chef was installed (Rubygems?
RPMs?), what bootstram template you’re using with knife and if you’re
using the chef-client cookbook.

This is the best place to get help. The best place to file a bug would
be at http://tickets.opscode.com.

Bryan


#2

In my group, we use rpms from rbel.frameos.org for our centos/rhel
machines, but we use the chef-client cookbook to maintain the init
scripts (and we have since switched to cron).
The cookbook seems to be the best place for establishing the init
scripts or not.

I had problems with the daemon dying off after a random number of
days, which is why we switched to a cron job.

-Jesse

On Fri, Apr 20, 2012 at 13:36, Bryan McLellan btm@loftninjas.org wrote:

On Fri, Apr 20, 2012 at 1:30 PM, Arthur Kalmenson arthur.kalm@gmail.com wrote:

Not sure if this would be the best thread to ask, but it’d be nice if knife
bootstrap on a Red Hat server would create an init.d entry.

I’m also finding that when chef-client is installed on Red Hat boxes, it
doesn’t continue to check in with the chef server.

You’ll need to be specific about your installation, such as the
version of Redhat, version of Chef, how Chef was installed (Rubygems?
RPMs?), what bootstram template you’re using with knife and if you’re
using the chef-client cookbook.

This is the best place to get help. The best place to file a bug would
be at http://tickets.opscode.com.

Bryan