Sudden increase in boot time.

My boot time has suddenly increased by about 30 secs (probably after a recent zypper dup). I’m running KDE 4.7.4 (release 11) from KR47 and kernel 3.1.0-1.2 desktop x86.

If I use ESC to look at the boot as it happens, we get to the line -

systemd-fsck[748]: /dev/sda3: clean, 18001/5890048 files, 13818367/23535872 blocks

Then there is the 30s delay before the boot completes.

I was hoping to find some info in /var/log/boot.msg but the file is missing.

Has anybody else seen this? Any ideas?

EDIT: Sudden thought - how do I switch to systemv

Switching to system V is done like this:

Start Yast - Software - Software Manager
Search for sysvinit
Check “sysvinit-init” for install. It will tell you “systemd-sysvinit” has to be uninstalled. Accept. Reboot, done.

Before worrying about sysremd make sure that you perform an On-Line Update. Most of the systemd problems seem to have been solved in the last 36 hours.

Also remember that fsck is run periodically. See /etc/sysconfig settings.

On 01/08/2012 04:36 PM, petermcph wrote:

> (probably after a recent zypper dup)

i wonder why did you do a “zypper dup” ??

that particular incantation is only useful to upgrade from one version
(like 11.4) to the next higher (like 12.1) or to rescue a system
polluted with conflicting and/or broken software…


DD http://tinyurl.com/DD-Caveat
openSUSE®, the “German Engineered Automobiles” of operating systems!

Peter had upgraded from KDE-4.7.2 to KDE-4.7.4.
The dup option will install a lower numbered version in compliance with a pattern. This is often necessary when changing repositories, and generally safer than up.

On 2012-01-08 17:06, Knurpht wrote:
>
> Switching to system V is done like this:
>
> Start Yast - Software - Software Manager
> Search for sysvinit
> Check “sysvinit-init” for install. It will tell you “systemd-sysvinit”
> has to be uninstalled. Accept. Reboot, done.

Don’t do that, at least not before you know that it works better. Simply
press “F5” at the boot grub screen and choose.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

On 2012-01-08 16:36, petermcph wrote:
>
> My boot time has suddenly increased by about 30 secs (probably after a
> recent zypper dup). I’m running KDE 4.7.4 (release 11) from KR47 and
> kernel 3.1.0-1.2 desktop x86.

Zypper dup? With what repos exactly? Running a dup is asking for trouble,
unless you really know what you are doing.

> I was hoping to find some info in /var/log/boot.msg but the file is
> missing.

In 12.1 with systemD it goes to “messages” instead.

> EDIT: Sudden thought - how do I switch to systemv

F5 at the boot grub screen and choose. Not permanent change.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

On 2012-01-08 16:36, petermcph wrote:
> My boot time has suddenly increased by about 30 secs (probably after a
> recent zypper dup). I’m running KDE 4.7.4 (release 11) from KR47 and
> kernel 3.1.0-1.2 desktop x86.

I forgot. In a terminal, as root, run:


systemd-analyze blame

and find out where the time is spent. Alternatively, you can also do


systemd-analyze plot > p.svg

Then you can use “display p.svg” to see the graphics, or use the tool you
prefer. The graphics shows where time is used.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

That was fixed with the last update.

On 2012-01-08 19:36, eng-int wrote:
>
> robin_listas;2427957 Wrote:
>>
>>> I was hoping to find some info in /var/log/boot.msg but the file is
>>> missing.
>>
>> In 12.1 with systemD it goes to “messages” instead.
>>
> That was fixed with the last update.

No, it wasn’t.


Elanor:~ # l /var/log/boot.msg
-rw-r--r-- 1 root root 95670 Nov 11 03:32 /var/log/boot.msg

See the date? The file was not touched after the last update.

Further, not writing to boot.msg is an intentional feature of systemd. I
wrote bugzilla 732933 on this and was wontfixed, so I know.


Frederic Crozat <> changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
Status|NEW                         |RESOLVED
Resolution|                            |WONTFIX

--- Comment #1 from Frederic Crozat <> 2011-11-29 13:21:59 UTC ---
won't fix, /var/log/boot.msg is not supported by systemd.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

Hi Carlos,

That is weird. Today I updated the kernel, on-line update, edited menu.lst, then rebooted.


valeria:~ # l /var/log/boot*
-rw-r--r-- 1 root root 65266 Jan  8 13:12 /var/log/boot.msg
-rw-r--r-- 1 root root 72729 Jan  8 13:10 /var/log/boot.omsg
valeria:~ # uptime
 18:25pm  up   5:13,  1 user,  load average: 0.00, 0.01, 0.05
valeria:~ # l /boot/grub/menu.lst
-rw------- 1 root root 1148 Jan  8 13:09 /boot/grub/menu.lst
valeria:~ # cat /boot/grub/menu.lst
# Modified by YaST2. Last modification on Sun Jan  8 11:09:39 GMT 2012
# THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader
# For the new kernel it try to figure out old parameters. In case we are not able to recognize it (e.g. change of flavor or strange install order ) it it use as fallback installation parameters from /etc/sysconfig/bootloader

default 0
timeout 8
##YaST - generic_mbr
gfxmenu (hd0,0)/boot/message
##YaST - activate

###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE 12.1 - 3.2.0-1
    root (hd0,0)
    kernel /boot/vmlinuz-3.2.0-1-desktop root=/dev/sda1 resume=/dev/disk/by-id/ata-Maxtor_6L200S0_L50QCYYH-part5 splash=silent quiet showopts vga=0x31a
    initrd /boot/initrd-3.2.0-1-desktop
#init=/sbin/sysvinit

Requires some thinking


ray H

Note the date of this WONTFIX


Frederic Crozat <> changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
Status|NEW                         |RESOLVED
Resolution|                            |WONTFIX

--- Comment #1 from Frederic Crozat <> 2011-11-29 13:21:59 UTC ---
won't fix, /var/log/boot.msg is not supported by systemd.

This was actually fixed along with the RAID incompatibility before Christmass in the systemd build from Frederic’s home repository.

On 2012-01-08 20:56, eng-int wrote:
>
> Note the date of this WONTFIX

I know.
Doesn’t matter. They have no intention to fix it, ever.

> This was actually fixed along with the RAID incompatibility before
> Christmass in the -systemd- build from Frederic’s home repository.

No, it wasn’t. The file is not written. I installed the update today, then
rebooted, and I got no new file.

Show me the the release notes where they say that they create that file now.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

On 2012-01-08 20:36, eng-int wrote:
>
> Hi Carlos,
>
> That is weird. Today I updated the kernel, on-line update, edited
> menu.lst, then rebooted.

Menu.lst is not related at all to /var/log/boot.msg. What are you talking
about?


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

hi

the same here, 30 second delay without disk activity is a bind but stuff is happening.

The 100 second boot time is tolerable but could do better.
(in openSUSE11.2 the boot time used to be about 55 second to the start of kde jingle)

but at least with the 3.2 kernel booting is reliable.

with the last 3.1 kernels, failing to load grub, failing to load kernel modules, failing to reach the login window were not uncommon

this is how the boot time in now made up,

<2012Jan08><20:41><~>  systemd-analyze blame    
mSecs    
5992    cycle.service
5941    media.mount
5921    var-lock.mount
5895    var-run.mount
5785    dev-hugepages.mount
5754    udev-trigger.service
5753    dev-mqueue.mount
5721    sys-kernel-debug.mount
5689    bootsplash-startup.service
5666    sys-kernel-security.mount
5579    udev.service
5517    localnet.service
5516    systemd-remount-api-vfs.service
5515    remount-rootfs.service
4954    xfs.service
3528    systemd-sysctl.service
3403    systemd-vconsole-setup.service
1025    bootsplash-quit.service
504    systemd-readahead-collect.service
473    systemd-readahead-replay.service
401    systemd-logind.service
259    SuSEfirewall2_setup.service
251    systemd-tmpfiles-setup.service
228    syslog.service
140    NetworkManager.service
138    apparmor.service
136    ntp.service
135    console-kit-log-system-start.service
135    auditd.service
133    SuSEfirewall2_init.service
124    dbus.service
116    avahi-daemon.service
108    irq_balancer.service
106    fbset.service
106    smpppd.service
105    cpufreq.service
104    microcode.ctl.service
88    acpid.service
87    systemd-user-sessions.service
86    xdm.service
83    purge-kernels.service
77    rc-local.service
74    cups.service
70    bluez-coldplug.service
59    home.mount
58    gpm.service
52    network-remotefs.service
51    splash_early.service
50    console-kit-daemon.service
42    mcelog.service
41    home-Fuj\x2dSie.mount
39    network.service
37    nscd.service
30    splash.service
27    rpcbind.service
97907    Total

this is just how things are at moment

useing openSUSE12.1 is a pleasure

OS Information
OS: Linux 3.2.0-1-desktop x86_64
Current user: michael@linux-qz4c
System: openSUSE 12.1 (x86_64)
KDE: 4.7.4 (4.7.4) “release 11”

On 01/08/2012 02:43 PM, Carlos E. R. wrote:
> On 2012-01-08 20:56, eng-int wrote:
>>
>> Note the date of this WONTFIX
>
> I know.
> Doesn’t matter. They have no intention to fix it, ever.
>
>> This was actually fixed along with the RAID incompatibility before
>> Christmass in the -systemd- build from Frederic’s home repository.
>
> No, it wasn’t. The file is not written. I installed the update today, then
> rebooted, and I got no new file.
>
> Show me the the release notes where they say that they create that file now.

File /var/log/boot.msg is defunct with systemd. All that info is now written to
/var/log/messages, which is better as it is preserved forever, unlike boot.msg
and boot.omsg, which kept only the current and one previous boot.

Carlos E. R. wrote:

> Menu.lst is not related at all to /var/log/boot.msg. What are you talking
> about?

That sequence demonstrated what I did, and the outcome.

init=/sbin/sysvinit was removed from grub kernel parameters at Jan 8 13:09
the system was shutdown
/var/log/boot.msg finished logging the shutdown at Jan 8 13:10
the systerted was restarted
/var/log/boot.msg was copied to /var/log/boot.omsg and
the startup messages were written to a new /var/log/boot.msg at Jan 8 13:12

I looked in the notice for the recent systemd patch, and did not see anything that seemed relevant


Patch: openSUSE-2012-1 Kind: recommended Version: 1

This update fixes the following issues for systemd: -
722539: Prevent dependency cycle -
724912: Ensure fsck/cryptsetup is run after lvm/md/dmraid have landed -
731358: Fix cron filling logs -
732912: Fix PID warning in logs -
732041: Update modules_on_boot.patch -
731719, 699829: Replace private_tmp_crash.patch with log_on_close.patch,┴better upstream fix for bnc#699829 and fix bnc#731719. -
734527: Update vconsole patch to fix memleaks and crash -
732912: Fix warnings with sendmail -
727771: Support PIDFile: and X-Systemd-RemainAfterExit: header in initscript -
727771: Update bootsplash services to not start if vga= is missing from cmdline -
733523: Disable /var/lock/{subsys,lockdev} and change default permissions on /var/lock -
730496: Add support for crypt file loop - Add libtool as buildrequire to avoid implicit dependency - Ensure swap and mount output is
redirected to default log target - Ensure colored status are displayed at boot time - Ensure error units are correctly garbage
collected

Neither did I notice anything in the previous systemd patch.

Writing to boot.msg is effecred by /etc/init.d/boot.klog


if test -e /dev/shm/initrd.msg ; then
cat /dev/shm/initrd.msg >> /var/log/boot.msg
rm -f /dev/shm/initrd.msg
fi

If this is not a systemd problem, it could lie with initrd. Presumably this is part of the kernel package. Note that the reason for
the 13:10 shutdown was the installation of the 3.2.0 kernel. This system has never had the 3.1.0 kernel as the initial install used
the 3.1.2 kernel and KDE-4.7.3.

Because this machine uses RAID it has only used either Frederic Crozat’s home repository systemd and/or sysvinit.

Larry Finger wrote:

> File /var/log/boot.msg is defunct with systemd. All that info is now
> written to /var/log/messages, which is better as it is preserved forever,
> unlike boot.msg and boot.omsg, which kept only the current and one
> previous boot.

Well my 12.1 systemd system is still writing logs to /log/boot.msg


valeria:~ # l /var/log/boot*
-rw-r--r-- 1 root root 65267 Jan  8 23:58 /var/log/boot.msg
-rw-r--r-- 1 root root 70981 Jan  8 23:56 /var/log/boot.omsg
valeria:~ #

???

eng-int wrote:

> Because this machine uses RAID it has only used either Frederic Crozat’s
> home repository systemd and/or sysvinit.

That is before yesterday’s On-Line Update


rpm -q systemd
systemd-37-3.6.1.x86_64

An interesting discussion! I started this thread because my system files are on a Sata 3 SSD and booting is quite fast. To suddenly see an extra 30 sec delay was annoying to say the least.

I tried the simplest suggestion (ie. F5 switch to systemv) and the 30s delay has gone. Not only that, but I now have a boot.msg file but of course it won’t be updated when I use systemd again (I think).

I also have the latest systemd 37-3.6.1, but my latest check shows that the 30s delay is still there.