LINUX.ORG.RU

Долгая загрузка до логинскрина

 , , , ,


0

1

Доброго утра! Наблюдаю уже больше месяца проблему:

$ systemd-analyze
Startup finished in 2.449s (kernel) + 2min 56.711s (userspace) = 2min 59.161s 
graphical.target reached after 2.903s in userspace

gdm грузится ОЧЕНЬ медленно. Та же проблема с sddm. Грешил на железо, снёс Арч, поставил манжаро - загрузка секунд за 5. Поставил Арч с нуля, проблема вернулась. Поставил lxdm, загрузка примерно 5 секунд. Наблюдается ли у кого-то такая же проблема? Куда смотреть?

★★

Ответ на: комментарий от anti_win
$ systemd-analyze blame                                                                      
2min 54.978s man-db.service                                     
      2.344s systemd-random-seed.service                        
      1.391s docker.service                                     
      1.179s systemd-logind.service                             
       886ms lvm2-monitor.service                               
       833ms dev-sda1.device                                    
       666ms upower.service                                     
       463ms systemd-udevd.service                              
       385ms systemd-journal-flush.service                      
       385ms ldconfig.service                                   
       328ms systemd-journald.service                           
       231ms udisks2.service                                    
       183ms accounts-daemon.service                            
       150ms polkit.service                                     
       131ms NetworkManager.service                             
       130ms systemd-modules-load.service                       
       116ms nginx.service                                      
       115ms user@120.service                                   
        91ms systemd-udev-trigger.service                       
        87ms systemd-vconsole-setup.service                     
        77ms logrotate.service                                  
        57ms user@1000.service                                  
        52ms systemd-sysusers.service                           
        52ms NetworkManager-wait-online.service                 
        47ms colord.service                                     
        46ms systemd-journal-catalog-update.service             
        42ms gdm.service                                        
        41ms systemd-tmpfiles-setup.service                     
        36ms systemd-fsck@dev-sda3.service                      
2min 54.978s man-db.service                                     
      2.344s systemd-random-seed.service                        
      1.391s docker.service                                     
      1.179s systemd-logind.service                             
       886ms lvm2-monitor.service                               
       833ms dev-sda1.device                                    
       666ms upower.service                                     
       463ms systemd-udevd.service                              
       385ms systemd-journal-flush.service                      
       385ms ldconfig.service                                   
       328ms systemd-journald.service                           
       231ms udisks2.service                                    
       183ms accounts-daemon.service                            
       150ms polkit.service                                     
       131ms NetworkManager.service                             
       130ms systemd-modules-load.service                       
       116ms nginx.service                                      
       115ms user@120.service                                   
        91ms systemd-udev-trigger.service                       
        87ms systemd-vconsole-setup.service                     
        77ms logrotate.service                                  
        57ms user@1000.service                                  
        52ms systemd-sysusers.service                           
        52ms NetworkManager-wait-online.service                 
        47ms colord.service                                     
        46ms systemd-journal-catalog-update.service             
        42ms gdm.service                                        
        41ms systemd-tmpfiles-setup.service                     
        36ms systemd-fsck@dev-sda3.service            
$ systemd-analyze critical-chain                                                             
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 @2.903s
└─multi-user.target @2.903s
  └─systemd-logind.service @1.723s +1.179s
    └─nss-user-lookup.target @2.910s
dnb ★★ ()

Отключение man-db.service не помогло.

$ systemd-analyze blame
2.299s systemd-random-seed.service                        
1.573s systemd-logind.service                             
 890ms lvm2-monitor.service                               
 832ms dev-sda1.device                                    
 526ms upower.service                                     
 478ms systemd-udevd.service                              
 476ms ldconfig.service                                   
 377ms systemd-journal-flush.service                      
 325ms systemd-journald.service                           
 232ms udisks2.service                                    
 135ms systemd-modules-load.service                       
 130ms accounts-daemon.service                            
 117ms NetworkManager.service                             
 104ms polkit.service                                     
  90ms nginx.service                                      
  89ms systemd-vconsole-setup.service                     
  87ms systemd-udev-trigger.service                       
  80ms user@120.service                                   
  67ms gdm.service                                        
  59ms user@1000.service                                  
  48ms systemd-sysusers.service                           
  45ms systemd-tmpfiles-setup.service                     
  44ms systemd-journal-catalog-update.service             
  42ms wpa_supplicant.service                             
  42ms plymouth-quit-wait.service                         
  39ms plymouth-start.service                             
  39ms systemd-fsck@dev-sda3.service                      
  38ms plymouth-quit.service                              
  36ms colord.service                                     
  28ms systemd-binfmt.service                             
  25ms systemd-tmpfiles-setup-dev.service                 
  21ms bluetooth.service                                  
  17ms dev-hugepages.mount                                
  17ms dev-mqueue.mount                                   
  16ms plymouth-read-write.service                        
  16ms sys-kernel-debug.mount                             
  15ms home.mount                                         
  13ms systemd-remount-fs.service                         
  13ms tmp.mount                                          
  13ms kmod-static-nodes.service                          
  11ms systemd-user-sessions.service                      
  11ms user-runtime-dir@120.service                       
  10ms systemd-update-utmp.service                        
  10ms user-runtime-dir@1000.service                      
   9ms systemd-sysctl.service                             
   9ms systemd-rfkill.service                             
   8ms systemd-update-done.service                        
   7ms systemd-backlight@backlight:intel_backlight.service
   5ms sys-fs-fuse-connections.mount                      
   4ms rtkit-daemon.service                               
   3ms proc-sys-fs-binfmt_misc.mount                      
   3ms sys-kernel-config.mount          

Но на самом деле загрузка такая же медленная.

@alexferman haveged не установлен.

dnb ★★ ()
Ответ на: комментарий от dnb

Отключение man-db.service не помогло.

И не поможет, потому что его запускает man-db.timer раз в день и необязательно на этапе загрузки.

haveged не установлен.

Установи и сделай systemctl enable haveged.service.

rassol ()
Ответ на: комментарий от xDShot
$ locale
LANG=ru_RU.UTF-8
LC_CTYPE="ru_RU.UTF-8"
LC_NUMERIC="ru_RU.UTF-8"
LC_TIME="ru_RU.UTF-8"
LC_COLLATE="ru_RU.UTF-8"
LC_MONETARY="ru_RU.UTF-8"
LC_MESSAGES=ru_RU.UTF-8
LC_PAPER="ru_RU.UTF-8"
LC_NAME="ru_RU.UTF-8"
LC_ADDRESS="ru_RU.UTF-8"
LC_TELEPHONE="ru_RU.UTF-8"
LC_MEASUREMENT="ru_RU.UTF-8"
LC_IDENTIFICATION="ru_RU.UTF-8"
LC_ALL=
dnb ★★ ()
Ответ на: комментарий от rassol
$ systemd-analyze critical-chain
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 @2.840s
└─multi-user.target @2.840s
  └─systemd-logind.service @1.785s +1.054s
    └─basic.target @1.759s
      └─sockets.target @1.759s
        └─dbus.socket @1.759s
          └─sysinit.target @1.756s
            └─systemd-update-done.service @1.748s +7ms
              └─ldconfig.service @1.379s +367ms
                └─local-fs.target @1.378s
                  └─home.mount @1.361s +16ms
                    └─systemd-fsck@dev-sda3.service @1.318s +40ms
                      └─local-fs-pre.target @1.317s
                        └─lvm2-monitor.service @326ms +990ms
                          └─lvm2-lvmetad.service @356ms
                            └─systemd-journald.socket @318ms
                              └─-.mount @296ms
                                └─systemd-journald.socket @318ms
                                  └─...

journalctl -b -p 4 https://pastebin.com/7EqXbv0s

systemd-analyze plot > load.svg https://dropmefiles.com/j3JMe

dnb ★★ ()