Logs persistence

The logs are not persisted on reboot and will therefore be lost.

By default, logs are stored to RAM and are not kept over a reboot. This is because intensive logging on persistent memory (NAND memory) will reduce the longevity of the memory.

If you need persistent logging, please check the Persisting logs page.

10MB of the RAM is reserved for logs. This means that logs are not eternal and are erased after some time. This is done by logrotate depending on the configuration of /etc/logrotate.d/logs.

Consult the logs

You can access the logs through the System > Logs page.

  1. Log files list. This panel will expand on hover/click.
    1. Click on a file to make it the actively displayed log.
    2. Click on the refresh button in the files panel to refresh the files list.
  2. Name of the log currently displayed
  3. Filters and search
    1. Click on the filter button on the right to clear all filters
  4. Heading
    1. Click on the Time column header to sort in reverse order
  5. Logs main view panel
    1. Click on a date to set it as a reference date and see the offset with other event. Click on the cross that will appear near (9) to clear.
    2. Click on a service label to filter by this service
  6. Refresh the logs of the active file
  7. Show dates as ISO (toggle)
  8. Wrap lines (toggle)
  9. Export the active log as CSV/JSON
  10. Pagination

The logs are not refreshed automatically, use the refresh button to refresh a single file.

The logs are store in the  /var/log/messages file.

You can display the logs using less:

less /var/log/messages
BASH

You can also displaying in live new incoming messages with tail:

tail -F /var/log/messages
BASH

To avoid too large files, a new file is created when it reaches 200KB. The old file is automatically renamed with an index as suffix. After some time, you may have:

lorix-one-0b98c9:~$ ll /var/log/messages*
-rw-r--r--    1 root     root         59742 Dec 13 17:15 /var/log/messages
-rw-r--r--    1 root     root        204867 Dec 13 17:04 /var/log/messages.0
-rw-r--r--    1 root     root        204922 Dec 13 16:19 /var/log/messages.1
-rw-r--r--    1 root     root        204850 Dec 13 15:35 /var/log/messages.2
-rw-r--r--    1 root     root        204961 Dec 13 14:59 /var/log/messages.3
-rw-r--r--    1 root     root        204932 Dec 13 14:21 /var/log/messages.4
-rw-r--r--    1 root     root        204843 Dec 13 13:43 /var/log/messages.5
-rw-r--r--    1 root     root        204865 Dec 13 13:02 /var/log/messages.6
-rw-r--r--    1 root     root        204860 Dec 13 12:18 /var/log/messages.7
-rw-r--r--    1 root     root        204945 Dec 13 11:34 /var/log/messages.8
-rw-r--r--    1 root     root        204863 Dec 13 10:50 /var/log/messages.9

Inconsistent chronological order

If you have a log that does not follow a correct chronological order regarding the date/time information (for example steps of multiple hours at some moments) it is probably related to timezone change.

The time information in the logs has no timezone information. So when you change the timezone, the new logs can appear "before" regarding the time information. Keep in mind that the display order is always the correct chronological order.