Bug 1363813

Summary: Line way too long in engine.log
Product: [oVirt] ovirt-engine Reporter: Fabrice Bacchella <fabrice.bacchella>
Component: GeneralAssignee: Martin Betak <mbetak>
Status: CLOSED CURRENTRELEASE QA Contact: sefi litmanovich <slitmano>
Severity: high Docs Contact:
Priority: low    
Version: 4.0.1.1CC: amureini, bugs, gklein, michal.skrivanek, tjelinek
Target Milestone: ovirt-4.1.0-alphaFlags: rule-engine: ovirt-4.1+
rule-engine: planning_ack+
rule-engine: devel_ack+
mavital: testing_ack+
Target Release: 4.1.0.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-01 14:55:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Fabrice Bacchella 2016-08-03 15:58:07 UTC
In engine.log, I get many lines like:

grep '2016-08-03 13:00:46,371 INFO  .org.ovirt.engine.core.vdsbroker.HostDevListByCapsVDSCommand. .org.ovirt.thread.pool-8-thread-16. .28054a0c. ' /var/log/ovirt-engine/engine.log | wc   
     1    8574  179635

1 line
8574 words
179635 characters.

I think there is one such line for each host, I have about 15 hosts, it makes logs unusable.

This info should be logged as trace, so it will be activated only when needed, or it should be send to a dedicated file.

Comment 1 Tomas Jelinek 2016-08-04 14:05:42 UTC
It does not happen too often, only on refresh host devices, setting priority to low.

Comment 2 Tomas Jelinek 2016-08-19 10:44:12 UTC
The hostdev support is going to be changed significantly in 4.1 - setting same milestone to handle also this.

Comment 3 Sandro Bonazzola 2016-12-12 14:00:01 UTC
The fix for this issue should be included in oVirt 4.1.0 beta 1 released on December 1st. If not included please move back to modified.

Comment 4 sefi litmanovich 2017-01-26 12:51:30 UTC
Verified with rhevm-4.1.0.2-0.2.el7.noarch.
Invoking refresh capabilities on a host will produce just basic INFO messages in engine.log.
When setting log level to debug level and re running the action, the full details including the output of HostDevListByCapsVDSCommand appear on DEBUG level messages.