Repository navigation
Помогите мне решить проблему с мёртвый сервисом zapret при старте системы | Please help me resolve an issue where the "zapret" service fails to start when the system boot #343
Replies: 1 comment 1 reply
|
zapret2 isn't failing, it's waiting. Here, 2 minutes is the default systemd-analyze blame | head -n 5
systemctl is-enabled NetworkManager-wait-online.service systemd-networkd-wait-online.service
systemctl --failed
journalctl -b -u systemd-networkd-wait-online.serviceUnlike Normally only one wait service should be enabled (systemd docs) and only one network manager should run (Arch Wiki). If you use NetworkManager, turn networkd off and reboot: sudo systemctl disable systemd-networkd.service systemd-networkd.socket systemd-networkd-wait-online.serviceAfter the reboot, If you use networkd on purpose for some interface, keep it and stop wait-online from waiting for all links instead ( Last resort: |
Uh oh!
There was an error while loading. Please reload this page.
при загрузке системы (Arch linux), сервис
zapret2долгое время находится в статусеinactive (dead), и запускается (переходит вactive) только примерно через 2 минуты после старта системы. Сделалsystemd-analyze critical-chain zapret2.service:🇬🇧
When booting the system (Arch Linux), the
zapret2service stays in aninactive (dead)state for a long time and only starts (becomesactive) about 2 minutes after system startup.systemd-analyze critical-chain zapret2.serviceoutput is shown above.All reactions