[SOLVED] Debian 9 LXC container won`t start after upgrade to latest updates

V

[villain]

Member
Dec 29, 2015
2
0
6
52
Russia, Chelyabinsk
Hi
After upgrade to latest updates from debian repos (include debian-proposed-updates) any lxc container with debian 9 (stretch) also updated to latest updates wont start on proxmox ve

Code: 
cat /etc/debian_version
9.1

cat /etc/apt/sources.list
deb http ://httpredir .debian.org/debian stretch main contrib non-free
deb http ://httpredir .debian.org/debian stretch-updates main contrib non-free
deb http ://httpredir .debian.org/debian stretch-proposed-updates main contrib non-free
deb http ://security .debian.org stretch/updates main contrib non-free

deb http ://download .proxmox.com/debian stretch pvetest

Code: 
proxmox-ve: 5.0-16 (running kernel: 4.10.17-1-pve)
pve-manager: 5.0-23 (running version: 5.0-23/af4267bf)
pve-kernel-4.10.15-1-pve: 4.10.15-15
pve-kernel-4.10.17-1-pve: 4.10.17-16
libpve-http-server-perl: 2.0-5
lvm2: 2.02.168-pve2
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-12
qemu-server: 5.0-14
pve-firmware: 2.0-2
libpve-common-perl: 5.0-16
libpve-guest-common-perl: 2.0-11
libpve-access-control: 5.0-5
libpve-storage-perl: 5.0-12
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.0-9
pve-qemu-kvm: 2.9.0-2
pve-container: 2.0-14
pve-firewall: 3.0-2
pve-ha-manager: 2.0-2
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-3
lxcfs: 2.0.7-pve2
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90


Code: 
lxc-start --name=101 -l debug -o 101.log
lxc-start: tools/lxc_start.c: main: 366 The container failed to start.
lxc-start: tools/lxc_start.c: main: 368 To get more details, run the container in foreground mode.
lxc-start: tools/lxc_start.c: main: 370 Additional information can be obtained by setting the --logfile and --logpriority options.

Code: 
      lxc-start 20170718073554.123 INFO     lxc_start_ui - tools/lxc_start.c:main:275 - using rcfile /var/lib/lxc/101/config
      lxc-start 20170718073554.123 WARN     lxc_confile - confile.c:config_pivotdir:2022 - lxc.pivotdir is ignored.  It will soon become an error.
      lxc-start 20170718073554.123 DEBUG    lxc_monitor - monitor.c:lxc_monitord_spawn:330 - Going to wait for pid 17425.
      lxc-start 20170718073554.124 DEBUG    lxc_monitor - monitor.c:lxc_monitord_spawn:349 - Trying to sync with child process.
      lxc-start 20170718073554.124 INFO     lxc_start - start.c:lxc_check_inherited:235 - Closed inherited fd: 4.
      lxc-start 20170718073554.124 DEBUG    lxc_monitor - monitor.c:lxc_monitord_spawn:387 - Using pipe file descriptor 5 for monitord.
      lxc-start 20170718073554.126 DEBUG    lxc_monitor - monitor.c:lxc_monitord_spawn:364 - Successfully synced with child process.
      lxc-start 20170718073554.126 DEBUG    lxc_monitor - monitor.c:lxc_monitord_spawn:333 - Finished waiting on pid 17425.
      lxc-start 20170718073554.126 INFO     lxc_container - lxccontainer.c:do_lxcapi_start:802 - Attempting to set proc title to [lxc monitor] /var/lib/lxc 101
      lxc-start 20170718073554.127 DEBUG    lxc_monitor - monitor.c:lxc_monitord_spawn:330 - Going to wait for pid 17430.
      lxc-start 20170718073554.127 INFO     lxc_lsm - lsm/lsm.c:lsm_init:48 - LSM security driver AppArmor
      lxc-start 20170718073554.127 INFO     lxc_seccomp - seccomp.c:parse_config_v2:418 - processing: .reject_force_umount  # comment this to allow umount -f;  not recommended.
      lxc-start 20170718073554.127 INFO     lxc_seccomp - seccomp.c:parse_config_v2:590 - Adding native rule for reject_force_umount action 0.
      lxc-start 20170718073554.127 INFO     lxc_seccomp - seccomp.c:do_resolve_add_rule:259 - Setting Seccomp rule to reject force umounts.
      lxc-start 20170718073554.127 INFO     lxc_seccomp - seccomp.c:parse_config_v2:593 - Adding compat rule for reject_force_umount action 0.
      lxc-start 20170718073554.127 INFO     lxc_seccomp - seccomp.c:do_resolve_add_rule:259 - Setting Seccomp rule to reject force umounts.
      lxc-start 20170718073554.127 INFO     lxc_seccomp - seccomp.c:do_resolve_add_rule:259 - Setting Seccomp rule to reject force umounts.
      lxc-start 20170718073554.127 INFO     lxc_seccomp - seccomp.c:parse_config_v2:418 - processing: .[all].
      lxc-start 20170718073554.127 INFO     lxc_seccomp - seccomp.c:parse_config_v2:418 - processing: .kexec_load errno 1.
      lxc-start 20170718073554.127 INFO     lxc_seccomp - seccomp.c:parse_config_v2:590 - Adding native rule for kexec_load action 327681.
      lxc-start 20170718073554.127 INFO     lxc_seccomp - seccomp.c:parse_config_v2:593 - Adding compat rule for kexec_load action 327681.
      lxc-start 20170718073554.127 INFO     lxc_seccomp - seccomp.c:parse_config_v2:418 - processing: .open_by_handle_at errno 1.
      lxc-start 20170718073554.127 INFO     lxc_seccomp - seccomp.c:parse_config_v2:590 - Adding native rule for open_by_handle_at action 327681.
      lxc-start 20170718073554.127 INFO     lxc_seccomp - seccomp.c:parse_config_v2:593 - Adding compat rule for open_by_handle_at action 327681.
      lxc-start 20170718073554.127 INFO     lxc_seccomp - seccomp.c:parse_config_v2:418 - processing: .init_module errno 1.
      lxc-start 20170718073554.127 INFO     lxc_seccomp - seccomp.c:parse_config_v2:590 - Adding native rule for init_module action 327681.
      lxc-start 20170718073554.127 INFO     lxc_seccomp - seccomp.c:parse_config_v2:593 - Adding compat rule for init_module action 327681.
      lxc-start 20170718073554.127 INFO     lxc_seccomp - seccomp.c:parse_config_v2:418 - processing: .finit_module errno 1.
      lxc-start 20170718073554.127 INFO     lxc_seccomp - seccomp.c:parse_config_v2:590 - Adding native rule for finit_module action 327681.
      lxc-start 20170718073554.127 INFO     lxc_seccomp - seccomp.c:parse_config_v2:593 - Adding compat rule for finit_module action 327681.
      lxc-start 20170718073554.127 INFO     lxc_seccomp - seccomp.c:parse_config_v2:418 - processing: .delete_module errno 1.
      lxc-start 20170718073554.127 INFO     lxc_seccomp - seccomp.c:parse_config_v2:590 - Adding native rule for delete_module action 327681.
      lxc-start 20170718073554.127 INFO     lxc_seccomp - seccomp.c:parse_config_v2:593 - Adding compat rule for delete_module action 327681.
      lxc-start 20170718073554.127 INFO     lxc_seccomp - seccomp.c:parse_config_v2:603 - Merging in the compat Seccomp ctx into the main one.
      lxc-start 20170718073554.127 INFO     lxc_conf - conf.c:run_script_argv:483 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "101", config section "lxc".
      lxc-start 20170718073554.128 DEBUG    lxc_monitor - monitor.c:lxc_monitord_spawn:349 - Trying to sync with child process.
      lxc-start 20170718073554.128 INFO     lxc_start - start.c:lxc_check_inherited:235 - Closed inherited fd: 4.
      lxc-start 20170718073554.128 DEBUG    lxc_monitor - monitor.c:lxc_monitord_spawn:387 - Using pipe file descriptor 5 for monitord.
      lxc-start 20170718073554.130 DEBUG    lxc_monitor - monitor.c:lxc_monitord_spawn:364 - Successfully synced with child process.
      lxc-start 20170718073554.130 DEBUG    lxc_monitor - monitor.c:lxc_monitord_spawn:333 - Finished waiting on pid 17430.
      lxc-start 20170718073554.130 INFO     lxc_monitor - monitor.c:lxc_monitor_sock_name:201 - using monitor socket name "lxc/ad055575fe28ddd5//var/lib/lxc" (length of socket name 33 must be <= 105)
      lxc-start 20170718073554.130 DEBUG    lxc_monitor - monitor.c:lxc_monitor_open:225 - opening monitor socket lxc/ad055575fe28ddd5//var/lib/lxc with len 33
      lxc-start 20170718073554.673 ERROR    lxc_conf - conf.c:run_buffer:464 - Script exited with status 25.
      lxc-start 20170718073554.673 ERROR    lxc_start - start.c:lxc_init:450 - Failed to run lxc.hook.pre-start for container "101".
      lxc-start 20170718073554.673 ERROR    lxc_start - start.c:__lxc_start:1337 - Failed to initialize container "101".
      lxc-start 20170718073554.673 WARN     lxc_commands - commands.c:lxc_cmd_rsp_recv:177 - Command get_cgroup failed to receive response: Connection reset by peer.
      lxc-start 20170718073559.678 ERROR    lxc_start_ui - tools/lxc_start.c:main:366 - The container failed to start.
      lxc-start 20170718073559.679 ERROR    lxc_start_ui - tools/lxc_start.c:main:368 - To get more details, run the container in foreground mode.
      lxc-start 20170718073559.679 ERROR    lxc_start_ui - tools/lxc_start.c:main:370 - Additional information can be obtained by setting the --logfile and --logpriority options.
 
Encountered the same issue myself now. Looks like the problem lies within "/usr/share/perl5/PVE/LXC/Setup/Debian.pm". It seems that it does not know what to do with Debian version 9.1 yet.

Added
$version = 9.0 if $version eq '9.1';
Click to expand...
above the line
$version = 9.0 if $version eq 'stretch/sid';
Click to expand...
to fool the module to treat Debian 9.1 as 9.0, that made my containers functional again.
 
  • Like
Reactions: vooze
Modifying /usr/share/perl5/PVE/LXC/Setup/Debian.pm is not needed, installing the last upgrade for pve-containers is enough, but having someting more explicit that "script exit with status 25" would have been better. I had to strace the command to get what was the error, and only after that i got here.
 
Hi! First: sorry for re-open this, but I have the same problem, and I'm newbie in proxmox.
Second: "I do not have a valid subscription" (For the doubts I clarify it)

Well, here my pveversion:

proxmox-ve: 4.2-48 (running kernel: 4.4.6-1-pve)
pve-manager: 4.2-2 (running version: 4.2-2/725d76f0)
pve-kernel-4.4.6-1-pve: 4.4.6-48
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-39
qemu-server: 4.0-72
pve-firmware: 1.1-8
libpve-common-perl: 4.0-59
libpve-access-control: 4.0-16
libpve-storage-perl: 4.0-50
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-14
pve-container: 1.0-62
pve-firewall: 2.0-25
pve-ha-manager: 1.0-28
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve9~jessie
Click to expand...

Already make an update and upgrade, as far as I can the free version, but I had to edit the file /usr/share/perl5/PVE/LXC/Setup/Debian.pm, just like Sakarias said.

Question: Is there any alternative for my version of proxmox to recognize debian 9.1? (Remember, "I do not have a valid subscription")

Thanks
 
hectorejch said:
Hi! First: sorry for re-open this, but I have the same problem, and I'm newbie in proxmox.
Second: "I do not have a valid subscription" (For the doubts I clarify it)

Well, here my pveversion:



Already make an update and upgrade, as far as I can the free version, but I had to edit the file /usr/share/perl5/PVE/LXC/Setup/Debian.pm, just like Sakarias said.

Question: Is there any alternative for my version of proxmox to recognize debian 9.1? (Remember, "I do not have a valid subscription")

Thanks
Click to expand...

Just use the pve-no-subscription repo for updates, read again:

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

and the linked article:
https://pve.proxmox.com/wiki/Package_Repositories
 
Hello,

This problem reappears for me with an up-to-date PVE and debian 9.2.
Is there a way to fix this besides editing /usr/share/perl5/PVE/LXC/Setup/Debian.pm ?

Thank you
 
cserem said:
Hello,

This problem reappears for me with an up-to-date PVE and debian 9.2.
Is there a way to fix this besides editing /usr/share/perl5/PVE/LXC/Setup/Debian.pm ?

Thank you
Click to expand...

I do not see this problem here. Post your pveversion -v.
 
Code: 
pveversion  -v
proxmox-ve: 5.0-15 (running kernel: 4.10.15-1-pve)
pve-manager: 5.0-23 (running version: 5.0-23/af4267bf)
pve-kernel-4.10.15-1-pve: 4.10.15-15
libpve-http-server-perl: 2.0-5
lvm2: 2.02.168-pve2
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-10
qemu-server: 5.0-12
pve-firmware: 2.0-2
libpve-common-perl: 5.0-16
libpve-guest-common-perl: 2.0-11
libpve-access-control: 5.0-5
libpve-storage-perl: 5.0-12
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.0-6
pve-qemu-kvm: 2.9.0-2
pve-container: 2.0-14
pve-firewall: 3.0-1
pve-ha-manager: 2.0-2
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-3
lxcfs: 2.0.7-pve2
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90

The used lxc template is "debian-9.0-standard_9.0-2_amd64.tar.gz" booting it, then doing "apt update; apt upgrade;poweroff", then trying to start it up again is not working with the error code noted in the topic.

Adding "$version=9.0 if $version eq '9.2';" to Debian.pm allows it to boot.
 
cserem said:
Code: 
pveversion  -v
proxmox-ve: 5.0-15 (running kernel: 4.10.15-1-pve)
pve-manager: 5.0-23 (running version: 5.0-23/af4267bf)
pve-kernel-4.10.15-1-pve: 4.10.15-15
libpve-http-server-perl: 2.0-5
lvm2: 2.02.168-pve2
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-10
qemu-server: 5.0-12
pve-firmware: 2.0-2
libpve-common-perl: 5.0-16
libpve-guest-common-perl: 2.0-11
libpve-access-control: 5.0-5
libpve-storage-perl: 5.0-12
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.0-6
pve-qemu-kvm: 2.9.0-2
pve-container: 2.0-14
pve-firewall: 3.0-1
pve-ha-manager: 2.0-2
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-3
lxcfs: 2.0.7-pve2
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90

The used lxc template is "debian-9.0-standard_9.0-2_amd64.tar.gz" booting it, then doing "apt update; apt upgrade;poweroff", then trying to start it up again is not working with the error code noted in the topic.

Adding "$version=9.0 if $version eq '9.2';" to Debian.pm allows it to boot.
Click to expand...

you are running an outdated PVE 5..
 
Oops, had my apt.sources messed up, that is why i didn't receive the PVE upgrades.
Upgrading did solve the issue.
Sorry, and thank you for your time.
 
Hi @All,

First of all Im sorry, I see this is a really old thread but its the only one that describes my issue exactly.
I have not been able to solve this.

I have followed the guide in this article. This is my scenario.

1. I created a LXC CT and a CentOS VM and they worked perfectly. I decided then to:
apt-get update and apt dist-upgrade before putting this into production.

2. Servers did their update/upgrade and they were rebooted. After this they came back online just fine.
The VM was able to get started, NOT the LXC CT though.

I figured something might have gone wrong with that CT, so i simply removed it.
Created another CT, gives me the same error.

This is the error:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Job for lxc@102.service failed because the control process exited with error code.
See "systemctl status lxc@102.service" and "journalctl -xe" for details.
TASK ERROR: command 'systemctl start lxc@102' failed: exit code 1
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

This is my REPO List

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
root@cloud:~# cat /etc/apt/sources.list
deb http://ftp.at.debian.org/debian stretch main contrib

# security updates
deb http://security.debian.org stretch/updates main contrib
root@cloud:~# cat /etc/apt/sources.list.d/pve-enterprise.list
deb https://enterprise.proxmox.com/debian/pve stretch pve-enterprise
root@cloud:~#
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

And this is the current status of the system.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
root@cloud:~# pveversion -v
proxmox-ve: 5.0-19 (running kernel: 4.10.17-2-pve)
pve-manager: 5.0-30 (running version: 5.0-30/5ab26bc)
pve-kernel-4.10.17-2-pve: 4.10.17-19
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve3
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-12
qemu-server: 5.0-15
pve-firmware: 2.0-2
libpve-common-perl: 5.0-16
libpve-guest-common-perl: 2.0-11
libpve-access-control: 5.0-6
libpve-storage-perl: 5.0-14
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.0-9
pve-qemu-kvm: 2.9.0-3
pve-container: 2.0-15
pve-firewall: 3.0-2
pve-ha-manager: 2.0-2
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-3
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90
root@cloud:~#
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Thanks, advise is appreciated.

Foster
 
Right. Noticed that AFTER i reinstalled the 4 nodes.
Simply commented out the "enterprise" repo and now apt-update gives no error.

Thanks for the input.
 
Hi im having similiar issue on my proxmox cluster, details below.

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

###@###:~# journalctl -xe
-- The result is failed.
Apr 26 12:46:48 3s1 systemd[1]: pve-container@104.service: Unit entered failed state.
Apr 26 12:46:48 3s1 systemd[1]: pve-container@104.service: Failed with result 'exit-code'.
Apr 26 12:46:48 3s1 pct[6562]: command 'systemctl start pve-container@104' failed: exit code 1
Apr 26 12:46:48 3s1 pct[6518]: <root@pam> end task UPID:3s1:000019A2:000027BB:5CC2E197:vzstart:104:root@pam: command 'systemctl start pve-container@104' failed: exit code 1

###@###:~# pveversion -v
proxmox-ve: 5.4-1 (running kernel: 4.15.18-13-pve)
pve-manager: 5.4-4 (running version: 5.4-4/97a96833)
pve-kernel-4.15: 5.4-1
pve-kernel-4.15.18-13-pve: 4.15.18-37
pve-kernel-4.15.18-11-pve: 4.15.18-34
pve-kernel-4.15.18-4-pve: 4.15.18-23
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-51
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-13
libpve-storage-perl: 5.0-41
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-3
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-26
pve-cluster: 5.0-36
pve-container: 2.0-37
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-20
pve-firmware: 2.0-6
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 2.12.1-3
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-50
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2

###@###:~# cat /etc/apt/sources.list
deb h**p://ftp.pl.debian.org/debian stretch main contrib
deb h**ps://packages.fluentbit.io/debian/stretch stretch main
# security updates
deb h**p://security.debian.org stretch/updates main contrib
 
You must log in or register to reply here.
Top Bottom