[Bug 458001] Re: LOGLEVEL in eucalyptus.conf doesn't affect cloud-output.log verbosity

[Mathias Gug]

** Description changed:

  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
+ 
+ Impact:
+ The logging level of most components are set to debug which is too verbose for a production setup in a release.
+ 
+ How the bug has been addressed:
+ The init script has been modified to use the LOGLEVEL option from the configuration file when starting the daemons.
+ 
+ To reproduce the bug:
+ 1. Install a CC.
+ 2. Check the verbosity level in  /var/log/eucalyptus/cloud-*.log. There should be message of INFO and DEBUG level.
+ 3. After the upgrade, edit  /etc/eucalyptus/eucalyptus.conf to set LOGLEVEL to ERROR and restart the CC. There shouldn't be any messages of INFO or DEBUG level in /var/log/eucalyptus/cloud-*.log anymore.
+ 
+ Regression potential:
+ The actual log levels are not changed by the update. Only local modifications of the LOG level will be taken into account. The default level are still set to DEBUG.
+ 
+ ==================

-- 
LOGLEVEL in eucalyptus.conf doesn't affect cloud-output.log verbosity
https://bugs.launchpad.net/bugs/458001
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.