Description of problem:
When shutting down I see:
plymouthd: could not log bootup: Address already in use
Version-Release number of selected component (if applicable):
Steps to Reproduce:
I suspect this to be systemd's fault.
Just a note: for me this issue pops up during the bootup sequence (pressing escape during the plymouth bootup splashscreen). Perhaps you're only seeing this message on shutdown because 1) the message was covered up during graphical bootup, and 2) on shutdown you see the console output for a brief moment.
I also suspect this to be a systemd issue, but I have nothing to back that up.
fedora rawhide (15) on virtualbox.
saw this on bootup once and it hung the vm guest
(In reply to comment #2)
> fedora rawhide (15) on virtualbox.
> saw this on bootup once and it hung the vm guest
I boot on runlevel 3. I see the same error message and the vm seems frozen but it's only a problem of this console. After a while I press Alt+F2 and i have a login!
Created attachment 472874 [details]
Screenshot of the fedora 15 vm with the error message
Is the apparent freeze really bug #663703 (no cursor on tty1 when booting in kvm)? Note that the cursor does not disappear when booting with real hardware or after dismissing the plymouth splash screen to view boot messages.
Also, I think /var/log/boot.log is empty in f15 rawhide. I assume this is related?
my /var/log/boot.log is 3 bytes long.
[root@myvboxlinux log]# od -x boot.log
0000000 251b 0047
I'm seeing this too. I disabled graphical boot and I clearly see it at startup, when systemd tries to start "/sbin/plymouthd --mode=boot".
This seems to have been fixed in the meantime (plymouth-0.8.4-0.20101119.2.fc15.x86_64).
(In reply to comment #8)
> This seems to have been fixed in the meantime
Not here - the "could not log bootup" message still appears when booting kde-x86_64-20110122.16.iso in kvm.
This happens when I reboot it the second time after installation.
Reproduced it on i386 as well:
+1 on hitting this error.
I'm not sure this qualifies as an F15Alpha blocker based on current criteria (https://fedoraproject.org/wiki/Fedora_15_Alpha_Release_Criteria). In my experience, while the message is displayed, I am still presented with a graphical login prompt.
Can someone confirm whether you eventually get a graphical login prompt (depending on if you installed the necessary packages)?
For me, graphical login works. Text login works too, though tty1 has no cursor so it appears frozen until you start typing (bug #663703).
Tested on Fedora-15-Alpha-x86_64-Live-KDE.iso with kvm.
(In reply to comment #12)
> +1 on hitting this error.
> I'm not sure this qualifies as an F15Alpha blocker based on current criteria
> (https://fedoraproject.org/wiki/Fedora_15_Alpha_Release_Criteria). In my
> experience, while the message is displayed, I am still presented with a
> graphical login prompt.
> Can someone confirm whether you eventually get a graphical login prompt
> (depending on if you installed the necessary packages)?
I installed Fedora-15-Alpha-i386-DVD.iso with kvm, the graphical login prompted after the message displayed.
I had this issue. I hit Alt+2, and as root, "startx". It complained about not being able to find the vbox driver. So I did as root:
> mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup
This worked for me.
I don't believe we have release criteria that require this issue be resolved at a particular milestone. I'm adding this to the Alpha NICE-TO-HAVE (F15Alpha-accepted) and the BETA blocker (F15Beta). I believe the presence of this issue will impact boot problem determination.
AGREED: 654762 - RejectedNTH. Error message is benign. Update post-alpha systemd resolves issue.
This was caused because systemd ended up starting Plymouth a second time if it was already started from the initrd to support initrd-less boots. This has since been changed in systemd, to not start plymouth a second time, and hence this warning doesn't show up anymore.
So, this bug should probably just be closed.
And it should definitely not be a beta blocker...
(In reply to comment #19)
> And it should definitely not be a beta blocker...
Hey Lennart! Does the presence of this bug cause /var/log/boot.log to be empty? If so, it would be more concerning that an empty log might reduce debugging or problem identification. If it's just cosmetic, I agree it doesn't need to block the beta.
This seems to be fixed on kde-x86_64-20110305.01.iso, i.e.
but /var/log/boot.log is still empty (really empty this time not 3 butes empty as noted in comment #6):
# od -x /var/log/boot.log
(In reply to comment #20)
> (In reply to comment #19)
> > And it should definitely not be a beta blocker...
> Hey Lennart! Does the presence of this bug cause /var/log/boot.log to be
> empty? If so, it would be more concerning that an empty log might reduce
> debugging or problem identification. If it's just cosmetic, I agree it doesn't
> need to block the beta.
No, this bug was purely cosmetic and has been fixed anyway... If /var/log/boot.log is empty, please file a new bug against plymouth.
(In reply to comment #22)
> If /var/log/boot.log is empty, please file a new bug against plymouth.
Filed as bug #683514.
Discussed at 2011-03-11 blocker review meeting. Per Lennart, this bug was purely cosmetic and never was the cause of any of the various serious issues people above attributed to it. :) So it's not a blocker. Lennart also says it should be fixed now, so setting MODIFIED. Reporters, please confirm if you still see the message with up-to-date F15.
(In reply to comment #24)
> Reporters, please confirm if you
> still see the message with up-to-date F15.
See comment #21. (Don't have permissions to mark the bug as fixed otherwise I would do it now).
Thanks Oliver. I'm moving this bug to VERIFIED based on your feedback. We can re-open this issue if the problem resurfaces.
Hasn't happened for a long time now.