Bug 848648 - [Doc] Add annotation about how to enable stack traces in log messages
[Doc] Add annotation about how to enable stack traces in log messages
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt (Show other bugs)
Unspecified Unspecified
unspecified Severity medium
: rc
: ---
Assigned To: Jiri Denemark
Virtualization Bugs
Depends On:
  Show dependency treegraph
Reported: 2012-08-16 02:31 EDT by hongming
Modified: 2013-02-21 02:21 EST (History)
6 users (show)

See Also:
Fixed In Version: libvirt-0.10.0-0rc1.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-21 02:21:37 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description hongming 2012-08-16 02:31:08 EDT
Description of problem:
The feature - Enable stack traces in log  have been add to libvirt-0.10.0-0rc0.el6.x86_64 build . It needs to add  annotation about it in libvirtd.conf.


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

How reproducible:

Steps to Reproduce:
1.Configure the following settings  in /etc/libvirt/libvirtd.conf. and there isn't any annotation about how to enable stack traces.

log_filters="1:+libvirt 1:util 1:qemu"

2.Check the log file. It should  includes stack traces 

2012-08-09 06:52:15.990+0000: 37394: debug : do_open:1130 : name "qemu:///system" to URI components:
  scheme qemu
  server (null)
  user (null)
  port 0
  path /system


Actual results:
There isn't any annotation about it.

Expected results:
Add annotation about how to enable stack traces in log messages

Additional info:
Comment 2 Jiri Denemark 2012-08-17 15:41:59 EDT
Fixed upstream by v0.10.0-rc0-152-g395be3c:

commit 395be3c2b8d8e14eb93167de003fa7d872d1547e
Author: Jiri Denemark <jdenemar@redhat.com>
Date:   Fri Aug 17 14:12:51 2012 +0200

    docs: Enhance documentation of log_filters
    Also make sure documentation in libvirtd.conf matches the one from
Comment 4 yuping zhang 2012-08-23 23:29:20 EDT
Verified this bug with:

1.# vim /etc/libvirt/libvirtd.conf

# Logging filters:
# A filter allows to select a different logging level for a given category
# of logs
# The format for a filter is one of:
#    x:name
#    x:+name
#      where name is a string which is matched against source file name,
#      e.g., "remote", "qemu", or "util/json", the optional "+" prefix
#      tells libvirt to log stack trace for each message matching name,
#      and x is the minimal level where matching messages should be logged:
#    1: DEBUG
#    2: INFO
#    3: WARNING
#    4: ERROR

2.Configure the following settings  in /etc/libvirt/libvirtd.conf. 

log_filters="1:+libvirt 1:util 1:qemu"

3.Restart libvirtd,then destroy a guest with virsh.
Stack trace log:

2012-08-24 16:26:18.932+0000: 17440: debug : remoteDispatchDomainLookupByNameHelper:2892 : server=0x13d8430 client=0x13e0cc0 msg=0x13d9760 rerr=0x7f4f92adbb80 args=0x7f4f7c001d50 ret=0x7f4f7c001d70
2012-08-24 16:26:18.932+0000: 17440: debug : virDomainLookupByName:2114 : conn=0x7f4f84002b70, name=rhel6.3

2012-08-24 16:26:18.932+0000: 17440: debug : virObjectNew:110 : OBJECT_NEW: obj=0x7f4f7c002340 classname=virDomain
2012-08-24 16:26:18.932+0000: 17440: debug : virObjectRef:168 : OBJECT_REF: obj=0x7f4f84002b70
2012-08-24 16:26:18.932+0000: 17440: debug : virDomainFree:2278 : dom=0x7f4f7c002340, (VM: name=rhel6.3, uuid=4e10f61b-9e6c-b85a-cce1-1f97d30ce899)

So change the bug status to VERIFIED.
Comment 5 errata-xmlrpc 2013-02-21 02:21:37 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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