Too many references: cannot splice - Error sending tty fd to parent

[BelCloud]

On one of my nodes, i'm unable to start few containers (that used to work).

The logs show:

lxc-start 20170413215245.766 ERROR    lxc_conf - conf.c:send_fd:3794 - Too many references: cannot splice - Error sending tty fd to parent
      lxc-start 20170413215245.766 ERROR    lxc_conf - conf.c:send_ttys_to_parent:3826 - Error writing tty fd to parent
      lxc-start 20170413215245.766 ERROR    lxc_conf - conf.c:lxc_setup:3949 - failure sending console info to parent
      lxc-start 20170413215245.766 ERROR    lxc_start - start.c:do_start:811 - Failed to setup container "5554".
      lxc-start 20170413215245.766 ERROR    lxc_sync - sync.c:__sync_wait:57 - An error occurred in another process (expected sequence number 3)
      lxc-start 20170413215245.858 ERROR    lxc_start - start.c:__lxc_start:1365 - Failed to spawn container "5554".

The node seems to have enough general resources available.

After moving the container to another node, it started without problems.

I'm assuming some of the other containers are abusing some resource, but not sure which.

Any thoughts?

 

[BelCloud]

Weirdly, if i start it using lxc-start -n ID it starts.
However, pct fails:
Job for lxc@1000000.service failed. See 'systemctl status lxc@1000000.service' and 'journalctl -xn' for details.

root@dx411-s19:/etc/pve/lxc# systemctl status lxc@1000000.service
â lxc@1000000.service - LXC Container: 1000000
   Loaded: loaded (/lib/systemd/system/lxc@.service; disabled)
  Drop-In: /usr/lib/systemd/system/lxc@.service.d
           ââpve-reboot.conf
   Active: failed (Result: exit-code) since Sat 2017-04-15 18:58:09 EEST; 9s ago
     Docs: man:lxc-start
           man:lxc
  Process: 12261 ExecStart=/usr/bin/lxc-start -n %i (code=exited, status=1/FAILURE)

Apr 15 18:58:09 dx411-s19 lxc-start[12261]: lxc-start: tools/lxc_start.c: main: 366 The container failed to start.
Apr 15 18:58:09 dx411-s19 lxc-start[12261]: lxc-start: tools/lxc_start.c: main: 368 To get more details, run the container in foreground mode.
Apr 15 18:58:09 dx411-s19 lxc-start[12261]: lxc-start: tools/lxc_start.c: main: 370 Additional information can be obtained by setting the --logfile and --logpri...y options.
Apr 15 18:58:09 dx411-s19 systemd[1]: lxc@1000000.service: control process exited, code=exited status=1
Apr 15 18:58:09 dx411-s19 systemd[1]: Failed to start LXC Container: 1000000.
Apr 15 18:58:09 dx411-s19 systemd[1]: Unit lxc@1000000.service entered failed state.

 

[dietmar]

what is the output of

# pveversion -v

 

[BelCloud]

This is the output:

root@dx411-s19:~# pveversion -V
proxmox-ve: 4.4-86 (running kernel: 4.4.40-1-pve)
pve-manager: 4.4-13 (running version: 4.4-13/7ea56165)
pve-kernel-4.4.35-1-pve: 4.4.35-77
pve-kernel-4.4.35-2-pve: 4.4.35-79
pve-kernel-4.4.49-1-pve: 4.4.49-86
pve-kernel-4.4.40-1-pve: 4.4.40-82
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-2~pve4+1
libqb0: 1.0.1-1
pve-cluster: 4.0-49
qemu-server: 4.0-110
pve-firmware: 1.1-11
libpve-common-perl: 4.0-94
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-76
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-2
pve-docs: 4.4-4
pve-qemu-kvm: 2.7.1-4
pve-container: 1.0-97
pve-firewall: 2.0-33
pve-ha-manager: 1.0-40
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-4
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.9-pve15~bpo80