Package: isc-dhcp-client
Version: 4.4.1-2.3
Severity: important

Dear Maintainer,

we are currently migrating a number of servers from Stretch to
Bullseye by either manually upgrading them or by a fresh reinstall.

After a reboot, ifup configures the interface and starts dhclient, e.g.

/sbin/dhclient -4 -v -i -pf /run/dhclient.enp7s0f0.pid -lf 
/var/lib/dhcp/dhclient.enp7s0f0.leases -I -df 
/var/lib/dhcp/dhclient6.enp7s0f0.leases enp7s0f0

and leases are properly written to
/var/lib/dhcp/dhclient.enp7s0f0.leases.

As most of our machines are "static" and will not change their IP over
their multi-year lifetime, we use a rather long lease time of 15 days
and thus the lease's renew time is always of the order of 7.5 days.

However, dhclient seems to miss the "renew" time quite often with
Bullseye (at least relative to Stretch or Buster where e did not
really knotice this) and after reaching the "expire" time, removing
the IP from the interface.

>From the journal:
journalctl |grep -iE 'eno2|grep dhc'     
Jun 14 06:30:54 nr20 kernel: tg3 0000:0b:00.1 eno2: renamed from eth1
Jun 14 06:31:07 nr20 dhclient[1374]: Listening on LPF/eno2/40:f2:e9:c9:03:81
Jun 14 06:31:07 nr20 ifup[1374]: Listening on LPF/eno2/40:f2:e9:c9:03:81
Jun 14 06:31:07 nr20 ifup[1374]: Sending on   LPF/eno2/40:f2:e9:c9:03:81
Jun 14 06:31:07 nr20 ifup[1374]: DHCPDISCOVER on eno2 to 255.255.255.255 port 
67 interval 6
Jun 14 06:31:07 nr20 dhclient[1374]: Sending on   LPF/eno2/40:f2:e9:c9:03:81
Jun 14 06:31:07 nr20 dhclient[1374]: DHCPDISCOVER on eno2 to 255.255.255.255 
port 67 interval 6
Jun 14 06:31:10 nr20 kernel: tg3 0000:0b:00.1 eno2: Link is up at 1000 Mbps, 
full duplex
Jun 14 06:31:10 nr20 kernel: tg3 0000:0b:00.1 eno2: Flow control is off for TX 
and off for RX
Jun 14 06:31:10 nr20 kernel: tg3 0000:0b:00.1 eno2: EEE is disabled
Jun 14 06:31:10 nr20 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eno2: link becomes 
ready
Jun 14 06:31:13 nr20 dhclient[1374]: DHCPDISCOVER on eno2 to 255.255.255.255 
port 67 interval 7
Jun 14 06:31:13 nr20 ifup[1374]: DHCPDISCOVER on eno2 to 255.255.255.255 port 
67 interval 7
Jun 14 06:31:13 nr20 ifup[1374]: DHCPREQUEST for 10.30.94.20 on eno2 to 
255.255.255.255 port 67
Jun 14 06:31:13 nr20 dhclient[1374]: DHCPREQUEST for 10.30.94.20 on eno2 to 
255.255.255.255 port 67
Jun 14 06:31:13 nr20 kernel: tg3 0000:0b:00.1 eno2: Link is down
Jun 14 06:31:17 nr20 kernel: tg3 0000:0b:00.1 eno2: Link is up at 1000 Mbps, 
full duplex
Jun 14 06:31:17 nr20 kernel: tg3 0000:0b:00.1 eno2: Flow control is off for TX 
and off for RX
Jun 14 06:31:17 nr20 kernel: tg3 0000:0b:00.1 eno2: EEE is disabled
Jun 14 06:31:19 nr20 ntpd[1482]: Listen normally on 6 eno2 10.30.94.20:123
Jun 14 06:31:19 nr20 ntpd[1482]: Listen normally on 7 eno2 
[fe80::42f2:e9ff:fec9:381%3]:123
Jun 14 10:18:42 nr20 ntpd[4324]: Listen normally on 4 eno2 10.30.94.20:123
Jun 14 10:18:42 nr20 ntpd[4324]: Listen normally on 7 eno2 
[fe80::42f2:e9ff:fec9:381%3]:123
Jun 14 10:56:26 nr20 avahi-daemon[46781]: Joining mDNS multicast group on 
interface eno2.IPv6 with address fe80::42f2:e9ff:fec9:381.
Jun 14 10:56:26 nr20 avahi-daemon[46781]: New relevant interface eno2.IPv6 for 
mDNS.
Jun 14 10:56:26 nr20 avahi-daemon[46781]: Joining mDNS multicast group on 
interface eno2.IPv4 with address 10.30.94.20.
Jun 14 10:56:26 nr20 avahi-daemon[46781]: New relevant interface eno2.IPv4 for 
mDNS.
Jun 14 10:56:26 nr20 avahi-daemon[46781]: Registering new address record for 
fe80::42f2:e9ff:fec9:381 on eno2.*.
Jun 14 10:56:26 nr20 avahi-daemon[46781]: Registering new address record for 
10.30.94.20 on eno2.IPv4.
Jun 29 06:31:13 nr20 avahi-daemon[46781]: Withdrawing address record for 
10.30.94.20 on eno2.
Jun 29 06:31:13 nr20 avahi-daemon[46781]: Leaving mDNS multicast group on 
interface eno2.IPv4 with address 10.30.94.20.
Jun 29 06:31:13 nr20 avahi-daemon[46781]: Interface eno2.IPv4 no longer 
relevant for mDNS.
Jun 29 06:31:14 nr20 ntpd[4324]: Deleting interface #4 eno2, 10.30.94.20#123, 
interface stats: received=5084, sent=11215, dropped=0, active_time=1282352 secs

[... later running dhclient manually on machine ...]
Jul 01 15:51:09 nr20 dhclient[110432]: DHCPDISCOVER on eno2 to 255.255.255.255 
port 67 interval 7
Jul 01 15:51:09 nr20 dhclient[110432]: DHCPREQUEST for 10.30.94.20 on eno2 to 
255.255.255.255 port 67
Jul 01 15:51:09 nr20 avahi-daemon[46781]: Joining mDNS multicast group on 
interface eno2.IPv4 with address 10.30.94.20.
Jul 01 15:51:09 nr20 avahi-daemon[46781]: New relevant interface eno2.IPv4 for 
mDNS.
Jul 01 15:51:09 nr20 avahi-daemon[46781]: Registering new address record for 
10.30.94.20 on eno2.IPv4.
Jul 01 15:51:10 nr20 ntpd[4324]: Listen normally on 8 eno2 10.30.94.20:123

Unfortunately, there does not seem to be more information in the logs :(

>From what the interwebs and the bug tracker showed, similar errors
seemed to be common on virtual machines and/or systems which
hibernate/dual-boot often or where the clock source jumps, but that
should not be the case here. The machines run 24/7 and are
synchronized via ntp with our internal GPS clock and external servers.

Also, package changes between Buster and Bullseye seem to be extremely
tiny, thus I don't see the failure reason there either.

A quick glance at moving over to dhcpcd5 was unsuccessful as Jumbo
frame/MTU settings provided by the DHCP server were not honored.

Any idea what may be amiss here?

Cheers

Carsten

-- System Information:
Debian Release: 11.3
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-15-amd64 (SMP w/80 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages isc-dhcp-client depends on:
ii  debianutils        4.11.2
ii  iproute2           5.10.0-4
ii  libc6              2.31-13+deb11u3
ii  libdns-export1110  1:9.11.19+dfsg-2.1
ii  libisc-export1105  1:9.11.19+dfsg-2.1

Versions of packages isc-dhcp-client recommends:
ii  isc-dhcp-common  4.4.1-2.3

Versions of packages isc-dhcp-client suggests:
pn  avahi-autoipd         <none>
pn  isc-dhcp-client-ddns  <none>
pn  resolvconf            <none>

-- no debconf information

Reply via email to