TASK ERROR: command 'systemctl start pve-container@198' failed: exit code 1

omzen

New Member
Mar 19, 2021
1
0
1
46
I am using Proxmox CT, since last night one of the vm CT was stopped, so the server was not running, while the other vm in one proxmox server was in normal life.

several times it was tried to start and the condition still stopped with the message on the server status as follows:
root@proxmox:~# pct start 198
Job for pve-container@198.service failed because the control process exited with error code.
See "systemctl status pve-container@198.service" and "journalctl -xe" for details.
command 'systemctl start pve-container@198' failed: exit code 1

root@proxmox:~# pveversion -v
proxmox-ve: 6.1-2 (running kernel: 5.3.10-1-pve)
pve-manager: 6.1-3 (running version: 6.1-3/37248ce6)
pve-kernel-5.3: 6.0-12
pve-kernel-helper: 6.0-12
pve-kernel-5.3.10-1-pve: 5.3.10-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.2-pve4
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.13-pve1
libpve-access-control: 6.0-5
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-9
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-3
libpve-storage-perl: 6.1-2
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve3
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-1
pve-cluster: 6.1-2
pve-container: 3.0-14
pve-docs: 6.1-3
pve-edk2-firmware: 2.20191002-1
pve-firewall: 4.0-9
pve-firmware: 3.0-4
pve-ha-manager: 3.0-8
pve-i18n: 2.0-3
pve-qemu-kvm: 4.1.1-2
pve-xtermjs: 3.13.2-1
qemu-server: 6.1-2
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.2-pve2

root@proxmox:~# pct config 198
arch: amd64
cores: 4
hostname: da.dns.biz.id
memory: 8192
net0: name=eth0,bridge=vmbr0,firewall=1,gw=49.0.2.193,hwaddr=46:E9:05:BB:28:BC,ip=49.0.2.198/29,type=veth
onboot: 1
ostype: centos
rootfs: local-lvm:vm-198-disk-0,size=120G
swap: 8192
unprivileged: 1

root@proxmox:~# lxc-start -n 198 -F -l DEBUG -o /tmp/lxc-198.log
lxc-start: 198: conf.c: run_buffer: 352 Script exited with status 2
lxc-start: 198: start.c: lxc_init: 897 Failed to run lxc.hook.pre-start for container "198"
lxc-start: 198: start.c: __lxc_start: 2032 Failed to initialize container "198"
Segmentation fault

lxc-start 198 20210318233043.884 INFO seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for finit_module action 327681(errno)
lxc-start 198 20210318233043.884 INFO seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for finit_module action 327681(errno)
lxc-start 198 20210318233043.884 INFO seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for finit_module action 327681(errno)
lxc-start 198 20210318233043.884 INFO seccomp - seccomp.c:parse_config_v2:789 - Processing "delete_module errno 1"
lxc-start 198 20210318233043.884 INFO seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for delete_module action 327681(errno)
lxc-start 198 20210318233043.884 INFO seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for delete_module action 327681(errno)
lxc-start 198 20210318233043.884 INFO seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for delete_module action 327681(errno)
lxc-start 198 20210318233043.884 INFO seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for delete_module action 327681(errno)
lxc-start 198 20210318233043.884 INFO seccomp - seccomp.c:parse_config_v2:789 - Processing "keyctl errno 38"
lxc-start 198 20210318233043.884 INFO seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for keyctl action 327718(errno)
lxc-start 198 20210318233043.884 INFO seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for keyctl action 327718(errno)
lxc-start 198 20210318233043.884 INFO seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for keyctl action 327718(errno)
lxc-start 198 20210318233043.884 INFO seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for keyctl action 327718(errno)
lxc-start 198 20210318233043.884 INFO seccomp - seccomp.c:parse_config_v2:1008 - Merging compat seccomp contexts into main context
lxc-start 198 20210318233043.884 INFO conf - conf.c:run_script_argv:372 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "198", config section "lxc"
lxc-start 198 20210318233044.470 DEBUG conf - conf.c:run_buffer:340 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 198 lxc pre-start produced output: unable to detect OS distribution

lxc-start 198 20210318233044.475 ERROR conf - conf.c:run_buffer:352 - Script exited with status 2
lxc-start 198 20210318233044.475 ERROR start - start.c:lxc_init:897 - Failed to run lxc.hook.pre-start for container "198"
lxc-start 198 20210318233044.475 ERROR start - start.c:__lxc_start:2032 - Failed to initialize container "198"

root@proxmox:~# pct mount 198
mounted CT 198 in '/var/lib/lxc/198/rootfs'

root@proxmox:~# cat /etc/pve/storage.cfg
dir: local
path /var/lib/vz
content iso,vztmpl,backup

lvmthin: local-lvm
thinpool data
vgname pve
content rootdir,images

Please help, thank you.
 
hi,

here is the relevant error:
Code:
lxc-start 198 20210318233043.884 INFO conf - conf.c:run_script_argv:372 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "198", config section "lxc"
lxc-start 198 20210318233044.470 DEBUG conf - conf.c:run_buffer:340 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 198 lxc pre-start produced output: unable to detect OS distribution

after you run pct mount 198 could you also run: find /var/lib/lxc/198/rootfs -maxdepth 3 and post the output here?


also your version proxmox-ve: 6.1-2 (running kernel: 5.3.10-1-pve) is a bit old so i would recommend you to upgrade to the latest packages to get the new features and security fixes.
 

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 yours easily in our online shop.

Buy now!