PT-Kill not logging to file












0















Run command for pt-kill



/usr/bin/pt-kill --ignore-state User lock --rds --match-command Query --victims all --match-user phppoint --daemonize --busy-time 10 --kill --print --log /var/log/pt-kill.log h=HOST,u=master,p=PaSS,P=3306


Queries are killed but not logged. Runs as root on Amazon Linux and file /var/log/put-kill.log exists and has 600 permissions










share|improve this question














bumped to the homepage by Community 2 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.




















    0















    Run command for pt-kill



    /usr/bin/pt-kill --ignore-state User lock --rds --match-command Query --victims all --match-user phppoint --daemonize --busy-time 10 --kill --print --log /var/log/pt-kill.log h=HOST,u=master,p=PaSS,P=3306


    Queries are killed but not logged. Runs as root on Amazon Linux and file /var/log/put-kill.log exists and has 600 permissions










    share|improve this question














    bumped to the homepage by Community 2 mins ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      0












      0








      0








      Run command for pt-kill



      /usr/bin/pt-kill --ignore-state User lock --rds --match-command Query --victims all --match-user phppoint --daemonize --busy-time 10 --kill --print --log /var/log/pt-kill.log h=HOST,u=master,p=PaSS,P=3306


      Queries are killed but not logged. Runs as root on Amazon Linux and file /var/log/put-kill.log exists and has 600 permissions










      share|improve this question














      Run command for pt-kill



      /usr/bin/pt-kill --ignore-state User lock --rds --match-command Query --victims all --match-user phppoint --daemonize --busy-time 10 --kill --print --log /var/log/pt-kill.log h=HOST,u=master,p=PaSS,P=3306


      Queries are killed but not logged. Runs as root on Amazon Linux and file /var/log/put-kill.log exists and has 600 permissions







      percona-tools






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Aug 5 '17 at 5:03









      Chris MuenchChris Muench

      682822




      682822





      bumped to the homepage by Community 2 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 2 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          1 Answer
          1






          active

          oldest

          votes


















          0














          The command seems right.



          You can try to debug using PTDEBUG:



          PTDEBUG=1 (your complete pt-kill command with daemonize and log ) 2>/var/log/pt-kill.err 


          Be careful to watch disk space; don't let it run in debug mode indefinitely.






          share|improve this answer
























          • I am on amazon linux and had to use sudo for the command (even as root user) and I also updated rc.local

            – Chris Muench
            Aug 7 '17 at 20:33











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "182"
          };
          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%2fdba.stackexchange.com%2fquestions%2f182754%2fpt-kill-not-logging-to-file%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














          The command seems right.



          You can try to debug using PTDEBUG:



          PTDEBUG=1 (your complete pt-kill command with daemonize and log ) 2>/var/log/pt-kill.err 


          Be careful to watch disk space; don't let it run in debug mode indefinitely.






          share|improve this answer
























          • I am on amazon linux and had to use sudo for the command (even as root user) and I also updated rc.local

            – Chris Muench
            Aug 7 '17 at 20:33
















          0














          The command seems right.



          You can try to debug using PTDEBUG:



          PTDEBUG=1 (your complete pt-kill command with daemonize and log ) 2>/var/log/pt-kill.err 


          Be careful to watch disk space; don't let it run in debug mode indefinitely.






          share|improve this answer
























          • I am on amazon linux and had to use sudo for the command (even as root user) and I also updated rc.local

            – Chris Muench
            Aug 7 '17 at 20:33














          0












          0








          0







          The command seems right.



          You can try to debug using PTDEBUG:



          PTDEBUG=1 (your complete pt-kill command with daemonize and log ) 2>/var/log/pt-kill.err 


          Be careful to watch disk space; don't let it run in debug mode indefinitely.






          share|improve this answer













          The command seems right.



          You can try to debug using PTDEBUG:



          PTDEBUG=1 (your complete pt-kill command with daemonize and log ) 2>/var/log/pt-kill.err 


          Be careful to watch disk space; don't let it run in debug mode indefinitely.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Aug 5 '17 at 12:25









          Derek DowneyDerek Downey

          18.6k106397




          18.6k106397













          • I am on amazon linux and had to use sudo for the command (even as root user) and I also updated rc.local

            – Chris Muench
            Aug 7 '17 at 20:33



















          • I am on amazon linux and had to use sudo for the command (even as root user) and I also updated rc.local

            – Chris Muench
            Aug 7 '17 at 20:33

















          I am on amazon linux and had to use sudo for the command (even as root user) and I also updated rc.local

          – Chris Muench
          Aug 7 '17 at 20:33





          I am on amazon linux and had to use sudo for the command (even as root user) and I also updated rc.local

          – Chris Muench
          Aug 7 '17 at 20:33


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Database Administrators 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%2fdba.stackexchange.com%2fquestions%2f182754%2fpt-kill-not-logging-to-file%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

          ف. موراي أبراهام

          صرب

          كأس إنترتوتو