[lxc-devel] console patch
Stéphane Graber
stgraber at ubuntu.com
Fri Mar 7 16:27:23 UTC 2014
On Fri, Mar 07, 2014 at 11:14:56AM -0500, Dwight Engen wrote:
> On Thu, 6 Mar 2014 16:54:51 -0600
> Serge Hallyn <serge.hallyn at ubuntu.com> wrote:
>
> > Hi Dwight,
> >
> > commit 1da0ad1, 'fix console stdin,stdout,stderr fds', seems to have
> > regressed 'lxc-test-concurrent -j 20 -i 10'. Containers sometimes
> > fail to start when dup2 fails with ebadf. I can't see any reason
> > why it would have done so though. Do you have any idea?
>
> Hmm, no I'm not sure why that would happen. I'll try to reproduce and
> look into it.
If that helps track down the issue, I just noticed that your patch was
also causing some failures with lxc-autostart, at least for unprivileged
containers:
stgraber at castiana:~$ lxc-autostart -g teams
lxc_container 1394209391.187 ERROR lxc_console - Bad file descriptor - failed to dup console
lxc_container 1394209391.187 ERROR lxc_sync - sync wake failure : Bad file descriptor
lxc_container 1394209391.899 ERROR lxc_console - Bad file descriptor - failed to dup console
lxc_container 1394209391.899 ERROR lxc_sync - sync wake failure : Bad file descriptor
lxc_container 1394209392.583 ERROR lxc_console - Bad file descriptor - failed to dup console
lxc_container 1394209392.583 ERROR lxc_sync - sync wake failure : Bad file descriptor
The above is with 3 unprivileged auto-started containers (in lxc.group
teams) with the first declaring:
lxc.loglevel = debug
lxc.logfile = /dev/stdout
To make debugging possible. Without those two statements, lxc-autostart
simply silently fails to start them.
--
Stéphane Graber
Ubuntu developer
http://www.ubuntu.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.linuxcontainers.org/pipermail/lxc-devel/attachments/20140307/000adb32/attachment.pgp>
More information about the lxc-devel
mailing list