Problem turning on container

Bestbeast

Well-Known Member
Jul 29, 2016
163
5
58
30
Hello,

I was opening my containers in lxc and I received this error when trying this command:
lxc-start -lDEBUG -o /root/prueba2.log -F -n 128

lxc-start 20161117000148.310 INFO lxc_start_ui - tools/lxc_start.c:main:264 - using rcfile /var/lib/lxc/128/config
lxc-start 20161117000148.310 WARN lxc_confile - confile.c:config_pivotdir:1879 - lxc.pivotdir is ignored. It will soon become an error.
lxc-start 20161117000148.311 INFO lxc_lsm - lsm/lsm.c:lsm_init:48 - LSM security driver AppArmor
lxc-start 20161117000148.311 INFO lxc_seccomp - seccomp.c:parse_config_v2:411 - processing: .reject_force_umount # comment this to allow umount -f; not recommended.
lxc-start 20161117000148.311 INFO lxc_seccomp - seccomp.c:parse_config_v2:576 - Adding native rule for reject_force_umount action 0.
lxc-start 20161117000148.311 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:251 - Setting Seccomp rule to reject force umounts.
lxc-start 20161117000148.311 INFO lxc_seccomp - seccomp.c:parse_config_v2:579 - Adding compat rule for reject_force_umount action 0.
lxc-start 20161117000148.311 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:251 - Setting Seccomp rule to reject force umounts.
lxc-start 20161117000148.311 INFO lxc_seccomp - seccomp.c:parse_config_v2:411 - processing: .[all].
lxc-start 20161117000148.311 INFO lxc_seccomp - seccomp.c:parse_config_v2:411 - processing: .kexec_load errno 1.
lxc-start 20161117000148.311 INFO lxc_seccomp - seccomp.c:parse_config_v2:576 - Adding native rule for kexec_load action 327681.
lxc-start 20161117000148.311 INFO lxc_seccomp - seccomp.c:parse_config_v2:579 - Adding compat rule for kexec_load action 327681.
lxc-start 20161117000148.311 INFO lxc_seccomp - seccomp.c:parse_config_v2:411 - processing: .open_by_handle_at errno 1.
lxc-start 20161117000148.311 INFO lxc_seccomp - seccomp.c:parse_config_v2:576 - Adding native rule for open_by_handle_at action 327681.
lxc-start 20161117000148.311 INFO lxc_seccomp - seccomp.c:parse_config_v2:579 - Adding compat rule for open_by_handle_at action 327681.
lxc-start 20161117000148.311 INFO lxc_seccomp - seccomp.c:parse_config_v2:411 - processing: .init_module errno 1.
lxc-start 20161117000148.311 INFO lxc_seccomp - seccomp.c:parse_config_v2:576 - Adding native rule for init_module action 327681.
lxc-start 20161117000148.311 INFO lxc_seccomp - seccomp.c:parse_config_v2:579 - Adding compat rule for init_module action 327681.
lxc-start 20161117000148.311 INFO lxc_seccomp - seccomp.c:parse_config_v2:411 - processing: .finit_module errno 1.
lxc-start 20161117000148.311 INFO lxc_seccomp - seccomp.c:parse_config_v2:576 - Adding native rule for finit_module action 327681.
lxc-start 20161117000148.311 WARN lxc_seccomp - seccomp.c:do_resolve_add_rule:270 - Seccomp: got negative for syscall: -10085: finit_module.
lxc-start 20161117000148.311 WARN lxc_seccomp - seccomp.c:do_resolve_add_rule:271 - This syscall will NOT be blacklisted.
lxc-start 20161117000148.311 INFO lxc_seccomp - seccomp.c:parse_config_v2:579 - Adding compat rule for finit_module action 327681.
lxc-start 20161117000148.311 WARN lxc_seccomp - seccomp.c:do_resolve_add_rule:270 - Seccomp: got negative for syscall: -10085: finit_module.
lxc-start 20161117000148.311 WARN lxc_seccomp - seccomp.c:do_resolve_add_rule:271 - This syscall will NOT be blacklisted.
lxc-start 20161117000148.311 INFO lxc_seccomp - seccomp.c:parse_config_v2:411 - processing: .delete_module errno 1.
lxc-start 20161117000148.311 INFO lxc_seccomp - seccomp.c:parse_config_v2:576 - Adding native rule for delete_module action 327681.
lxc-start 20161117000148.311 INFO lxc_seccomp - seccomp.c:parse_config_v2:579 - Adding compat rule for delete_module action 327681.
lxc-start 20161117000148.311 INFO lxc_seccomp - seccomp.c:parse_config_v2:589 - Merging in the compat Seccomp ctx into the main one.
lxc-start 20161117000148.311 INFO lxc_conf - conf.c:run_script_argv:367 - Executing script '/usr/share/lxc/hooks/lxc-pve-prestart-hook' for container '128', config section 'lxc'
lxc-start 20161117000148.718 ERROR lxc_conf - conf.c:run_buffer:347 - Script exited with status 24
lxc-start 20161117000148.718 ERROR lxc_start - start.c:lxc_init:465 - failed to run pre-start hooks for container '128'.
lxc-start 20161117000148.718 ERROR lxc_start - start.c:__lxc_start:1313 - failed to initialize the container
lxc-start 20161117000148.718 ERROR lxc_start_ui - tools/lxc_start.c:main:344 - The container failed to start.
lxc-start 20161117000148.718 ERROR lxc_start_ui - tools/lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options.


I tried that command because I could not get the container working through the interface:

()

Task viewer: CT 124 - Start

OutputStatus

Stop
lxc-start: tools/lxc_start.c: main: 344 The container failed to start.
lxc-start: tools/lxc_start.c: main: 346 To get more details, run the container in foreground mode.
lxc-start: tools/lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options.
TASK ERROR: command 'lxc-start -n 124' failed: exit code 1


Waiting your answer,
Pedro
 
Also getting this error when trying a pct command:
Unable to create new inotify object: Too many open files at /usr/share/perl5/PVE/INotify.pm line 389.
 
pveversion -v:

root@ns504266:~# pveversion -v
proxmox-ve: 4.3-71 (running kernel: 4.4.21-1-pve)
pve-manager: 4.3-10 (running version: 4.3-10/7230e60f)
pve-kernel-4.4.21-1-pve: 4.4.21-71
pve-kernel-4.4.19-1-pve: 4.4.19-66
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-47
qemu-server: 4.0-94
pve-firmware: 1.1-10
libpve-common-perl: 4.0-80
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-68
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-docs: 4.3-14
pve-qemu-kvm: 2.7.0-6
pve-container: 1.0-81
pve-firewall: 2.0-31
pve-ha-manager: 1.0-35
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.5-1
lxcfs: 2.0.4-pve2
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.8-pve13~bpo80

and how do you want me to post the container config?
 
Is there some other software running on that host? Other containers?
Yes there are more container running, but currently I can not run more than the ones that are already on. If I turn someone off I can turn on others, do not know why this is happening
 
Does it help if you increase max_user_watches? To show current value use:

# cat /proc/sys/fs/inotify/max_user_watches

To set a newValue use:

# echo newValue > /proc/sys/fs/inotify/max_user_watches

Simply duplicate old value for testing.
 
Does it help if you increase max_user_watches? To show current value use:

# cat /proc/sys/fs/inotify/max_user_watches

To set a newValue use:

# echo newValue > /proc/sys/fs/inotify/max_user_watches

Simply duplicate old value for testing.
root@ns504266:~# cat /proc/sys/fs/inotify/max_user_watches
8192
root@ns504266:~# echo 16000 > /proc/sys/fs/inotify/max_user_watches
root@ns504266:~# cat /proc/sys/fs/inotify/max_user_watches
16000
root@ns504266:~# pct config 128
Unable to create new inotify object: Demasiados ficheros abiertos at /usr/share/perl5/PVE/INotify.pm line 389.
 

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!