You are not logged in.

#1 2013-05-03 17:42:29

citron
Member
Registered: 2013-05-03
Posts: 7

delay at system start

System boot-up used to be fast, < 20 seconds, but now I'm getting a delay, half a minute or more (black screen), nothing seems to happen until finally the LXDE Graphical Interface shows up.

The delay is reflected in the logs, see below.

What might be responsible for the delay?

[root@myhost hmeyer]# journalctl -b /usr/lib/systemd/systemd
...
Mai 03 20:42:52 myhost systemd[1]: Starting Login Service...
Mai 03 20:42:52 myhost systemd[1]: Started Restore Sound Card State.
Mai 03 20:42:52 myhost systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
Mai 03 20:42:52 myhost systemd[1]: Starting Permit User Sessions...
Mai 03 20:42:53 myhost systemd[1]: Started Permit User Sessions.
Mai 03 20:42:53 myhost systemd[1]: Starting Getty on tty1...
Mai 03 20:42:53 myhost systemd[1]: Started Getty on tty1.
Mai 03 20:42:53 myhost systemd[1]: Starting Login Prompts.
Mai 03 20:42:53 myhost systemd[1]: Reached target Login Prompts.
Mai 03 20:42:53 myhost systemd[1]: Starting LXDE Display Manager...
Mai 03 20:42:53 myhost systemd[1]: Started LXDE Display Manager.
Mai 03 20:42:53 myhost systemd[1]: Started dhcpcd on all interfaces.
Mai 03 20:42:53 myhost systemd[1]: Starting Network.
Mai 03 20:43:24 myhost systemd[1]: Started Network Time Service.
Mai 03 20:43:24 myhost systemd[1]: Starting Multi-User System.
Mai 03 20:43:24 myhost systemd[1]: Reached target Multi-User System.
Mai 03 20:43:24 myhost systemd[1]: Starting Graphical Interface.
Mai 03 20:43:24 myhost systemd[1]: Reached target Graphical Interface.
Mai 03 20:43:24 myhost systemd[1]: Startup finished in 3.818s (kernel) + 38.131s (userspace) = 41.949s.
[root@myhost hmeyer]# journalctl -b 
...
Mai 03 20:42:53 myhost systemd[1]: Starting Login Prompts.
Mai 03 20:42:53 myhost systemd[1]: Reached target Login Prompts.
Mai 03 20:42:53 myhost systemd[1]: Starting LXDE Display Manager...
Mai 03 20:42:53 myhost systemd[1]: Started LXDE Display Manager.
Mai 03 20:42:53 myhost systemd[1]: Started dhcpcd on all interfaces.
Mai 03 20:42:53 myhost systemd[1]: Starting Network.
Mai 03 20:42:53 myhost acpid[183]: 1 rule loaded
Mai 03 20:42:53 myhost acpid[183]: waiting for events: event logging is off
Mai 03 20:42:53 myhost dhcpcd[184]: version 5.6.7 starting
Mai 03 20:42:53 myhost dhcpcd[184]: forked to background, child pid 193
Mai 03 20:42:54 myhost avahi-daemon[180]: Successfully called chroot().
Mai 03 20:42:54 myhost avahi-daemon[180]: Successfully dropped remaining capabilities.
Mai 03 20:42:54 myhost avahi-daemon[180]: Loading service file /services/sftp-ssh.service.
Mai 03 20:42:54 myhost avahi-daemon[180]: Loading service file /services/ssh.service.
Mai 03 20:42:54 myhost avahi-daemon[180]: Loading service file /services/udisks.service.
Mai 03 20:42:54 myhost avahi-daemon[180]: Network interface enumeration completed.
Mai 03 20:42:54 myhost avahi-daemon[180]: Registering new address record for fe80::250:fcff:feef:70c7 on eth0.
Mai 03 20:43:24 myhost avahi-daemon[180]: Server startup complete. Host name is myhost.local. Local service co
Mai 03 20:43:24 myhost ntpd[196]: ntpd 4.2.6p5@1.2349-o Tue Dec 18 22:49:50 UTC 2012 (1)
Mai 03 20:43:24 myhost dhcpcd[193]: eth0: sending IPv6 Router Solicitation
Mai 03 20:43:24 myhost dbus[185]: [system] Activating via systemd: service name='org.freedesktop.ColorManager'
Mai 03 20:43:24 myhost lxdm-binary[192]: pam_unix(lxdm:session): session opened for user hmeyer by (uid=0)
Mai 03 20:43:24 myhost avahi-daemon[180]: Service "myhost" (/services/udisks.service) successfully established
Mai 03 20:43:24 myhost dbus[185]: [system] Failed to activate service 'org.freedesktop.ColorManager': timed ou
Mai 03 20:43:24 myhost ntpd[220]: proto: precision = 0.380 usec
Mai 03 20:43:24 myhost avahi-daemon[180]: Service "myhost" (/services/ssh.service) successfully established.
Mai 03 20:43:25 myhost dbus[185]: [system] Activating via systemd: service name='org.freedesktop.ColorManager'
Mai 03 20:43:25 myhost avahi-daemon[180]: Service "myhost" (/services/sftp-ssh.service) successfully establish
Mai 03 20:43:25 myhost dhcpcd[193]: eth0: rebinding lease of 192.168.1.2
Mai 03 20:43:25 myhost ntpd[220]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Mai 03 20:43:25 myhost avahi-daemon[180]: Registering HINFO record with values 'I686'/'LINUX'.
Mai 03 20:43:25 myhost ntpd[220]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Mai 03 20:43:26 myhost dhcpcd[193]: eth1: waiting for carrier
Mai 03 20:43:27 myhost colord[221]: Using config file /etc/colord.conf
Mai 03 20:43:27 myhost ntpd[220]: Listen and drop on 1 v6wildcard :: UDP 123
Mai 03 20:43:27 myhost dhcpcd[193]: eth0: acknowledged 192.168.1.2 from 192.168.1.1
Mai 03 20:43:27 myhost ntpd[220]: Listen normally on 2 lo 127.0.0.1 UDP 123
Mai 03 20:43:27 myhost colord[221]: Using mapping database file /var/lib/colord/mapping.db
Mai 03 20:43:27 myhost dhcpcd[193]: eth0: checking for 192.168.1.2
Mai 03 20:43:27 myhost ntpd[220]: Listen normally on 3 lo ::1 UDP 123
Mai 03 20:43:27 myhost colord[221]: Using device database file /var/lib/colord/storage.db
Mai 03 20:43:27 myhost ntpd[220]: Listen normally on 4 eth0 fe80::250:fcff:feef:70c7 UDP 123
Mai 03 20:43:27 myhost ntpd[220]: peers refreshed
Mai 03 20:43:27 myhost ntpd[220]: Listening on routing socket on fd #21 for interface updates
Mai 03 20:43:28 myhost colord[221]: loaded plugin libcd_plugin_camera.so
Mai 03 20:43:28 myhost colord[221]: plugin /usr/lib/colord-plugins/libcd_plugin_sane.so not loaded: plugin ref
Mai 03 20:43:28 myhost colord[221]: loaded plugin libcd_plugin_scanner.so
Mai 03 20:43:28 myhost colord[221]: Daemon ready for requests
Mai 03 20:43:28 myhost dbus[185]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Mai 03 20:43:28 myhost colord[221]: Profile added: HP_LaserJet_6MP-Gray..
Mai 03 20:43:28 myhost colord[221]: Device added: cups-HP_LaserJet_6MP
Mai 03 20:43:28 myhost colord[221]: Profile added: MFC7360N-Gray..
Mai 03 20:43:28 myhost colord[221]: Device added: cups-MFC7360N
Mai 03 20:43:28 myhost kernel: 8139too 0000:07:09.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Mai 03 20:43:28 myhost dbus-daemon[185]: dbus[185]: [system] Activating via systemd: service name='org.freedes
Mai 03 20:43:28 myhost dbus-daemon[185]: dbus[185]: [system] Failed to activate service 'org.freedesktop.Color
Mai 03 20:43:28 myhost dbus-daemon[185]: dbus[185]: [system] Activating via systemd: service name='org.freedes
Mai 03 20:43:28 myhost dbus-daemon[185]: dbus[185]: [system] Successfully activated service 'org.freedesktop.C
Mai 03 20:43:24 myhost systemd[1]: Started Network Time Service.
Mai 03 20:43:24 myhost systemd[1]: Starting Multi-User System.
Mai 03 20:43:24 myhost systemd[1]: Reached target Multi-User System.
Mai 03 20:43:24 myhost systemd[1]: Starting Graphical Interface.
Mai 03 20:43:24 myhost systemd[1]: Reached target Graphical Interface.
Mai 03 20:43:24 myhost systemd[1]: Startup finished in 3.818s (kernel) + 38.131s (userspace) = 41.949s.

Also strange, dmesg gets flooded by the following message, every 6 seconds, but I don't know if there is any relation to the delay mentioned above:

[   95.953450] mei 0000:00:03.0: unexpected reset: dev_state = RESETING
[  101.973356] mei 0000:00:03.0: unexpected reset: dev_state = RESETING

Offline

#2 2013-05-03 17:53:19

Inxsible
Forum Fellow
From: Chicago
Registered: 2008-06-09
Posts: 9,071

Re: delay at system start

enable verbose on your boot to see where it gets stuck

citron wrote:
Mai 03 20:43:28 myhost dbus-daemon[185]: dbus[185]: [system] Successfully activated service 'org.freedesktop.C
Mai 03 20:43:24 myhost systemd[1]: Started Network Time Service.

How did you make your time go back here?


Forum Rules

There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !

Offline

#3 2013-05-04 06:17:18

citron
Member
Registered: 2013-05-03
Posts: 7

Re: delay at system start

enable verbose on your boot to see where it gets stuck

I disabled "quiet" in /etc/default/grub and showed up the logs, see above.
Is there any place, where I can set it even more verbose?
Still don't know, why it gets stuck...

How did you make your time go back here?

that's also on my to-do list. Currently ntpd corrects time some minutes after launch.

Offline

#4 2013-05-04 08:29:27

x33a
Forum Moderator
Registered: 2009-08-15
Posts: 3,287
Website

Re: delay at system start

you can try "systemd-analyze blame"

Last edited by x33a (2013-05-04 08:30:22)

Offline

#5 2013-05-04 08:40:11

citron
Member
Registered: 2013-05-03
Posts: 7

Re: delay at system start

you can try "systemd-analyze blame"

Gives me this:

[hmeyer@myhost ~]$ systemd-analyze blame
         33.733s ntpd.service
          7.936s colord.service
          2.562s udisks2.service
          1.973s systemd-vconsole-setup.service
          1.494s avahi-daemon.service
          1.434s polkit.service
          1.416s sys-kernel-debug.mount
          1.393s systemd-logind.service
          1.359s systemd-modules-load.service
          1.322s dev-mqueue.mount
          1.278s systemd-tmpfiles-clean.service
          1.074s dev-hugepages.mount
           967ms systemd-fsck@dev-disk-by\x2dlabel-home.service
           940ms dhcpcd.service
           933ms systemd-remount-fs.service
           920ms systemd-sysctl.service
           893ms tmp.mount
           582ms systemd-udev-trigger.service
           197ms systemd-journal-flush.service
           170ms systemd-user-sessions.service
           122ms systemd-udevd.service
           117ms alsa-restore.service
           100ms dev-disk-by\x2dlabel-swap.swap
            96ms sys-kernel-config.mount
            48ms home.mount
            37ms systemd-static-nodes.service
            33ms systemd-tmpfiles-setup.service
             6ms systemd-random-seed-load.service
             1ms sys-fs-fuse-connections.mount

when I deactivate ntpd.service then I still get the same delay only caused by something else

Offline

#6 2013-05-04 08:49:15

sistematico
Member
From: Campo Grande / MS / Brasil
Registered: 2008-07-26
Posts: 74
Website

Re: delay at system start

Maybe:

systemctl disable NetworkManager-wait-online.service

Lucas Saliés Brum
blog | medium | vk | twitter | github | .share
Forgive the spelling and grammar, English is not my native language.

Offline

#7 2013-05-04 09:28:34

65kid
Member
From: Germany
Registered: 2011-01-26
Posts: 663

Re: delay at system start

your boot plot svg might help:

systemd-analyze plot > boot.svg

And although this may not cause the problem, you may want to use dhcpcd@<interface>.service instead of dhcpcd.service. dhcpcd.service may take control of the the network devices before udev, so udev will fail to rename them. However, this shouldn't have any effect on you if you have the rule blacklisted in /etc/udev/rules.d/.

Offline

#8 2013-05-05 07:54:39

citron
Member
Registered: 2013-05-03
Posts: 7

Re: delay at system start

no luck, I deactivated web access completely, and, perfectly fast boot-up according to boot.svg, 11 seconds (hope the link works):
boot.svg
But, watching the screen, black screen, 35 seconds. Delay is reflected in the log, see below, gap between *:24 and *:58.
May be I should live with that, boot-up less frequently...

Mai 04 18:35:23 myhost systemd[1]: Started Permit User Sessions.
Mai 04 18:35:23 myhost systemd[1]: Starting Getty on tty1...
Mai 04 18:35:23 myhost systemd[1]: Started Getty on tty1.
Mai 04 18:35:23 myhost systemd[1]: Starting Login Prompts.
Mai 04 18:35:23 myhost systemd[1]: Reached target Login Prompts.
Mai 04 18:35:23 myhost systemd[1]: Starting LXDE Display Manager...
Mai 04 18:35:23 myhost systemd[1]: Started LXDE Display Manager.
Mai 04 18:35:24 myhost systemd[1]: Started Login Service.
Mai 04 18:35:24 myhost systemd-logind[183]: New seat seat0.
Mai 04 18:35:23 myhost acpid[181]: starting up with netlink and the input layer
Mai 04 18:35:23 myhost acpid[181]: 1 rule loaded
Mai 04 18:35:23 myhost acpid[181]: waiting for events: event logging is off
Mai 04 18:35:24 myhost avahi-daemon[179]: Found user 'avahi' (UID 84) and group 'avahi' (GID 84).
Mai 04 18:35:24 myhost avahi-daemon[179]: Successfully dropped root privileges.
Mai 04 18:35:24 myhost avahi-daemon[179]: avahi-daemon 0.6.31 starting up.
Mai 04 18:35:24 myhost avahi-daemon[179]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Mai 04 18:35:24 myhost avahi-daemon[179]: Successfully called chroot().
Mai 04 18:35:24 myhost avahi-daemon[179]: Successfully dropped remaining capabilities.
Mai 04 18:35:24 myhost avahi-daemon[179]: Loading service file /services/sftp-ssh.service.
Mai 04 18:35:24 myhost avahi-daemon[179]: Loading service file /services/ssh.service.
Mai 04 18:35:58 myhost avahi-daemon[179]: Loading service file /services/udisks.service.
Mai 04 18:35:58 myhost dbus[182]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit=
Mai 04 18:35:58 myhost lxdm-binary[189]: pam_unix(lxdm:session): session opened for user hmeyer by (uid=0)
Mai 04 18:35:58 myhost avahi-daemon[179]: Network interface enumeration completed.
Mai 04 18:35:58 myhost dbus[182]: [system] Failed to activate service 'org.freedesktop.ColorManager': timed out
Mai 04 18:35:58 myhost avahi-daemon[179]: Registering HINFO record with values 'I686'/'LINUX'.
Mai 04 18:35:58 myhost dbus[182]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit=
Mai 04 18:35:58 myhost avahi-daemon[179]: Server startup complete. Host name is myhost.local. Local service cookie i
Mai 04 18:35:58 myhost avahi-daemon[179]: Service "myhost" (/services/udisks.service) successfully established.
Mai 04 18:35:58 myhost avahi-daemon[179]: Service "myhost" (/services/ssh.service) successfully established.
Mai 04 18:35:58 myhost avahi-daemon[179]: Service "myhost" (/services/sftp-ssh.service) successfully established.
Mai 04 18:35:59 myhost systemd-logind[183]: Watching system buttons on /dev/input/event3 (Power Button)
Mai 04 18:35:59 myhost dbus-daemon[182]: dbus[182]: [system] Activating via systemd: service name='org.freedesktop.C
Mai 04 18:35:59 myhost dbus-daemon[182]: dbus[182]: [system] Failed to activate service 'org.freedesktop.ColorManage
Mai 04 18:35:59 myhost dbus-daemon[182]: dbus[182]: [system] Activating via systemd: service name='org.freedesktop.C
Mai 04 18:35:58 myhost systemd[1]: Starting Manage, Install and Generate Color Profiles...
Mai 04 18:35:58 myhost systemd-logind[183]: New session 1 of user hmeyer.
Mai 04 18:35:58 myhost systemd-logind[183]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display.
Mai 04 18:36:00 myhost systemd[1]: Started Manage, Install and Generate Color Profiles.
Mai 04 18:35:59 myhost colord[197]: Using config file /etc/colord.conf
Mai 04 18:35:59 myhost colord[197]: Using mapping database file /var/lib/colord/mapping.db
Mai 04 18:35:59 myhost colord[197]: Using device database file /var/lib/colord/storage.db
Mai 04 18:36:00 myhost colord[197]: loaded plugin libcd_plugin_camera.so
Mai 04 18:36:00 myhost colord[197]: plugin /usr/lib/colord-plugins/libcd_plugin_sane.so not loaded: plugin refused t
Mai 04 18:36:00 myhost colord[197]: loaded plugin libcd_plugin_scanner.so
Mai 04 18:36:00 myhost colord[197]: Daemon ready for requests
Mai 04 18:36:00 myhost dbus[182]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Mai 04 18:36:00 myhost colord[197]: Profile added: HP_LaserJet_6MP-Gray..
Mai 04 18:36:00 myhost colord[197]: Device added: cups-HP_LaserJet_6MP
Mai 04 18:36:00 myhost colord[197]: Profile added: MFC7360N-Gray..
Mai 04 18:36:00 myhost colord[197]: Device added: cups-MFC7360N
Mai 04 18:36:02 myhost colord[197]: Profile added: icc-ed12dff9d009d530f54ef8361b412886
Mai 04 18:36:06 myhost dbus[182]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udis
Mai 04 18:36:06 myhost colord[197]: Profile added: icc-b883d2303b1503cca406319750a5110a
Mai 04 18:36:06 myhost colord[197]: Profile added: icc-c96a233b3a75ad0ee3052a9421421318
Mai 04 18:36:06 myhost systemd-logind[183]: Watching system buttons on /dev/input/event6 (Video Bus)
Mai 04 18:36:06 myhost dbus-daemon[182]: dbus[182]: [system] Successfully activated service 'org.freedesktop.ColorMa
Mai 04 18:36:06 myhost dbus-daemon[182]: dbus[182]: [system] Activating via systemd: service name='org.freedesktop.U
Mai 04 18:36:06 myhost systemd[1]: Mounting FUSE Control File System...
Mai 04 18:36:06 myhost systemd[1]: Mounted FUSE Control File System.
Mai 04 18:36:06 myhost systemd[1]: Starting Disk Manager...
Mai 04 18:36:06 myhost systemd[1]: Starting Authorization Manager...
Mai 04 18:36:06 myhost colord[197]: Profile added: icc-bf01aa61cc697742d767d68d7e8fd08d
Mai 04 18:36:06 myhost udisksd[251]: udisks daemon version 2.1.0 starting
Mai 04 18:36:06 myhost dbus[182]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='p
Mai 04 18:36:06 myhost colord[197]: Profile added: icc-01cc873b0c8ba2a4bb00cec48b2636bb
Mai 04 18:36:06 myhost colord[197]: Profile added: icc-4b4819a2b2a614fb223382787585176c
Mai 04 18:36:06 myhost colord[197]: Profile added: icc-6ab221cf79f348f677c9f5c3909669d2
Mai 04 18:36:06 myhost polkitd[255]: Started polkitd version 0.110
Mai 04 18:36:06 myhost colord[197]: Profile added: icc-a0b5efb4aea38f22677e816a50917b33
Mai 04 18:36:06 myhost colord[197]: Profile added: icc-7ff9ca58ce9026eb4f4787150b9ee48f
Mai 04 18:36:06 myhost colord[197]: Profile added: icc-1ff7668789c41d97e4fc214ef0b54e21
Mai 04 18:36:06 myhost colord[197]: Profile added: icc-8298763041cd24a0ef9da6f2cd97e9ab
Mai 04 18:36:06 myhost colord[197]: Profile added: icc-ea2843ac72088332568ae7657774b5b1
Mai 04 18:36:06 myhost colord[197]: Profile added: icc-484b403bd5bdbdac329edaa4a25c2b6b
Mai 04 18:36:07 myhost colord[197]: Profile added: icc-f6d3fb1fa8a6399877dc6b85729fe746
Mai 04 18:36:07 myhost polkitd[255]: Loading rules from directory /etc/polkit-1/rules.d
Mai 04 18:36:07 myhost polkitd[255]: Loading rules from directory /usr/share/polkit-1/rules.d
Mai 04 18:36:07 myhost colord[197]: Profile added: icc-6f47aab2aa7263b2f3b1528663e80050
Mai 04 18:36:08 myhost colord[197]: Profile added: icc-8cadd05b52e1eb44599f5da33dfccf20
Mai 04 18:36:08 myhost polkitd[255]: Finished loading, compiling and executing 1 rules
Mai 04 18:36:08 myhost dbus[182]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Mai 04 18:36:08 myhost polkitd[255]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
Mai 04 18:36:08 myhost colord[197]: Profile added: icc-c94bbf6ef50ccdbb5b29d75b7007e77e
Mai 04 18:36:08 myhost dbus[182]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Mai 04 18:36:08 myhost udisksd[251]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Mai 04 18:36:08 myhost colord[197]: Profile added: icc-a86a502a9fdc58f261eb321b40946488
Mai 04 18:36:08 myhost colord[197]: Profile added: icc-ee1009629d7100895a6b380788ccc43b
Mai 04 18:36:08 myhost colord[197]: Profile added: icc-6fb3a23d8d7d23908c613c556d3e10cf
Mai 04 18:36:08 myhost colord[197]: Profile added: icc-53c0505e7c78a2f0e209225edf8a076c
Mai 04 18:36:08 myhost colord[197]: Profile added: icc-99e1cb8aae315f3241bc6866325d7e1e
Mai 04 18:36:08 myhost colord[197]: Profile added: icc-cf618b76f0288e759fcea8b8b7eb3a41
Mai 04 18:36:08 myhost colord[197]: Profile added: icc-fe0295e8c064e272a905799201f55920
Mai 04 18:36:08 myhost systemd-logind[183]: Watching system buttons on /dev/input/event2 (Power Button)
Mai 04 18:36:08 myhost dbus-daemon[182]: dbus[182]: [system] Activating via systemd: service name='org.freedesktop.P
Mai 04 18:36:08 myhost dbus-daemon[182]: dbus[182]: [system] Successfully activated service 'org.freedesktop.PolicyK
Mai 04 18:36:08 myhost dbus-daemon[182]: dbus[182]: [system] Successfully activated service 'org.freedesktop.UDisks2
Mai 04 18:36:08 myhost systemd[1]: Started Authorization Manager.
Mai 04 18:36:08 myhost systemd[1]: Started Disk Manager.
Mai 04 18:36:08 myhost colord[197]: Profile added: icc-efeabbb7fe8739b8982642138548b80d
Mai 04 18:36:08 myhost kernel: mei 0000:00:03.0: unexpected reset: dev_state = RESETING

Offline

#9 2013-05-05 10:18:31

65kid
Member
From: Germany
Registered: 2011-01-26
Posts: 663

Re: delay at system start

that's weird, never seen this. Remove the "quiet" parameter from your kernel command line so you can see where it actually hangs.

Only other thing I can think of is to disable one service after the other one by one to see which one causes this.

Offline

#10 2013-05-05 15:28:22

jrussell
Member
From: Cape Town, South Africa
Registered: 2012-08-16
Posts: 510

Re: delay at system start

Similar problem, only noticed this recently:

admin@russell-server ~ % sudo systemd-analyze blame
         51.075s plexmediaserver.service
         49.336s ntpd.service
         41.070s couchpotato.service
         17.098s httpd.service
         14.278s nmbd.service
         13.835s minidlna.service
          8.530s colord.service
          7.837s netctl@ethernet\x2dstatic.service
          6.865s smbd.service
          4.712s transmission.service
          4.658s avahi-daemon.service
          4.592s systemd-logind.service
          3.342s systemd-tmpfiles-clean.service
          3.045s alsa-restore.service
          2.689s iptables.service
          1.729s systemd-fsck@dev-disk-by\x2duuid-a628b153\x2d4f97\x2d45f7\x2db8b1\x2d23c3557cdd72.service
          1.068s systemd-journal-flush.service
           929ms systemd-static-nodes.service
           866ms systemd-modules-load.service
           863ms sys-kernel-debug.mount
           850ms dev-mqueue.mount
           707ms systemd-udev-trigger.service
           623ms dev-hugepages.mount
           610ms systemd-remount-fs.service
           501ms dyndns.service
           486ms systemd-sysctl.service
           423ms storage.mount
           387ms systemd-vconsole-setup.service
           271ms tmp.mount
           181ms systemd-random-seed-load.service
           161ms systemd-user-sessions.service
           130ms systemd-tmpfiles-setup.service
            50ms systemd-udevd.service
            15ms sys-kernel-config.mount

bitcoin: 1G62YGRFkMDwhGr5T5YGovfsxLx44eZo7U

Offline

#11 2013-05-05 17:47:47

citron
Member
Registered: 2013-05-03
Posts: 7

Re: delay at system start

65kid wrote:

Remove the "quiet" parameter from your kernel command line

I changed /etc/default/grub:

#GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""

Is that what you mean?
I didn't find any other place where I explicitely could "enable verbose on your boot" as Inxsible advised me (above).

Offline

#12 2013-05-05 17:58:18

65kid
Member
From: Germany
Registered: 2011-01-26
Posts: 663

Re: delay at system start

citron wrote:
65kid wrote:

Remove the "quiet" parameter from your kernel command line

I changed /etc/default/grub:

#GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""

Is that what you mean?
I didn't find any other place where I explicitely could "enable verbose on your boot" as Inxsible advised me (above).

yes. I don't use grub, but I think you will also have to rebuild your grub config. Without "quiet" you should see the startup messages by systemd and maybe see where it hangs.

Offline

#13 2013-05-06 12:00:15

citron
Member
Registered: 2013-05-03
Posts: 7

Re: delay at system start

you will also have to rebuild your grub config

I didn't mention it but I had done that.
startup messages appear to be part of the overall log.
Tankyou for help!

Offline

Board footer

Powered by FluxBB