[SOLVED] when clicking on package versions I see ifupdown2 not installed correctly ?

Spirog

Member
Jan 31, 2022
230
25
18
Chicago, IL
hello, when clicking on package versions I see ifupdown2 not installed correctly ?
should this be installed instead of ifupdown or is ifupdown the better version ?

Code:
proxmox-ve: 7.2-1 (running kernel: 5.15.35-3-pve)
pve-manager: 7.2-5 (running version: 7.2-5/12f1e639)
pve-kernel-5.15: 7.2-5
pve-kernel-helper: 7.2-5
pve-kernel-5.13: 7.1-9
pve-kernel-5.4: 6.4-11
pve-kernel-5.15.35-3-pve: 5.15.35-6
pve-kernel-5.15.35-2-pve: 5.15.35-5
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.4.157-1-pve: 5.4.157-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 16.2.9-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: 0.8.36+pve1
ifupdown2: not correctly installed
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-2
libpve-storage-perl: 7.2-5
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.12-1
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.3-1
proxmox-backup-file-restore: 2.2.3-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-1
pve-container: 4.2-1
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-2
pve-ha-manager: 3.3-4
pve-i18n: 2.7-2
pve-qemu-kvm: 6.2.0-10
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1

thanks in advance for your help
 

fiona

Proxmox Staff Member
Staff member
Aug 1, 2019
2,436
483
88
Hi,
ifupdown2 is recommended, because you can apply changes to the network configuration without rebooting. Please try apt --fix-broken install or apt install ifupdown2. The ifupdown package should be automatically removed by apt, because ifupdown2 conflicts with it.
 
  • Like
Reactions: Spirog

Spirog

Member
Jan 31, 2022
230
25
18
Chicago, IL
Hi,
ifupdown2 is recommended, because you can apply changes to the network configuration without rebooting. Please try apt --fix-broken install or apt install ifupdown2. The ifupdown package should be automatically removed by apt, because ifupdown2 conflicts with it.
hello @Fabian_E
Thanks for your replies in advance

When I Install ifupdown2 then the ifupdown shows not correctly installed ?

Code:
proxmox-ve: 7.2-1 (running kernel: 5.15.35-2-pve)
pve-manager: 7.2-5 (running version: 7.2-5/12f1e639)
pve-kernel-5.15: 7.2-5
pve-kernel-helper: 7.2-5
pve-kernel-5.13: 7.1-9
pve-kernel-5.4: 6.4-11
pve-kernel-5.15.35-3-pve: 5.15.35-6
pve-kernel-5.15.35-2-pve: 5.15.35-5
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.4.157-1-pve: 5.4.157-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 16.2.9-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: not correctly installed
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-2
libpve-storage-perl: 7.2-5
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.12-1
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.3-1
proxmox-backup-file-restore: 2.2.3-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-1
pve-container: 4.2-1
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-2
pve-ha-manager: 3.3-4
pve-i18n: 2.7-2
pve-qemu-kvm: 6.2.0-10
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1

so I also ran apt --fix-broken install
Code:
root@proxmox:~# apt --fix-broken install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@proxmox:~#


should I purge the ifupdown or leave it as is even though it's stating not installed correctly ?
 

fiona

Proxmox Staff Member
Staff member
Aug 1, 2019
2,436
483
88
What does dpkg-query --list ifupdown show?
 
  • Like
Reactions: Spirog

Spirog

Member
Jan 31, 2022
230
25
18
Chicago, IL
What does dpkg-query --list ifupdown show?
@Fabian_E
root@proxmox:~# dpkg-query --list ifupdown Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==============-============-============-================================================ rc ifupdown 0.8.36+pve1 amd64 high level tools to configure network interfaces root@proxmox:~#
 
Last edited:

fiona

Proxmox Staff Member
Staff member
Aug 1, 2019
2,436
483
88
The rc means that there is still configuration for the package left over. Please check with dpkg-query --listfiles ifupdown what is still there. You just need to check for files, not directories. If you never modified those files, you likely won't need them. Afterwards you can run apt purge ifupdown.
 
  • Like
Reactions: Spirog

Spirog

Member
Jan 31, 2022
230
25
18
Chicago, IL
The rc means that there is still configuration for the package left over. Please check with dpkg-query --listfiles ifupdown what is still there. You just need to check for files, not directories. If you never modified those files, you likely won't need them. Afterwards you can run apt purge ifupdown.
@Fabian_E so I would check these directories for files ? I never modified any type of files so hopefully safe to purge. :)


Code:
root@proxmox:~# dpkg-query --listfiles ifupdown
/etc
/etc/default
/etc/init.d
/etc/init.d/networking
/usr
/usr/lib
/usr/lib/systemd
/usr/lib/systemd/system
root@proxmox:~#

Thanks for your help
Regards,
Spiro
 

Spirog

Member
Jan 31, 2022
230
25
18
Chicago, IL
The rc means that there is still configuration for the package left over. Please check with dpkg-query --listfiles ifupdown what is still there. You just need to check for files, not directories. If you never modified those files, you likely won't need them. Afterwards you can run apt purge ifupdown.
@Fabian_E

I just ran Purge
dpkg: warning: while removing ifupdown, directory '/usr/lib/systemd/system' not empty so not removed


Code:
root@proxmox:~# apt purge ifupdown
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
  ifupdown*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 93914 files and directories currently installed.)
Purging configuration files for ifupdown (0.8.36+pve1) ...
dpkg: warning: while removing ifupdown, directory '/usr/lib/systemd/system' not empty so not removed
root@proxmox:~#
 

fiona

Proxmox Staff Member
Staff member
Aug 1, 2019
2,436
483
88
@Fabian_E

I just ran Purge
dpkg: warning: while removing ifupdown, directory '/usr/lib/systemd/system' not empty so not removed
Yes, the directories don't won't be removed, if not empty, so if not belonging only to that package ;)
 
  • Like
Reactions: Spirog

Spirog

Member
Jan 31, 2022
230
25
18
Chicago, IL
Yes, the directories don't won't be removed, if not empty, so if not belonging only to that package ;)
@Fabian_E

I did a ls under that directory and found 2 files one was ifupdown2
and the other was below
ifup@.service
not sure if that belongs to ifupdown2 or ifupdown ?
should I leave it or remove it ?
Thanks alot for your help again!!
Totally appreciate you and the Whole team on Proxmox :)
Code:
root@proxmox:/usr/lib/systemd/system# cat ifup@.service
[Unit]
Description=ifup for %I
After=local-fs.target network-pre.target networking.service systemd-sysctl.service
Before=network.target shutdown.target network-online.target
Conflicts=shutdown.target
BindsTo=sys-subsystem-net-devices-%i.device
After=sys-subsystem-net-devices-%i.device
DefaultDependencies=no
IgnoreOnIsolate=yes

[Service]
# avoid stopping on shutdown via stopping system-ifup.slice
Slice=system.slice
ExecStart=/sbin/ifup --allow=hotplug %I
ExecStop=/sbin/ifdown %I
RemainAfterExit=true
TimeoutStartSec=2min
root@proxmox:/usr/lib/systemd/system#
 
Last edited:

fiona

Proxmox Staff Member
Staff member
Aug 1, 2019
2,436
483
88
@Fabian_E

I did a ls under that directory and found 2 files one was ifupdown2
and the other was below
ifup@.service
not sure if that belongs to ifupdown2 or ifupdown ?
should I leave it or remove it ?
No, please don't remove any files there manually if you're not sure. Since you used apt purge ifupdown, all files belonging to the ifupdown package are already gone. What I meant by "check for files, not directories" is in this list
Code:
root@proxmox:~# dpkg-query --listfiles ifupdown
/etc
/etc/default
/etc/init.d
/etc/init.d/networking
/usr
/usr/lib
/usr/lib/systemd
/usr/lib/systemd/system
root@proxmox:~#
the only file is /etc/init.d/networking and you should've checked if you modified that. But in this specific case it's arguably not even a proper configuration file and I'd be surprised if you ever made any changes (worth preserving) to it ;)
 
  • Like
Reactions: Spirog

Spirog

Member
Jan 31, 2022
230
25
18
Chicago, IL
I'd be surprised if you ever made any changes (worth preserving) to it
yes you are correct. I never made any changes that's for sure.

OK I will make this resolved and as ALWAYS THANKS SO MUCH!!

you make my days less stressful ;)

Warm Regards,
Spiro
 

Spirog

Member
Jan 31, 2022
230
25
18
Chicago, IL
After your instructions and purge it all looks good now :)

Code:
proxmox-ve: 7.2-1 (running kernel: 5.15.35-2-pve)
pve-manager: 7.2-5 (running version: 7.2-5/12f1e639)
pve-kernel-5.15: 7.2-5
pve-kernel-helper: 7.2-5
pve-kernel-5.13: 7.1-9
pve-kernel-5.4: 6.4-11
pve-kernel-5.15.35-3-pve: 5.15.35-6
pve-kernel-5.15.35-2-pve: 5.15.35-5
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.4.157-1-pve: 5.4.157-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 16.2.9-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-2
libpve-storage-perl: 7.2-5
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.12-1
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.3-1
proxmox-backup-file-restore: 2.2.3-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-1
pve-container: 4.2-1
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-2
pve-ha-manager: 3.3-4
pve-i18n: 2.7-2
pve-qemu-kvm: 6.2.0-10
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1
 

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 your own in 60 seconds.

Buy now!