Estou tendo esse problema há um bom tempo, então hoje tentei uma sugestão que encontrei on-line, executando systemd-analyze plote verificando o resultado.
Estou anexando o arquivo SVG aqui porque salvo engano só tem duas coisas demorando absurdamente para inicializar, uma delas systemd-networkd-wait-online(claro) mas depois, estranhamente, sendmailque eu nem uso nesse servidor é dentro da minha rede doméstica e funciona apenas como um servidor seedbox/mídia.
Estou faltando alguma coisa aqui? Desativei wlananteriormente para descartá-lo, pois é uma máquina com fio e não precisa de wlan.
Desativei sendmail, reiniciei, observei o tempo limite e depois executei novamente e agora a única coisa que está demorando é o que estou tentando consertar. Qualquer ajuda seria graciosamente apreciada.
https://c0ld.net/slowboot-nosendmail.svg
Aqui está um diário completo:http://0x0.st/Xo36.txt
Ele tem um IP estático, não é voltado para a Internet, roda plex, bittorrent-noxe jellyfintem alguns discos rígidos USB montados na inicialização para armazenamento e isso é tudo que está rodando, exceto webmine cockpit. Ele tem o Ubuntu GNome completo instalado, mas não inicializa na inicialização, eu só queria isso para me divertir se precisar usá-lo como um PC de backup.
Eu realmente não quero simplesmente mascarar o problema desativando o serviço. Eu até tentei mudar renderer: networkdpara renderer: NetworkManagerinnetplan
Destinado a adicionar, saída denetworkctl
1 lo loopback carrier unmanaged
2 eno1 ether routable configured
3 wlp1s0 wlan off unmanaged
3 links listed.
Então não há nada de louco aí.
Também tenho optional: trueconfiguração do eno1 no netplan.
EDIT: Também tentei adicionar --any e --interface=eno1 conforme especificado abaixo e ambos ainda têm o mesmo tempo limite. https://ubuntuforums.org/showthread.php?t=2490962
Apr 21 15:15:16 jays-lenovo systemd[1]: Starting Wait for Network to be Configured...
░░ Subject: A start job for unit systemd-networkd-wait-online.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit systemd-networkd-wait-online.service has begun execution.
░░
░░ The job identifier is 3886.
Apr 21 15:17:16 jays-lenovo systemd-networkd-wait-online[4967]: Timeout occurred while waiting for network connectivity.
Apr 21 15:17:16 jays-lenovo systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit systemd-networkd-wait-online.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Apr 21 15:17:16 jays-lenovo systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit systemd-networkd-wait-online.service has entered the 'failed' state with result 'exit-code'.
Apr 21 15:17:16 jays-lenovo systemd[1]: Failed to start Wait for Network to be Configured.
░░ Subject: A start job for unit systemd-networkd-wait-online.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit systemd-networkd-wait-online.service has finished with a failure.
░░
░░ The job identifier is 3886 and the job result is failed.
Isso foi depois de reiniciar o serviço com --interface=eno1 que está definitivamente ativo !!!!
A mesma verificação para systemd-networkd.service
-- Boot 984031206640442cb02a40798ddf3b7f --
Apr 21 14:21:12 jays-lenovo systemd[1]: Starting Network Configuration...
░░ Subject: A start job for unit systemd-networkd.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit systemd-networkd.service has begun execution.
░░
░░ The job identifier is 49.
Apr 21 14:21:12 jays-lenovo systemd-networkd[1178]: lo: Link UP
Apr 21 14:21:12 jays-lenovo systemd-networkd[1178]: lo: Gained carrier
Apr 21 14:21:12 jays-lenovo systemd-networkd[1178]: Enumeration completed
Apr 21 14:21:12 jays-lenovo systemd[1]: Started Network Configuration.
░░ Subject: A start job for unit systemd-networkd.service has finished successfully
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit systemd-networkd.service has finished successfully.
░░
░░ The job identifier is 49.
Apr 21 14:23:15 jays-lenovo systemd-networkd[1178]: eno1: Link UP
Apr 21 14:23:18 jays-lenovo systemd-networkd[1178]: eno1: Gained carrier
Apr 21 14:23:19 jays-lenovo systemd-networkd[1178]: eno1: Gained IPv6LL
Apr 21 14:51:50 jays-lenovo systemd-networkd[1178]: eno1: Re-configuring with /run/systemd/network/10-netplan-eno1.network
Apr 21 14:51:51 jays-lenovo systemd-networkd[1178]: eno1: Re-configuring with /run/systemd/network/10-netplan-eno1.network
Apr 21 14:51:51 jays-lenovo systemd-networkd[1178]: eno1: DHCPv6 lease lost
Apr 21 14:52:23 jays-lenovo systemd[1]: Stopping Network Configuration...
░░ Subject: A stop job for unit systemd-networkd.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A stop job for unit systemd-networkd.service has begun execution.
░░
░░ The job identifier is 4966.
Apr 21 14:52:23 jays-lenovo systemd-networkd[1178]: eno1: DHCPv6 lease lost
Apr 21 14:52:23 jays-lenovo systemd[1]: systemd-networkd.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit systemd-networkd.service has successfully entered the 'dead' state.
Apr 21 14:52:23 jays-lenovo systemd[1]: Stopped Network Configuration.
░░ Subject: A stop job for unit systemd-networkd.service has finished
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A stop job for unit systemd-networkd.service has finished.
░░
░░ The job identifier is 4966 and the job result is done.
-- Boot dc2cb94cb1f649c49648ba8e085192db --
Apr 21 14:53:19 jays-lenovo systemd[1]: Starting Network Configuration...
░░ Subject: A start job for unit systemd-networkd.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit systemd-networkd.service has begun execution.
░░
░░ The job identifier is 25.
Apr 21 14:53:19 jays-lenovo systemd-networkd[1172]: lo: Link UP
Apr 21 14:53:19 jays-lenovo systemd-networkd[1172]: lo: Gained carrier
Apr 21 14:53:19 jays-lenovo systemd-networkd[1172]: Enumeration completed
Apr 21 14:53:19 jays-lenovo systemd[1]: Started Network Configuration.
░░ Subject: A start job for unit systemd-networkd.service has finished successfully
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit systemd-networkd.service has finished successfully.
░░
░░ The job identifier is 25.
Apr 21 14:53:19 jays-lenovo systemd-networkd[1172]: eno1: Link UP
Apr 21 14:53:22 jays-lenovo systemd-networkd[1172]: eno1: Gained carrier
Apr 21 14:53:24 jays-lenovo systemd-networkd[1172]: eno1: Gained IPv6LL
Apr 21 15:26:32 jays-lenovo systemd-networkd[1172]: eno1: Re-configuring with /run/systemd/network/10-netplan-eno1.network
Apr 21 15:26:32 jays-lenovo systemd-networkd[1172]: eno1: DHCPv6 lease lost
Apr 21 15:26:32 jays-lenovo systemd-networkd[1172]: eno1: Re-configuring with /run/systemd/network/10-netplan-eno1.network
Apr 21 15:26:32 jays-lenovo systemd-networkd[1172]: eno1: DHCPv6 lease lost
Completohttps://c0ld.net/dmesg.htmldisponivel aqui. Não sei mais o que tentar neste momento, vasculhei a internet.
eno1 também está configurado como um IP estático, então não faz sentido que demore mais para estar disponível do que mais curto.
192.168.2.1 é o roteador principal de toda a minha casa, com vários roteadores diferentes e dezenas de dispositivos, nenhum outro tem problemas.
# This is the network config written by 'subiquity'
network:
version: 2
renderer: networkd
ethernets:
eno1:
optional: false
addresses:
- 192.168.2.99/24
nameservers:
addresses: [192.168.2.1]
routes:
- to: default
via: 192.168.2.1
Responder1
Nossa, ok, demorou um pouco, para futuros viajantes, foi uma bagunça de NetworkManager, netplan e networkd, todos juntos. Eu fui e segui (ou faltaram os bits de qualquer maneira) desses dois e tudo funcionou perfeitamente, reiniciei em alguns segundos :)
https://linux.fernandocejas.com/docs/how-to/switch-from-network-manager-to-systemd-networkd
https://askubuntu.com/questions/1336247/removing-netplan-to-use-systemd-networkd-directly