Ubuntu
eucalyptus package

LOGLEVEL in eucalyptus.conf doesn't affect cloud-output.log verbosity

Bug #458001 reported by Thierry Carrez
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eucalyptus (Ubuntu)
Fix Released
Low
Thierry Carrez
Ubuntu karmic-updates
Karmic
Fix Released
Low
Thierry Carrez
Ubuntu karmic-updates

Bug Description

eucalyptus 1.6~bzr931-0ubuntu7, UEC Cluster install from 20091020.3
In an effort to set saner production-oriented default log levels, I tried to change LOGLEVEL from DEBUG et ERROR in /etc/eucalyptus/eucalyptus.conf.
I still get INFO and DEBUG type messages in /var/log/eucalyptus/cloud-*.log.

===========
SRU Verification
 1) Watch log file
  * tail -f /var/log/eucalyptus/cloud-output.log
 2) Modify the log level configuration
  * sudo -i "s/^LOGLEVEL=.*/LOGLEVEL=WARN/" /etc/eucalyptus/eucalyptus.conf
 3) Restart Eucalyptus
  * sudo restart eucalyptus
 4) Check the log, making sure that new INFO messages are not appended.

Regression Potential
This will need to be tested thoroughly to ensure that we do not discard wanted log messages.
===========

See original description
Revision history for this message
Thierry Carrez (ttx) wrote :

LOGLEVEL seems to affect cc.log but not cloud-output.log and cloud-debug.log.

Changed in eucalyptus (Ubuntu):
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Thierry Carrez (ttx) wrote :

I spent some time looking at the code:
1/ LOGLEVEL currently affects nc.log and cc.log correctly
2/ Adding "-l $LOGLEVEL" to eucalyptus-cloud opts (in /etc/init/eucalyptus.conf ) fixes verbosity for cloud-output.log
3/ cloud-debug.log and cloud-error.log are unaffected by this. Their verbosity is hardcoded in clc/modules/core/src/main/resources/log4j.xml.

I think we should fix (2) in an update and document what really is affected by LOGLEVEL in eucalyptus.conf

summary: - Changing LOGLEVEL in eucalyptus.conf doesn't affect log verbosity
+ LOGLEVEL in eucalyptus.conf doesn't affect cloud-*.log verbosity
Changed in eucalyptus (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Thierry Carrez (ttx) wrote :

Splitted the cloud-error and cloud-debug issue to bug 463449.

summary: - LOGLEVEL in eucalyptus.conf doesn't affect cloud-*.log verbosity
+ LOGLEVEL in eucalyptus.conf doesn't affect cloud-output.log verbosity
Changed in eucalyptus (Ubuntu Karmic):
milestone: none → karmic-updates
Thierry Carrez (ttx)
Changed in eucalyptus (Ubuntu Karmic):
assignee: nobody → Thierry Carrez (ttx)
Thierry Carrez (ttx)
Changed in eucalyptus (Ubuntu Karmic):
status: Triaged → Fix Committed
Mathias Gug (mathiaz)
description: updated
Revision history for this message
Dustin Kirkland  (kirkland) wrote :

I tested the package in Mathias's PPA.

It seems to work well.

However, I had to reboot the system to get the loglevel changes to take effect. I need to research a little more closely exactly which upstart jobs need to be restarted

description: updated
Mathias Gug (mathiaz)
tags: added: uec
Revision history for this message
Martin Pitt (pitti) wrote : Please test proposed package

Accepted eucalyptus into karmic-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

tags: added: verification-needed
Revision history for this message
Thierry Carrez (ttx) wrote :

Verified fixed.

description: updated
tags: added: verification-done
removed: verification-needed
Revision history for this message
Thierry Carrez (ttx) wrote :

Still fixed in 7.2

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package eucalyptus - 1.6~bzr931-0ubuntu7.3

---------------
eucalyptus (1.6~bzr931-0ubuntu7.3) karmic-proposed; urgency=low

  * debian/eucalyptus-cc.postinst: restart avahi daemon so that it uses
    eucalyptus specific configuration file (LP: #458904).
  * debian/eucalyptus-cc.eucalyptus-cc-publication{,-ip}.upstart: Respawn
    avahi publication jobs if they die (LP: #480885).

eucalyptus (1.6~bzr931-0ubuntu7.2) karmic-proposed; urgency=low

  [ Dustin Kirkland ]
  * cluster/handlers.c: euca_rootwrap rework did not whitelist powerwake;
    however, powerwake does *not* need root privs, drop euca_rootwrap wrapper
    (LP: #458163)
  * debian/rules, debian/euclayptus-cc.install: install the avahi-daemon.conf
    in /etc/eucalyptus, (LP: #458904).

  [ Thierry Carrez ]
  * clc/modules/www/src/main/java/edu/ucsb/eucalyptus/admin/public/EucalyptusWebInterface.html:
    Fix HTML title in the web UI for more consistency in naming (LP: #455293)
  * debian/eucalyptus-common.eucalyptus.upstart: Add -l to eucalyptus-cloud
    options so that cloud-output.log is affected by LOGLEVEL (LP: #458001)

  [ Mathias Gug ]
  * cluster/handlers.c: Fix the networkIndex returned by describeInstances.
    (LP: #454405 - upstream revno 933).
  * debian/eucalyptus-cc.eucalyptus-cc-publication{,-ip}.upstart: add an
    upstart job to explicitly publish the IP/CC hostname mapping via avahi
    instead of publishing the CC IP address via the service name (LP: #458904).
  * debian/avahi-daemon.conf: ship a specific avahi-daemon configuration file
    that doesn't publish IP addresses by default. (LP: #458904).
  * debian/eucalyptus-cloud.postinst: Fix postfix configuration to accept
    confirmation emails sent by eucalyptus (LP: #459101)
  * debian/eucalyptus-cc.upstart: Don't clean the CC network state when the CC is
    stopped by default (LP: #460089).
 -- Mathias Gug <email address hidden> Wed, 11 Nov 2009 15:15:48 -0500

Changed in eucalyptus (Ubuntu Karmic):
status: Fix Committed → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote :

I copied the karmic-proposed package to lucid. Ffor karmic-updates it is still missing two verifications.

Changed in eucalyptus (Ubuntu):
status: Triaged → Fix Released
Changed in eucalyptus (Ubuntu Karmic):
status: Fix Released → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package eucalyptus - 1.6~bzr931-0ubuntu7.3

---------------
eucalyptus (1.6~bzr931-0ubuntu7.3) karmic-proposed; urgency=low

  * debian/eucalyptus-cc.postinst: restart avahi daemon so that it uses
    eucalyptus specific configuration file (LP: #458904).
  * debian/eucalyptus-cc.eucalyptus-cc-publication{,-ip}.upstart: Respawn
    avahi publication jobs if they die (LP: #480885).

eucalyptus (1.6~bzr931-0ubuntu7.2) karmic-proposed; urgency=low

  [ Dustin Kirkland ]
  * cluster/handlers.c: euca_rootwrap rework did not whitelist powerwake;
    however, powerwake does *not* need root privs, drop euca_rootwrap wrapper
    (LP: #458163)
  * debian/rules, debian/euclayptus-cc.install: install the avahi-daemon.conf
    in /etc/eucalyptus, (LP: #458904).

  [ Thierry Carrez ]
  * clc/modules/www/src/main/java/edu/ucsb/eucalyptus/admin/public/EucalyptusWebInterface.html:
    Fix HTML title in the web UI for more consistency in naming (LP: #455293)
  * debian/eucalyptus-common.eucalyptus.upstart: Add -l to eucalyptus-cloud
    options so that cloud-output.log is affected by LOGLEVEL (LP: #458001)

  [ Mathias Gug ]
  * cluster/handlers.c: Fix the networkIndex returned by describeInstances.
    (LP: #454405 - upstream revno 933).
  * debian/eucalyptus-cc.eucalyptus-cc-publication{,-ip}.upstart: add an
    upstart job to explicitly publish the IP/CC hostname mapping via avahi
    instead of publishing the CC IP address via the service name (LP: #458904).
  * debian/avahi-daemon.conf: ship a specific avahi-daemon configuration file
    that doesn't publish IP addresses by default. (LP: #458904).
  * debian/eucalyptus-cloud.postinst: Fix postfix configuration to accept
    confirmation emails sent by eucalyptus (LP: #459101)
  * debian/eucalyptus-cc.upstart: Don't clean the CC network state when the CC is
    stopped by default (LP: #460089).
 -- Mathias Gug <email address hidden> Wed, 11 Nov 2009 15:15:48 -0500

Changed in eucalyptus (Ubuntu Karmic):
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.