/proc/pid/stat cpu ticks are not updated












0














I'll be as precise as possible:



On my RHEL7 machine (3.10.0-514.el7.x86_64), /proc/PID/stat is not updated in respect to CPU ticks, sometimes for a minute and more. I'm clearly at a loss how this can be possible. Here some additional information:




  • The process is a very long running one (our database server) with around 9.000.000.000 ticks user time in total and around 800 ticks per second.

  • minor page faults are updated correctly. Thats also the only value changing.

  • forked subprocesses (workers) are updated correctly.

  • The behaviour changes with time. Its almost exactly 80 Minutes between these "stalls", where the gaps are biggest. Then it gradualy normalises after 20 Minutes when values are fine again.


This behaviour completely messes up top, causing it to show values of 0% CPU usage most of the time and suddenly spiking to 1600 (we have 16 Cores there). And that with a database that is only licenced for (and limited to) 8 cores.



Furthermore, it confuses our monitoring tool, which seems to use the same values. When on a 1-minute average, what we get is the image depicted in the screenshot.
Obviously, the database does not really stall during this time. The question is, has anyone seen such a behaviour before? Unfortunately, I cannot simply restart the process, wich i would do if it were anything other than our main database :)



screenshot










share|improve this question





























    0














    I'll be as precise as possible:



    On my RHEL7 machine (3.10.0-514.el7.x86_64), /proc/PID/stat is not updated in respect to CPU ticks, sometimes for a minute and more. I'm clearly at a loss how this can be possible. Here some additional information:




    • The process is a very long running one (our database server) with around 9.000.000.000 ticks user time in total and around 800 ticks per second.

    • minor page faults are updated correctly. Thats also the only value changing.

    • forked subprocesses (workers) are updated correctly.

    • The behaviour changes with time. Its almost exactly 80 Minutes between these "stalls", where the gaps are biggest. Then it gradualy normalises after 20 Minutes when values are fine again.


    This behaviour completely messes up top, causing it to show values of 0% CPU usage most of the time and suddenly spiking to 1600 (we have 16 Cores there). And that with a database that is only licenced for (and limited to) 8 cores.



    Furthermore, it confuses our monitoring tool, which seems to use the same values. When on a 1-minute average, what we get is the image depicted in the screenshot.
    Obviously, the database does not really stall during this time. The question is, has anyone seen such a behaviour before? Unfortunately, I cannot simply restart the process, wich i would do if it were anything other than our main database :)



    screenshot










    share|improve this question



























      0












      0








      0







      I'll be as precise as possible:



      On my RHEL7 machine (3.10.0-514.el7.x86_64), /proc/PID/stat is not updated in respect to CPU ticks, sometimes for a minute and more. I'm clearly at a loss how this can be possible. Here some additional information:




      • The process is a very long running one (our database server) with around 9.000.000.000 ticks user time in total and around 800 ticks per second.

      • minor page faults are updated correctly. Thats also the only value changing.

      • forked subprocesses (workers) are updated correctly.

      • The behaviour changes with time. Its almost exactly 80 Minutes between these "stalls", where the gaps are biggest. Then it gradualy normalises after 20 Minutes when values are fine again.


      This behaviour completely messes up top, causing it to show values of 0% CPU usage most of the time and suddenly spiking to 1600 (we have 16 Cores there). And that with a database that is only licenced for (and limited to) 8 cores.



      Furthermore, it confuses our monitoring tool, which seems to use the same values. When on a 1-minute average, what we get is the image depicted in the screenshot.
      Obviously, the database does not really stall during this time. The question is, has anyone seen such a behaviour before? Unfortunately, I cannot simply restart the process, wich i would do if it were anything other than our main database :)



      screenshot










      share|improve this question















      I'll be as precise as possible:



      On my RHEL7 machine (3.10.0-514.el7.x86_64), /proc/PID/stat is not updated in respect to CPU ticks, sometimes for a minute and more. I'm clearly at a loss how this can be possible. Here some additional information:




      • The process is a very long running one (our database server) with around 9.000.000.000 ticks user time in total and around 800 ticks per second.

      • minor page faults are updated correctly. Thats also the only value changing.

      • forked subprocesses (workers) are updated correctly.

      • The behaviour changes with time. Its almost exactly 80 Minutes between these "stalls", where the gaps are biggest. Then it gradualy normalises after 20 Minutes when values are fine again.


      This behaviour completely messes up top, causing it to show values of 0% CPU usage most of the time and suddenly spiking to 1600 (we have 16 Cores there). And that with a database that is only licenced for (and limited to) 8 cores.



      Furthermore, it confuses our monitoring tool, which seems to use the same values. When on a 1-minute average, what we get is the image depicted in the screenshot.
      Obviously, the database does not really stall during this time. The question is, has anyone seen such a behaviour before? Unfortunately, I cannot simply restart the process, wich i would do if it were anything other than our main database :)



      screenshot







      linux-kernel proc top






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Sep 25 '18 at 13:07







      Christian Platzer

















      asked Sep 25 '18 at 13:00









      Christian PlatzerChristian Platzer

      12




      12






















          1 Answer
          1






          active

          oldest

          votes


















          0














          Identitcal issue have been on our system.
          Are you still having trouble with this?
          Could you explain a little bit more about your environment such as whether the machine is physical or virtual.
          If it's VM, what is the host OS?



          There are issue and fixed report that related to this in RHEL doc a few years ago.
          https://access.redhat.com/solutions/338733
          That's why we have a suspicion on host OS.



          I really appreciate any information you can share!






          share|improve this answer








          New contributor




          honser is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.


















            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "106"
            };
            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',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f471316%2fproc-pid-stat-cpu-ticks-are-not-updated%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Identitcal issue have been on our system.
            Are you still having trouble with this?
            Could you explain a little bit more about your environment such as whether the machine is physical or virtual.
            If it's VM, what is the host OS?



            There are issue and fixed report that related to this in RHEL doc a few years ago.
            https://access.redhat.com/solutions/338733
            That's why we have a suspicion on host OS.



            I really appreciate any information you can share!






            share|improve this answer








            New contributor




            honser is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.























              0














              Identitcal issue have been on our system.
              Are you still having trouble with this?
              Could you explain a little bit more about your environment such as whether the machine is physical or virtual.
              If it's VM, what is the host OS?



              There are issue and fixed report that related to this in RHEL doc a few years ago.
              https://access.redhat.com/solutions/338733
              That's why we have a suspicion on host OS.



              I really appreciate any information you can share!






              share|improve this answer








              New contributor




              honser is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.





















                0












                0








                0






                Identitcal issue have been on our system.
                Are you still having trouble with this?
                Could you explain a little bit more about your environment such as whether the machine is physical or virtual.
                If it's VM, what is the host OS?



                There are issue and fixed report that related to this in RHEL doc a few years ago.
                https://access.redhat.com/solutions/338733
                That's why we have a suspicion on host OS.



                I really appreciate any information you can share!






                share|improve this answer








                New contributor




                honser is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                Identitcal issue have been on our system.
                Are you still having trouble with this?
                Could you explain a little bit more about your environment such as whether the machine is physical or virtual.
                If it's VM, what is the host OS?



                There are issue and fixed report that related to this in RHEL doc a few years ago.
                https://access.redhat.com/solutions/338733
                That's why we have a suspicion on host OS.



                I really appreciate any information you can share!







                share|improve this answer








                New contributor




                honser is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                share|improve this answer



                share|improve this answer






                New contributor




                honser is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                answered 16 mins ago









                honserhonser

                1




                1




                New contributor




                honser is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.





                New contributor





                honser is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.






                honser is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Unix & Linux Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f471316%2fproc-pid-stat-cpu-ticks-are-not-updated%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    サソリ

                    広島県道265号伴広島線

                    Setup Asymptote in Texstudio