Couldn't get ifupdown2 installed. Need to repair.

iMagic

Member
Feb 13, 2020
8
0
6
20
A strange situation - I followed a recommendation on installing ifupdown2, but got in issues. The new package shows "not configured yet", while ifupdown is already removed.
ifupdown2 install log follows:
root@PVE:~# apt install ifupdown2
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
python-argcomplete
Suggested packages:
ethtool python-gvgen
The following packages will be REMOVED:
ifenslave ifupdown
The following NEW packages will be installed:
ifupdown2 python-argcomplete
0 upgraded, 2 newly installed, 2 to remove and 58 not upgraded.
Need to get 225 kB of archives.
After this operation, 1,213 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ftp.debian.org/debian buster/main amd64 ifupdown2 all 1.2.5-1 [196 kB]
Get:2 http://ftp.debian.org/debian buster/main amd64 python-argcomplete all 1.8.1-1 [29.2 kB]
Fetched 225 kB in 1s (176 kB/s)
dpkg: ifupdown: dependency problems, but removing anyway as you requested:
ifenslave depends on ifupdown (>= 0.7.46).

(Reading database ... 46558 files and directories currently installed.)
Removing ifupdown (0.8.35+pve1) ...
Selecting previously unselected package ifupdown2.
(Reading database ... 46522 files and directories currently installed.)
Preparing to unpack .../ifupdown2_1.2.5-1_all.deb ...
Unpacking ifupdown2 (1.2.5-1) ...
dpkg: ifenslave: dependency problems, but removing anyway as you requested:
pve-manager depends on ifenslave (>= 2.6) | ifupdown2; however:
Package ifenslave is to be removed.
Package ifupdown2 is not configured yet.

(Reading database ... 46626 files and directories currently installed.)
Removing ifenslave (2.9) ...
Selecting previously unselected package python-argcomplete.
(Reading database ... 46614 files and directories currently installed.)
Preparing to unpack .../python-argcomplete_1.8.1-1_all.deb ...
Unpacking python-argcomplete (1.8.1-1) ...
Setting up python-argcomplete (1.8.1-1) ...
Setting up ifupdown2 (1.2.5-1) ...
Installing new version of config file /etc/default/networking ...
Installing new version of config file /etc/init.d/networking ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for systemd (241-7~deb10u2) ...

root@PVE:~# ifupdown2
-bash: ifupdown2: command not found

Any ideas on how to get this repaired?

Update.
While trying to bring back any functionality, had lost network at all. So, it's likely that I have to edit locally network config files to enable networking and to be able to install packages. Right?
 
Last edited:
it seems you missed to add our repositories (since you installed ifupdown2 from the debian repos instead of ours)
-> try to install ifupdown from the local cache (/var/cache/apt/archives ) to get back networking
-> add our repositories https://pve.proxmox.com/wiki/Package_Repositories
-> install ifupdown2
 
  • Like
Reactions: iMagic
alternatively you can add networking manually with the 'ip' command
e.g. 'ip add'
see 'man ip' for details on how to do this
 
Thank you Dominik
As I can understand, there is at least one more package uninstalled - ifenslave. Will ifupdown2 put it back or a tool instead?
 
if both deb files are in the archive you can install both at the same time

dpkg -i 1.deb 2.deb
after that you have to probably fix your broken packages with 'apt --fix-broken install'
 
  • Like
Reactions: iMagic
Thank you Dominik
As I can understand, there is at least one more package uninstalled - ifenslave. Will ifupdown2 put it back or a tool instead?

ifupdown2 replace "ifupdown + ifenslave"

to revert, simply "apt install ifupdown", will install ifenslave too.
 
  • Like
Reactions: iMagic and matrix
Gents,
Will somebody help me understand what's going on?
I connected to console and found that enp1s0 is down. So, I applied ifup to the interface and set it with local IP. After this I could SSH into it and run apt set-source with proxmox repositories. All other repositories I have commented.
After this I get following.

root@PVE:~# apt install ifupdown2
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
net-tools
Use 'apt autoremove' to remove it.
Suggested packages:
ethtool python-gvgen
The following packages will be REMOVED:
ifenslave ifupdown
The following NEW packages will be installed:
ifupdown2
0 upgraded, 1 newly installed, 2 to remove and 61 not upgraded.
Need to get 216 kB of archives.
After this operation, 1,256 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://download.proxmox.com/debian/pve buster/pve-no-subscription amd64 ifupdown2 all 2.0.1-1+pve4 [216 kB]
Fetched 216 kB in 0s (989 kB/s)
dpkg: ifupdown: dependency problems, but removing anyway as you requested:
ifenslave depends on ifupdown (>= 0.7.46); however:
Package ifupdown is to be removed.
Package ifupdown2 which provides ifupdown is not installed.

(Reading database ... 46643 files and directories currently installed.)
Removing ifupdown (0.8.35) ...
Selecting previously unselected package ifupdown2.
(Reading database ... 46607 files and directories currently installed.)
Preparing to unpack .../ifupdown2_2.0.1-1+pve4_all.deb ...
Unpacking ifupdown2 (2.0.1-1+pve4) ...
dpkg: ifenslave: dependency problems, but removing anyway as you requested:
pve-manager depends on ifenslave (>= 2.6) | ifupdown2; however:
Package ifenslave is to be removed.
Package ifupdown2 is not configured yet.

(Reading database ... 46718 files and directories currently installed.)
Removing ifenslave (2.9) ...
Setting up ifupdown2 (2.0.1-1+pve4) ...
Installing new version of config file /etc/network/ifupdown2/addons.conf ...
Installing new version of config file /etc/network/ifupdown2/ifupdown2.conf ...
Processing triggers for man-db (2.8.5-2) ...
root@PVE:~#
root@PVE:~# ifupdown2
-bash: ifupdown2: command not found
root@PVE:~#

So, I guess I'm not able to change the network from GUI anymore, right?

Current config is:
auto lo
iface lo inet loopback

iface enp1s0 inet manual

iface enp4s0 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.55.18
netmask 255.255.255.0
gateway 192.168.55.15
bridge-ports enp1s0
bridge-stp off
bridge-fd 0

auto vmbr1
iface vmbr1 inet static
address 192.168.50.18
netmask 24
bridge-ports enp4s0
bridge-stp off
bridge-fd 0
#none
To be noted, all started with adding vmbr1 for a second Ethernet interface.
 
>>ifupdown2
>>-bash: ifupdown2: command not found
>>So, I guess I'm not able to change the network from GUI anymore, right?


they are no "ifupdown2" command.
ifupdown2 replace ifupdown, with same syntax (ifup ....), and manage /etc/network/interfaces with same format. (but with reload support)


your configuration seem to be ok

>> connected to console and found that enp1s0 is down.
after a server boot? if yes, that's seem strange. it should be up.
 
they are no "ifupdown2" command.
ifupdown2 replace ifupdown, with same syntax (ifup ....), and manage /etc/network/interfaces with same format. (but with reload support)

>> connected to console and found that enp1s0 is down.
after a server boot? if yes, that's seem strange. it should be up.
My God! I thought that there must be a distinct command ifupdown... :D
Ok, so I assume that my ifupdown2 is ok as long as there are both ifup and ifdown commands.
enp1s0 got down because some troubles while creating a second bridge. Right at the moment it seems to be working, but I don't know exactly am I missing something or not.
 
I am presenting the same problem, when I create a second bridge and reload the network the web interface does not load
 
pveversion -v ?

can you send your /etc/network/interfaces.new && /etc/network/interfaces files ?

any error on the reload task ?
Hi,
am a bit near all this, I think.
And it goes like:
after having installed the full proxmox via all Hetzner tutorials I was not sure, if I had the right /etc/network/interfaces at all:
Bash:
root@rescue /boot/grub # cat /etc/network/interfaces
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback
# iface lo inet6 loopback
# Network device LAN

auto enp0s31f6
iface enp0s31f6 inet static
        address 88.231.210.91/26
        gateway 88.231.210.65
        pointopoint 88.231.210.65
        up route add -net 88.231.210.64 netmask 255.255.255.192 gw 88.231.210.65 dev enp0s31f6
# route 88.231.210.64/26 via 88.231.210.65

auto vmbr0
iface vmbr0 inet static
        address 88.231.210.91/26
        bridge-ports none
        bridge-stp off
        bridge-fd 0
        up ip route add 88.231.210.117/32 dev vmbr0
        up ip route add 88.231.210.123/32 dev vmbr0

iface vmbr0 inet static
        address 88.231.210.91/26
        up ip route add 88.231.210.117/32 dev vmbr0
        up ip route add 88.231.210.123/32 dev vmbr0

auto vmbr1
iface vmbr1 inet manual
        address 178.53.197.209/29
        bridge-ports none
        bridge-stp off
        bridge-fd 0

auto vmbr2
iface vmbr2 inet static
        address 178.53.197.210/29
        bridge-ports none
        bridge-stp off
        bridge-fd 0

auto vmbr3
iface vmbr3 inet manual
        address 178.53.197.211/29
        bridge-ports none
        bridge-stp off
        bridge-fd 0

auto vmbr4
iface vmbr4 inet static
        address 178.53.197.212/29
        bridge-ports none
        bridge-stp off
        bridge-fd 0
(IPs slightly changed, but in order)
Usually I wanted to walk through because I made Proxmox with KVM and Windows already run couple of times in 2016 and 17. Setting up the windows VMs and that with bridged NIC was easy in the past.
Now I am still on the rescue, because I believe after I had finished this network interfaces setup that I need to use ifupdown to make the config work, which I had to first install. Unfullfilled dependencies and so, the other That what happened then confused me to the end... The computer did not let me in wether on shell nor on the GUI but its was up and running like normal.
I had installed and wanted to test netplan, and without uninstalling left it...
as well. All went faster than expected then...
Can it be the source of problems? Will purge this....

So, I suppose anything from this setup is mixed. And I want to have routed setup on the host, ok, that means, not a big main bridge whih gives full access for the whole host plus guests right? But a routed is desired to have more control, that each following routed (or forwarded) connection can be better controlled, correct me if am wrong, please. So, in the end, when all is set up, then I used many many attempts. But only to hear from you now, :D that on a windows machine I as well can use a VPN plugin, or wrong? So, I think of having 20 VMs but I wont need subnets for them do I? Can I not run the nodes with one IP or two and leave the rest to a software VPN running in the guest?
But now am still stuck.

Here my ifconfig.
Bash:
root@rescue ~ # ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 88.99.210.91  netmask 255.255.255.192  broadcast 0.0.0.0
        inet6 2a01:4f8:10a:3b5a::2  prefixlen 64  scopeid 0x0<global>
        ether 90:1b:0e:bd:a0:c8  txqueuelen 1000  (Ethernet)
        RX packets 354903  bytes 460667944 (439.3 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 170353  bytes 51175579 (48.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  memory 0xf7200000-f7220000 

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 102  bytes 16054 (15.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 102  bytes 16054 (15.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
The drives environment:
Bash:
NAME                 MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0                  7:0    0     4G  1 loop
nvme1n1              259:0    0   477G  0 disk
├─vg0-root           253:0    0    26G  0 lvm  /mnt
├─vg0-heavyload1     253:3    0   350G  0 lvm 
├─vg0-vmdata_tmeta   253:4    0   100M  0 lvm 
│ └─vg0-vmdata-tpool 253:6    0   100G  0 lvm 
│   └─vg0-vmdata     253:7    0   100G  0 lvm 
└─vg0-vmdata_tdata   253:5    0   100G  0 lvm 
  └─vg0-vmdata-tpool 253:6    0   100G  0 lvm 
    └─vg0-vmdata     253:7    0   100G  0 lvm 
nvme0n1              259:1    0   477G  0 disk
├─nvme0n1p1          259:2    0   512M  0 part
└─nvme0n1p2          259:3    0 476.4G  0 part
  ├─vg0-root         253:0    0    26G  0 lvm  /mnt
  ├─vg0-swap         253:1    0     6G  0 lvm 
  └─vg0-home         253:2    0 455.4G  0 lvm  /mnt/home
INI:
root@rescue ~ # blkid -o list
device                                   fs_type        label           mount point                                  UUID
---------------------------------------------------------------------------------------------------------------------------------------------------------
/dev/loop0                               ext2                           (in use)                                     40c4ea95-0ecc-4c51-9f3e-e49d8f62f167
/dev/nvme1n1                             LVM2_member                    (in use)                                     56d07n-5HHb-L37p-93O3-Yf25-5bFn-7OqYhp
/dev/nvme0n1p1                           ext3                           (not mounted)                                639f9dfb-4543-4731-9d48-247c9792bb83
/dev/nvme0n1p2                           LVM2_member                    (in use)                                     MtTK78-mINc-7Y2S-l150-ahnB-Jafg-TH9G9H
/dev/mapper/vg0-root                     ext3                           /mnt                                         8856777b-0851-4a1c-a1b4-2db939510a94
/dev/mapper/vg0-swap                     swap                           (not mounted)                                f2e1a5d0-c688-4bd7-b7f4b-7a1425e2a699
/dev/mapper/vg0-home                     xfs                            /mnt/home                                    56bbc717-b2b1-4ccd-91ce23-26b06a5f0d61
/dev/mapper/vg0-heavyload1               ext4                           (not mounted)                                4071b58d-19fb-4833-95a5-3f2dd4fc184d
/dev/nvme0n1

And the main challenge was now, why the rescue system let me not chroot into, and told me the lock file existed.
WHen I partly tried this way to chroot in I felt more secure about being really on the system in the background.
 
Code:
rm /etc/apt/sources.list.d/pve-enterprise.list
Bash:
echo 'deb http://download.proxmox.com/debian/pve buster pve-no-subscription' >> /etc/apt/sources.list.d/pve-no-subscription.list
Bash:
apt-get install ifupdown2
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!