[Bug 1197426] Re: starpar-upstart-inject causes upstart to consume a lot of cpu

[James Hunt]

get_started is a job that also specifes 'start on started', so upstart
was chasing both jobs constantly: only 1 job can reasonably specify such
an unspecific start condition.

** Changed in: sysvinit (Ubuntu)
       Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1197426

Title:
  starpar-upstart-inject causes upstart to consume a lot of cpu

Status in “sysvinit” package in Ubuntu:
  Invalid

Bug description:
  My machine was responding sluggishly. Top showed PID 1 consuming
  almost 70% CPU. The culprit seems to be the startpar-bridge job which
  had 2 running instances:

  $ sudo initctl list|grep startpar                                                                                                                                    
  startpar-bridge (get_started--started) start/running, process 9024
  startpar-bridge (get_started--stopped) start/running, process 9035

  The fix was to:

  1) Stop the job from restarting:

      echo manual | sudo tee /etc/init/startpar-bridge.override

  2) Stop the 2 running instances.

  CPU usage then returned to normal levels.

  strace confirmed that upstart was constantly processing startpar-
  bridge requests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1197426/+subscriptions