On 06/26/2013 07:47 PM, Winfried de Heiden wrote:
> Hi all,
>
> Using ovirt-node-iso-2.6.1-20120228.fc18.iso (2012 seems to be a typo,
> must be 2013?) is logging with too much debugging.
>
> Changing all the"DEBUG" to "WARNOMG" in /etc/vdsm/logger.conf and
> "persist /etc/vdsm/logger.conf" solved it for /var/log/vdsm/vdsm.log.
>
> However, /var/log/libvirtd.log also shows tons of debug messages. The
> file /etc/libvirt/libvirtd.conf shows:
>
> listen_addr="0.0.0.0"
> unix_sock_group="kvm"
> unix_sock_rw_perms="0770"
> auth_unix_rw="sasl"
> host_uuid="06304eff-1c91-4e1e-86e2-d773621dcab3"
> log_outputs="1:file:/var/log/libvirtd.log"
> ca_file="/etc/pki/vdsm/certs/cacert.pem"
> cert_file="/etc/pki/vdsm/certs/vdsmcert.pem"
> key_file="/etc/pki/vdsm/keys/vdsmkey.pem"
>
> Changing log_outputs="1:file:/var/log/libvirtd.log" to
> "log_outputs="3:file:/var/log/libvirtd.log"
>
> with persist (or unpersist first, thn persist) doesn't help. After a
> reboot log_outputs="1:file:/var/log/libvirtd.log" will appear again.
>
> How to decrease the log level for libvirtd?
>

Check also log_level and log_filter properties.  You can cut down the
logs a lot, but beware that in case something happens...  You probably
know.  The advantage with using something on top of libvirt (oVirt for
example) is that you will be probably able to reproduce libvirt problems
in case there will be any and then you can switch the debugging back.

For full options on logging, see http://libvirt.org/logging.html

Martin

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users