Container Not getting started in Proxmox 6.2-4

J

janiali

New Member
Mar 25, 2020
20
0
1
51
Hello,

Having strange issue after installation of new Proxmox 6.2.4 as below:

I have created one container with Centos 6 template.
after creating the container it is not getting started

it is giving me these logs in /var/log/messages

Jun 2 00:21:00 srv1 kernel: [ 7859.693428] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null)
Jun 2 00:21:00 srv1 kernel: [ 7859.851100] audit: type=1400 audit(1591057260.715:193): apparmor="STATUS" operation="profile_load" profile="/usr/bin/lxc-start" name="lxc-2100_</var/lib/lxc>" pid=8303 comm="apparmor_parser"
Jun 2 00:21:00 srv1 kernel: [ 7860.111259] fwbr2100i0: port 1(fwln2100i0) entered blocking state
Jun 2 00:21:00 srv1 kernel: [ 7860.114441] fwbr2100i0: port 1(fwln2100i0) entered disabled state
Jun 2 00:21:00 srv1 kernel: [ 7860.117621] device fwln2100i0 entered promiscuous mode
Jun 2 00:21:00 srv1 kernel: [ 7860.120796] fwbr2100i0: port 1(fwln2100i0) entered blocking state
Jun 2 00:21:00 srv1 kernel: [ 7860.123905] fwbr2100i0: port 1(fwln2100i0) entered forwarding state
Jun 2 00:21:01 srv1 kernel: [ 7860.129042] vmbr0: port 2(fwpr2100p0) entered blocking state
Jun 2 00:21:01 srv1 kernel: [ 7860.132072] vmbr0: port 2(fwpr2100p0) entered disabled state
Jun 2 00:21:01 srv1 kernel: [ 7860.135079] device fwpr2100p0 entered promiscuous mode
Jun 2 00:21:01 srv1 kernel: [ 7860.138014] vmbr0: port 2(fwpr2100p0) entered blocking state
Jun 2 00:21:01 srv1 kernel: [ 7860.140928] vmbr0: port 2(fwpr2100p0) entered forwarding state
Jun 2 00:21:01 srv1 kernel: [ 7860.145672] fwbr2100i0: port 2(veth2100i0) entered blocking state
Jun 2 00:21:01 srv1 kernel: [ 7860.148552] fwbr2100i0: port 2(veth2100i0) entered disabled state
Jun 2 00:21:01 srv1 kernel: [ 7860.151332] device veth2100i0 entered promiscuous mode
Jun 2 00:21:01 srv1 kernel: [ 7860.168225] eth0: renamed from vethxi6YNc
Jun 2 00:21:01 srv1 kernel: [ 7860.340309] audit: type=1400 audit(1591057261.207:194): apparmor="STATUS" operation="profile_remove" profile="/usr/bin/lxc-start" name="lxc-2100_</var/lib/lxc>" pid=8360 comm="apparmor_parser"
Jun 2 00:21:01 srv1 kernel: [ 7860.408430] fwbr2100i0: port 2(veth2100i0) entered disabled state
Jun 2 00:21:01 srv1 kernel: [ 7860.412247] device veth2100i0 left promiscuous mode
Jun 2 00:21:01 srv1 kernel: [ 7860.415311] fwbr2100i0: port 2(veth2100i0) entered disabled state
Jun 2 00:21:01 srv1 kernel: [ 7860.819547] fwbr2100i0: port 1(fwln2100i0) entered disabled state
Jun 2 00:21:01 srv1 kernel: [ 7860.823272] vmbr0: port 2(fwpr2100p0) entered disabled state
Jun 2 00:21:01 srv1 kernel: [ 7860.827122] device fwln2100i0 left promiscuous mode
Jun 2 00:21:01 srv1 kernel: [ 7860.830196] fwbr2100i0: port 1(fwln2100i0) entered disabled state
Jun 2 00:21:01 srv1 kernel: [ 7860.864775] device fwpr2100p0 left promiscuous mode
Jun 2 00:21:01 srv1 kernel: [ 7860.867743] vmbr0: port 2(fwpr2100p0) entered disabled state

Please help
 
Hi,
could you start the container with lxc-start -n 2100 -F -l DEBUG -o /tmp/lxc-2100.log and share the contents of the log file? Also, please provide the output of pveversion -v.
 
pveversion -v

nel-5.0.21-5-pve: 5.0.21-10
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libproxmox-acme-perl: 1.0.4
libpve-access-control: 6.1-1
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-2
libpve-guest-common-perl: 3.0-10
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-8
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve2
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-1
pve-cluster: 6.1-8
pve-container: 3.1-6
pve-docs: 6.2-4
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: 3.0-9
pve-i18n: 2.1-2
pve-qemu-kvm: 5.0.0-2
pve-xtermjs: 4.3.0-1
pve-zsync: 2.0-3
qemu-server: 6.2-2
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.4-pve1
root@srv1:~#
 
root@srv1:~# lxc-start -n 2100 -F -l DEBUG -o /tmp/lxc-2100.log
lxc-start: 2100: utils.c: lxc_can_use_pidfd: 1834 Kernel does not support pidfds
lxc-start: 2100: conf.c: run_buffer: 323 Script exited with status 1
lxc-start: 2100: conf.c: lxc_setup: 3364 Failed to run mount hooks
lxc-start: 2100: start.c: do_start: 1231 Failed to setup container "2100"
lxc-start: 2100: sync.c: __sync_wait: 41 An error occurred in another process (expected sequence number 5)
lxc-start: 2100: start.c: __lxc_start: 1957 Failed to spawn container "2100"
lxc-start: 2100: tools/lxc_start.c: main: 308 The container failed to start
lxc-start: 2100: tools/lxc_start.c: main: 314 Additional information can be obtained by setting the --logfile and --logpriority options
root@srv1:~#
 
Just to let you know that we have installed Proxmox from OVH templates on OVH dedicated Server.
 
From the log file:
lxc-start 2100 20200602124421.916 INFO conf - conf.c:run_script_argv:340 - Executing script "/usr/share/lxcfs/lxc.mount.hook" for container "2100", config section "lxc"
lxc-start 2100 20200602124421.918 DEBUG conf - conf.c:run_buffer:312 - Script exec /usr/share/lxcfs/lxc.mount.hook 2100 lxc mount produced output: missing /var/lib/lxcfs/proc/ - lxcfs not running?
lxc-start 2100 20200602124421.918 ERROR conf - conf.c:run_buffer:323 - Script exited with status 1
Click to expand...

What's the output of systemctl status lxcfs.service? Please try starting the service if it is not running.

To fix this other error (which isn't blocking AFAICT):
lxc-start: 2100: utils.c: lxc_can_use_pidfd: 1834 Kernel does not support pidfds
Click to expand...
using a newer kernel should be enough.
 
  • Like
Reactions: janiali
Thank you very much the issue is fixed by starting lxcfs service . all is well .

issue Resolved.
 
You must log in or register to reply here.
Top Bottom