syslog stops logging when lxc containers autostart

[Tim Penhey]

I noticed that my syslog file was empty, and some cursory googling suggested that it may be libvirt.

I had a juju local environment set up which had some containers autostarting. Destroying this environment, and making sure there were no autostart containers, followed by a reboot fixed this problem.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: lxc 0.9.0-0ubuntu3.4
ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
Uname: Linux 3.8.0-27-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
Date: Fri Aug 9 09:06:45 2013
InstallationDate: Installed on 2012-04-26 (469 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
SourcePackage: lxc
UpgradeStatus: Upgraded to raring on 2013-02-22 (168 days ago)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Serge Hallyn (serge-hallyn)]

Quoting Tim Penhey (<email address hidden>):
> Public bug reported:
>
> I noticed that my syslog file was empty, and some cursory googling
> suggested that it may be libvirt.

Note that juju does not use libvirt-lxc. libvirt should not be
involved.

> I had a juju local environment set up which had some containers
> autostarting. Destroying this environment, and making sure there were
> no autostart containers, followed by a reboot fixed this problem.

Can you attach a listing of the host's /var/log when this happens, as
well as the /var/lib/lxc/$container/config files? Also please run

 apport-collect 1210431

to have apport post general lxc related information.

 status: incomplete
 priority: high

[Launchpad Janitor (janitor)]

[Expired for lxc (Ubuntu) because there has been no activity for 60 days.]