lxc-contianer won't start after upgrade

C

cgr

Active Member
Apr 9, 2018
4
0
41
40
Hello all:)
After updating the system, the containers do not start. After creating a new container, lxc will not start. Below is the log of one of the containers.

Proxmox VE 5.1

Code: 
pve-container@105.service - PVE LXC Container: 105
   Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2018-04-09 13:06:11 CEST; 7min ago
     Docs: man:lxc-start
           man:lxc
           man:pct
  Process: 10811 ExecStart=/usr/bin/lxc-start -n 105 (code=exited, status=1/FAILURE)

Apr 09 13:06:11 pve systemd[1]: Starting PVE LXC Container: 105...
Apr 09 13:06:11 pve lxc-start[10811]: lxc-start: 105: lxccontainer.c: wait_on_daemonized_start: 751 No such file or directory - Failed to receive the container state
Apr 09 13:06:11 pve lxc-start[10811]: lxc-start: 105: tools/lxc_start.c: main: 368 The container failed to start.
Apr 09 13:06:11 pve lxc-start[10811]: lxc-start: 105: tools/lxc_start.c: main: 370 To get more details, run the container in foreground mode.
Apr 09 13:06:11 pve lxc-start[10811]: lxc-start: 105: tools/lxc_start.c: main: 372 Additional information can be obtained by setting the --logfile and --logpriority options.
Apr 09 13:06:11 pve systemd[1]: pve-container@105.service: Control process exited, code=exited status=1
Apr 09 13:06:11 pve systemd[1]: pve-container@105.service: Killing process 10814 (lxc-start) with signal SIGKILL.
Apr 09 13:06:11 pve systemd[1]: Failed to start PVE LXC Container: 105.
Apr 09 13:06:11 pve systemd[1]: pve-container@105.service: Unit entered failed state.
Apr 09 13:06:11 pve systemd[1]: pve-container@105.service: Failed with result 'exit-code'.

Please help...
 
Code: 
proxmox-ve: 5.1-25 (running kernel: 4.13.4-1-pve)
pve-manager: 5.1-35 (running version: 5.1-35/722cc488)
pve-kernel-4.13.4-1-pve: 4.13.4-25
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-15
qemu-server: 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-20
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-16
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-2
pve-container: 2.0-17
pve-firewall: 3.0-3
pve-ha-manager: 2.0-3
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.0-2
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.2-pve1~bpo90
 
Thank you for the quick reply. Will inform you whether the problem has been solved
 
Hallo,

I have a similar problem. I updatted the system via the guy. Afer that, lxc wound start anymore. After I used the kernel 4.15 some container start, but some still did't.

Code: 
      lxc-start 108 20180408171928.493 INFO     lxc_start_ui - tools/lxc_start.c:main:280 - using rcfile /var/lib/lxc/108/config
      lxc-start 108 20180408171928.493 INFO     lxc_lsm - lsm/lsm.c:lsm_init:48 - LSM security driver AppArmor
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:435 - processing: .reject_force_umount  # comment this to allow umount -f;  not recommended.
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:610 - Adding native rule for reject_force_umount action 0(kill).
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:do_resolve_add_rule:276 - Setting Seccomp rule to reject force umounts.
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:614 - Adding compat rule for reject_force_umount action 0(kill).
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:do_resolve_add_rule:276 - Setting Seccomp rule to reject force umounts.
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:do_resolve_add_rule:276 - Setting Seccomp rule to reject force umounts.
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:435 - processing: .[all].
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:435 - processing: .kexec_load errno 1.
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:610 - Adding native rule for kexec_load action 327681(errno).
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:614 - Adding compat rule for kexec_load action 327681(errno).
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:435 - processing: .open_by_handle_at errno 1.
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:610 - Adding native rule for open_by_handle_at action 327681(errno).
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:614 - Adding compat rule for open_by_handle_at action 327681(errno).
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:435 - processing: .init_module errno 1.
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:610 - Adding native rule for init_module action 327681(errno).
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:614 - Adding compat rule for init_module action 327681(errno).
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:435 - processing: .finit_module errno 1.
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:610 - Adding native rule for finit_module action 327681(errno).
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:614 - Adding compat rule for finit_module action 327681(errno).
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:435 - processing: .delete_module errno 1.
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:610 - Adding native rule for delete_module action 327681(errno).
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:614 - Adding compat rule for delete_module action 327681(errno).
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:624 - Merging in the compat Seccomp ctx into the main one.
      lxc-start 108 20180408171928.493 INFO     lxc_conf - conf.c:run_script_argv:457 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "108", config section "lxc".
      lxc-start 108 20180408171928.885 DEBUG    lxc_conf - conf.c:run_buffer:429 - Script /usr/share/lxc/hooks/lxc-pve-prestart-hook 108 lxc pre-start with output: mount: /dev/mapper/ssd1--vg-vm--108--disk--1 is already mounted or /var/lib/lxc/108/rootfs busy
.
      lxc-start 108 20180408171928.885 DEBUG    lxc_conf - conf.c:run_buffer:429 - Script /usr/share/lxc/hooks/lxc-pve-prestart-hook 108 lxc pre-start with output:        /dev/mapper/ssd1--vg-vm--108--disk--1 is already mounted on /var/lib/lxc/108/rootfs
.
      lxc-start 108 20180408171928.885 DEBUG    lxc_conf - conf.c:run_buffer:429 - Script /usr/share/lxc/hooks/lxc-pve-prestart-hook 108 lxc pre-start with output: command 'mount /dev/dm-15 /var/lib/lxc/108/rootfs//' failed: exit code 32
.
      lxc-start 108 20180408171928.894 ERROR    lxc_conf - conf.c:run_buffer:438 - Script exited with status 32.
      lxc-start 108 20180408171928.894 ERROR    lxc_start - start.c:lxc_init:651 - Failed to run lxc.hook.pre-start for container "108".
      lxc-start 108 20180408171928.894 ERROR    lxc_start - start.c:__lxc_start:1444 - Failed to initialize container "108".
      lxc-start 108 20180408171928.894 ERROR    lxc_start_ui - tools/lxc_start.c:main:371 - The container failed to start.
      lxc-start 108 20180408171928.894 ERROR    lxc_start_ui - tools/lxc_start.c:main:375 - Additional information can be obtained by setting the --logfile and --logpriority options.

Code: 
proxmox-ve: 5.1-42 (running kernel: 4.15.10-1-pve)
pve-manager: 5.1-46 (running version: 5.1-46/ae8241d4)
pve-kernel-4.13: 5.1-43
pve-kernel-4.15: 5.1-2
pve-kernel-4.15.10-1-pve: 4.15.10-2
pve-kernel-4.13.16-1-pve: 4.13.16-43
pve-kernel-4.13.13-2-pve: 4.13.13-33
corosync: 2.4.2-pve3
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.0-8
libpve-common-perl: 5.0-28
libpve-guest-common-perl: 2.0-14
libpve-http-server-perl: 2.0-8
libpve-storage-perl: 5.0-17
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 2.1.1-3
lxcfs: 2.0.8-2
novnc-pve: 0.6-4
proxmox-widget-toolkit: 1.0-11
pve-cluster: 5.0-20
pve-container: 2.0-19
pve-docs: 5.1-16
pve-firewall: 3.0-5
pve-firmware: 2.0-4
pve-ha-manager: 2.0-5
pve-i18n: 1.0-4
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.9.1-9
pve-xtermjs: 1.0-2
qemu-server: 5.0-22
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.6-pve1~bpo9

The container 107 is running after using the 4.15. But the 108 still wont't work.

Code: 
#PiHole
arch: amd64
cores: 1
hostname: Mown
lock: mounted
memory: 256
net0: name=eth0,bridge=vmbr0,hwaddr=32:82:F2:17:4C:37,ip=dhcp,type=veth
onboot: 1
ostype: debian
rootfs: VM-Image-ssd1-thin:vm-108-disk-1,size=8G
swap: 256

Code: 
#SFTP Norbert, Sebastian
arch: amd64
cores: 1
hostname: TrinTragula
memory: 256
net0: name=eth0,bridge=vmbr0,hwaddr=7A:A0:76:2F:D9:75,ip=dhcp,type=veth
onboot: 1
ostype: debian
rootfs: herzog:vm-107-disk-1,size=2T
swap: 512

Code: 
  --- Logical volume ---
  LV Path                /dev/ssd1-vg/vm-108-disk-1
  LV Name                vm-108-disk-1
  VG Name                ssd1-vg
  LV UUID                K7vxBo-EajJ-z6xH-63JE-kiKq-FKFI-BqTuiV
  LV Write Access        read/write
  LV Creation host, time arthur, 2018-02-23 18:42:23 +0100
  LV Pool name           ssd-thin
  LV Status              available
  # open                 1
  LV Size                8.00 GiB
  Mapped size            99.59%
  Current LE             2048
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:15

  --- Logical volume ---
  LV Path                /dev/ironwolf10tb_1/vm-107-disk-1
  LV Name                vm-107-disk-1
  VG Name                ironwolf10tb_1
  LV UUID                XbnQDx-gk5y-t0eq-iFzX-fP0a-ND9L-r7JjIz
  LV Write Access        read/write
  LV Creation host, time arthur, 2018-01-29 21:19:24 +0100
  LV Pool name           herzog
  LV Status              available
  # open                 1
  LV Size                2.00 TiB
  Mapped size            39.15%
  Current LE             524288
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:20

Code: 
Hit:1 http://security.debian.org stretch/updates InRelease
Ign:2 http://ftp.de.debian.org/debian stretch InRelease
Hit:3 http://ftp.de.debian.org/debian stretch Release
Hit:5 https://enterprise.proxmox.com/debian/pve stretch InRelease
Reading package lists... Done
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.

Code: 
proxmox-ve: 5.1-42 (running kernel: 4.15.10-1-pve)
pve-manager: 5.1-46 (running version: 5.1-46/ae8241d4)
pve-kernel-4.13: 5.1-43
pve-kernel-4.15: 5.1-2
pve-kernel-4.15.10-1-pve: 4.15.10-2
pve-kernel-4.13.16-1-pve: 4.13.16-43
pve-kernel-4.13.13-2-pve: 4.13.13-33
corosync: 2.4.2-pve3
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.0-8
libpve-common-perl: 5.0-28
libpve-guest-common-perl: 2.0-14
libpve-http-server-perl: 2.0-8
libpve-storage-perl: 5.0-17
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 2.1.1-3
lxcfs: 2.0.8-2
novnc-pve: 0.6-4
proxmox-widget-toolkit: 1.0-11
pve-cluster: 5.0-20
pve-container: 2.0-19
pve-docs: 5.1-16
pve-firewall: 3.0-5
pve-firmware: 2.0-4
pve-ha-manager: 2.0-5
pve-i18n: 1.0-4
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.9.1-9
pve-xtermjs: 1.0-2
qemu-server: 5.0-22
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.6-pve1~bpo9
 
  • Like
Reactions: Mereck
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom