Networking issue : container won't start after last update

romainrbr

Active Member
Dec 7, 2015
4
0
41
Hello,

After updating Proxmox to 4.0-16, none of my containers won't start, throwing the following error :
Undefined subroutine &PVE::Network::is_ip_in_cidr called at /usr/share/perl5/PVE/LXC/Setup/Debian.pm

Here is the network configuration that was previously working :
427ZCN0.png


And here is the bridge configuration :
Hjjhlbf.png



I fixed the issue by editing commenting the following lines in /usr/share/perl5/PVE/LXC/Setup/Debian.pm

if (defined($cidr) && !PVE::Network::is_ip_in_cidr($d->{gw}, $cidr, 4)) {
# gateway is not reachable, need an extra route
$net->{needsroute} = 1;
}

Can anyone confirm that this is indeed a bug ?
 
Last edited:
No this should not be a bug, but rather a bit off an outdated version, you need to have the libpve-common package in version 4.0-34 version or newer as they implement the PVE::Network::is_ip_in_cidr methods.
Proxmox VE 4.0-22 is also the newest stable version.

Did you upgrade to the newest PVE4.0 by
# apt-get update
# apt-get dist-upgrade
 

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!