commit e4ad7d6fc7047ba322aea64a846f7781129aa508 · pyrox.dev/nixpkgs

+38

nixos/doc/manual/administration/logging.chapter.md

···

       1
       1
       +
       # Logging {#sec-logging}

     

       2
       2
       +
       

     

       3
       3
       +
       System-wide logging is provided by systemd's *journal*, which subsumes

     

       4
       4
       +
       traditional logging daemons such as syslogd and klogd. Log entries are

     

       5
       5
       +
       kept in binary files in `/var/log/journal/`. The command `journalctl`

     

       6
       6
       +
       allows you to see the contents of the journal. For example,

     

       7
       7
       +
       

     

       8
       8
       +
       ```ShellSession

     

       9
       9
       +
       $ journalctl -b

     

       10
       10
       +
       ```

     

       11
       11
       +
       

     

       12
       12
       +
       shows all journal entries since the last reboot. (The output of

     

       13
       13
       +
       `journalctl` is piped into `less` by default.) You can use various

     

       14
       14
       +
       options and match operators to restrict output to messages of interest.

     

       15
       15
       +
       For instance, to get all messages from PostgreSQL:

     

       16
       16
       +
       

     

       17
       17
       +
       ```ShellSession

     

       18
       18
       +
       $ journalctl -u postgresql.service

     

       19
       19
       +
       -- Logs begin at Mon, 2013-01-07 13:28:01 CET, end at Tue, 2013-01-08 01:09:57 CET. --

     

       20
       20
       +
       ...

     

       21
       21
       +
       Jan 07 15:44:14 hagbard postgres[2681]: [2-1] LOG:  database system is shut down

     

       22
       22
       +
       -- Reboot --

     

       23
       23
       +
       Jan 07 15:45:10 hagbard postgres[2532]: [1-1] LOG:  database system was shut down at 2013-01-07 15:44:14 CET

     

       24
       24
       +
       Jan 07 15:45:13 hagbard postgres[2500]: [1-1] LOG:  database system is ready to accept connections

     

       25
       25
       +
       ```

     

       26
       26
       +
       

     

       27
       27
       +
       Or to get all messages since the last reboot that have at least a

     

       28
       28
       +
       "critical" severity level:

     

       29
       29
       +
       

     

       30
       30
       +
       ```ShellSession

     

       31
       31
       +
       $ journalctl -b -p crit

     

       32
       32
       +
       Dec 17 21:08:06 mandark sudo[3673]: pam_unix(sudo:auth): auth could not identify password for [alice]

     

       33
       33
       +
       Dec 29 01:30:22 mandark kernel[6131]: [1053513.909444] CPU6: Core temperature above threshold, cpu clock throttled (total events = 1)

     

       34
       34
       +
       ```

     

       35
       35
       +
       

     

       36
       36
       +
       The system journal is readable by root and by users in the `wheel` and

     

       37
       37
       +
       `systemd-journal` groups. All users have a private journal that can be

     

       38
       38
       +
       read using `journalctl`.

-43

nixos/doc/manual/administration/logging.xml

···

       1
       1
       -
       <chapter xmlns="http://docbook.org/ns/docbook"

     

       2
       2
       -
               xmlns:xlink="http://www.w3.org/1999/xlink"

     

       3
       3
       -
               xmlns:xi="http://www.w3.org/2001/XInclude"

     

       4
       4
       -
               version="5.0"

     

       5
       5
       -
               xml:id="sec-logging">

     

       6
       6
       -
        <title>Logging</title>

     

       7
       7
       -
        <para>

     

       8
       8
       -
         System-wide logging is provided by systemd’s <emphasis>journal</emphasis>,

     

       9
       9
       -
         which subsumes traditional logging daemons such as syslogd and klogd. Log

     

       10
       10
       -
         entries are kept in binary files in <filename>/var/log/journal/</filename>.

     

       11
       11
       -
         The command <literal>journalctl</literal> allows you to see the contents of

     

       12
       12
       -
         the journal. For example,

     

       13
       13
       -
       <screen>

     

       14
       14
       -
       <prompt>$ </prompt>journalctl -b

     

       15
       15
       -
       </screen>

     

       16
       16
       -
         shows all journal entries since the last reboot. (The output of

     

       17
       17
       -
         <command>journalctl</command> is piped into <command>less</command> by

     

       18
       18
       -
         default.) You can use various options and match operators to restrict output

     

       19
       19
       -
         to messages of interest. For instance, to get all messages from PostgreSQL:

     

       20
       20
       -
       <screen>

     

       21
       21
       -
       <prompt>$ </prompt>journalctl -u postgresql.service

     

       22
       22
       -
       -- Logs begin at Mon, 2013-01-07 13:28:01 CET, end at Tue, 2013-01-08 01:09:57 CET. --

     

       23
       23
       -
       ...

     

       24
       24
       -
       Jan 07 15:44:14 hagbard postgres[2681]: [2-1] LOG:  database system is shut down

     

       25
       25
       -
       -- Reboot --

     

       26
       26
       -
       Jan 07 15:45:10 hagbard postgres[2532]: [1-1] LOG:  database system was shut down at 2013-01-07 15:44:14 CET

     

       27
       27
       -
       Jan 07 15:45:13 hagbard postgres[2500]: [1-1] LOG:  database system is ready to accept connections

     

       28
       28
       -
       </screen>

     

       29
       29
       -
         Or to get all messages since the last reboot that have at least a

     

       30
       30
       -
         “critical” severity level:

     

       31
       31
       -
       <screen>

     

       32
       32
       -
       <prompt>$ </prompt>journalctl -b -p crit

     

       33
       33
       -
       Dec 17 21:08:06 mandark sudo[3673]: pam_unix(sudo:auth): auth could not identify password for [alice]

     

       34
       34
       -
       Dec 29 01:30:22 mandark kernel[6131]: [1053513.909444] CPU6: Core temperature above threshold, cpu clock throttled (total events = 1)

     

       35
       35
       -
       </screen>

     

       36
       36
       -
        </para>

     

       37
       37
       -
        <para>

     

       38
       38
       -
         The system journal is readable by root and by users in the

     

       39
       39
       -
         <literal>wheel</literal> and <literal>systemd-journal</literal> groups. All

     

       40
       40
       -
         users have a private journal that can be read using

     

       41
       41
       -
         <command>journalctl</command>.

     

       42
       42
       -
        </para>

     

       43
       43
       -
       </chapter>

+1 -1

nixos/doc/manual/administration/running.xml

···

       14
       14
        
        <xi:include href="../from_md/administration/rebooting.chapter.xml" />

     

       15
       15
        
        <xi:include href="../from_md/administration/user-sessions.chapter.xml" />

     

       16
       16
        
        <xi:include href="../from_md/administration/control-groups.chapter.xml" />

     

       17
       17
       -
        <xi:include href="logging.xml" />

     

       17
       17
       +
        <xi:include href="../from_md/administration/logging.chapter.xml" />

     

       18
       18
        
        <xi:include href="cleaning-store.xml" />

     

       19
       19
        
        <xi:include href="containers.xml" />

     

       20
       20
        
        <xi:include href="troubleshooting.xml" />

+45

nixos/doc/manual/from_md/administration/logging.chapter.xml

···

       1
       1
       +
       <chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xml:id="sec-logging">

     

       2
       2
       +
         <title>Logging</title>

     

       3
       3
       +
         <para>

     

       4
       4
       +
           System-wide logging is provided by systemd’s

     

       5
       5
       +
           <emphasis>journal</emphasis>, which subsumes traditional logging

     

       6
       6
       +
           daemons such as syslogd and klogd. Log entries are kept in binary

     

       7
       7
       +
           files in <literal>/var/log/journal/</literal>. The command

     

       8
       8
       +
           <literal>journalctl</literal> allows you to see the contents of the

     

       9
       9
       +
           journal. For example,

     

       10
       10
       +
         </para>

     

       11
       11
       +
         <programlisting>

     

       12
       12
       +
       $ journalctl -b

     

       13
       13
       +
       </programlisting>

     

       14
       14
       +
         <para>

     

       15
       15
       +
           shows all journal entries since the last reboot. (The output of

     

       16
       16
       +
           <literal>journalctl</literal> is piped into <literal>less</literal>

     

       17
       17
       +
           by default.) You can use various options and match operators to

     

       18
       18
       +
           restrict output to messages of interest. For instance, to get all

     

       19
       19
       +
           messages from PostgreSQL:

     

       20
       20
       +
         </para>

     

       21
       21
       +
         <programlisting>

     

       22
       22
       +
       $ journalctl -u postgresql.service

     

       23
       23
       +
       -- Logs begin at Mon, 2013-01-07 13:28:01 CET, end at Tue, 2013-01-08 01:09:57 CET. --

     

       24
       24
       +
       ...

     

       25
       25
       +
       Jan 07 15:44:14 hagbard postgres[2681]: [2-1] LOG:  database system is shut down

     

       26
       26
       +
       -- Reboot --

     

       27
       27
       +
       Jan 07 15:45:10 hagbard postgres[2532]: [1-1] LOG:  database system was shut down at 2013-01-07 15:44:14 CET

     

       28
       28
       +
       Jan 07 15:45:13 hagbard postgres[2500]: [1-1] LOG:  database system is ready to accept connections

     

       29
       29
       +
       </programlisting>

     

       30
       30
       +
         <para>

     

       31
       31
       +
           Or to get all messages since the last reboot that have at least a

     

       32
       32
       +
           <quote>critical</quote> severity level:

     

       33
       33
       +
         </para>

     

       34
       34
       +
         <programlisting>

     

       35
       35
       +
       $ journalctl -b -p crit

     

       36
       36
       +
       Dec 17 21:08:06 mandark sudo[3673]: pam_unix(sudo:auth): auth could not identify password for [alice]

     

       37
       37
       +
       Dec 29 01:30:22 mandark kernel[6131]: [1053513.909444] CPU6: Core temperature above threshold, cpu clock throttled (total events = 1)

     

       38
       38
       +
       </programlisting>

     

       39
       39
       +
         <para>

     

       40
       40
       +
           The system journal is readable by root and by users in the

     

       41
       41
       +
           <literal>wheel</literal> and <literal>systemd-journal</literal>

     

       42
       42
       +
           groups. All users have a private journal that can be read using

     

       43
       43
       +
           <literal>journalctl</literal>.

     

       44
       44
       +
         </para>

     

       45
       45
       +
       </chapter>