|
Bugzilla – Full Text Bug Listing |
| Summary: | systemd: long boot pause due to systemd-kmsg-syslog.service | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 12.1 | Reporter: | Stefan Seyfried <seife> |
| Component: | Basesystem | Assignee: | Frederic Crozat <fcrozat> |
| Status: | VERIFIED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Minor | ||
| Priority: | P5 - None | CC: | fcrozat |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Third Party Developer/Partner | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
"systemd-analyze plot > plot3.svg"
dmesg after boot with systemd.log_level=debug systemd.log_target=kmsg |
||
please boot with systemd.log_level=debug systemd.log_target=kmsg and attach dmesg output 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... Created attachment 462966 [details]
dmesg after boot with systemd.log_level=debug systemd.log_target=kmsg
here it is...
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 :-) 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. |
Created attachment 462446 [details] "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?