Bug 1363813 - Line way too long in engine.log
Summary: Line way too long in engine.log
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: General
Version: 4.0.1.1
Hardware: Unspecified
OS: Unspecified
low
high
Target Milestone: ovirt-4.1.0-alpha
: 4.1.0.2
Assignee: Martin Betak
QA Contact: sefi litmanovich
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-03 15:58 UTC by Fabrice Bacchella
Modified: 2017-02-01 14:55 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-02-01 14:55:43 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-4.1+
rule-engine: planning_ack+
rule-engine: devel_ack+
mavital: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 67240 0 None None None 2016-11-23 16:01:57 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.