[Bug 730776] New: systemd: long boot pause due to systemd-kmsg-syslog.service
https://bugzilla.novell.com/show_bug.cgi?id=730776 https://bugzilla.novell.com/show_bug.cgi?id=730776#c0 Summary: systemd: long boot pause due to systemd-kmsg-syslog.service Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: seife@novell.slipkontur.de QAContact: qa@suse.de CC: fcrozat@suse.com Found By: Third Party Developer/Partner Blocker: --- Created an attachment (id=462446) --> (http://bugzilla.novell.com/attachment.cgi?id=462446) "systemd-analyze plot > plot3.svg" I updated a 11.4 server to 12.1 which switched from sysv init to systemd. Everything went well - great job. I had to reenable apache2 service, but that's all. However, the system is not booting fast. It is, in fact, slower than before. Much slower: server:~ # systemd-analyze Startup finished in 4151ms (kernel) + 100588ms (userspace) = 104740ms I looked and found that it waits about 80 seconds for systemd-kmsg-syslog.service to finish. See the attached svg. It's really doing nothing during most of that time (no disk access e.g.). CPU is a 2.66GHz core2 duo with 6GB RAM - no way this CPU needs 80 seconds to boot the system ;-) I already tried: * add "quiet" to kernel options (because this is an update, it was not added) I was guessing that lots of kernel messages bog down the service. * switch from syslog-ng to rsyslog both made no real difference. Any ideas what to try next? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=730776 https://bugzilla.novell.com/show_bug.cgi?id=730776#c1 --- Comment #1 from Frederic Crozat <fcrozat@suse.com> 2011-11-17 15:17:09 UTC --- please boot with systemd.log_level=debug systemd.log_target=kmsg and attach dmesg output -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=730776 https://bugzilla.novell.com/show_bug.cgi?id=730776#c2 --- Comment #2 from Stefan Seyfried <seife@novell.slipkontur.de> 2011-11-17 19:47:02 CET --- can I later - withouth rebooting - revert those settings? This machine is somewhat productive, so rebooting it too often is not an option, especially if it naps for a long time during boot ;-) OTOH, permanently running the machine with debug log is probably also not a good idea... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=730776 https://bugzilla.novell.com/show_bug.cgi?id=730776#c3 --- Comment #3 from Stefan Seyfried <seife@novell.slipkontur.de> 2011-11-18 18:56:31 CET --- Created an attachment (id=462966) --> (http://bugzilla.novell.com/attachment.cgi?id=462966) dmesg after boot with systemd.log_level=debug systemd.log_target=kmsg here it is... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=730776 https://bugzilla.novell.com/show_bug.cgi?id=730776#c4 --- Comment #4 from Stefan Seyfried <seife@novell.slipkontur.de> 2011-11-18 19:03:20 CET --- Ok. Got it. [ 20.048404] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus /Local [ 95.716485] systemd[1]: Job dev-disk-by\x2did-ata\x2dFUJITSU_MHZ2320BH_G2_K60LT912RPY6\x2dpart1.device/start timed out. And - voila. After exchanging the disk, the fstab entry of the swap partititon was not updated. Never noticed because the box has enough RAM ;-) But systemd was waiting for the device to show up. Would there have been a way to find this out only with systemctl? without the debug reboot? Anyway, we can probably close this bug :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=730776 https://bugzilla.novell.com/show_bug.cgi?id=730776#c Andreas Jaeger <aj@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |fcrozat@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=730776 https://bugzilla.novell.com/show_bug.cgi?id=730776#c5 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |INVALID --- Comment #5 from Frederic Crozat <fcrozat@suse.com> 2011-11-29 09:59:42 UTC --- I've just checked and this error message is visible in dmesg output without any debug flag (but not in systemctl output nor /var/log/message, unfortunately). closing but as invalid. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com