Red Hat Bugzilla – Bug 988231
GDM fails to start because of journal
Last modified: 2013-10-15 09:15:31 EDT
Description of problem:
On Fedora 19, sometimes GDM refuses to start on bootup but it works after removing /var/log/journal. Other people have similar problems:
It is not clear what lead to this error, but the X log file for GDM mentions an IO Error 11, but does not specify for which resource.
Do you use the btrfs filesystem?
(In reply to Michal Schmidt from comment #1)
> Do you use the btrfs filesystem?
Additional information: It is a system upgraded from F18 to F19 and the bug appeared recently.
Also after logging in as root and running "systemctl restart gdm", gdm started without problems.
this might be a duplicate of bug 987242
Please provide the output of "journalctl -b" when this happens and attach it to this bug!
(In reply to Lennart Poettering from comment #5)
> Please provide the output of "journalctl -b" when this happens and attach it
> to this bug!
I believe the broken journal was deleted, therefore the error cannot reproduced on the affected system.
Created attachment 787071 [details]
output of journalctl -b
I had this issue, I ran journalctl -b and save the output. removing the /var/log/journal directory solved the boot timeout issue for me as well. Hope it helps
FWIW, bug 985038, bug 967521, bug 970801, and bug 987242 are all duplicates.
In my case, it started after a Fedora 18 -> 19 upgrade.
Thanks for your attention to this issue.
I'm noticing "boot slow down" when journaling is enabled and when /var/log/journal exists.
I attach below plots from "systemd-analyze plot" for 2 consecutive boots (same kernel, same packages, same ...), the only difference being that I moved /var/log/journal to /var/log/journal.old.
The difference was striking: the first boot (with journal) took 46 seconds; the second boot (with journal moved to journal.old) took 22 seconds.
Although the first plot shows the "missing 24 seconds", I can't figure out where the time went.
Besides this (graphical) output, what info can I provide that would be helpful?
Created attachment 794548 [details]
Output of "systemd-analyze plot" of system with /var/log/journal
Created attachment 794549 [details]
Output of "systemd-analyze plot" of system without /var/log/journal
(In reply to Tom London from comment #10)
> Created attachment 794548 [details]
> Output of "systemd-analyze plot" of system with /var/log/journal
Wow.. please boot with "systemd.log_level=debug" on the kernel command line.
Then, when you are booted attach the output of:
# journalctl -o short-monotonic -ab
oh, btw, are you running on a 32bit or 64bit kernel?
pushed some journal fixes in systemd-206-11
Similar issue with plymouth-quit-wait.service failing happens here too. Probably removing the journal directory un-triggers the race condition between plymouth and gdm, and is not the real issue.
*** This bug has been marked as a duplicate of bug 967521 ***
(In reply to Harald Hoyer from comment #13)
> oh, btw, are you running on a 32bit or 64bit kernel?
64 bit: kernel-3.12.0-0.rc0.git11.2.fc21.x86_64
Believe this has been occurring for quite some time however (months...).
I am having this on F20,
and plymouth is not installed
Xfce fully updated, lightdm.
(In reply to Frank Murphy from comment #17)
> I am having this on F20,
> and plymouth is not installed
> No btrfs
> Xfce fully updated, lightdm.
Apologies, ignore above. added to wrong bz.