[SOLVED] lxc-start fails! --> unsupported debian version '9.1'

[Maren]

Debian 10.2, out and still bug is still there..... don't forget you need to edit it in two places... Don't forget the

4=> && <=10

 

[dietmar]

Seems you run an old version. Please update.

 

[pawkor]

Two and a half years later... it's still not SOLVED
apt update doesn't show any updates.

Unsupported Debian version 10.3
pve-manager/6.0-4/2a719255 (running kernel: 5.0.15-1-pve)

Solution, edit /usr/share/perl5/PVE/LXC/Setup/Debian.pm and modify version to for example 11.
$version <= 11

--
Kind regards,
pawkor

 

[tom]

Two and a half years later... it's still not SOLVED
apt update doesn't show any updates.

Seems you missed to configure your update repositories.

Read again the docs, e.g.

https://pve.proxmox.com/wiki/Downloads

 

[Maren]

I got myself update to 6.17 and it is still broken...

 

[tom]

I got myself update to 6.17 and it is still broken...

works here, seems there is still an issue with your installation.

 

[oguz]

I got myself update to 6.17 and it is still broken...

this is already fixed since a long time ago. you probably have something missing.

please post your:

* pveversion -v
* output of apt update
* pct config CTID
* debug logs from CT start[0]

[0]: https://pve.proxmox.com/pve-docs/chapter-pct.html#_obtaining_debugging_logs

 

[Maren]

proxmox-ve: 6.1-2 (running kernel: 5.3.18-1-pve)
pve-manager: 6.1-7 (running version: 6.1-7/13e58d5e)
pve-kernel-helper: 6.1-7
pve-kernel-5.3: 6.1-4
pve-kernel-5.0: 6.0-11
pve-kernel-5.3.18-1-pve: 5.3.18-1
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libpve-access-control: 6.0-6
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.0-13
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-4
libpve-storage-perl: 6.1-5
proxmox-ve: 6.1-2 (running kernel: 5.3.18-1-pve)
pve-manager: 6.1-7 (running version: 6.1-7/13e58d5e)
pve-kernel-helper: 6.1-7
pve-kernel-5.3: 6.1-4
pve-kernel-5.0: 6.0-11
pve-kernel-5.3.18-1-pve: 5.3.18-1
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libpve-access-control: 6.0-6
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.0-13
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-4
libpve-storage-perl: 6.1-5
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-3
pve-cluster: 6.1-4
pve-container: 3.0-19
pve-docs: 6.1-6
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.0-10
pve-firmware: 3.0-6
pve-ha-manager: 3.0-8
pve-i18n: 2.0-4
pve-qemu-kvm: 4.1.1-3
pve-xtermjs: 4.3.0-1
qemu-server: 6.1-6
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1
root@bob:~#

libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-3
pve-cluster: 6.1-4
pve-container: 3.0-19
pve-docs: 6.1-6
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.0-10
pve-firmware: 3.0-6
pve-ha-manager: 3.0-8
pve-i18n: 2.0-4
pve-qemu-kvm: 4.1.1-3
pve-xtermjs: 4.3.0-1
qemu-server: 6.1-6
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1
root@bob:~#




root@bob:~# apt update
Hit:1 http://ftp.hk.debian.org/debian buster InRelease
Get:2 http://ftp.hk.debian.org/debian buster-updates InRelease [49.3 kB]
Get:3 http://security.debian.org buster/updates InRelease [65.4 kB]
Hit:4 http://download.proxmox.com/debian/pve buster InRelease
Fetched 115 kB in 1s (105 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
9 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@bob:~#

root@bob:~# pct config 915
arch: amd64
cores: 4
hostname: nginx-template
memory: 2000
nameserver: 192.168.123.123
net0: name=eth0,bridge=vmbr6,gw=192.168.16.254,hwaddr=B2:4D:40:F1:59:B9,ip=192.168.16.20/24,type=veth
onboot: 1
ostype: debian
rootfs: local-lvm:vm-915-disk-0,size=50G
searchdomain: x.com
swap: 512



root@bob:~# pct start 915
Job for pve-container@915.service failed because the control process exited with error code.
See "systemctl status pve-container@915.service" and "journalctl -xe" for details.
command 'systemctl start pve-container@915' failed: exit code 1

^^^^^^^^^^^^^ this is only fixed by editing the debian version in the file prior.

 

[oguz]

hi,

can you please post the debug log of the container? (check the link i've sent you)

the command will create a file /tmp/lxc-ID.log. attach/paste that file here

 

[Maren]

will do, next time I see a container doing this. As the debian version varies on the containers (not all are the same version) some have issues some don't....

I've found that in some cases removing the NIC and recrating it fixes the problem.

will follow up later.

 

[Maren]

Once more i have this issue wen moving a container from one server / proxmox version to another.
Even i have edited the files that check the version
when starting this container I sets all the containers with ? on the proxmox until I stop it..

there is no log file in /tmp/lxc*

 

[oguz]

there is no log file in /tmp/lxc*

you need to run the debug command first. [0]

[0]: https://pve.proxmox.com/pve-docs/chapter-pct.html#_obtaining_debugging_logs

 

[Andres Vargas Duarte]

We also got this error. Here is a quick patch until the Proxmox folks provide an update:

--- /usr/share/perl5/PVE/LXC/Setup/Debian.pm.orig    2017-07-22 08:57:59.495838723 -0700
+++ /usr/share/perl5/PVE/LXC/Setup/Debian.pm    2017-07-22 08:53:18.607049610 -0700
@@ -28,7 +28,7 @@
     $version = $1;

     die "unsupported debian version '$version'\n"
-    if !($version >= 4 && $version <= 9);
+    if !($version >= 4 && $version <= 9.1);

     my $self = { conf => $conf, rootdir => $rootdir, version => $version };

Hello everyone, You always forget to mention that you must restart the PROXMOX server, to make it work, otherwise it is useless to modify this file and the line. Greetings.

 

[Riesling.Dry]

I know, I know: we should regularly update PVE, but this happened on an OLD box w. proxmox-ve: 5.4-2 (running kernel: 4.15.18-8-pve) to which I do not have physical access, so if anything fails, it will go "belly up"...

Only due to this constellation and considering the ol' slogan "Never change a running System" I was too cheeky and edited line 33 in /usr/share/perl5/PVE/LXC/Setup/Debian.pm upping 11 to 12 :

    die "unsupported debian version '$version'\n"
        if !($version >= 4 && $version <= 12);

...and a just yesterday newly installed Deb 11.2 re-started (even without re-booting the host, @ Andres :°). Interestingly during install PVE5.4 didn't complain about the version, let me pull the 11.2 template from the official repo, create a new CT, let me work in/on it with no problems, just refused to re-start after shutdown. Would have been a pitty to have worked half a day on a CT which would never start again (...without a lil "hack" :°)

This is not a recommended "workaround" though - use at your own risk, not on production systems and keep your PVE versions current!

I reckon this issue is solved in newer versions of proxmox anyways :°)

Keep up the great work, guys!
~R.

 

[mathx]

ongoing. oddly, it's <=12, which means '12.0' would qualify, but 12.1 and 12.2 wont. shouldnt it be <=12.9999 or just <13?

 

[Neobin]

ongoing. oddly, it's <=12, which means '12.0' would qualify, but 12.1 and 12.2 wont. shouldnt it be <=12.9999 or just <13?

It already is: <= 13 since mid June this year...:
https://forum.proxmox.com/threads/w...-future-container-versions.131699/post-588096

 

[mathx]

Missing my point, it should be <14 then not <=13.