Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #198742 > unrolled thread

Slow boot

Back to article view | Back to linux.debian.user

Contents

  Slow boot Johann Spies <johann.spies@gmail.com> - 2018-08-14 08:50 +0200
    Re: Slow boot Anders Andersson <pipatron@gmail.com> - 2018-08-14 12:30 +0200
      Re: Slow boot Johann Spies <johann.spies@gmail.com> - 2018-08-14 12:40 +0200
    Re: Slow boot Martin <keine-eile@online.de> - 2018-08-14 12:40 +0200
      Re: Slow boot Johann Spies <johann.spies@gmail.com> - 2018-08-14 12:50 +0200
    Re: Slow boot Patrick Bartek <nemommxiv@gmail.com> - 2018-08-14 17:20 +0200
      Re: Slow boot Johann Spies <johann.spies@gmail.com> - 2018-08-14 22:50 +0200
        Re: Slow boot Cindy-Sue Causey <butterflybytes@gmail.com> - 2018-08-15 00:40 +0200
        Re: Slow boot Patrick Bartek <nemommxiv@gmail.com> - 2018-08-15 19:10 +0200

#198742 — Slow boot

I can push the power on button on my laptop, go and make coffee and
come back and wait a few minutes before I can work.

The following services each takes longer than 10 seconds to activate:

 systemd-analyze blame
    1min 21.617s apt-daily.service
     1min 2.473s systemd-tmpfiles-setup.service
      1min 926ms console-setup.service
         47.192s postgresql@10-main.service
         38.873s exim4.service
         29.176s shorewall.service
         23.365s wicd.service
         22.402s mariadb.service
         18.925s nmbd.service
         13.917s udisks2.service
         13.177s ModemManager.service
         11.865s libvirtd.service

I can disable apt-daily.service but I do not think the system will
work properly if I disable the second.  The third one (console-setup)
seems to have a bug:

systemd[1]: Failed to start Set console font and keymap.
It is looking for a file (symbols/us-intl) that does not exist
Aug 14 08:02:55 sitasie console-setup.sh[769]: setupcon: The keyboard
model is unknown, assuming 'pc105'. Keyboard may be configured
incorrectly.
Aug 14 08:03:55 sitasie console-setup.sh[769]: /usr/bin/ckbcomp: Can
not find file "symbols/us-intl" in any known directory

This is the joy that I get since systemd became the standard.

Regards
Johann

-- 
Because experiencing your loyal love is better than life itself,
my lips will praise you.  (Psalm 63:3)

[toc] | [next] | [standalone]

#198763

On Tue, Aug 14, 2018 at 8:45 AM, Johann Spies <johann.spies@gmail.com> wrote:
> I can push the power on button on my laptop, go and make coffee and
> come back and wait a few minutes before I can work.
>
> The following services each takes longer than 10 seconds to activate:
>
>  systemd-analyze blame
>     1min 21.617s apt-daily.service
>      1min 2.473s systemd-tmpfiles-setup.service
>       1min 926ms console-setup.service
>          47.192s postgresql@10-main.service
>          38.873s exim4.service
>          29.176s shorewall.service
>          23.365s wicd.service
>          22.402s mariadb.service
>          18.925s nmbd.service
>          13.917s udisks2.service
>          13.177s ModemManager.service
>          11.865s libvirtd.service
>
> I can disable apt-daily.service but I do not think the system will
> work properly if I disable the second.  The third one (console-setup)
> seems to have a bug:
>
> systemd[1]: Failed to start Set console font and keymap.
> It is looking for a file (symbols/us-intl) that does not exist
> Aug 14 08:02:55 sitasie console-setup.sh[769]: setupcon: The keyboard
> model is unknown, assuming 'pc105'. Keyboard may be configured
> incorrectly.
> Aug 14 08:03:55 sitasie console-setup.sh[769]: /usr/bin/ckbcomp: Can
> not find file "symbols/us-intl" in any known directory
>
> This is the joy that I get since systemd became the standard.

Not sure you can blame systemd here, except that without systemd you
would have no clue what took so much time. Most of these services
shouldn't take that long to start, and systemd is just the messenger
here. What more, the system should still boot up without most of
these, especially the databases.

Part from console-setup being broken, I'm a bit curious about your
hard drive activity and if you have a rotating platter drive or an
SSD.

If you start up apt-daily, two databases and libvirt in parallel on a
rotating platter laptop drive, I'd expect a huge amount of disk
thrashing.

I don't remember now if it's possible to log I/O activity, but maybe
you can inform us about the physical drive at least?

[toc] | [prev] | [next] | [standalone]

#198766

On Tue, 14 Aug 2018 at 12:22, Anders Andersson <pipatron@gmail.com> wrote:
>
> On Tue, Aug 14, 2018 at 8:45 AM, Johann Spies <johann.spies@gmail.com> wrote:

> I don't remember now if it's possible to log I/O activity, but maybe
> you can inform us about the physical drive at least?

I have a rotating disk - no ssd.  I have since removed mariadb - which
was installed as a
dependency somewhere in the past.  I will also remove libvirt as I do
not really use it.

Regards
Johann


-- 
Because experiencing your loyal love is better than life itself,
my lips will praise you.  (Psalm 63:3)

[toc] | [prev] | [next] | [standalone]

#198765

Am 14.08.2018 um 08:45 schrieb Johann Spies:
> I can push the power on button on my laptop, go and make coffee and
> come back and wait a few minutes before I can work.
> 
> The following services each takes longer than 10 seconds to activate:
> 
>  systemd-analyze blame
>     1min 21.617s apt-daily.service
>      1min 2.473s systemd-tmpfiles-setup.service
>       1min 926ms console-setup.service
>          47.192s postgresql@10-main.service
>          38.873s exim4.service
>          29.176s shorewall.service
>          23.365s wicd.service
>          22.402s mariadb.service
>          18.925s nmbd.service
>          13.917s udisks2.service
>          13.177s ModemManager.service
>          11.865s libvirtd.service
> 
> I can disable apt-daily.service but I do not think the system will
> work properly if I disable the second.  The third one (console-setup)
> seems to have a bug:
> 
> systemd[1]: Failed to start Set console font and keymap.
> It is looking for a file (symbols/us-intl) that does not exist
> Aug 14 08:02:55 sitasie console-setup.sh[769]: setupcon: The keyboard
> model is unknown, assuming 'pc105'. Keyboard may be configured
> incorrectly.
> Aug 14 08:03:55 sitasie console-setup.sh[769]: /usr/bin/ckbcomp: Can
> not find file "symbols/us-intl" in any known directory
> 
> This is the joy that I get since systemd became the standard.
> 
> Regards
> Johann
> 

Just a guess: If you have no working network, DNS in specific, it may take ages until you local resolver terminates with a time out error. This could be one reason, why this apt-daily.service (and may be exim) takes that long.

[toc] | [prev] | [next] | [standalone]

#198767

On Tue, 14 Aug 2018 at 12:32, Martin <keine-eile@online.de> wrote:

> Just a guess: If you have no working network, DNS in specific, it may take ages until you local resolver terminates with a time out error. This could be one reason, why this apt-daily.service (and may be exim) takes that long.
>

Correct guess.  I did not realize before today that the
apt-daily.service was part of the problem.
As part of the university's network I have to unlock access to the internet.
And that can only happen through a web browser.

Regards
Johann


-- 
Because experiencing your loyal love is better than life itself,
my lips will praise you.  (Psalm 63:3)

[toc] | [prev] | [next] | [standalone]

#198781

On Tue, 14 Aug 2018 08:45:09 +0200
Johann Spies <johann.spies@gmail.com> wrote:

> I can push the power on button on my laptop, go and make coffee and
> come back and wait a few minutes before I can work.
> 
> The following services each takes longer than 10 seconds to activate:
> 
>  systemd-analyze blame
>     1min 21.617s apt-daily.service
>      1min 2.473s systemd-tmpfiles-setup.service
>       1min 926ms console-setup.service
>          47.192s postgresql@10-main.service
>          38.873s exim4.service
>          29.176s shorewall.service
>          23.365s wicd.service
>          22.402s mariadb.service
>          18.925s nmbd.service
>          13.917s udisks2.service
>          13.177s ModemManager.service
>          11.865s libvirtd.service
> 
> I can disable apt-daily.service but I do not think the system will
> work properly if I disable the second.  The third one (console-setup)
> seems to have a bug:
> 
> systemd[1]: Failed to start Set console font and keymap.
> It is looking for a file (symbols/us-intl) that does not exist
> Aug 14 08:02:55 sitasie console-setup.sh[769]: setupcon: The keyboard
> model is unknown, assuming 'pc105'. Keyboard may be configured
> incorrectly.
> Aug 14 08:03:55 sitasie console-setup.sh[769]: /usr/bin/ckbcomp: Can
> not find file "symbols/us-intl" in any known directory
> 
> This is the joy that I get since systemd became the standard.

I'm curious.  Did you just do a distribution upgrade on this laptop?
From what to what? Or was it a clean install? Or is it an old install
with everything working fine until now?

B

[toc] | [prev] | [next] | [standalone]

#198792

On Tue, 14 Aug 2018 at 17:18, Patrick Bartek <nemommxiv@gmail.com> wrote:

> I'm curious.  Did you just do a distribution upgrade on this laptop?
> From what to what? Or was it a clean install? Or is it an old install
> with everything working fine until now?

I do regular dist-upgrades (testing) and have installed it as a new
computer about two or three years ago.

Regards
Johann
-- 
Because experiencing your loyal love is better than life itself,
my lips will praise you.  (Psalm 63:3)

[toc] | [prev] | [next] | [standalone]

#198794

On 8/14/18, Johann Spies <johann.spies@gmail.com> wrote:
> On Tue, 14 Aug 2018 at 17:18, Patrick Bartek <nemommxiv@gmail.com> wrote:
>
>> I'm curious.  Did you just do a distribution upgrade on this laptop?
>> From what to what? Or was it a clean install? Or is it an old install
>> with everything working fine until now?
>
> I do regular dist-upgrades (testing) and have installed it as a new
> computer about two or three years ago.


I started having some SLOW response times going back maybe 2 weeks
ago. I've not tied it to anything specific until today.

Mine's not at bootup, that goes quickly. This is immediately after I'm
already in. It's both Thunar file manager and Mousepad text editor in
Xfce4 environment. I'll click... pick a feature, ANY feature, and
wait... and wait.. and wait..

And that's on a brand new, fresh reboot with approximate 6GB memory.

Today something happened, and I ended up kicking an operating system's
liveCD out of /dev/sr0 where it had been sitting quietly doing
nothing. At least I think it was not engaged in any activity... :D

Everything's been working fabulously ever since...

That drive started automounting a few days ago after years of not
doing so. No intervention from me *that I know of*. I've played with
virtual machines, but I don't  think that came into it because it has
happened multiple times on reboots where I haven't touched VMs at all.

Just tossing it out there because it's an exasperatingly slow
something and may lead to an answer for someone eventually.... :)

Cindy :)
-- 
Cindy-Sue Causey
Backyard Pishing (Very active private birding adventure)

* runs with duct tape *

[toc] | [prev] | [next] | [standalone]

#198827

On Tue, 14 Aug 2018 22:43:03 +0200
Johann Spies <johann.spies@gmail.com> wrote:

> On Tue, 14 Aug 2018 at 17:18, Patrick Bartek <nemommxiv@gmail.com>
> wrote:
> 
> > I'm curious.  Did you just do a distribution upgrade on this laptop?
> > From what to what? Or was it a clean install? Or is it an old
> > install with everything working fine until now?  
> 
> I do regular dist-upgrades (testing) and have installed it as a new
> computer about two or three years ago.

Using Testing can be problematical as you've discovered. I'm assuming
that everything was working fine, then you did a dist-upgrade and the
long boot times began.  I'm also assuming that your notebook is set to
connect to a network at boot up.  So, turn off the wireless transceiver
(or disconnect your ethernet cable), reboot and see what happens.

Also, here's a link how best to install and use Testing like a
"rolling" release.  Something I do not recommend.

   https://wiki.debian.org/DebianTesting

B
   

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web