Arch Linux

Enla

Member

Registered: 2024-12-04

Posts: 16

Extremely long startup time

Hello, please forgive me if I forget to attach some logs
I installed Arch recently and I'm quite pleased with it, however I have a very long startup time.
Here is my systemd-analyze output :

Startup finished in 14.590s (firmware) + 1.951s (loader) + 8.118s (kernel) + 2min 36.127s (userspace) = 3min 787ms 
graphical.target reached after 2min 1.204s in userspace.

And when running systemd-analyze blame :

2min 35.617s systemd-time-wait-sync.service
2min 17.133s reflector.service
   2min 86ms systemd-networkd-wait-online.service

I couldn't really find decent information online sadly, so any help is appreciated !

Some more info :
I'm using a rog zephyrus G14 2022 ( GA402RJ )
Running systemd (obviously)
And using Hyprland started with uwsm.

twelveeighty

Member

Registered: 2011-09-04

Posts: 1,451

Re: Extremely long startup time

Check your journal for startup errors. If the reflector service is taking a long time, it's either busy because you have a lot of mirrors selected in /etc/xdg/reflector/reflector.conf, or perhaps your network configuration is incorrect and it's timing-out on a network connection. Try disabling the reflector service, then run reflector manually to see if there's specific errors/messages.

gromit

Administrator

From: Germany

Registered: 2024-02-10

Posts: 1,529

Website

Re: Extremely long startup time

Could you post the output of "systemd-analyze critical-chain"?

Enla

Member

Registered: 2024-12-04

Posts: 16

Re: Extremely long startup time

Here's the journalctl

déc. 04 17:24:53 tea-cup reflector[2436]: [2024-12-04 17:24:53] WARNING: failed to rate http(s) download (https://archlinux.thaller.ws/extra/os/x86_64/extra.db): Download timed out after 5 second(s).
déc. 04 17:24:59 tea-cup reflector[2436]: [2024-12-04 17:24:59] WARNING: failed to rate http(s) download (https://london.mirror.pkgbuild.com/extra/os/x86_64/extra.db): Download timed out after 5 second(s).
déc. 04 17:25:06 tea-cup reflector[2436]: [2024-12-04 17:25:06] WARNING: failed to rate http(s) download (https://mirror.ufscar.br/archlinux/extra/os/x86_64/extra.db): Download timed out after 5 second(s).
déc. 04 17:25:14 tea-cup reflector[2436]: [2024-12-04 17:25:14] WARNING: failed to rate http(s) download (https://mirror.moson.org/arch/extra/os/x86_64/extra.db): Download timed out after 5 second(s).
déc. 04 17:25:21 tea-cup reflector[2436]: [2024-12-04 17:25:21] WARNING: failed to rate http(s) download (https://md.mirrors.hacktegic.com/archlinux/extra/os/x86_64/extra.db): Download timed out after 5 second(>
déc. 04 17:25:28 tea-cup reflector[2436]: [2024-12-04 17:25:28] WARNING: failed to rate http(s) download (https://archlinux.uk.mirror.allworldit.com/archlinux/extra/os/x86_64/extra.db): Download timed out after>
déc. 04 17:25:35 tea-cup reflector[2436]: [2024-12-04 17:25:35] WARNING: failed to rate http(s) download (https://archlinux.za.mirror.allworldit.com/archlinux/extra/os/x86_64/extra.db): Download timed out after>
déc. 04 17:25:41 tea-cup reflector[2436]: [2024-12-04 17:25:41] WARNING: failed to rate http(s) download (https://arch.phinau.de/extra/os/x86_64/extra.db): Download timed out after 5 second(s).
déc. 04 17:25:41 tea-cup reflector[2436]: [2024-12-04 17:25:41] WARNING: failed to rate http(s) download (https://mirror.theash.xyz/arch/extra/os/x86_64/extra.db): HTTP Error 403: Forbidden
déc. 04 17:25:47 tea-cup reflector[2436]: [2024-12-04 17:25:47] WARNING: failed to rate http(s) download (https://at.arch.mirror.kescher.at/extra/os/x86_64/extra.db): Download timed out after 5 second(s).
déc. 04 17:25:53 tea-cup reflector[2436]: [2024-12-04 17:25:53] WARNING: failed to rate http(s) download (https://de.arch.mirror.kescher.at/extra/os/x86_64/extra.db): Download timed out after 5 second(s).
déc. 04 17:25:59 tea-cup reflector[2436]: [2024-12-04 17:25:59] WARNING: failed to rate http(s) download (https://america.mirror.pkgbuild.com/extra/os/x86_64/extra.db): Download timed out after 5 second(s).
déc. 04 17:26:05 tea-cup reflector[2436]: [2024-12-04 17:26:05] WARNING: failed to rate http(s) download (https://asia.mirror.pkgbuild.com/extra/os/x86_64/extra.db): Download timed out after 5 second(s).
déc. 04 17:26:11 tea-cup reflector[2436]: [2024-12-04 17:26:11] WARNING: failed to rate http(s) download (https://europe.mirror.pkgbuild.com/extra/os/x86_64/extra.db): Download timed out after 5 second(s).
déc. 04 17:26:16 tea-cup reflector[2436]: [2024-12-04 17:26:16] WARNING: failed to rate http(s) download (https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db): Download timed out after 5 second(s).
déc. 04 17:26:23 tea-cup reflector[2436]: [2024-12-04 17:26:23] WARNING: failed to rate http(s) download (https://sydney.mirror.pkgbuild.com/extra/os/x86_64/extra.db): Download timed out after 5 second(s).
déc. 04 17:26:29 tea-cup reflector[2436]: [2024-12-04 17:26:29] WARNING: failed to rate http(s) download (https://repo.jing.rocks/archlinux/extra/os/x86_64/extra.db): Download timed out after 5 second(s).
déc. 04 17:26:35 tea-cup reflector[2436]: [2024-12-04 17:26:35] WARNING: failed to rate http(s) download (https://al.arch.niranjan.co/extra/os/x86_64/extra.db): Download timed out after 5 second(s).
déc. 04 17:26:40 tea-cup reflector[2436]: [2024-12-04 17:26:40] WARNING: failed to rate http(s) download (https://de.arch.niranjan.co/extra/os/x86_64/extra.db): Download timed out after 5 second(s).
déc. 04 17:26:46 tea-cup reflector[2436]: [2024-12-04 17:26:46] WARNING: failed to rate http(s) download (https://in.arch.niranjan.co/extra/os/x86_64/extra.db): Download timed out after 5 second(s).
déc. 04 17:26:46 tea-cup systemd[1]: reflector.service: Deactivated successfully.

When starting it manually I get the same messages. I don't know if that's a normal amount of mirrors to have ? I do have a pretty slow connection ahah

Enla

Member

Registered: 2024-12-04

Posts: 16

Re: Extremely long startup time

Could you post the output of "systemd-analyze critical-chain"?

There you go :

The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @2min 1.204s
└─multi-user.target @2min 1.204s
  └─sshd.service @2.972s +98ms
    └─network.target @2.968s
      └─wpa_supplicant.service @3.331s +73ms
        └─basic.target @2.180s
          └─dbus-broker.service @2.095s +81ms
            └─dbus.socket @2.090s
              └─sysinit.target @2.090s
                └─systemd-vconsole-setup.service @8.076s +16ms
                  └─run-credentials-systemd\x2dvconsole\x2dsetup.service.mount @8.083s

mesaprotector

Member

Registered: 2024-03-03

Posts: 197

Re: Extremely long startup time

Is there any reason to wait for the reflector service on every boot? If you use the included reflector.timer instead, systemd will only run it once a week, which should be more than adequate.

twelveeighty

Member

Registered: 2011-09-04

Posts: 1,451

Re: Extremely long startup time

I don't know if that's a normal amount of mirrors to have ?

Those are just the mirrors that fail - reflector will put those at the bottom of the output (or not at all, I can't remember). Either way, I think you misunderstood the purpose of reflector - there's really no need to run it at boot every time. Just run it on a scheduled timer, or before you update. Personally, I rarely run reflector; I only run it when the DB download part of 'pacman -Syu' (before you get the prompt to continue) is slow, or when I switched my uplink to a completely different location (different place on the planet, that is).

Regardless, reflector paired with a possible slow network and failing mirrors looks like the cause for your long startup time. I would simply disable the service and run reflector manually when needed.

Enla

Member

Registered: 2024-12-04

Posts: 16

Re: Extremely long startup time

I don't know if that's a normal amount of mirrors to have ?

Those are just the mirrors that fail - reflector will put those at the bottom of the output (or not at all, I can't remember). Either way, I think you misunderstood the purpose of reflector - there's really no need to run it at boot every time. Just run it on a scheduled timer, or before you update. Personally, I rarely run reflector; I only run it when the DB download part of 'pacman -Syu' (before you get the prompt to continue) is slow, or when I switched my uplink to a completely different location (different place on the planet, that is).

Regardless, reflector paired with a possible slow network and failing mirrors looks like the cause for your long startup time. I would simply disable the service and run reflector manually when needed.

I see, that's the default config I believe which is weird. I disabled it and I'll see if it works out.