Bug 684077

Summary:	libvirtd.log size increases hugely
Product:	Red Hat Enterprise Linux 6	Reporter:	zhanghaiyan <yoyzhang>
Component:	libvirt	Assignee:	Daniel Veillard <veillard>
Status:	CLOSED NOTABUG	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.1	CC:	berrange, dyuan, eblake, llim, xen-maint
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-03-11 07:54:03 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description zhanghaiyan 2011-03-11 02:43:24 UTC

Description of problem:
After set log_level = 1 in /etc/libvirt/libvirtd.conf, libvirtd.log files increased to 29G only in 2 days while I didn't do much libvirt operation on that host.

Version-Release number of selected component (if applicable):
- libvirt-0.8.7-10.el6.x86_64
 log_outputs="1:file:/tmp/libvirtd.log"

How reproducible:
always

Steps to Reproduce:
1. Edit /etc/libvirt/libvirtd.conf
log_level = 1
log_outputs="1:file:/tmp/libvirtd.log"
  
Actual results:
In 2 days, libvirtd.log increased to 29G

Expected results:
Don't increase so hugely

Additional info:

Comment 2 zhanghaiyan 2011-03-11 07:54:03 UTC

Per IRC talking with jdenemar, it is expected behaviour since having virt-manager running means that you actually do a lot with libvirt. Every second or so virt-manager tries to get update on domains status.
So close this as not a bug.

Comment 3 Daniel Berrangé 2011-03-11 10:52:22 UTC

As a further note, setting  log_debug=1 is almost *never* the right thing todo. You are always better off selectively enabled just the debug areas you want, eg

  log_filters="1:qemu 1:security 1:util"
  log_outputs="1:file:/some/file.log"