i can't start container

[charef]

pct start 119
Job for lxc@119.service failed. See 'systemctl status lxc@119.service' and 'journalctl -xn' for details.
command 'systemctl start lxc@121' failed: exit code 1

lxc-start -n 119 -F -lDEBUG -o lxc-119.log
unsupported debian version '9.6'
lxc-start: conf.c: run_buffer: 405 Script exited with status 25.
lxc-start: start.c: lxc_init: 450 Failed to run lxc.hook.pre-start for container "119".
lxc-start: start.c: __lxc_start: 1321 Failed to initialize container "119".
lxc-start: tools/lxc_start.c: main: 366 The container failed to start.
lxc-start: tools/lxc_start.c: main: 370 Additional information can be obtained by setting the --logfile and --logpriority options.


cat /etc/pve/storage.cfg
dir: local
path /var/lib/vz
content rootdir,images,vztmpl,iso
maxfiles 0

nfs: nfs
export /var/lib/vz/nfs
path /mnt/pve/nfs
server 127.0.0.1
content backup
maxfiles 1
options vers=3

dir: save
path /root/back
content backup
maxfiles 1
shared 0

 

[Stoiko Ivanov]

unsupported debian version '9.6'

sounds like you're running a rather old version of pve - could you post the output of `pveversion -v`?

The debug information should be available in the file `lxc-119.log` in the directory you ran the `lxc-start -n 119 -F -lDEBUG -o lxc-119.log`
please post its contents (replace all sensitive information)

 

[charef]

Thanks for yout replay

I am running a proxmox4.4 with kernel: 4.4.62-1-pve

pveversion -v
proxmox-ve: 4.4-88 (running kernel: 4.4.62-1-pve)
pve-manager: 4.4-13 (running version: 4.4-13/7ea56165)
pve-kernel-4.4.59-1-pve: 4.4.59-87
pve-kernel-4.4.44-1-pve: 4.4.44-84
pve-kernel-4.4.62-1-pve: 4.4.62-88
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-2~pve4+1
libqb0: 1.0.1-1
pve-cluster: 4.0-49
qemu-server: 4.0-110
pve-firmware: 1.1-11
libpve-common-perl: 4.0-94
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-76
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-2
pve-docs: 4.4-4
pve-qemu-kvm: 2.7.1-4
pve-container: 1.0-100
pve-firewall: 2.0-33
pve-ha-manager: 1.0-40
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-4
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1~pve80

here is the log file

cat lxc-119.log
      lxc-start 20180104084842.945 INFO     lxc_start_ui - tools/lxc_start.c:main:275 - using rcfile /var/lib/lxc/119/config
      lxc-start 20180104084842.945 WARN     lxc_confile - confile.c:config_pivotdir:1910 - lxc.pivotdir is ignored.  It will soon become an error.
      lxc-start 20180104084842.945 WARN     lxc_start - start.c:lxc_check_inherited:238 - Inherited fd: 3.
      lxc-start 20180104084842.945 INFO     lxc_lsm - lsm/lsm.c:lsm_init:48 - LSM security driver AppArmor
      lxc-start 20180104084842.945 INFO     lxc_seccomp - seccomp.c:parse_config_v2:402 - processing: .reject_force_umount  # comment this to allow umount -f;  not recommended.
      lxc-start 20180104084842.946 INFO     lxc_seccomp - seccomp.c:parse_config_v2:567 - Adding native rule for reject_force_umount action 0.
      lxc-start 20180104084842.946 INFO     lxc_seccomp - seccomp.c:do_resolve_add_rule:251 - Setting Seccomp rule to reject force umounts.
      lxc-start 20180104084842.946 INFO     lxc_seccomp - seccomp.c:parse_config_v2:570 - Adding compat rule for reject_force_umount action 0.
      lxc-start 20180104084842.946 INFO     lxc_seccomp - seccomp.c:do_resolve_add_rule:251 - Setting Seccomp rule to reject force umounts.
      lxc-start 20180104084842.946 INFO     lxc_seccomp - seccomp.c:parse_config_v2:402 - processing: .[all].
      lxc-start 20180104084842.946 INFO     lxc_seccomp - seccomp.c:parse_config_v2:402 - processing: .kexec_load errno 1.
      lxc-start 20180104084842.946 INFO     lxc_seccomp - seccomp.c:parse_config_v2:567 - Adding native rule for kexec_load action 327681.
      lxc-start 20180104084842.946 INFO     lxc_seccomp - seccomp.c:parse_config_v2:570 - Adding compat rule for kexec_load action 327681.
      lxc-start 20180104084842.946 INFO     lxc_seccomp - seccomp.c:parse_config_v2:402 - processing: .open_by_handle_at errno 1.
      lxc-start 20180104084842.946 INFO     lxc_seccomp - seccomp.c:parse_config_v2:567 - Adding native rule for open_by_handle_at action 327681.
      lxc-start 20180104084842.946 INFO     lxc_seccomp - seccomp.c:parse_config_v2:570 - Adding compat rule for open_by_handle_at action 327681.
      lxc-start 20180104084842.946 INFO     lxc_seccomp - seccomp.c:parse_config_v2:402 - processing: .init_module errno 1.
      lxc-start 20180104084842.946 INFO     lxc_seccomp - seccomp.c:parse_config_v2:567 - Adding native rule for init_module action 327681.
      lxc-start 20180104084842.946 INFO     lxc_seccomp - seccomp.c:parse_config_v2:570 - Adding compat rule for init_module action 327681.
      lxc-start 20180104084842.946 INFO     lxc_seccomp - seccomp.c:parse_config_v2:402 - processing: .finit_module errno 1.
      lxc-start 20180104084842.946 INFO     lxc_seccomp - seccomp.c:parse_config_v2:567 - Adding native rule for finit_module action 327681.
      lxc-start 20180104084842.946 WARN     lxc_seccomp - seccomp.c:do_resolve_add_rule:270 - Seccomp: got negative for syscall: -10085: finit_module.
      lxc-start 20180104084842.946 WARN     lxc_seccomp - seccomp.c:do_resolve_add_rule:271 - This syscall will NOT be blacklisted.
      lxc-start 20180104084842.946 INFO     lxc_seccomp - seccomp.c:parse_config_v2:570 - Adding compat rule for finit_module action 327681.
      lxc-start 20180104084842.946 WARN     lxc_seccomp - seccomp.c:do_resolve_add_rule:270 - Seccomp: got negative for syscall: -10085: finit_module.
      lxc-start 20180104084842.946 WARN     lxc_seccomp - seccomp.c:do_resolve_add_rule:271 - This syscall will NOT be blacklisted.
      lxc-start 20180104084842.946 INFO     lxc_seccomp - seccomp.c:parse_config_v2:402 - processing: .delete_module errno 1.
      lxc-start 20180104084842.946 INFO     lxc_seccomp - seccomp.c:parse_config_v2:567 - Adding native rule for delete_module action 327681.
      lxc-start 20180104084842.946 INFO     lxc_seccomp - seccomp.c:parse_config_v2:570 - Adding compat rule for delete_module action 327681.
      lxc-start 20180104084842.946 INFO     lxc_seccomp - seccomp.c:parse_config_v2:580 - Merging in the compat Seccomp ctx into the main one.
      lxc-start 20180104084842.946 INFO     lxc_conf - conf.c:run_script_argv:424 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "119", config section "lxc".
      lxc-start 20180104084843.450 ERROR    lxc_conf - conf.c:run_buffer:405 - Script exited with status 25.
      lxc-start 20180104084843.450 ERROR    lxc_start - start.c:lxc_init:450 - Failed to run lxc.hook.pre-start for container "119".
      lxc-start 20180104084843.450 ERROR    lxc_start - start.c:__lxc_start:1321 - Failed to initialize container "119".
      lxc-start 20180104084843.450 ERROR    lxc_start_ui - tools/lxc_start.c:main:366 - The container failed to start.
      lxc-start 20180104084843.450 ERROR    lxc_start_ui - tools/lxc_start.c:main:370 - Additional information can be obtained by setting the --logfile and --logpriority options.

 

[charef]

Is the fact that i am running a debian9 container on proxmox4 causes a problem. Then to solve it, i should upgrade proxmox to 5 or downgrade container to debian 8?

 

[Stoiko Ivanov]

PVE 4.x has been EOL for quite some time now (see https://pve.proxmox.com/wiki/FAQ) - please consider upgrading!

seem that the prestart-hook exited with an error - please post the container config - maybe we'll see something there

 

[charef]

here is the 119.conf

arch: amd64
cpulimit: 10
cpuunits: 1024
hostname: xxxx
memory: 8000
net0: name=eth0,bridge=vmbr0,gw=xxx,hwaddr=xxxx,ip=xxxx/32,type=veth
ostype: debian
rootfs: local:119/vm-119-disk-1.raw,size=26G
swap: 8512