Your message dated Sat, 29 Oct 2016 15:19:15 +0200
with message-id <[email protected]>
and subject line Re: Bug#827142: [LXC] lxc_console - got SIGWINCH fd 17 on
lxc-start
has caused the Debian Bug report #827142,
regarding [LXC] lxc_console - got SIGWINCH fd 17 on lxc-start
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
827142: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827142
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lxc
Version: 1:1.0.6-6+deb8u2
Dear Maintainers,
On Debian Jessie 8.5 running LXC, with following config, some times, not
possible to create all container
My kernel release is from jessie-backports
admlocal@syspeo:~$ uname -a
Linux syspeo 4.5.0-0.bpo.1-amd64 #1 SMP Debian 4.5.1-1~bpo8+1
(2016-04-20) x86_64 GNU/Linux
My configuration is :
admlocal@syspeo:~$ cat /etc/lxc/auto/vm-template |grep -v "#" |sort
lxc.arch = amd64
lxc.autodev = 0
lxc.cgroup.cpuset.cpus = 3
lxc.cgroup.cpu.shares = 1
lxc.cgroup.devices.allow = c 10:235 rwm
lxc.cgroup.devices.allow = c 136:* rwm
lxc.cgroup.devices.allow = c 1:3 rwm
lxc.cgroup.devices.allow = c 1:5 rwm
lxc.cgroup.devices.allow = c 1:8 rwm
lxc.cgroup.devices.allow = c 1:9 rwm
lxc.cgroup.devices.allow = c 254:0 rwm
lxc.cgroup.devices.allow = c 4:0 rwm
lxc.cgroup.devices.allow = c 4:1 rwm
lxc.cgroup.devices.allow = c 5:0 rwm
lxc.cgroup.devices.allow = c 5:1 rwm
lxc.cgroup.devices.allow = c 5:2 rwm
lxc.cgroup.devices.deny = a
lxc.cgroup.memory.limit_in_bytes = 300M
lxc.cgroup.memory.memsw.limit_in_bytes = 300M
lxc.kmsg = 0
lxc.mount.entry = devpts
/var/lib/lxc/vm-template/rootfs/dev/pts devpts defaults 0 0
lxc.mount.entry = proc /var/lib/lxc/vm-template/rootfs/proc
proc nodev,noexec,nosuid 0 0
lxc.mount.entry = sysfs /var/lib/lxc/vm-template/rootfs/sys
sysfs defaults 0 0
lxc.network.flags = up
lxc.network.flags = up
lxc.network.flags = up
lxc.network.hwaddr = 02:00:00:01:04:00
lxc.network.hwaddr = 02:00:00:01:04:01
lxc.network.hwaddr = 02:00:00:01:04:02
lxc.network.link = br-admin
lxc.network.link = br-services
lxc.network.link = br-users
lxc.network.name = eth0-admin
lxc.network.name = eth1-services
lxc.network.name = eth2-users
lxc.network.type = veth
lxc.network.type = veth
lxc.network.type = veth
lxc.network.veth.pair = e0-nfs1-adm
lxc.network.veth.pair = e1-nfs1-srv
lxc.network.veth.pair = e2-nfs1-usr
lxc.pts = 1024
lxc.rootfs = /var/lib/lxc/vm-template/rootfs
lxc.start.auto = 0
lxc.start.delay = 1
lxc.start.order = 1
lxc.tty = 4
lxc.utsname = vm-template
When launching following command...
admlocal@syspeo:~$ sudo lxc-start --name vm-template --rcfile
/etc/lxc/auto/vm-template --logpriority=DEBUG
--logfile=/var/log/lxc/vm-template.log
lxc-start: failed to create e2-nfs1-usr-vethODRI0Y : File exists
lxc-start: failed to create netdev
lxc-start: failed to create the network
lxc-start: failed to spawn 'vm-template'
lxc-start: The container failed to start.
lxc-start: Additional information can be obtained by setting the
--logfile and --logpriority options.
then the command can not end correctly, instead , logfile is :
admlocal@syspeo:~$ sudo tail -f /var/log/lxc/vm-template.log
lxc-start 1465765004.405 WARN lxc_log - lxc_log_init called
with log already initialized
lxc-start 1465765004.406 INFO lxc_lsm - LSM security driver nop
lxc-start 1465765004.406 DEBUG lxc_conf - allocated pty
'/dev/pts/57' (5/6)
lxc-start 1465765004.406 DEBUG lxc_conf - allocated pty
'/dev/pts/58' (7/8)
lxc-start 1465765004.406 DEBUG lxc_conf - allocated pty
'/dev/pts/59' (9/10)
lxc-start 1465765004.406 DEBUG lxc_conf - allocated pty
'/dev/pts/60' (11/12)
lxc-start 1465765004.406 INFO lxc_conf - tty's configured
lxc-start 1465765004.406 DEBUG lxc_start - sigchild handler set
lxc-start 1465765004.406 DEBUG lxc_console - opening /dev/tty
for console peer
lxc-start 1465765004.406 DEBUG lxc_console - using '/dev/tty'
as console
lxc-start 1465765004.406 DEBUG lxc_console - 10738 got
SIGWINCH fd 17
lxc-start 1465765004.406 DEBUG lxc_console - set winsz
dstfd:14 cols:151 rows:26
lxc-start 1465765004.406 INFO lxc_start - 'vm-template' is
initialized
lxc-start 1465765004.407 DEBUG lxc_start - Not dropping
cap_sys_boot or watching utmp
lxc-start 1465765004.408 ERROR lxc_conf - failed to create
e2-nfs1-usr-vethODRI0Y : File exists
lxc-start 1465765004.477 ERROR lxc_conf - failed to create netdev
lxc-start 1465765004.478 ERROR lxc_start - failed to create
the network
lxc-start 1465765004.478 ERROR lxc_start - failed to spawn
'vm-template'
lxc-start 1465765004.478 ERROR lxc_start_ui - The container
failed to start.
lxc-start 1465765004.478 ERROR lxc_start_ui - Additional
information can be obtained by setting the --logfile and --logpriority
options.
No idea about SIGWINCH ?
About error : 'lxc-start 1465765004.408 ERROR lxc_conf - failed to
create e2-nfs1-usr-vethODRI0Y : File exists'
i dont understand because on the host, all bridges seems OK
admlocal@syspeo:~$ sudo brctl show
bridge name bridge id STP enabled interfaces
br-admin 8000.f4ce46b8cddc no e0-amd6-adm
e0-cloud-adm
e0-gito-2-adm
e0-gito-adm
e0-ldap-adm
e0-leny-adm
e0-nfs1-adm
e0-splk-adm
e0-sqamd-adm
e0-sqi32-adm
e0-whi32-adm
e0-whi64-adm
eth0.9
br-ntp 8000.f4ce46b8cddc no eth0.7
br-services 8000.f4ce46b8cddc no e1-amd6-srv
e1-cloud-srv
e1-gito-2-srv
e1-gito-srv
e1-ldap-srv
e1-leny-srv
e1-nfs1-srv
e1-splk-srv
e1-sqamd-srv
e1-sqi32-srv
e1-whi32-srv
e1-whi64-srv
eth0.6
br-trusted 8000.f4ce46b8cddc no eth0.12
br-users 8000.f4ce46b8cddc no e2-amd6-usr
e2-cloud-usr
e2-gito-2-usr
e2-gito-usr
e2-ldap-usr
e2-leny-usr
e2-splk-usr
e2-sqamd-usr
e2-sqi32-usr
e2-whi32-usr
e2-whi64-usr
eth0.8
br-vpn 8000.f4ce46b8cddc no eth0.13
br-wifi-usr 8000.f4ce46b8cddc no
e2-cloud-wifi
eth0.11
Thanks in advance for your help
--
--------------------------------------
-- Jean-Marc LACROIX --
-- mailto : [email protected] --
---------------------------------------
--- End Message ---
--- Begin Message ---
Hi,
On Sun, Jun 12, 2016 at 10:52:05PM +0200, LACROIX Jean Marc wrote:
> On Debian Jessie 8.5 running LXC, with following config, some times, not
> possible to create all container
>
> My configuration is :
> admlocal@syspeo:~$ cat /etc/lxc/auto/vm-template |grep -v "#" |sort
As you have sorted the config, I cannot reproduce your issue.
LXC configs cannot be sorted.
Quoting lxc.container.conf(5):
Each time a lxc.network.type field is found a new round of network
configuration begins. In this way, several network virtualization
types can be specified for the same container, as well as assigning
several network interfaces for one container.
As such, the pasted config is not usable, as it defines multiple NICs,
but only configures one of them.
> When launching following command...
>
> admlocal@syspeo:~$ sudo lxc-start --name vm-template --rcfile
> /etc/lxc/auto/vm-template --logpriority=DEBUG
> --logfile=/var/log/lxc/vm-template.log
> lxc-start: failed to create e2-nfs1-usr-vethODRI0Y : File exists
> lxc-start: failed to create netdev
> lxc-start: failed to create the network
> lxc-start: failed to spawn 'vm-template'
> lxc-start: The container failed to start.
> lxc-start: Additional information can be obtained by setting the --logfile
> and --logpriority options.
something is weird with your network setup.
> lxc-start 1465765004.406 DEBUG lxc_console - 10738 got SIGWINCH fd
> 17
>
> No idea about SIGWINCH ?
Completelly irrelevant to your issue :)
lxc_console does that to every container, and it works fine.
> About error : 'lxc-start 1465765004.408 ERROR lxc_conf - failed to create
> e2-nfs1-usr-vethODRI0Y : File exists'
Are you starting a lot of containers in parallel?
I am going to close this bug as there is no bug about SIGWINCH here.
If you would like to debug your network setup, feel free to mail
[email protected]
Or open a new bug with a proper config and description please.
Greets
Evgeni
--- End Message ---
