Project

General

Profile

Bug #16677

Journal size is too small when booting with the "debug" boot option

Added by segfault 7 months ago. Updated 4 months ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:
Greeter

Description

After seeing #12373, I expected to see debug messages from the greeter in the journal when booting Tails with the "debug" kernel command line option, but I don't see any messages from the greeter in the journal, not even tails-greeter is ready. which should be logged with the INFO level (which should be the default level if I interpret data/tails-logging.conf correctly). Am I doing something wrong?

Screenshot_tails-amd64-bugfix_13438-parts-of-greeter-translation-not-applied-3.14-20190425T1757Z-60cfe544f9.iso_2019-04-28_13_04_47.png View - Few log lines (unexpected) (113 KB) segfault, 04/28/2019 02:10 PM

Screenshot_tails-amd64-bugfix_13438-parts-of-greeter-translation-not-applied-3.14-20190425T1757Z-60cfe544f9.iso_2019-04-28_16_08_38.png View - Many log lines (as expected) (185 KB) segfault, 04/28/2019 02:10 PM

Screenshot_tails-amd64-tmp-13438-16337-3.14-20190427T1818Z-f8fda11d94.img_2019-04-28_12_44_37.png View - No greeter logs at all (that's the boot I created this ticket for) (56.4 KB) segfault, 04/28/2019 02:10 PM


Related issues

Blocks Tails - Feature #16925: Always add "debug nosplash" in troubleshooting mode New

History

#1 Updated by intrigeri 7 months ago

  • Status changed from New to Confirmed
  • Affected tool set to Greeter

#2 Updated by intrigeri 7 months ago

  • Assignee set to segfault
  • QA Check set to Info Needed

On Tails 3.13.1:

  • without passing debug, I see tails-greeter.desktop[3740]: [INFO] tails-greeter.py:127 usermanager_loaded: tails-greeter is ready. in the Journal.
  • when I pass debug, I see lots more debugging messages in the Journal

In both cases, I'm booting from an ISO in a VM, I set a admin password, and in a root terminal I run journalctl | grep -i greeter.

How can I reproduce your findings?

#3 Updated by segfault 7 months ago

intrigeri wrote:

On Tails 3.13.1:

  • without passing debug, I see tails-greeter.desktop[3740]: [INFO] tails-greeter.py:127 usermanager_loaded: tails-greeter is ready. in the Journal.
  • when I pass debug, I see lots more debugging messages in the Journal

In both cases, I'm booting from an ISO in a VM, I set a admin password, and in a root terminal I run journalctl | grep -i greeter.

How can I reproduce your findings?

I also can't reproduce the exact result. But I still sometimes get fewer log lines than expected, see the screenshots. I'm wondering whether this could be due to rate limiting of journald.

#4 Updated by segfault 7 months ago

  • Assignee deleted (segfault)
  • QA Check deleted (Info Needed)

#5 Updated by segfault 7 months ago

  • Subject changed from Greeter doesn't write logs to Journal sometimes misses log lines

#6 Updated by segfault 7 months ago

Now I noticed that on one machine which had the greeter lines, a few minutes later they were gone.

It seems like journald deleted the old logs because the maximum disk space was exceeded. The maximum disk space for journald is 10% of the filesystem that stores the logs. In Tails, that filesystem is /run. On my system, /run is mounted with a 200 MB tmpfs, so journald has 20 MB for logs. That doesn't seem to be enough when booting with debug, because it's used up after a short time.

#7 Updated by segfault 7 months ago

We could consider storing the logs in /var/log instead of /run/log, by setting Storage=persistent or by creating the /var/log/journal directory, which will cause the default setting Storage=auto to use this directory instead of /run/log (see man journald.conf). In my VM, that would increase the maximum size for logs from 20 MB to 100 MB.

#8 Updated by intrigeri 6 months ago

  • Subject changed from Journal sometimes misses log lines to Journal size is too small when booting with the "debug" boot option

#9 Updated by sajolida 4 months ago

  • Blocks Feature #16925: Always add "debug nosplash" in troubleshooting mode added

#10 Updated by sajolida 4 months ago

Solving this ticket would make it possible to simplify a lot the troubleshooting instructions that we have in "Tails is not starting entirely", see #16925.

Also available in: Atom PDF