Re: slow starting up jessie

[Umarzuki Mochlis]

2016-09-22 20:01 GMT+08:00 Darac Marjal :

>
>
> Another avenue, then, might be "systemd-analyze critical-chain". That will
> give you a tree of what the slowest dependencies of graphical.target are.
> Slow units will get two times: one preceded by "@" tells you how long into
> the boot the unit became active and the one preceded by "+" tells you how
> long the unit took to start.
>
>


graphical.target @17.794s
└─multi-user.target @17.794s
  └─libvirt-guests.service @17.633s +160ms
└─libvirtd.service @13.658s +3.785s
  └─dbus.service @12.095s
└─basic.target @12.045s
  └─paths.target @12.043s
└─cups.path @12.043s
  └─sysinit.target @11.985s
└─nfs-common.service @11.460s +524ms
  └─rpcbind.target @11.458s
└─rpcbind.service @11.243s +214ms
  └─network-online.target @11.242s
└─network.target @11.242s
  └─networking.service @7.113s +4.129s
└─local-fs.target @7.104s
  └─run-rpc_pipefs.mount @11.877s
└─local-fs-pre.target @3.796s
  └─systemd-remount-fs.service @3.723s +71ms
└─keyboard-setup.service @2.555s +1.166s
  └─systemd-udevd.service @2.504s +48ms

└─systemd-tmpfiles-setup-dev.service @1.598s +905ms
  └─kmod-static-nodes.service
@1.291s +305ms
└─system.slice @1.265s
  └─-.slice @1.265s


Some services took more than 7 seconds to start

Which one should I disable considering this PC mainly used for KVM?


>> dmesg output shows some error regarding firmware-linux-nonfree but
>> other desktop with same model also does not have it installed and did
>> not have this problem
>>
>> dmesg pastebin:
>> http://paste.debian.net/834468/
>>
>
> --
> For more information, please reread.

Re: slow starting up jessie

[Darac Marjal]

On Thu, Sep 22, 2016 at 05:35:48PM +0800, Umarzuki Mochlis wrote:

2016-09-22 17:16 GMT+08:00 Floris :





try:
$ systemd-analyze blame
to find out which services are slow to start

Floris



it seemed that most services less than 5 seconds to start


Another avenue, then, might be "systemd-analyze critical-chain". That 
will give you a tree of what the slowest dependencies of 
graphical.target are. Slow units will get two times: one preceded by "@" 
tells you how long into the boot the unit became active and the one 
preceded by "+" tells you how long the unit took to start.



dmesg output shows some error regarding firmware-linux-nonfree but
other desktop with same model also does not have it installed and did
not have this problem

dmesg pastebin:
http://paste.debian.net/834468/



--
For more information, please reread.


signature.asc
Description: PGP signature

Re: slow starting up jessie

[Umarzuki Mochlis]

2016-09-22 17:16 GMT+08:00 Floris :

>>
>
> try:
> $ systemd-analyze blame
> to find out which services are slow to start
>
> Floris
>

it seemed that most services less than 5 seconds to start

root@pc2:~# systemd-analyze blame
  4.129s networking.service
  3.785s libvirtd.service
  3.763s exim4.service
  3.681s ModemManager.service
  2.460s lvm2-activation-early.service
  2.239s systemd-udev-settle.service
  1.652s alsa-restore.service
  1.648s systemd-logind.service
  1.619s rc-local.service
  1.615s speech-dispatcher.service
  1.614s wicd.service
  1.375s avahi-daemon.service
  1.166s keyboard-setup.service
  1.008s polkitd.service
   936ms systemd-modules-load.service
   905ms systemd-tmpfiles-setup-dev.service
   869ms kbd.service
   720ms rsyslog.service
   652ms resolvconf.service
   615ms systemd-setup-dgram-qlen.service
   588ms dev-mqueue.mount
   576ms colord.service
   569ms sys-kernel-debug.mount
   567ms dev-hugepages.mount
   550ms lvm2-activation.service
   524ms nfs-common.service
   401ms hdparm.service
   340ms
systemd-fsck@dev-disk-by\x2duuid-b110590a\x2d5007\x2d4836\x2d9d59\x2d9cb8055fe933.service
   336ms systemd-udev-trigger.service
   329ms console-setup.service
   305ms kmod-static-nodes.service
   240ms systemd-user-sessions.service
   214ms rpcbind.service
   196ms lvm2-monitor.service
   196ms ebtables.service
   173ms boot.mount
   165ms systemd-tmpfiles-setup.service
   160ms libvirt-guests.service
   124ms systemd-random-seed.service
   114ms systemd-sysctl.service
   101ms systemd-journal-flush.service
93ms systemd-update-utmp.service
86ms qemu-system-x86.service
85ms dev-mapper-pc2\x2d\x2dvg\x2dswap_1.swap
71ms systemd-remount-fs.service
51ms udev-finish.service
48ms systemd-udevd.service
32ms user@1000.service
29ms lightdm.service
14ms systemd-update-utmp-runlevel.service
11ms systemd-tmpfiles-clean.service
 5ms lvm2-pvscan@8:5.service
 2ms sys-fs-fuse-connections.mount

dmesg output shows some error regarding firmware-linux-nonfree but
other desktop with same model also does not have it installed and did
not have this problem

dmesg pastebin:
http://paste.debian.net/834468/

Re: slow starting up jessie

[Floris]

Op Thu, 22 Sep 2016 10:42:43 +0200 schreef Umarzuki Mochlis  
:



one of my desktop is very slow to read log in prompt (no DE)

I can't seem to find any error log in syslog

Debian 8 amd64
compaq dc5850 sff


...

where should I check next? It got to this since I installed LXDE and
even after I removed lxde, it is still like this.



try:
$ systemd-analyze blame
to find out which services are slow to start

Floris

slow starting up jessie

[Umarzuki Mochlis]

one of my desktop is very slow to read log in prompt (no DE)

I can't seem to find any error log in syslog

Debian 8 amd64
compaq dc5850 sff

syslog:
Sep 22 16:30:50 pc2 rsyslogd: [origin software="rsyslogd"
swVersion="8.4.2" x-pid="743" x-info="http://www.rsyslog.com;]
rsyslogd was HUPed
Sep 22 16:30:59 pc2 systemd[1515]: Starting Paths.
Sep 22 16:30:59 pc2 systemd[1515]: Reached target Paths.
Sep 22 16:30:59 pc2 systemd[1515]: Starting Timers.
Sep 22 16:30:59 pc2 systemd[1515]: Reached target Timers.
Sep 22 16:30:59 pc2 systemd[1515]: Starting Sockets.
Sep 22 16:30:59 pc2 systemd[1515]: Reached target Sockets.
Sep 22 16:30:59 pc2 systemd[1515]: Starting Basic System.
Sep 22 16:30:59 pc2 systemd[1515]: Reached target Basic System.
Sep 22 16:30:59 pc2 systemd[1515]: Starting Default.
Sep 22 16:30:59 pc2 systemd[1515]: Reached target Default.
Sep 22 16:30:59 pc2 systemd[1515]: Startup finished in 90ms.
Sep 22 16:31:04 pc2 systemd[1528]: Starting Paths.
Sep 22 16:31:04 pc2 systemd[1528]: Reached target Paths.
Sep 22 16:31:04 pc2 systemd[1528]: Starting Timers.
Sep 22 16:31:04 pc2 systemd[1528]: Reached target Timers.
Sep 22 16:31:04 pc2 systemd[1528]: Starting Sockets.
Sep 22 16:31:04 pc2 systemd[1528]: Reached target Sockets.
Sep 22 16:31:04 pc2 systemd[1528]: Starting Basic System.
Sep 22 16:31:04 pc2 systemd[1528]: Reached target Basic System.
Sep 22 16:31:04 pc2 systemd[1528]: Starting Default.
Sep 22 16:31:04 pc2 systemd[1528]: Reached target Default.
Sep 22 16:31:04 pc2 systemd[1528]: Startup finished in 12ms.
Sep 22 16:31:18 pc2 rsyslogd0: action 'action 17' resumed (module
'builtin:ompipe') [try http://www.rsyslog.com/e/0 ]
Sep 22 16:31:18 pc2 rsyslogd-2359: action 'action 17' resumed (module
'builtin:ompipe') [try http://www.rsyslog.com/e/2359 ]
Sep 22 16:31:18 pc2 systemd[1515]: Stopping Default.
Sep 22 16:31:18 pc2 systemd[1515]: Stopped target Default.
Sep 22 16:31:18 pc2 systemd[1515]: Stopping Basic System.
Sep 22 16:31:18 pc2 systemd[1515]: Stopped target Basic System.
Sep 22 16:31:18 pc2 systemd[1515]: Stopping Paths.
Sep 22 16:31:18 pc2 systemd[1515]: Stopped target Paths.
Sep 22 16:31:18 pc2 systemd[1515]: Stopping Timers.
Sep 22 16:31:18 pc2 systemd[1515]: Stopped target Timers.
Sep 22 16:31:18 pc2 systemd[1515]: Stopping Sockets.
Sep 22 16:31:18 pc2 systemd[1515]: Stopped target Sockets.
Sep 22 16:31:18 pc2 systemd[1515]: Starting Shutdown.
Sep 22 16:31:18 pc2 systemd[1515]: Reached target Shutdown.
Sep 22 16:31:18 pc2 systemd[1515]: Starting Exit the Session...
Sep 22 16:31:18 pc2 systemd[1515]: Received SIGRTMIN+24 from PID 1551 (kill).
Sep 22 16:31:20 pc2 anacron[679]: Job `cron.daily' terminated
Sep 22 16:31:20 pc2 anacron[679]: Normal exit (1 job run)

where should I check next? It got to this since I installed LXDE and
even after I removed lxde, it is still like this.