Bug 981669

Summary:	Boot Time Increased
Product:	[Fedora] Fedora	Reporter:	Himanshu Garg <hgarg.india>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	19	CC:	johannbg, lnykryn, msekleta, notting, plautrba, systemd-maint, vpavlin, zbyszek
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-13 03:21:18 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Himanshu Garg 2013-07-05 12:48:18 UTC

Description of problem:
After upgrading to Fedora 19 from Fedora 18 using Fedup, additional things have started coming up during boot time which has increased the boot time to over 40 seconds.

Version-Release number of selected component (if applicable): systemd-204-9.fc19.x86_64


How reproducible:


Steps to Reproduce:
1. Boot system
2.
3.

Actual results:

Things come up at boot time.

(1 of 4) A start job is running for firewalld - dynamic firewall daemon

(2 of 4) A start job is running for Wait for Plymouth Boot Screen to Quit

(3 of 4) A start job is running for LSB: Automatically install DKMS modules for new kernels

(4 of 4) A start job is running for Accounts Service

Failed to start Wait for Plymouth Boot Screen to Quit.
See 'systemctl status plymouth-quit-wait.service' for details

Expected results: Boot shoudl be continuous.


Additional info:  After all these, I am able to login but these are causing a lot of wait at boot.

Comment 1 Jóhann B. Guðmundsson 2013-07-05 13:06:11 UTC

Most likely this one "Automatically install DKMS modules for new kernels
"  is causing that delay but in any case please file reports against each service that's causing the delay not systemd. 

You can find out which ones those are by opening a terminal window and run "systemd-analyze blame" and the respectful maintainers that own those components will look at it.

Comment 2 Himanshu Garg 2013-07-10 03:26:29 UTC

I found that on renaming /var/log/journal to /var/log/journal.org, I found no such problem and my boot time is like before.

Comment 3 Lennart Poettering 2013-09-13 03:21:18 UTC

Sounds like 983688

*** This bug has been marked as a duplicate of bug 983688 ***