[SOLVED] LXC Debian 10 no longer start

Bristow

Member
Oct 4, 2019
12
3
8
48
I'm on Proxmox 6

I have images based on Debian 10, yesterday I stopped one and it never restarted:


Code:
Job for pve-container@100.service failed because the control process exited with error code.
See "systemctl status pve-container@100.service" and "journalctl -xe" for details.
TASK ERROR: command 'systemctl start pve-container@100' failed: exit code 1

I updated my Proxmox (without restarting), but not better.

Here's what I found.

I create my container with the Debian 10 template, turn it on, connect, turn it off and restart it without any problem.
On the other hand, if I turn it on, I connect, I do an 'apt update' and then a 'apt dist-upgrade', so if I turn it off, I can no longer turn it on again.

I tested with Ubuntu 18.04, I have no problem. With Debian 9, the same, no problem.

Thank you for your help!
 

Attachments

  • pvereport.log
    48.2 KB · Views: 2

Chris

Proxmox Staff Member
Staff member
Jan 2, 2019
697
76
48

Bristow

Member
Oct 4, 2019
12
3
8
48
Thanks Chris !

Here the output :

Code:
root@proxmox:~# pveversion -v
proxmox-ve: 6.0-2 (running kernel: 5.0.15-1-pve)
pve-manager: 6.0-4 (running version: 6.0-4/2a719255)
pve-kernel-5.0: 6.0-5
pve-kernel-helper: 6.0-5
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.2-pve2
criu: 3.11-3
glusterfs-client: 5.5-3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.10-pve1
libpve-access-control: 6.0-2
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-2
libpve-guest-common-perl: 3.0-1
libpve-http-server-perl: 3.0-2
libpve-storage-perl: 6.0-5
libqb0: 1.0.5-1
lvm2: 2.03.02-pve3
lxc-pve: 3.1.0-61
lxcfs: 3.0.3-pve60
novnc-pve: 1.0.0-60
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.0-5
pve-cluster: 6.0-4
pve-container: 3.0-3
pve-docs: 6.0-4
pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-5
pve-firmware: 3.0-2
pve-ha-manager: 3.0-2
pve-i18n: 2.0-2
pve-qemu-kvm: 4.0.0-3
pve-xtermjs: 3.13.2-1
qemu-server: 6.0-5
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.1-pve1

And the log is attached. Thanks
 

Attachments

  • lxc-102.log
    7.3 KB · Views: 3

oguz

Proxmox Retired Staff
Retired Staff
Nov 19, 2018
5,207
704
118
hi,

it is indeed related to the thread @Chris mentioned.

problem lies here:
Code:
lxc-start 102 20191004135907.288 DEBUG    conf - conf.c:run_buffer:326 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 102 lxc pre-start with output: unsupported debian version '10.1'

this has already been fixed, you just need to upgrade your packages on the PVE nodes (apt update && apt full-upgrade) and then it should work.
 

Bristow

Member
Oct 4, 2019
12
3
8
48
this has already been fixed, you just need to upgrade your packages on the PVE nodes (apt update && apt full-upgrade) and then it should work.

Do i need a reboot ? Because :

Code:
root@proxmox:~# apt update
Hit:1 http://ftp.fr.debian.org/debian buster InRelease
Hit:2 http://ftp.fr.debian.org/debian buster-updates InRelease
Hit:3 http://security.debian.org buster/updates InRelease
Err:4 https://enterprise.proxmox.com/debian/pve buster InRelease
  401  Unauthorized [IP: XXX.YYY.ZZZ.XXX 443]
Reading package lists... Done                          
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/buster/InRelease  401  Unauthorized [IP: XXX.YYY.ZZZ.XXX 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve buster InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
root@proxmox:~# apt full-upgrade
Reading package lists... Done
Building dependency tree      
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@proxmox:~#
 
Last edited:

Chris

Proxmox Staff Member
Staff member
Jan 2, 2019
697
76
48
Do i need a reboot ? Because :

Code:
root@proxmox:~# apt update
Hit:1 http://ftp.fr.debian.org/debian buster InRelease
Hit:2 http://ftp.fr.debian.org/debian buster-updates InRelease
Hit:3 http://security.debian.org buster/updates InRelease
Err:4 https://enterprise.proxmox.com/debian/pve buster InRelease
  401  Unauthorized [IP: XXX.YYY.ZZZ.XXX 443]
Reading package lists... Done                         
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/buster/InRelease  401  Unauthorized [IP: XXX.YYY.ZZZ.XXX 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve buster InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
root@proxmox:~# apt full-upgrade
Reading package lists... Done
Building dependency tree     
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@proxmox:~#
Please make sure you correctly set up the no-subscription repository. Have a look at the documentation on how to do that https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_package_repositories
A reboot should not be necessary for most of the updates, except for such as e.g. kernel updates.
 

Bristow

Member
Oct 4, 2019
12
3
8
48
Thanks @Chris and @oguz for your help.

I'm a little french college and i can't buy support for ProxMox but i appreciate your help. It solved my problem.
 

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!