New PVE6 Issue - Starting a new container

J

jtvdw

Member
Dec 6, 2018
44
0
6
Cape Town, South Africa
Hi,

When I start a newly created container I'm getting this error:

May 19 21:52:03 liq001-truserv-jhb1-001 kernel: EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null)
May 19 21:52:03 liq001-truserv-jhb1-001 systemd-udevd[45329]: Could not generate persistent MAC address for vethURYASN: No such file or directory
May 19 21:52:03 liq001-truserv-jhb1-001 kernel: IPv6: ADDRCONF(NETDEV_UP): veth100i0: link is not ready
May 19 21:52:03 liq001-truserv-jhb1-001 lxc-start[45312]: lxc-start: 100: lxccontainer.c: wait_on_daemonized_start: 865 Received container state "ABORTING" instead of "RU
May 19 21:52:03 liq001-truserv-jhb1-001 lxc-start[45312]: lxc-start: 100: tools/lxc_start.c: main: 330 The container failed to start
May 19 21:52:03 liq001-truserv-jhb1-001 lxc-start[45312]: lxc-start: 100: tools/lxc_start.c: main: 333 To get more details, run the container in foreground mode
May 19 21:52:03 liq001-truserv-jhb1-001 lxc-start[45312]: lxc-start: 100: tools/lxc_start.c: main: 336 Additional information can be obtained by setting the --logfile and
May 19 21:52:03 liq001-truserv-jhb1-001 systemd[1]: pve-container@100.service: Control process exited, code=exited status=1
May 19 21:52:03 liq001-truserv-jhb1-001 systemd[1]: pve-container@100.service: Killing process 45314 (3) with signal SIGKILL.
May 19 21:52:03 liq001-truserv-jhb1-001 systemd[1]: pve-container@100.service: Killing process 45359 (3) with signal SIGKILL.
May 19 21:52:03 liq001-truserv-jhb1-001 systemd[1]: Failed to start PVE LXC Container: 100.
Click to expand...

When I try starting the container via terminal, this message pop's up: (It's not part of a cluster, how can I set it to run as stand alone machine)

perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_ZA:en",
LC_ALL = (unset),
LC_CTYPE = "UTF-8",
LANG = "en_ZA.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_ZA.UTF-8").
Corosync config '/etc/pve/corosync.conf' does not exist - is this node part of a cluster?
Cannot initialize CMAP service
Click to expand...

Any help would be appreciated.

Thanks.
 
Hi,

post the command you use to start the CT, this doesn't look like a pct start VMID output triggered by root..

Can you try: lxc-start -o /tmp/ctlog -l info -F -n 100 as root, and if it fails post the output of "/tmp/ctlog" here.
 
Hi,

I started the container via the webgui.

Thanks for the reply and assistance, please see output below :

root@liq001-truserv-jhb1-001:~# cat /tmp/ctlog
lxc-start 100 20200520071428.937 INFO lsm - lsm/lsm.c:lsm_init:50 - LSM security driver nop
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:759 - Processing "reject_force_umount # comment this to allow umount -f; not recommended"
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for reject_force_umount action 0(kill)
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for reject_force_umount action 0(kill)
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for reject_force_umount action 0(kill)
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for reject_force_umount action 0(kill)
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:759 - Processing "[all]"
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:759 - Processing "kexec_load errno 1"
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for kexec_load action 327681(errno)
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for kexec_load action 327681(errno)
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for kexec_load action 327681(errno)
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for kexec_load action 327681(errno)
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:759 - Processing "open_by_handle_at errno 1"
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for open_by_handle_at action 327681(errno)
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for open_by_handle_at action 327681(errno)
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for open_by_handle_at action 327681(errno)
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for open_by_handle_at action 327681(errno)
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:759 - Processing "init_module errno 1"
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for init_module action 327681(errno)
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for init_module action 327681(errno)
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for init_module action 327681(errno)
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for init_module action 327681(errno)
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:759 - Processing "finit_module errno 1"
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for finit_module action 327681(errno)
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for finit_module action 327681(errno)
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for finit_module action 327681(errno)
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for finit_module action 327681(errno)
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:759 - Processing "delete_module errno 1"
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for delete_module action 327681(errno)
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for delete_module action 327681(errno)
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for delete_module action 327681(errno)
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for delete_module action 327681(errno)
lxc-start 100 20200520071428.937 INFO seccomp - seccomp.c:parse_config_v2:970 - Merging compat seccomp contexts into main context
lxc-start 100 20200520071428.937 INFO conf - conf.c:run_script_argv:356 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "100", config section "lxc"
lxc-start 100 20200520071429.598 INFO start - start.c:lxc_init:906 - Container "100" is initialized
lxc-start 100 20200520071429.599 INFO conf - conf.c:run_script:495 - Executing script "/usr/share/lxc/lxcnetaddbr" for container "100", config section "net"
lxc-start 100 20200520071430.262 ERROR conf - conf.c:run_buffer:335 - Script exited with status 2
lxc-start 100 20200520071430.451 ERROR network - network.c:lxc_create_network_priv:2462 - Failed to create network device
lxc-start 100 20200520071430.451 ERROR start - start.c:lxc_spawn:1646 - Failed to create the network
lxc-start 100 20200520071430.452 WARN network - network.c:lxc_delete_network_priv:2594 - Operation not permitted - Failed to remove interface "eth0" with index 11
lxc-start 100 20200520071430.452 ERROR start - start.c:__lxc_start:1989 - Failed to spawn container "100"
lxc-start 100 20200520071430.453 INFO conf - conf.c:run_script_argv:356 - Executing script "/usr/share/lxc/hooks/lxc-pve-poststop-hook" for container "100", config section "lxc"
lxc-start 100 20200520071430.891 INFO conf - conf.c:run_script_argv:356 - Executing script "/usr/share/lxcfs/lxc.reboot.hook" for container "100", config section "lxc"
lxc-start 100 20200520071431.402 ERROR lxc_start - tools/lxc_start.c:main:330 - The container failed to start
lxc-start 100 20200520071431.402 ERROR lxc_start - tools/lxc_start.c:main:336 - Additional information can be obtained by setting the --logfile and --logpriority options
Click to expand...

Thanks.
 
Last edited:
SOLVED!
See: Solution by Mr. Lamprecht

I got a smiliar issue.
The "pct"-tool seems to be missing since the update to 6.2-4:
root@Proxer:/home/lvmprox# pct start 119
bash: pct: command not found

The try with "lxc-start"-command also fails:
root@Proxer:/home/lvmprox# lxc-start -o /tmp/ctlog.txt -l info -F -n 119
lxc-start: 119: conf.c: run_buffer: 323 Script exited with status 2
lxc-start: 119: start.c: lxc_init: 804 Failed to run lxc.hook.pre-start for container "119"
lxc-start: 119: start.c: __lxc_start: 1903 Failed to initialize container "119"
lxc-start: 119: conf.c: run_buffer: 323 Script exited with status 1
lxc-start: 119: start.c: lxc_end: 971 Failed to run lxc.hook.post-stop for container "119"
lxc-start: 119: tools/lxc_start.c: main: 308 The container failed to start
lxc-start: 119: tools/lxc_start.c: main: 314 Additional information can be obtained by setting the --logfile and --logpriority options


Nevertheless, the start via the webinterface works perfectly.


My versions look like that:
root@Proxer:/home/lvmprox# pveversion -v
proxmox-ve: 6.2-1 (running kernel: 5.4.41-1-pve)
pve-manager: 6.2-4 (running version: 6.2-4/9824574a)
pve-kernel-5.4: 6.2-2
pve-kernel-helper: 6.2-2
pve-kernel-5.4.41-1-pve: 5.4.41-1
pve-kernel-4.15: 5.4-17
pve-kernel-4.15.18-28-pve: 4.15.18-56
pve-kernel-4.13.13-5-pve: 4.13.13-38
pve-kernel-4.13.13-4-pve: 4.13.13-35
pve-kernel-4.13.13-2-pve: 4.13.13-33
pve-kernel-4.13.8-2-pve: 4.13.8-28
pve-kernel-4.13.4-1-pve: 4.13.4-26
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+pve1
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
qemu-server: 6.2-2
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.4-pve1

Do i miss some package or is the "pct"-tool abandoned?

Thank you :)

Kind regards
Alex :)
 
Last edited:
Alexa023 said:
The "pct"-tool seems to be missing since the update to 6.2-4:
root@Proxer:/home/lvmprox# pct start 119
bash: pct: command not found
Click to expand...

Works fine here, seems rather that your $PATH environment variable doesn't include /usr/sbin/

Can you run it manually: /usr/sbin/pct?
If so, check (and fix) your PATH variable.
 
t.lamprecht said:
Works fine here, seems rather that your $PATH environment variable doesn't include /usr/sbin/

Can you run it manually: /usr/sbin/pct?
If so, check (and fix) your PATH variable.
Click to expand...

That helped immediately! :D
I didn`t perceive a new env var handling since Debian buster. This "disabled" the correct setting of my "$PATH"-Var.

Vielen Dank, Herr Lamprecht!
 
  • Like
Reactions: t.lamprecht
You must log in or register to reply here.
Top Bottom