Bug#1030725: dhcpcd-base: service does not restart after package updates

2023-02-11 Thread Beat Bolli

On 11.02.23 14:58, Martin-Éric Racine wrote:

sudo systemctl restart ifup@eth1.service

This should do what you need. If this works, the host should boot
correctly as well.


Oh, I also had to manually "systemctl stop dhcpcd". This service was not 
stopped by the purge of package dhcpcd. Afterwards, restarting ifup@eth1 
also started dhcpcd.


Thanks again!

Beat
--
https://drbeat.li
tel:+41-79-7706774
gpg: 0x506A903A; 49D5 794A EA77 F907 764F  D89E 304B 93CF 506A 903A
icbm: 47.0452 N, 7.2715 E

"It takes love over gold, and mind over matter" — Dire Straits



Bug#1030725: dhcpcd-base: service does not restart after package updates

2023-02-11 Thread Martin-Éric Racine
On Sat, Feb 11, 2023 at 3:53 PM Beat Bolli  wrote:
>
> On 11.02.23 14:36, Martin-Éric Racine wrote:
> > On Sat, Feb 11, 2023 at 3:25 PM Beat Bolli  wrote:
> >>
> >> On 11.02.23 14:03, Martin-Éric Racine wrote:
> >>> On Sat, Feb 11, 2023 at 2:42 PM Beat Bolli  wrote:
>  On 11.02.23 12:01, Martin-Éric Racine wrote:
> > On Wed, 8 Feb 2023 08:35:02 +0200
> > =?UTF-8?Q?Martin=2D=C3=89ric_Racine?= 
> > wrote:
> >> On Mon, 06 Feb 2023 20:39:36 +0100 Beat Bolli  wrote:
> >>>  This morning, version 9.4.1-16 was installed by my daily
> >>>  unattended-upgrade run. As after all recent updates, the 
> >>> service
> >>>  was stopped, but not restarted after the update. This leads 
> >>> to
> >>>  loss of Internet connectivity after the DHCP lease expires.
> >>
> >> If you are only using dhcpcd-base, it implies that DHCP is restarted
> >> by ifupdown via /etc/network/interfaces. Is that the case here?
> >
> > Can you confirm?
> 
>  Honestly, I don't get the distinction between dhcpcd and &-base, but I
>  now see in the package file list that the systemd integration is part of
>  dhcpcd, not -base. So I have reported the bug for the wrong package.
> 
>  Regarding point 2 in the original report, I had to run "systemctl start
>  dhcpcd.service" to restart the daemon.
> >>>
> >>> Can you paste me the content of /etc/network/interfaces and
> >>> /etc/network/interfaces.d/ just to be sure?
> >>
> >> Sure:
> >
> >> # The internal LAN interface
> >> allow-hotplug eth0
> >> iface eth0 inet static
> >>  address 192.168.11.1/26
> >>
> >> # The external WAN interface
> >> allow-hotplug eth1
> >> iface eth1 inet dhcp
> >>  # address 192.168.254.2/24
> >>  # gateway 192.168.254.1
> >>  up /usr/local/bin/freedns
> >
> > That explains it. The systemd unit conflicts with
> > /etc/network/interfaces since both are trying to start the same
> > interfaces.
> >
> > Can you check with 'dpkg -l | grep ifupdown' that you indeed have
> > ifupdown installed? If yes, you can purge 'dhcpcd' and only keep
> > 'dhcpcd-base' installed. It should do what you need.
>
> I have ifupdown installed. Now I've purged dhcpcd. I'll have to wait
> until the next update to verify.

sudo systemctl restart ifup@eth1.service

This should do what you need. If this works, the host should boot
correctly as well.

Martin-Éric



Bug#1030725: dhcpcd-base: service does not restart after package updates

2023-02-11 Thread Beat Bolli

On 11.02.23 14:36, Martin-Éric Racine wrote:

On Sat, Feb 11, 2023 at 3:25 PM Beat Bolli  wrote:


On 11.02.23 14:03, Martin-Éric Racine wrote:

On Sat, Feb 11, 2023 at 2:42 PM Beat Bolli  wrote:

On 11.02.23 12:01, Martin-Éric Racine wrote:

On Wed, 8 Feb 2023 08:35:02 +0200
=?UTF-8?Q?Martin=2D=C3=89ric_Racine?= 
wrote:

On Mon, 06 Feb 2023 20:39:36 +0100 Beat Bolli  wrote:

 This morning, version 9.4.1-16 was installed by my daily
 unattended-upgrade run. As after all recent updates, the service
 was stopped, but not restarted after the update. This leads to
 loss of Internet connectivity after the DHCP lease expires.


If you are only using dhcpcd-base, it implies that DHCP is restarted
by ifupdown via /etc/network/interfaces. Is that the case here?


Can you confirm?


Honestly, I don't get the distinction between dhcpcd and &-base, but I
now see in the package file list that the systemd integration is part of
dhcpcd, not -base. So I have reported the bug for the wrong package.

Regarding point 2 in the original report, I had to run "systemctl start
dhcpcd.service" to restart the daemon.


Can you paste me the content of /etc/network/interfaces and
/etc/network/interfaces.d/ just to be sure?


Sure:



# The internal LAN interface
allow-hotplug eth0
iface eth0 inet static
 address 192.168.11.1/26

# The external WAN interface
allow-hotplug eth1
iface eth1 inet dhcp
 # address 192.168.254.2/24
 # gateway 192.168.254.1
 up /usr/local/bin/freedns


That explains it. The systemd unit conflicts with
/etc/network/interfaces since both are trying to start the same
interfaces.

Can you check with 'dpkg -l | grep ifupdown' that you indeed have
ifupdown installed? If yes, you can purge 'dhcpcd' and only keep
'dhcpcd-base' installed. It should do what you need.


I have ifupdown installed. Now I've purged dhcpcd. I'll have to wait 
until the next update to verify.


Thanks,
Beat
--
https://drbeat.li
tel:+41-79-7706774
gpg: 0x506A903A; 49D5 794A EA77 F907 764F  D89E 304B 93CF 506A 903A
icbm: 47.0452 N, 7.2715 E

"It takes love over gold, and mind over matter" — Dire Straits



Bug#1030725: dhcpcd-base: service does not restart after package updates

2023-02-11 Thread Martin-Éric Racine
On Sat, Feb 11, 2023 at 3:25 PM Beat Bolli  wrote:
>
> On 11.02.23 14:03, Martin-Éric Racine wrote:
> > On Sat, Feb 11, 2023 at 2:42 PM Beat Bolli  wrote:
> >> On 11.02.23 12:01, Martin-Éric Racine wrote:
> >>> On Wed, 8 Feb 2023 08:35:02 +0200
> >>> =?UTF-8?Q?Martin=2D=C3=89ric_Racine?= 
> >>> wrote:
>  On Mon, 06 Feb 2023 20:39:36 +0100 Beat Bolli  wrote:
> > This morning, version 9.4.1-16 was installed by my daily
> > unattended-upgrade run. As after all recent updates, the service
> > was stopped, but not restarted after the update. This leads to
> > loss of Internet connectivity after the DHCP lease expires.
> 
>  If you are only using dhcpcd-base, it implies that DHCP is restarted
>  by ifupdown via /etc/network/interfaces. Is that the case here?
> >>>
> >>> Can you confirm?
> >>
> >> Honestly, I don't get the distinction between dhcpcd and &-base, but I
> >> now see in the package file list that the systemd integration is part of
> >> dhcpcd, not -base. So I have reported the bug for the wrong package.
> >>
> >> Regarding point 2 in the original report, I had to run "systemctl start
> >> dhcpcd.service" to restart the daemon.
> >
> > Can you paste me the content of /etc/network/interfaces and
> > /etc/network/interfaces.d/ just to be sure?
>
> Sure:

> # The internal LAN interface
> allow-hotplug eth0
> iface eth0 inet static
> address 192.168.11.1/26
>
> # The external WAN interface
> allow-hotplug eth1
> iface eth1 inet dhcp
> # address 192.168.254.2/24
> # gateway 192.168.254.1
> up /usr/local/bin/freedns

That explains it. The systemd unit conflicts with
/etc/network/interfaces since both are trying to start the same
interfaces.

Can you check with 'dpkg -l | grep ifupdown' that you indeed have
ifupdown installed? If yes, you can purge 'dhcpcd' and only keep
'dhcpcd-base' installed. It should do what you need.

Martin-Éric



Bug#1030725: dhcpcd-base: service does not restart after package updates

2023-02-11 Thread Beat Bolli

On 11.02.23 14:03, Martin-Éric Racine wrote:

On Sat, Feb 11, 2023 at 2:42 PM Beat Bolli  wrote:

On 11.02.23 12:01, Martin-Éric Racine wrote:

On Wed, 8 Feb 2023 08:35:02 +0200
=?UTF-8?Q?Martin=2D=C3=89ric_Racine?= 
wrote:

On Mon, 06 Feb 2023 20:39:36 +0100 Beat Bolli  wrote:

This morning, version 9.4.1-16 was installed by my daily
unattended-upgrade run. As after all recent updates, the service
was stopped, but not restarted after the update. This leads to
loss of Internet connectivity after the DHCP lease expires.


If you are only using dhcpcd-base, it implies that DHCP is restarted
by ifupdown via /etc/network/interfaces. Is that the case here?


Can you confirm?


Honestly, I don't get the distinction between dhcpcd and &-base, but I
now see in the package file list that the systemd integration is part of
dhcpcd, not -base. So I have reported the bug for the wrong package.

Regarding point 2 in the original report, I had to run "systemctl start
dhcpcd.service" to restart the daemon.


Can you paste me the content of /etc/network/interfaces and
/etc/network/interfaces.d/ just to be sure?


Sure:

# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The internal LAN interface
allow-hotplug eth0
iface eth0 inet static
address 192.168.11.1/26

# The external WAN interface
allow-hotplug eth1
iface eth1 inet dhcp
# address 192.168.254.2/24
# gateway 192.168.254.1
up /usr/local/bin/freedns

# wireguard
auto wg0
iface wg0 inet static
address 10.0.2.1/24
pre-up ip link add $IFACE type wireguard
pre-up wg setconf $IFACE /etc/wireguard/$IFACE.conf
post-down ip link del $IFACE
# ls -l /etc/network/interfaces.d
total 0
#

Beat
--
https://drbeat.li
tel:+41-79-7706774
gpg: 0x506A903A; 49D5 794A EA77 F907 764F  D89E 304B 93CF 506A 903A
icbm: 47.0452 N, 7.2715 E

"It takes love over gold, and mind over matter" — Dire Straits



Bug#1030725: dhcpcd-base: service does not restart after package updates

2023-02-11 Thread Martin-Éric Racine
On Sat, Feb 11, 2023 at 2:42 PM Beat Bolli  wrote:
> On 11.02.23 12:01, Martin-Éric Racine wrote:
> > On Wed, 8 Feb 2023 08:35:02 +0200
> > =?UTF-8?Q?Martin=2D=C3=89ric_Racine?= 
> > wrote:
> >> On Mon, 06 Feb 2023 20:39:36 +0100 Beat Bolli  wrote:
> >>>This morning, version 9.4.1-16 was installed by my daily
> >>>unattended-upgrade run. As after all recent updates, the service
> >>>was stopped, but not restarted after the update. This leads to
> >>>loss of Internet connectivity after the DHCP lease expires.
> >>
> >> If you are only using dhcpcd-base, it implies that DHCP is restarted
> >> by ifupdown via /etc/network/interfaces. Is that the case here?
> >
> > Can you confirm?
>
> Honestly, I don't get the distinction between dhcpcd and &-base, but I
> now see in the package file list that the systemd integration is part of
> dhcpcd, not -base. So I have reported the bug for the wrong package.
>
> Regarding point 2 in the original report, I had to run "systemctl start
> dhcpcd.service" to restart the daemon.

Can you paste me the content of /etc/network/interfaces and
/etc/network/interfaces.d/ just to be sure?

Martin-Éric



Bug#1030725: dhcpcd-base: service does not restart after package updates

2023-02-11 Thread Beat Bolli

Hi Martin-Éric

On 11.02.23 12:01, Martin-Éric Racine wrote:

On Wed, 8 Feb 2023 08:35:02 +0200
=?UTF-8?Q?Martin=2D=C3=89ric_Racine?= 
wrote:

On Mon, 06 Feb 2023 20:39:36 +0100 Beat Bolli  wrote:

   This morning, version 9.4.1-16 was installed by my daily
   unattended-upgrade run. As after all recent updates, the service
   was stopped, but not restarted after the update. This leads to
   loss of Internet connectivity after the DHCP lease expires.


If you are only using dhcpcd-base, it implies that DHCP is restarted
by ifupdown via /etc/network/interfaces. Is that the case here?


Can you confirm?


Honestly, I don't get the distinction between dhcpcd and &-base, but I 
now see in the package file list that the systemd integration is part of 
dhcpcd, not -base. So I have reported the bug for the wrong package.


Regarding point 2 in the original report, I had to run "systemctl start 
dhcpcd.service" to restart the daemon.


Thanks,

Beat
--
https://drbeat.li
tel:+41-79-7706774
gpg: 0x506A903A; 49D5 794A EA77 F907 764F  D89E 304B 93CF 506A 903A
icbm: 47.0452 N, 7.2715 E

"It takes love over gold, and mind over matter" — Dire Straits



Bug#1030725: dhcpcd-base: service does not restart after package updates

2023-02-11 Thread Martin-Éric Racine
On Wed, 8 Feb 2023 08:35:02 +0200
=?UTF-8?Q?Martin=2D=C3=89ric_Racine?= 
wrote:
> On Mon, 06 Feb 2023 20:39:36 +0100 Beat Bolli  wrote:
> >   This morning, version 9.4.1-16 was installed by my daily
> >   unattended-upgrade run. As after all recent updates, the service
> >   was stopped, but not restarted after the update. This leads to
> >   loss of Internet connectivity after the DHCP lease expires.
>
> If you are only using dhcpcd-base, it implies that DHCP is restarted
> by ifupdown via /etc/network/interfaces. Is that the case here?

Can you confirm?

Martin-Éric



Bug#1030725: dhcpcd-base: service does not restart after package updates

2023-02-07 Thread Martin-Éric Racine
On Mon, 06 Feb 2023 20:39:36 +0100 Beat Bolli  wrote:
>   This morning, version 9.4.1-16 was installed by my daily
>   unattended-upgrade run. As after all recent updates, the service
>   was stopped, but not restarted after the update. This leads to
>   loss of Internet connectivity after the DHCP lease expires.

If you are only using dhcpcd-base, it implies that DHCP is restarted
by ifupdown via /etc/network/interfaces. Is that the case here?

Martin-Éric



Bug#1030725: dhcpcd-base: service does not restart after package updates

2023-02-06 Thread Beat Bolli
Package: dhcpcd-base
Version: 9.4.1-16
Severity: important

Dear Maintainer,

   * What led up to the situation?

  This morning, version 9.4.1-16 was installed by my daily
  unattended-upgrade run. As after all recent updates, the service
  was stopped, but not restarted after the update. This leads to
  loss of Internet connectivity after the DHCP lease expires.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

  I had to restart the service by hand after the upgrade.

   * What was the outcome of this action?

  Again a working Internet connection :-)

   * What outcome did you expect instead?

  I would expect a service to be restarted after an upgrade.


Cheers, Beat

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dhcpcd-base depends on:
ii  adduser   3.130
ii  libc6 2.36-8
ii  libudev1  252.5-2

dhcpcd-base recommends no packages.

dhcpcd-base suggests no packages.

-- Configuration Files:
/etc/dhcpcd.conf changed:
hostname
duid
persistent
vendorclassid
option domain_name_servers, domain_name, domain_search
option classless_static_routes
option interface_mtu
option rapid_commit
require dhcp_server_identifier
slaac private
allowinterfaces eth0 eth1
noipv4ll
noipv6rs
interface eth1
ipv6rs
ia_na 1
ia_pd 2 eth0/0


-- no debconf information