Chef Server oc_id Process Running Wild In The Streets

Sean Horn -

If you notice that your idle Chef Server is unusually busy, possibly even taking up an entire CPU, the oc_id process is often to blame. It will be cycling, outputting endless repetitions of the following output in its logfile.

You can confirm by noticing the following in the /var/log/opscode/oc_id/current file

2017-03-21_16:58:03.74555 Array values in the parameter to `Gem.paths=` are deprecated.
2017-03-21_16:58:03.74563 Please use a String or nil.
2017-03-21_16:58:03.74563 An Array ({"GEM_PATH"=>["/opt/opscode/embedded/service/gem/ruby/2.2.0"]}) was passed in from bin/rails:3:in `load'
2017-03-21_16:58:06.37624 /opt/opscode/embedded/service/gem/ruby/2.2.0/gems/chef-11.18.12/lib/chef/data_bag_item.rb:161: warning: circular argument reference - data_bag
2017-03-21_16:58:09.05636 => Booting Unicorn
2017-03-21_16:58:09.05637 => Rails 4.2.5.2 application starting in production on http://127.0.0.1:9090
2017-03-21_16:58:09.05638 => Run `rails server -h` for more startup options
2017-03-21_16:58:09.05638 => Ctrl-C to shutdown server
2017-03-21_16:58:09.05711 A server is already running. Check /opt/opscode/embedded/service/oc_id/tmp/pids/server.pid.
2017-03-21_16:58:09.05712 Exiting


If you do see this kind of output, you can clear the condition with the following command

rm -f /opt/opscode/embedded/service/oc_id/tmp/pids/server.pid 
Have more questions? Submit a request

Comments

Powered by Zendesk