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, 범희대
< >
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
root 857 1 0 Mar10 ? 00:13:17 runsvdir -P
/opt/opscode/service log: ary failure?runsv postgresql: fatal: unable to
lock supervise/lock: temporary failure?runsv redis_lb: fatal: unable to lock
supervise/lock: temporary failure?runsv opscode-erchef: fatal: unable to
lock supervise/lock: temporary failure?runsv opscode-expander-reindexer:
fatal: unable to lock supervise/lock: temporary failure?runsv nginx: fatal:
unable to lock supervise/lock: temporary failure?
root 18489 1 0 Mar10 ? 00:00:00 runsv opscode-erchef
opscode 18492 18489 0 Mar10 ? 00:00:06 svlogd -tt
/var/log/opscode/opscode-erchef
root 20649 1 0 Mar10 ? 00:00:00 runsv opscode-chef-mover
opscode 20650 20649 0 Mar10 ? 00:00:00 svlogd -tt
/var/log/opscode/opscode-chef-mover
opscode 20651 20649 0 Mar10 ? 00:00:09
/opt/opscode/embedded/service/opscode-chef-mover/erts-5.10.4/bin/beam.smp -K
true -A 5 -- -root /opt/opscode/embedded/service/opscode-chef-mover
-progname mover -- -home /var/opt/opscode/opscode-chef-mover -- -noshell
-boot /opt/opscode/embedded/service/opscode-chef-mover/releases/2.2.20/mover
-embedded -config
/opt/opscode/embedded/service/opscode-chef-mover/etc/sys.config -name
-setcookie mover -- runit
root 26356 15114 0 17:51 pts/7 00:00:00 grep chef
So how can i stop all the processes related chef, completely?
Thx
Archive powered by MHonArc 2.6.16.