On Tue, 11 Nov 2025, Daniel Gröber wrote: >Just now a powercut caused a reboot and dhclient seems to have given up (or >crashed without leaving a trace in dmesg?) while the cable modem was still >booting. > >I can see it tries to DISCOVER a couple of times, goes to sleep, tries >again but then it's not heard from again with no process left behind - >until I restarted the interface at 21:02.
That’s roughly what I expect from dhclient, actually. If there’s no DHCP response for $smallnum minutes after the system come up, to give up and exit anyway, so the boot process continues and the local admin can login on the console and fix the situation (e.g. net.ifnames=0 on the kernel command line and reboot to fix interface names). >Curiously the "Removed stale PID file" would suggest to me that perhaps it >did crash or exit uncleanly somehow(?) since I can't see any segfault lines >in dmesg. > >On dhcp release via ifdown /run/dhclient.enp1s0.pid does get removed >properly -- I checked. That’s a bit puzzling, but cosmetic apparently. Gruß //Thorsten -- Thorsten Glaser Linux / Unix Developer Tel.: +49 160 91168501 E-Mail: [email protected] B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / https://www.b1-systems.de/ GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt, HRB 3537
