Bug 790054 - ovirt-engine-core: log flood from GetConfigurationValueQuery in engine.log
Summary: ovirt-engine-core: log flood from GetConfigurationValueQuery in engine.log
Keywords:
Status: CLOSED DUPLICATE of bug 760100
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-webadmin
Version: unspecified
Hardware: x86_64
OS: Linux
medium
urgent
Target Milestone: ---
: ---
Assignee: Einav Cohen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-13 15:04 UTC by Dafna Ron
Modified: 2012-05-17 09:23 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-17 09:23:48 UTC
oVirt Team: ---


Attachments (Terms of Use)
log (80.72 KB, application/x-gzip)
2012-02-13 15:04 UTC, Dafna Ron
no flags Details

Description Dafna Ron 2012-02-13 15:04:32 UTC
Created attachment 561577 [details]
log

Description of problem:

we have log flooding for GetConfigurationValueQuery in engine.log

also, I am not sure it should be in log level WARN and not in INFO 

out of 5372 lines in my log 2437 of them are for GetConfigurationValueQuery:

[root@dafna-web-admin ~]# less /var/log/ovirt-engine/engine.log |wc -l
5372

[root@dafna-web-admin ~]# less /var/log/ovirt-engine/engine.log |grep GetConfigurationValueQuery |wc -l
2437

Version-Release number of selected component (if applicable):

ovirt-engine-webadmin-portal-3.0.0_0001-1.4.fc16.x86_64
ovirt-engine-3.0.0_0001-1.4.fc16.x86_64

How reproducible:
100%

Steps to Reproduce:
1. look in engine.log
2.
3.
  
Actual results:

log flood of WARN status entries for GetConfigurationValueQuery

Expected results:
 
I am not sure this entry should be in WARN status and not INFO and we should also prevent this entry from repeating every second. 



Additional info:

2012-02-13 16:55:32,709 WARN  [org.ovirt.engine.core.bll.GetConfigurationValueQuery] (http--0.0.0.0-8080-1) calling GetConfigurationValueQuery with null version, using default general for version
2012-02-13 16:55:32,712 WARN  [org.ovirt.engine.core.bll.GetConfigurationValueQuery] (http--0.0.0.0-8080-6) calling GetConfigurationValueQuery with null version, using default general for version
2012-02-13 16:55:32,714 WARN  [org.ovirt.engine.core.bll.GetConfigurationValueQuery] (http--0.0.0.0-8080-1) calling GetConfigurationValueQuery with null version, using default general for version
2012-02-13 16:55:32,716 WARN  [org.ovirt.engine.core.bll.GetConfigurationValueQuery] (http--0.0.0.0-8080-6) calling GetConfigurationValueQuery with null version, using default general for version
2012-02-13 16:55:32,723 WARN  [org.ovirt.engine.core.bll.GetConfigurationValueQuery] (http--0.0.0.0-8080-6) calling GetConfigurationValueQuery with null version, using default general for version
2012-02-13 16:55:32,725 WARN  [org.ovirt.engine.core.bll.GetConfigurationValueQuery] (http--0.0.0.0-8080-1) calling GetConfigurationValueQuery with null version, using default general for version
2012-02-13 16:55:32,727 WARN  [org.ovirt.engine.core.bll.GetConfigurationValueQuery] (http--0.0.0.0-8080-6) calling GetConfigurationValueQuery with null version, using default general for version
2012-02-13 16:55:32,729 WARN  [org.ovirt.engine.core.bll.GetConfigurationValueQuery] (http--0.0.0.0-8080-1) calling GetConfigurationValueQuery with null version, using default general for version
2012-02-13 16:55:32,731 WARN  [org.ovirt.engine.core.bll.GetConfigurationValueQuery] (http--0.0.0.0-8080-6) calling GetConfigurationValueQuery with null version, using default general for version
2012-02-13 16:55:32,734 WARN  [org.ovirt.engine.core.bll.GetConfigurationValueQuery] (http--0.0.0.0-8080-1) calling GetConfigurationValueQuery with null version, using default general for version
2012-02-13 16:55:32,736 WARN  [org.ovirt.engine.core.bll.GetConfigurationValueQuery] (http--0.0.0.0-8080-6) calling GetConfigurationValueQuery with null version, using default general for version
2012-02-13 16:55:32,738 WARN  [org.ovirt.engine.core.bll.GetConfigurationValueQuery] (http--0.0.0.0-8080-1) calling GetConfigurationValueQuery with null version, using default general for version
2012-02-13 16:55:32,740 WARN  [org.ovirt.engine.core.bll.GetConfigurationValueQuery] (http--0.0.0.0-8080-6) calling GetConfigurationValueQuery with null version, using default general for version
2012-02-13 16:55:32,742 WARN  [org.ovirt.engine.core.bll.GetConfigurationValueQuery] (http--0.0.0.0-8080-1) calling GetConfigurationValueQuery with null version, using default general for version
2012-02-13 16:55:32,744 WARN  [org.ovirt.engine.core.bll.GetConfigurationValueQuery] (http--0.0.0.0-8080-6) calling GetConfigurationValueQuery with null version, using default general for version
2012-02-13 16:55:32,747 WARN  [org.ovirt.engine.core.bll.GetConfigurationValueQuery] (http--0.0.0.0-8080-1) calling GetConfigurationValueQuery with null version, using default general for version
2012-02-13 16:55:32,749 WARN  [org.ovirt.engine.core.bll.GetConfigurationValueQuery] (http--0.0.0.0-8080-6) calling GetConfigurationValueQuery with null version, using default general for version
2012-02-13 16:55:32,758 WARN  [org.ovirt.engine.core.bll.GetConfigurationValueQuery] (http--0.0.0.0-8080-6) calling GetConfigurationValueQuery with null version, using default general for version
2012-02-13 16:55:33,061 WARN  [org.ovirt.engine.core.bll.GetConfigurationValueQuery] (http--0.0.0.0-8080-4) calling GetConfigurationValueQuery with null version, using default general for version
2012-02-13 16:55:33,063 WARN  [org.ovirt.engine.core.bll.GetConfigurationValueQuery] (http--0.0.0.0-8080-5) calling GetConfigurationValueQuery with null version, using default general for version

Comment 1 Yaniv Kaul 2012-02-19 14:24:02 UTC
This makes debugging issues annoying, please fix.

Comment 2 Omer Frenkel 2012-02-20 12:40:46 UTC
this warning is good, as it warn about wrong parameter sent to the query (version) clients need to fix the calls.
moving to webadmin, but may be relevant also for user portal and cli

Comment 3 Itamar Heim 2012-05-17 09:23:48 UTC

*** This bug has been marked as a duplicate of bug 760100 ***


Note You need to log in before you can comment on or make changes to this bug.