How to see full log from systemctl status service?

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











up vote
206
down vote

favorite
57












I check service status with systemctl status service-name.



By default, I see few rows only, so I add -n50 to see more.



Sometimes, I want to see full log, from start. It could have 1000s of rows.

Now, I check it with -n10000 but that doesn't look like neat solution.



Is there an option to check full systemd service log similar to less command?










share|improve this question



























    up vote
    206
    down vote

    favorite
    57












    I check service status with systemctl status service-name.



    By default, I see few rows only, so I add -n50 to see more.



    Sometimes, I want to see full log, from start. It could have 1000s of rows.

    Now, I check it with -n10000 but that doesn't look like neat solution.



    Is there an option to check full systemd service log similar to less command?










    share|improve this question

























      up vote
      206
      down vote

      favorite
      57









      up vote
      206
      down vote

      favorite
      57






      57





      I check service status with systemctl status service-name.



      By default, I see few rows only, so I add -n50 to see more.



      Sometimes, I want to see full log, from start. It could have 1000s of rows.

      Now, I check it with -n10000 but that doesn't look like neat solution.



      Is there an option to check full systemd service log similar to less command?










      share|improve this question















      I check service status with systemctl status service-name.



      By default, I see few rows only, so I add -n50 to see more.



      Sometimes, I want to see full log, from start. It could have 1000s of rows.

      Now, I check it with -n10000 but that doesn't look like neat solution.



      Is there an option to check full systemd service log similar to less command?







      logs systemd






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Aug 25 '15 at 23:33









      Gilles

      516k12210271555




      516k12210271555










      asked Aug 25 '15 at 15:30









      10robinho

      1,1393915




      1,1393915




















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          277
          down vote



          accepted










          Just use the journalctl command, as in:



          journalctl -u service-name.service


          Or, to see only log messages for the current boot:



          journalctl -u service-name.service -b


          For things named <something>.service, you can actually just use <something>, as in:



          journalctl -u service-name


          But for other sorts of units (sockets, targets, timers, etc), you need to be explicit.



          In the above commands, the -u flag is short for --unit, and specifies the name of the unit in which you're interested. -b is short for --boot, and restricts the output to only the current boot so that you don't see lots of older messages. See the journalctl man page for more information.






          share|improve this answer


















          • 16




            appending --no-pager will print full log, so you wont have to scroll
            – Dushyant Bangal
            May 29 '17 at 11:41






          • 21




            appending -e will start the log at the end removing the need to scroll, but without printing the entire log beforehand.
            – timlyo
            Jul 28 '17 at 14:45






          • 34




            appending -f will follow (print) updates to the log
            – Joe J
            Sep 6 '17 at 17:10







          • 9




            appending --help will let you see all available options
            – Tzafrir
            Mar 26 at 20:14

















          up vote
          8
          down vote













          systemctl can include the complete output of its status listing, without truncation., by adding the -l flag:



          systemctl -l status service-name


          -l: don't truncate entries with ellipses (...)



          --no-pager can be added to avoid invoking a pager when the output is an interactive terminal.






          share|improve this answer


















          • 6




            Could you explicit your answer somehow? Adding some explanation about the options, and don't hesitate to format your answer!
            – joH1
            Jan 24 at 10:20










          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',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          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%2funix.stackexchange.com%2fquestions%2f225401%2fhow-to-see-full-log-from-systemctl-status-service%23new-answer', 'question_page');

          );

          Post as a guest






























          2 Answers
          2






          active

          oldest

          votes








          2 Answers
          2






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          277
          down vote



          accepted










          Just use the journalctl command, as in:



          journalctl -u service-name.service


          Or, to see only log messages for the current boot:



          journalctl -u service-name.service -b


          For things named <something>.service, you can actually just use <something>, as in:



          journalctl -u service-name


          But for other sorts of units (sockets, targets, timers, etc), you need to be explicit.



          In the above commands, the -u flag is short for --unit, and specifies the name of the unit in which you're interested. -b is short for --boot, and restricts the output to only the current boot so that you don't see lots of older messages. See the journalctl man page for more information.






          share|improve this answer


















          • 16




            appending --no-pager will print full log, so you wont have to scroll
            – Dushyant Bangal
            May 29 '17 at 11:41






          • 21




            appending -e will start the log at the end removing the need to scroll, but without printing the entire log beforehand.
            – timlyo
            Jul 28 '17 at 14:45






          • 34




            appending -f will follow (print) updates to the log
            – Joe J
            Sep 6 '17 at 17:10







          • 9




            appending --help will let you see all available options
            – Tzafrir
            Mar 26 at 20:14














          up vote
          277
          down vote



          accepted










          Just use the journalctl command, as in:



          journalctl -u service-name.service


          Or, to see only log messages for the current boot:



          journalctl -u service-name.service -b


          For things named <something>.service, you can actually just use <something>, as in:



          journalctl -u service-name


          But for other sorts of units (sockets, targets, timers, etc), you need to be explicit.



          In the above commands, the -u flag is short for --unit, and specifies the name of the unit in which you're interested. -b is short for --boot, and restricts the output to only the current boot so that you don't see lots of older messages. See the journalctl man page for more information.






          share|improve this answer


















          • 16




            appending --no-pager will print full log, so you wont have to scroll
            – Dushyant Bangal
            May 29 '17 at 11:41






          • 21




            appending -e will start the log at the end removing the need to scroll, but without printing the entire log beforehand.
            – timlyo
            Jul 28 '17 at 14:45






          • 34




            appending -f will follow (print) updates to the log
            – Joe J
            Sep 6 '17 at 17:10







          • 9




            appending --help will let you see all available options
            – Tzafrir
            Mar 26 at 20:14












          up vote
          277
          down vote



          accepted







          up vote
          277
          down vote



          accepted






          Just use the journalctl command, as in:



          journalctl -u service-name.service


          Or, to see only log messages for the current boot:



          journalctl -u service-name.service -b


          For things named <something>.service, you can actually just use <something>, as in:



          journalctl -u service-name


          But for other sorts of units (sockets, targets, timers, etc), you need to be explicit.



          In the above commands, the -u flag is short for --unit, and specifies the name of the unit in which you're interested. -b is short for --boot, and restricts the output to only the current boot so that you don't see lots of older messages. See the journalctl man page for more information.






          share|improve this answer














          Just use the journalctl command, as in:



          journalctl -u service-name.service


          Or, to see only log messages for the current boot:



          journalctl -u service-name.service -b


          For things named <something>.service, you can actually just use <something>, as in:



          journalctl -u service-name


          But for other sorts of units (sockets, targets, timers, etc), you need to be explicit.



          In the above commands, the -u flag is short for --unit, and specifies the name of the unit in which you're interested. -b is short for --boot, and restricts the output to only the current boot so that you don't see lots of older messages. See the journalctl man page for more information.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Jun 14 at 14:08

























          answered Aug 25 '15 at 15:44









          larsks

          10.2k32739




          10.2k32739







          • 16




            appending --no-pager will print full log, so you wont have to scroll
            – Dushyant Bangal
            May 29 '17 at 11:41






          • 21




            appending -e will start the log at the end removing the need to scroll, but without printing the entire log beforehand.
            – timlyo
            Jul 28 '17 at 14:45






          • 34




            appending -f will follow (print) updates to the log
            – Joe J
            Sep 6 '17 at 17:10







          • 9




            appending --help will let you see all available options
            – Tzafrir
            Mar 26 at 20:14












          • 16




            appending --no-pager will print full log, so you wont have to scroll
            – Dushyant Bangal
            May 29 '17 at 11:41






          • 21




            appending -e will start the log at the end removing the need to scroll, but without printing the entire log beforehand.
            – timlyo
            Jul 28 '17 at 14:45






          • 34




            appending -f will follow (print) updates to the log
            – Joe J
            Sep 6 '17 at 17:10







          • 9




            appending --help will let you see all available options
            – Tzafrir
            Mar 26 at 20:14







          16




          16




          appending --no-pager will print full log, so you wont have to scroll
          – Dushyant Bangal
          May 29 '17 at 11:41




          appending --no-pager will print full log, so you wont have to scroll
          – Dushyant Bangal
          May 29 '17 at 11:41




          21




          21




          appending -e will start the log at the end removing the need to scroll, but without printing the entire log beforehand.
          – timlyo
          Jul 28 '17 at 14:45




          appending -e will start the log at the end removing the need to scroll, but without printing the entire log beforehand.
          – timlyo
          Jul 28 '17 at 14:45




          34




          34




          appending -f will follow (print) updates to the log
          – Joe J
          Sep 6 '17 at 17:10





          appending -f will follow (print) updates to the log
          – Joe J
          Sep 6 '17 at 17:10





          9




          9




          appending --help will let you see all available options
          – Tzafrir
          Mar 26 at 20:14




          appending --help will let you see all available options
          – Tzafrir
          Mar 26 at 20:14












          up vote
          8
          down vote













          systemctl can include the complete output of its status listing, without truncation., by adding the -l flag:



          systemctl -l status service-name


          -l: don't truncate entries with ellipses (...)



          --no-pager can be added to avoid invoking a pager when the output is an interactive terminal.






          share|improve this answer


















          • 6




            Could you explicit your answer somehow? Adding some explanation about the options, and don't hesitate to format your answer!
            – joH1
            Jan 24 at 10:20














          up vote
          8
          down vote













          systemctl can include the complete output of its status listing, without truncation., by adding the -l flag:



          systemctl -l status service-name


          -l: don't truncate entries with ellipses (...)



          --no-pager can be added to avoid invoking a pager when the output is an interactive terminal.






          share|improve this answer


















          • 6




            Could you explicit your answer somehow? Adding some explanation about the options, and don't hesitate to format your answer!
            – joH1
            Jan 24 at 10:20












          up vote
          8
          down vote










          up vote
          8
          down vote









          systemctl can include the complete output of its status listing, without truncation., by adding the -l flag:



          systemctl -l status service-name


          -l: don't truncate entries with ellipses (...)



          --no-pager can be added to avoid invoking a pager when the output is an interactive terminal.






          share|improve this answer














          systemctl can include the complete output of its status listing, without truncation., by adding the -l flag:



          systemctl -l status service-name


          -l: don't truncate entries with ellipses (...)



          --no-pager can be added to avoid invoking a pager when the output is an interactive terminal.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited 2 mins ago









          Dan Farrell

          1053




          1053










          answered Jan 24 at 9:56









          Julien

          9711




          9711







          • 6




            Could you explicit your answer somehow? Adding some explanation about the options, and don't hesitate to format your answer!
            – joH1
            Jan 24 at 10:20












          • 6




            Could you explicit your answer somehow? Adding some explanation about the options, and don't hesitate to format your answer!
            – joH1
            Jan 24 at 10:20







          6




          6




          Could you explicit your answer somehow? Adding some explanation about the options, and don't hesitate to format your answer!
          – joH1
          Jan 24 at 10:20




          Could you explicit your answer somehow? Adding some explanation about the options, and don't hesitate to format your answer!
          – joH1
          Jan 24 at 10:20

















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f225401%2fhow-to-see-full-log-from-systemctl-status-service%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          How to check contact read email or not when send email to Individual?

          Displaying single band from multi-band raster using QGIS

          How many registers does an x86_64 CPU actually have?