[Bug 1181136] Re: Empty log file when a container is started with the API

2015-11-09 Thread Stéphane Graber
** Changed in: lxc (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181136 Title: Empty log file when a container is started with the API To manage notifi

Re: [Bug 1181136] Re: Empty log file when a container is started with the API

2013-05-21 Thread Serge Hallyn
Thanks, this is likely related to how the python bindings are interpreting the second command. I woudl actually expect c.set_config_item('lxc.loglevel', 'info') to work, but that fails here too. status: confirmed assignee: stgraber priority: medium -- You received this bug notification becau

[Bug 1181136] Re: Empty log file when a container is started with the API

2013-05-21 Thread Didier Roche
I tried multiple things: c.set_config_item("lxc.loglevel", "1") c.set_config_item("lxc.loglevel", "9") c.set_config_item("lxc.loglevel", "debug") And I always get: lxc: invalid log priority 9 Without those, setting in the lxc config: lxc.logfile = /tmp/foo lxc.loglevel = debug it creates an empt

[Bug 1181136] Re: Empty log file when a container is started with the API

2013-05-20 Thread Serge Hallyn
Thanks for reporting this bug. If you do c.set_config_item("lxc.log.loglevel', '1') before starting the container, does that help? Also, if you cause an actual error during startup (i.e. specify a wrong rootfs location in the configuration), does an error then at least show up in the logfile?