hello,
I newly entered chef a few weeks ago. therefore I’m really confused about
chef administration.
and there is a question about it.
Once I stopped chef server by running chef-server-ctl stop, most of
processes had started by chef, however there were still some processes of
chef like the followings
hello,
I newly entered chef a few weeks ago. therefore I'm really confused about
chef administration.
and there is a question about it.
Once I stopped chef server by running chef-server-ctl stop, most of
processes had started by chef, however there were still some processes of
chef like the followings
Kill 'em off and see if they come back: pkill -9 -f "(runsvdir|runsv|opscode|runit)"
I would probably expect chef-server-ctl stop to work in this case.
May be worth filing a bug.
cheers,
--aj
On Wed, Mar 11, 2015 at 9:52 PM, 범희대 heedae@solbox.com wrote:
hello,
I newly entered chef a few weeks ago. therefore I'm really confused about
chef administration.
and there is a question about it.
Once I stopped chef server by running chef-server-ctl stop, most of
processes had started by chef, however there were still some processes of
chef like the followings
chef-server-ctl stop leaves the runsvdir, runsv, svlogd, etc runit
processes running by design. i suspect the mover process is there for
supporting upgrades as well which needs to be running when the other
services are down.
On 3/11/15 12:09 PM, AJ Christensen wrote:
Kill 'em off and see if they come back: pkill -9 -f "(runsvdir|runsv|opscode|runit)"
I would probably expect chef-server-ctl stop to work in this case.
May be worth filing a bug.
hello,
I newly entered chef a few weeks ago. therefore I'm really confused about
chef administration.
and there is a question about it.
Once I stopped chef server by running chef-server-ctl stop, most of
processes had started by chef, however there were still some processes of
chef like the followings
chef-server-ctl stop leaves the runsvdir, runsv, svlogd, etc runit
processes running by design. i suspect the mover process is there for
supporting upgrades as well which needs to be running when the other
services are down.
On 3/11/15 12:09 PM, AJ Christensen wrote:
Kill 'em off and see if they come back: pkill -9 -f "(runsvdir|runsv|opscode|runit)"
I would probably expect chef-server-ctl stop to work in this case.
May be worth filing a bug.
hello,
I newly entered chef a few weeks ago. therefore I'm really confused about
chef administration.
and there is a question about it.
Once I stopped chef server by running chef-server-ctl stop, most of
processes had started by chef, however there were still some processes of
chef like the followings
In both cases, the systems init system will respawn runsvdir (the
top-level supervisor for runit that we use to manage servicies), which
in tern will restart all the services.
For SysV systems (RHEL 5), you probably want to do something like this
chef-server-ctl stop
modify inittab to remove the respawn entry
init q
For upstart it is a little more complicated because upstart will send
upstart the wrong signal by default and not all versions of upstart
allow you to control the kill signal. I would try something like
this:
chef-server-ctl stop leaves the runsvdir, runsv, svlogd, etc runit
processes running by design. i suspect the mover process is there for
supporting upgrades as well which needs to be running when the other
services are down.
On 3/11/15 12:09 PM, AJ Christensen wrote:
Kill 'em off and see if they come back: pkill -9 -f "(runsvdir|runsv|opscode|runit)"
I would probably expect chef-server-ctl stop to work in this case.
May be worth filing a bug.
hello,
I newly entered chef a few weeks ago. therefore I'm really confused
about
chef administration.
and there is a question about it.
Once I stopped chef server by running chef-server-ctl stop, most of
processes had started by chef, however there were still some processes
of
chef like the followings
In both cases, the systems init system will respawn runsvdir (the
top-level supervisor for runit that we use to manage servicies), which
in tern will restart all the services.
For SysV systems (RHEL 5), you probably want to do something like this
chef-server-ctl stop
modify inittab to remove the respawn entry
init q
For upstart it is a little more complicated because upstart will send
upstart the wrong signal by default and not all versions of upstart
allow you to control the kill signal. I would try something like
this:
chef-server-ctl stop leaves the runsvdir, runsv, svlogd, etc runit
processes running by design. i suspect the mover process is there for
supporting upgrades as well which needs to be running when the other
services are down.
On 3/11/15 12:09 PM, AJ Christensen wrote:
Kill 'em off and see if they come back: pkill -9 -f "(runsvdir|runsv|opscode|runit)"
I would probably expect chef-server-ctl stop to work in this case.
May be worth filing a bug.
hello,
I newly entered chef a few weeks ago. therefore I'm really confused
about
chef administration.
and there is a question about it.
Once I stopped chef server by running chef-server-ctl stop, most of
processes had started by chef, however there were still some processes
of
chef like the followings