[SOLVED] lxc with lxc.mount.entry: will not start

[RobFantini]

Hello

we have a few lxc's with this line:

lxc.mount.entry: /tv  tv  none bind,create=dir,optional 0 0

they've worked for years.

now when i try to start:

# pct start 22269
Job for pve-container@22269.service failed because the control process exited with error code.
See "systemctl status pve-container@22269.service" and "journalctl -xe" for details.
command 'systemctl start pve-container@22269' failed: exit code 1


# systemctl status pve-container@22269.service
● pve-container@22269.service - PVE LXC Container: 22269
   Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2019-07-13 22:42:56 EDT; 1min 32s ago
     Docs: man:lxc-start
           man:lxc
           man:pct
  Process: 5982 ExecStart=/usr/bin/lxc-start -n 22269 (code=exited, status=1/FAILURE)

Jul 13 22:42:56 s022 systemd[1]: Starting PVE LXC Container: 22269...
Jul 13 22:42:56 s022 lxc-start[5982]: lxc-start: 22269: lxccontainer.c: wait_on_daemonized_start: 856 No such file or director
Jul 13 22:42:56 s022 lxc-start[5982]: lxc-start: 22269: tools/lxc_start.c: main: 330 The container failed to start
Jul 13 22:42:56 s022 lxc-start[5982]: lxc-start: 22269: tools/lxc_start.c: main: 333 To get more details, run the container in
Jul 13 22:42:56 s022 lxc-start[5982]: lxc-start: 22269: tools/lxc_start.c: main: 336 Additional information can be obtained by
Jul 13 22:42:56 s022 systemd[1]: pve-container@22269.service: Control process exited, code=exited status=1
Jul 13 22:42:56 s022 systemd[1]: Failed to start PVE LXC Container: 22269.
Jul 13 22:42:56 s022 systemd[1]: pve-container@22269.service: Unit entered failed state.
Jul 13 22:42:56 s022 systemd[1]: pve-container@22269.service: Failed with result 'exit-code'.

pve version:

# pveversion -v
proxmox-ve: not correctly installed (running kernel: 4.15.18-18-pve)
pve-manager: 5.4-11 (running version: 5.4-11/6df3d8d0)
pve-kernel-4.15: 5.4-6
pve-kernel-4.15.18-18-pve: 4.15.18-44
pve-kernel-4.15.18-17-pve: 4.15.18-43
pve-kernel-4.13.4-1-pve: 4.13.4-26
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-11
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-53
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-13
libpve-storage-perl: 5.0-44
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-3
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-28
pve-cluster: 5.0-37
pve-container: 2.0-39
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-22
pve-firmware: 2.0-6
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 3.12.0-1
pve-zsync: 1.7-4
qemu-server: 5.0-54
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2

Also just noticed the 'proxmox-ve: not correctly installed (running kernel: 4.15.18-18-pve)'

So for lxc mount point something has also changed on the pve we interface. I tested trying to add a directory as a mount point - and that is not possible. More on that later..

What can I do to get the mount points back?


best regards,
Rob Fantini

 

[lhorace]

You made some change, what does lxc-start foreground tells you?

 

[RobFantini]

No changes were made to the .conf by me.

lxc-start -n $1     -F --logfile=lxc.log --logpriority=debug


lxc.log :

lxc-start 22219 20190714095921.991 INFO     lsm - lsm/lsm.c:lsm_init:50 - LSM security driver AppArmor
lxc-start 22219 20190714095921.993 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "reject_force_umount  # comment this to allow umount -f;  not recommended"
lxc-start 22219 20190714095921.993 INFO     seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start 22219 20190714095921.993 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for reject_force_umount action 0(kill)
lxc-start 22219 20190714095921.993 INFO     seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start 22219 20190714095921.993 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for reject_force_umount action 0(kill)
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for reject_force_umount action 0(kill)
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for reject_force_umount action 0(kill)
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "[all]"
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "kexec_load errno 1"
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for kexec_load action 327681(errno)
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for kexec_load action 327681(errno)
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for kexec_load action 327681(errno)
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for kexec_load action 327681(errno)
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "open_by_handle_at errno 1"
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for open_by_handle_at action 327681(errno)
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for open_by_handle_at action 327681(errno)
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for open_by_handle_at action 327681(errno)
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for open_by_handle_at action 327681(errno)
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "init_module errno 1"
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for init_module action 327681(errno)
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for init_module action 327681(errno)
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for init_module action 327681(errno)
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for init_module action 327681(errno)
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "finit_module errno 1"
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for finit_module action 327681(errno)
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for finit_module action 327681(errno)
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for finit_module action 327681(errno)
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for finit_module action 327681(errno)
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "delete_module errno 1"
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for delete_module action 327681(errno)
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for delete_module action 327681(errno)
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for delete_module action 327681(errno)
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for delete_module action 327681(errno)
lxc-start 22219 20190714095921.994 INFO     seccomp - seccomp.c:parse_config_v2:970 - Merging compat seccomp contexts into main context
lxc-start 22219 20190714095921.994 INFO     conf - conf.c:run_script_argv:356 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "22219", config section "lxc"
lxc-start 22219 20190714095922.479 DEBUG    conf - conf.c:run_buffer:326 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 22219 lxc pre-start with output: unable to parse version info 'bullseye/sid'

lxc-start 22219 20190714095922.488 ERROR    conf - conf.c:run_buffer:335 - Script exited with status 25
lxc-start 22219 20190714095922.488 ERROR    start - start.c:lxc_init:861 - Failed to run lxc.hook.pre-start for container "22219"
lxc-start 22219 20190714095922.488 ERROR    start - start.c:__lxc_start:1944 - Failed to initialize container "22219"
lxc-start 22219 20190714095922.488 ERROR    lxc_start - tools/lxc_start.c:main:330 - The container failed to start
lxc-start 22219 20190714095922.488 ERROR    lxc_start - tools/lxc_start.c:main:336 - Additional information can be obtained by setting the --logfile and --logpriority options

 

[RobFantini]

this lxc is running debian sid . so that could be the cause of issue. latest upgrade within the lxc could have done bad things.

I'll try restoring a backup and change the sources list etc..

 

[RobFantini]

other lxc systems handle mount points OK , so this issue was that particular lxc running sid.