On Thu, 13 Apr 2023 at 23:16:15 +0200, William Desportes wrote: > Right after boot&unlock and (user login?) it prints the missing > ipconfig missing message.
Just to confirm, you unlock (at initramfs stage) using keyboard + screen right, not remotely using dropbear SSH right? Because at that point the initramfs hasn't got network access right? > So the script is also called out of initramfs. Again if is nothing blocking at initramfs stage then execution is handed over to init(1) before configure_networking() has a chance to terminate (it runs in the background). This is going in circles, I have no idea how to explain better than I did in https://bugs.debian.org/1015810#10 : | However if you don't have BOOT=nfs then initramfs-tools-core's | configure_networking() runs asynchronously starting from init-premount | stage and might not give up before the execution is handed over to the | normal system. dropbear-initramfs' init-bottom scripts only wait for | 60s by default but configure_networking() might take much longer (180s | timeout for the device, up to 10s waiting time for udev to settle, then | exponential backoff of 2+3+4+6+9+16+25+36+64+100=265s for the network | configuration). | | Since 2020.81-2 the init-bottom timeout is configurable with | DROPBEAR_SHUTDOWN_TIMEOUT and you can set it to a value that exceeds the | typical configure_networking() duration on your system to be sure that | there is leftover process passed init-bottom stage. Can you please try to set DROPBEAR_SHUTDOWN_TIMEOUT=300 or so, as I pointed in my first replied, before insisting there is a bug or missing dependencies? -- Guilhem.
signature.asc
Description: PGP signature
