Bug 1170510

Summary:	ioprocess excessive logging in vdsm.log
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Michal Skrivanek <michal.skrivanek>
Component:	vdsm	Assignee:	Yeela Kaplan <ykaplan>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	high	Docs Contact:	Jiri Belka <jbelka>
Priority:	medium
Version:	3.5.0	CC:	aberezin, bazulay, ecohen, gklein, iheim, jbelka, lpeer, lsurette, oourfali, pstehlik, ybronhei, yeylon
Target Milestone:	---	Keywords:	Reopened
Target Release:	3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	infra
Fixed In Version:	vdsm-4.16.8.1-4.el6ev	Doc Type:	Release Note
Doc Text:	In case there are excessive ioprocess logging, (can be caused if the logger.conf file was changed manually), one can change the /etc/vdsm/logger.conf, and add the following: [logger_IOProcess] level=INFO handlers=logfile qualname=IOProcess propagate=1	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-16 13:40:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1164311

Description Michal Skrivanek 2014-12-04 08:19:24 UTC

thought to be fixed by bug 1114908 but it's not.
Still too much flooding, making any debugging close to impossible, stuff rotates away too quickly, too much noise...

see http://gerrit.ovirt.org/#/c/35837/ for a possible fix

Due to supportability concerns suggesting to block 3.5 release

Comment 5 Jiri Belka 2015-01-05 12:43:50 UTC

ok vdsm-4.16.8.1-4.el6ev.x86_64

(checked conf and log file)

# grep 'DEBUG.*::IO' /var/log/vdsm/vdsm.log 
Thread-26::DEBUG::2015-01-05 12:31:34,139::__init__::298::IOProcessClient::(_run) Starting IOProcess...

Comment 6 Michal Skrivanek 2015-01-06 15:43:44 UTC

note it does seem to NOT work on upgrade, logger.conf is not being update. so be careful when updating drom intermediate builds (beta included)

Comment 7 Jiri Belka 2015-01-08 14:47:24 UTC

usual rpm policy - if logger.conf is pristine (not modified) it would be replaced, if anybody touched logger.conf then the file would be saved on filesystem as logger.conf.rpmnew

Comment 8 Michal Skrivanek 2015-01-13 10:43:43 UTC

but it is not the case and on upgraded systems there is still excessive logging
reopening