Bug 799872

Summary: Error "Failed to start Console System Startup Logging." appears after reboot following first stage of installation
Product: [openSUSE] openSUSE 12.3 Reporter: Martin Pluskal <mpluskal>
Component: InstallationAssignee: E-mail List <yast2-maintainers>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None CC: fcrozat, tgoettlicher
Version: RC 1   
Target Milestone: ---   
Hardware: x86-64   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: YaST/y2log, boot.log and messages

Description Martin Pluskal 2013-01-22 13:45:24 UTC
Created attachment 521356 [details]
YaST/y2log, boot.log and messages

Steps to reproduce:
1) Start installation via network (PXE boot on x86_64 uefi machine) with usessh=1 an Y2DEBUG=1
2) After first stage of installation is finished (with issues described in 799669)reboot
3) Booting from hdd stops with following error:
systemctl status console-kit-log-system-start.service

Additional info:
It is not possible to reach machine via network (although I tried rcnetwork restart && rcsshd restart).
Comment 1 Martin Pluskal 2013-01-22 13:47:38 UTC
Full error is:
Failed to start Console System Startup Logging.
See 'systemctl status console-kit-log-system-start.service' for details.

I am able to continue boot after I hit ctrl-c (without networking etc. as described above)
Comment 2 Martin Pluskal 2013-02-07 17:29:51 UTC
It is definitely happening during first boot after installation (after stage 1 is finished) and during first boot after upgrade.

Once I finish stage installation and reboot, or in case of upgrade follow this sequence - upgrade && reboot && reboot, everything works properly.
Comment 3 Frederic Crozat 2013-02-20 15:45:38 UTC
This is not a problem, the service doesn't start because the directory doesn't exist at first boot. Moreover, ConsoleKit is almost dead, these days ;)

PS: it is not a systemd issue :)
Comment 4 Thomas Göttlicher 2013-02-22 17:05:07 UTC
The network problem is most likely bnc #800365.

*** This bug has been marked as a duplicate of bug 800365 ***
Comment 5 Martin Pluskal 2013-02-22 17:20:07 UTC
(In reply to comment #3)
> This is not a problem, the service doesn't start because the directory doesn't
> exist at first boot. Moreover, ConsoleKit is almost dead, these days ;)
It is problem, since it requires manual interaction during netinst.
> 
> PS: it is not a systemd issue :)
Who says that it is a systemd issue?