Error while installing fupdown2 version 3.2.0-1+pmx7

[jsabater]

Hey everyone!

So I have a server at OVH in France and just installed a Debian 12 Bookworm using their installer. And I started the installation of Proxmox Backup Server 3.0.1, just as I did a few days ago on a Debian 12 Bookworm on a server at Hetzner in Helsinki (one will be the replica of the other one).

Unfortunately, I got a post-installation error from ifupdown2:

root@pbs1:~# apt-get install ifupdown2
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Suggested packages:
  bridge-utils python3-gvgen python3-mako
The following packages will be REMOVED:
  ifupdown
The following NEW packages will be installed:
  ifupdown2
0 upgraded, 1 newly installed, 1 to remove and 9 not upgraded.
Need to get 253 kB of archives.
After this operation, 1,574 kB of additional disk space will be used.
Do you want to continue? [Y/n]  
Get:1 http://download.proxmox.com/debian/pbs bookworm/pbs-no-subscription amd64 ifupdown2 all 3.2.0-1+pmx7 [253 kB]
Fetched 253 kB in 0s (2,264 kB/s)  
(Reading database ... 49175 files and directories currently installed.)
Removing ifupdown (0.8.41) ...
Selecting previously unselected package ifupdown2.
(Reading database ... 49138 files and directories currently installed.)
Preparing to unpack .../ifupdown2_3.2.0-1+pmx7_all.deb ...
Unpacking ifupdown2 (3.2.0-1+pmx7) ...
Setting up ifupdown2 (3.2.0-1+pmx7) ...
Installing new version of config file /etc/default/networking ...
Reloading network config on first install
error: Another instance of this program is already running.
dpkg: error processing package ifupdown2 (--configure):
 installed ifupdown2 package post-installation script subprocess returned error exit status 89
Processing triggers for man-db (2.11.2-2) ...
Errors were encountered while processing:
 ifupdown2
E: Sub-process /usr/bin/dpkg returned an error code (1)

Then I attempted this:

root@pbs1:~# dpkg --configure -a
Setting up ifupdown2 (3.2.0-1+pmx7) ...
Reloading network config on first install
error: Another instance of this program is already running.
dpkg: error processing package ifupdown2 (--configure):
 installed ifupdown2 package post-installation script subprocess returned error exit status 89
Errors were encountered while processing:
 ifupdown2

I installed ifupdown, purged the configuration of ifupdown2 and rebooted. With the new Proxmox kernel, I attempted the installation again and it worked fine:

root@pbs1:~# apt-get install ifupdown2
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Suggested packages:
  bridge-utils python3-gvgen python3-mako
The following packages will be REMOVED:
  ifupdown
The following NEW packages will be installed:
  ifupdown2
0 upgraded, 1 newly installed, 1 to remove and 9 not upgraded.
Need to get 253 kB of archives.
After this operation, 1,574 kB of additional disk space will be used.
Do you want to continue? [Y/n]  
Get:1 http://download.proxmox.com/debian/pbs bookworm/pbs-no-subscription amd64 ifupdown2 all 3.2.0-1+pmx7 [253 kB]
Fetched 253 kB in 0s (15.8 MB/s)  
(Reading database ... 49175 files and directories currently installed.)
Removing ifupdown (0.8.41) ...
Selecting previously unselected package ifupdown2.
(Reading database ... 49138 files and directories currently installed.)
Preparing to unpack .../ifupdown2_3.2.0-1+pmx7_all.deb ...
Unpacking ifupdown2 (3.2.0-1+pmx7) ...
Setting up ifupdown2 (3.2.0-1+pmx7) ...
Installing new version of config file /etc/default/networking ...
Reloading network config on first install
Processing triggers for man-db (2.11.2-2) ...
[/ICODE]


Any idea on how to debug what happened? Maybe this will help, which I checked after the error, before reinstalling [ICODE]ifupdown[/ICODE] and rebooting:

[CODE]
root@pbs1:~# systemctl status networking.service  
○ networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.service; disabled; preset: enabled)
     Active: inactive (dead)
       Docs: man:interfaces(5)
root@pbs1:~# systemctl enable networking
Synchronizing state of networking.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable networking
Created symlink /etc/systemd/system/multi-user.target.wants/networking.service → /lib/systemd/system/networking.serv
ice.
Created symlink /etc/systemd/system/network-online.target.wants/networking.service → /lib/systemd/system/networking.
service.

And this is what I found after installing ifupdown2 after reboot, which apparently was a success but I didn't trust it and checked the status of the networking service:

root@pbs1:~# systemctl status networking.service  
● networking.service - Network initialization
Loaded: error (Reason: Unit networking.service failed to load properly, please adjust/correct and reload servi>
Active: active (exited) since Thu 2024-01-11 23:43:16 UTC; 6min ago
       Docs: man:interfaces(5)
             man:ifup(8)
             man:ifdown(8)
   Main PID: 559 (code=exited, status=0/SUCCESS)
        CPU: 31ms

Jan 11 23:43:16 pbs1 systemd[1]: Starting networking.service - Raise network interfaces...
Jan 11 23:43:16 pbs1 systemd[1]: Finished networking.service - Raise network interfaces.
root@pbs1:~# systemctl enable networking.service
Synchronizing state of networking.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable networking
root@pbs1:~# systemctl status networking.service  
● networking.service - Network initialization
Loaded: loaded (/lib/systemd/system/networking.service; enabled; preset: enabled)
Active: active (exited) since Thu 2024-01-11 23:43:16 UTC; 7min ago
       Docs: man:interfaces(5)
             man:ifup(8)
             man:ifdown(8)
   Main PID: 559 (code=exited, status=0/SUCCESS)
        CPU: 31ms

Jan 11 23:43:16 pbs1 systemd[1]: Starting networking.service - Raise network interfaces...
Jan 11 23:43:16 pbs1 systemd[1]: Finished networking.service - Raise network interfaces.

Should I report a bug in the bug tracker?

Thanks.

 

[silverstone]

Just experienced this as well on my latest Proxmox VE Upgrade to PVE 8.x.

In my case removing /tmp/.ifupdown2-first-install fixed / bypassed this Issue.