/sbin/upstart cpu usage

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
0
down vote

favorite












I have randomly getting >80% CPU usage from:



/sbin/upstart --user



enter image description here



Any idea how to stop that and the reason why is this happening?



version:



>>>lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial






share|improve this question
























    up vote
    0
    down vote

    favorite












    I have randomly getting >80% CPU usage from:



    /sbin/upstart --user



    enter image description here



    Any idea how to stop that and the reason why is this happening?



    version:



    >>>lsb_release -a
    No LSB modules are available.
    Distributor ID: Ubuntu
    Description: Ubuntu 16.04.3 LTS
    Release: 16.04
    Codename: xenial






    share|improve this question






















      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I have randomly getting >80% CPU usage from:



      /sbin/upstart --user



      enter image description here



      Any idea how to stop that and the reason why is this happening?



      version:



      >>>lsb_release -a
      No LSB modules are available.
      Distributor ID: Ubuntu
      Description: Ubuntu 16.04.3 LTS
      Release: 16.04
      Codename: xenial






      share|improve this question












      I have randomly getting >80% CPU usage from:



      /sbin/upstart --user



      enter image description here



      Any idea how to stop that and the reason why is this happening?



      version:



      >>>lsb_release -a
      No LSB modules are available.
      Distributor ID: Ubuntu
      Description: Ubuntu 16.04.3 LTS
      Release: 16.04
      Codename: xenial








      share|improve this question











      share|improve this question




      share|improve this question










      asked Apr 24 at 12:36









      Mpizos Dimitris

      1063




      1063




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          I suspect some fault (or an entirely missing) systemd service, could you check if you even have systemd by systemctl -v?



          Maybe you already have systemd but are not booting with it? In that case, could you go to your GRUB options at startup and boot by selecting your kernel + (systemd)?






          share|improve this answer




















            Your Answer







            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "89"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            convertImagesToLinks: true,
            noModals: false,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













             

            draft saved


            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1027796%2fsbin-upstart-cpu-usage%23new-answer', 'question_page');

            );

            Post as a guest






























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            I suspect some fault (or an entirely missing) systemd service, could you check if you even have systemd by systemctl -v?



            Maybe you already have systemd but are not booting with it? In that case, could you go to your GRUB options at startup and boot by selecting your kernel + (systemd)?






            share|improve this answer
























              up vote
              0
              down vote













              I suspect some fault (or an entirely missing) systemd service, could you check if you even have systemd by systemctl -v?



              Maybe you already have systemd but are not booting with it? In that case, could you go to your GRUB options at startup and boot by selecting your kernel + (systemd)?






              share|improve this answer






















                up vote
                0
                down vote










                up vote
                0
                down vote









                I suspect some fault (or an entirely missing) systemd service, could you check if you even have systemd by systemctl -v?



                Maybe you already have systemd but are not booting with it? In that case, could you go to your GRUB options at startup and boot by selecting your kernel + (systemd)?






                share|improve this answer












                I suspect some fault (or an entirely missing) systemd service, could you check if you even have systemd by systemctl -v?



                Maybe you already have systemd but are not booting with it? In that case, could you go to your GRUB options at startup and boot by selecting your kernel + (systemd)?







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Apr 24 at 13:53









                fatalVoltage

                113




                113



























                     

                    draft saved


                    draft discarded















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1027796%2fsbin-upstart-cpu-usage%23new-answer', 'question_page');

                    );

                    Post as a guest













































































                    Popular posts from this blog

                    pylint3 and pip3 broken

                    Missing snmpget and snmpwalk

                    How to enroll fingerprints to Ubuntu 17.10 with VFS491