<div dir="ltr">I have also libvirt logs with about 10GB of space, annoying, needs to be fixed.<br><br><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/6/28 Martin Kletzander <span dir="ltr">&lt;<a href="mailto:mkletzan@redhat.com" target="_blank">mkletzan@redhat.com</a>&gt;</span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 06/26/2013 07:47 PM, Winfried de Heiden wrote:<br>
&gt; Hi all,<br>
&gt;<br>
&gt; Using ovirt-node-iso-2.6.1-20120228.fc18.iso (2012 seems to be a typo,<br>
&gt; must be 2013?) is logging with too much debugging.<br>
&gt;<br>
&gt; Changing all the&quot;DEBUG&quot; to &quot;WARNOMG&quot; in /etc/vdsm/logger.conf and<br>
&gt; &quot;persist /etc/vdsm/logger.conf&quot; solved it for /var/log/vdsm/vdsm.log.<br>
&gt;<br>
&gt; However, /var/log/libvirtd.log also shows tons of debug messages. The<br>
&gt; file /etc/libvirt/libvirtd.conf shows:<br>
&gt;<br>
&gt; listen_addr=&quot;0.0.0.0&quot;<br>
&gt; unix_sock_group=&quot;kvm&quot;<br>
&gt; unix_sock_rw_perms=&quot;0770&quot;<br>
&gt; auth_unix_rw=&quot;sasl&quot;<br>
&gt; host_uuid=&quot;06304eff-1c91-4e1e-86e2-d773621dcab3&quot;<br>
&gt; log_outputs=&quot;1:file:/var/log/libvirtd.log&quot;<br>
&gt; ca_file=&quot;/etc/pki/vdsm/certs/cacert.pem&quot;<br>
&gt; cert_file=&quot;/etc/pki/vdsm/certs/vdsmcert.pem&quot;<br>
&gt; key_file=&quot;/etc/pki/vdsm/keys/vdsmkey.pem&quot;<br>
&gt;<br>
&gt; Changing log_outputs=&quot;1:file:/var/log/libvirtd.log&quot; to<br>
&gt; &quot;log_outputs=&quot;3:file:/var/log/libvirtd.log&quot;<br>
&gt;<br>
&gt; with persist (or unpersist first, thn persist) doesn&#39;t help. After a<br>
&gt; reboot log_outputs=&quot;1:file:/var/log/libvirtd.log&quot; will appear again.<br>
&gt;<br>
&gt; How to decrease the log level for libvirtd?<br>
&gt;<br>
<br>
</div>Check also log_level and log_filter properties.  You can cut down the<br>
logs a lot, but beware that in case something happens...  You probably<br>
know.  The advantage with using something on top of libvirt (oVirt for<br>
example) is that you will be probably able to reproduce libvirt problems<br>
in case there will be any and then you can switch the debugging back.<br>
<br>
For full options on logging, see <a href="http://libvirt.org/logging.html" target="_blank">http://libvirt.org/logging.html</a><br>
<span class="HOEnZb"><font color="#888888"><br>
Martin<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br></div>