the intent is that you can set the logfile and loglevel and find
out more about how it failed for those. While there is talk about
work to improve on the startup failure debugging, it is still
based on the logfile output.
As an example:
^C2 ✗ serge@sl ~ $ python3
Python 3.4.3+ (default, Oct 14 2015, 16:03:50)
[GCC 5.2.1 20151010] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import lxc
>>> c=lxc.Container("x1")
>>> c.set_config_item("lxc.loglevel", "1")
True
>>> c.set_config_item("lxc.logfile", "/tmp/outout")
True
>>> c.start()
False
but now /tmp/outout has the debug information.
It sounds like we could stand to have this better explained
somewhere, but I'm not sure where.
Hi,
the intent is that you can set the logfile and loglevel and find
out more about how it failed for those. While there is talk about
work to improve on the startup failure debugging, it is still
based on the logfile output.
As an example:
^C2 ✗ serge@sl ~ $ python3 ("x1") item("lxc. loglevel" , "1") item("lxc. logfile" , "/tmp/outout")
Python 3.4.3+ (default, Oct 14 2015, 16:03:50)
[GCC 5.2.1 20151010] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import lxc
>>> c=lxc.Container
>>> c.set_config_
True
>>> c.set_config_
True
>>> c.start()
False
but now /tmp/outout has the debug information.
It sounds like we could stand to have this better explained
somewhere, but I'm not sure where.