Ubuntu
ifupdown package

Large numbers of /var/log/upstart logs

Bug #1295620 reported by Stuart Bishop
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ifupdown (Ubuntu)
Fix Released
Medium
Stéphane Graber

Bug Description

I'm collecting large numbers of network interface logs in /var/log/upstart, named like /var/log/upstart/network-interface-vethzNgy6Y.log.1.gz

I believe these are being created by lxc or one of its dependencies.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: lxc 1.0.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
Uname: Linux 3.13.0-18-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Mar 21 17:57:31 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-02-26 (388 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130225)
SourcePackage: lxc
UpgradeStatus: Upgraded to trusty on 2014-03-07 (13 days ago)
defaults.conf:
 lxc.network.type = veth
 lxc.network.link = lxcbr0
 lxc.network.flags = up
 lxc.network.hwaddr = 00:16:3e:xx:xx:xx
modified.conffile..etc.default.lxc: [modified]
mtime.conffile..etc.default.lxc: 2013-10-11T17:12:04.425056

Revision history for this message
Stuart Bishop (stub) wrote :
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

This may be a leftover vestige of bug 1065589, or a dup of
460925 - it depends on whether the upstart job is being started
in the container - which seems unlikely as other upstart messages
do end up in the container - or on the host, due to a udev misfire.
The latter seems more likely.

The message says:

ifdown: interface veth9HRJRD not configured

Is there something we can do about this in ifupdown? Why should it
bother to spit this out?

 importance: low
 status: confirmed

Changed in lxc (Ubuntu):
importance: Undecided → Low
Revision history for this message
Stéphane Graber (stgraber) wrote :

Moving to ifupdown, if the upstart job indeed attempts a ifup and fails with an error, this is something we should fix (probably by using ifquery to check if the interface is actually configured).

I'll take a look.

affects: lxc (Ubuntu) → ifupdown (Ubuntu)
Changed in ifupdown (Ubuntu):
status: Confirmed → Triaged
importance: Low → Medium
assignee: nobody → Stéphane Graber (stgraber)
Stéphane Graber (stgraber)
Changed in ifupdown (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ifupdown - 0.7.47.2ubuntu2

---------------
ifupdown (0.7.47.2ubuntu2) trusty; urgency=medium

  [ Stéphane Graber ]
  * Allow setting the MTU and HWADDR on manual interfaces. (LP: #1294807)
  * The above change also means that manual interfaces will now be
    brought up and down (ias many users expected until now).
  * Disable link.defn as it's not covering all the cases supported by
    the vlan and bridge hooks and so causes more harm than good at this
    point. (LP: #1295304)
  * Also enable network-interface-container for OpenVZ. (LP: #1294155)
  * Update networking.init to exit 1 on reload when on an upstart system.
  * Pass --force to ifdown in network-interface to silence errors on
    non-existing interfaces. (LP: #1295620)

  [ Dimitri John Ledkov ]
  * Prevent the ability to stop or restart networking service
    interactively. As that is not supported. Networking job is only stopped
    during shutdown sequence. (LP: #1072518)
 -- Stephane Graber <email address hidden> Wed, 19 Mar 2014 18:04:49 -0400

Changed in ifupdown (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.