LXC container doesn't start after host reboot

K

Klaus Schulte

New Member
Feb 15, 2017
3
0
1
58
Hi all,

I'm facing the problem that the lxc container want to start after host reboot.
Proxmox message:
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options.
TASK ERROR: command 'lxc-start -n 100' failed: exit code 1​

Then I tried to start the container via command line:
lxc-start -n 100 --logfile=".." --logpriority=debug

The logfile content:
lxc-start 1487146729.593 INFO lxc_start_ui - lxc_start.c:main:264 - using rcfile /var/lib/lxc/100/config
lxc-start 1487146729.594 WARN lxc_confile - confile.c:config_pivotdir:1817 - lxc.pivotdir is ignored. It will soon become an error.
lxc-start 1487146729.595 WARN lxc_cgmanager - cgmanager.c:cgm_get:994 - do_cgm_get exited with error
lxc-start 1487146729.595 INFO lxc_lsm - lsm/lsm.c:lsm_init:48 - LSM security driver AppArmor
lxc-start 1487146729.596 INFO lxc_seccomp - seccomp.c:parse_config_v2:324 - processing: .reject_force_umount # comment this to allow umount -f; not recommended.
lxc-start 1487146729.596 INFO lxc_seccomp - seccomp.c:parse_config_v2:426 - Adding native rule for reject_force_umount action 0
lxc-start 1487146729.596 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

lxc-start 1487146729.596 INFO lxc_seccomp - seccomp.c:parse_config_v2:429 - Adding compat rule for reject_force_umount action 0
lxc-start 1487146729.596 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

lxc-start 1487146729.596 INFO lxc_seccomp - seccomp.c:parse_config_v2:324 - processing: .[all].
lxc-start 1487146729.596 INFO lxc_seccomp - seccomp.c:parse_config_v2:324 - processing: .kexec_load errno 1.
lxc-start 1487146729.596 INFO lxc_seccomp - seccomp.c:parse_config_v2:426 - Adding native rule for kexec_load action 327681
lxc-start 1487146729.596 INFO lxc_seccomp - seccomp.c:parse_config_v2:429 - Adding compat rule for kexec_load action 327681
lxc-start 1487146729.596 INFO lxc_seccomp - seccomp.c:parse_config_v2:324 - processing: .open_by_handle_at errno 1.
lxc-start 1487146729.596 INFO lxc_seccomp - seccomp.c:parse_config_v2:426 - Adding native rule for open_by_handle_at action 327681
lxc-start 1487146729.596 INFO lxc_seccomp - seccomp.c:parse_config_v2:429 - Adding compat rule for open_by_handle_at action 327681
lxc-start 1487146729.596 INFO lxc_seccomp - seccomp.c:parse_config_v2:324 - processing: .init_module errno 1.
lxc-start 1487146729.596 INFO lxc_seccomp - seccomp.c:parse_config_v2:426 - Adding native rule for init_module action 327681
lxc-start 1487146729.596 INFO lxc_seccomp - seccomp.c:parse_config_v2:429 - Adding compat rule for init_module action 327681
lxc-start 1487146729.596 INFO lxc_seccomp - seccomp.c:parse_config_v2:324 - processing: .finit_module errno 1.
lxc-start 1487146729.596 INFO lxc_seccomp - seccomp.c:parse_config_v2:426 - Adding native rule for finit_module action 327681
lxc-start 1487146729.596 WARN lxc_seccomp - seccomp.c:do_resolve_add_rule:233 - Seccomp: got negative # for syscall: finit_module
lxc-start 1487146729.596 WARN lxc_seccomp - seccomp.c:do_resolve_add_rule:234 - This syscall will NOT be blacklisted
lxc-start 1487146729.596 INFO lxc_seccomp - seccomp.c:parse_config_v2:429 - Adding compat rule for finit_module action 327681
lxc-start 1487146729.596 WARN lxc_seccomp - seccomp.c:do_resolve_add_rule:233 - Seccomp: got negative # for syscall: finit_module
lxc-start 1487146729.596 WARN lxc_seccomp - seccomp.c:do_resolve_add_rule:234 - This syscall will NOT be blacklisted
lxc-start 1487146729.596 INFO lxc_seccomp - seccomp.c:parse_config_v2:324 - processing: .delete_module errno 1.
lxc-start 1487146729.596 INFO lxc_seccomp - seccomp.c:parse_config_v2:426 - Adding native rule for delete_module action 327681
lxc-start 1487146729.596 INFO lxc_seccomp - seccomp.c:parse_config_v2:429 - Adding compat rule for delete_module action 327681
lxc-start 1487146729.596 INFO lxc_seccomp - seccomp.c:parse_config_v2:436 - Merging in the compat seccomp ctx into the main one
lxc-start 1487146729.596 INFO lxc_conf - conf.c:run_script_argv:362 - Executing script '/usr/share/lxc/hooks/lxc-pve-prestart-hook' for container '100', config section 'lxc'
lxc-start 1487146730.135 ERROR lxc_conf - conf.c:run_buffer:342 - Script exited with status 32
lxc-start 1487146730.135 ERROR lxc_start - start.c:lxc_init:436 - failed to run pre-start hooks for container '100'.
lxc-start 1487146730.135 ERROR lxc_start - start.c:__lxc_start:1170 - failed to initialize the container
lxc-start 1487146730.135 ERROR lxc_start_ui - lxc_start.c:main:344 - The container failed to start.
lxc-start 1487146730.135 ERROR lxc_start_ui - lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options.​

pveversion -v
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​

cat /etc/pve/lxc/100.conf
arch: i386
cpulimit: 2
cpuunits: 1024
hostname: enya
memory: 4096
net0: bridge=vmbr0,gw=10.46.130.1,hwaddr=3A:66:35:33:30:34,ip=10.46.130.228/24,name=eth0,type=veth
ostype: centos
rootfs: local-lvm:vm-100-disk-1,size=192G
swap: 4096​

cat /var/lib/lxc/100/config
lxc.arch = i386
lxc.include = /usr/share/lxc/config/centos.common.conf
lxc.monitor.unshare = 1
lxc.tty = 2
lxc.environment = TERM=linux
lxc.utsname = enya
lxc.cgroup.memory.limit_in_bytes = 4294967296
lxc.cgroup.memory.memsw.limit_in_bytes = 8589934592
lxc.cgroup.cpu.cfs_period_us = 100000
lxc.cgroup.cpu.cfs_quota_us = 200000
lxc.cgroup.cpu.shares = 1024
lxc.rootfs = /var/lib/lxc/100/rootfs
lxc.network.type = veth
lxc.network.veth.pair = veth100i0
lxc.network.hwaddr = 3A:66:35:33:30:34
lxc.network.name = eth0​

I've no clue why the container is not starting at all.
Any help is appreciated.
Klaus
 
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