[Users] avoid debug messages or explain better how to change log level
Gianluca Cecchi
gianluca.cecchi at gmail.com
Sat Dec 7 18:19:10 EST 2013
On Sun, Dec 8, 2013 at 1:41 AM, Douglas Schilling Landgraf wrote:
>
> IMO, looks reasonable. Could you please be more specific and share which
> messages are flooding the log files? Would be nice if you open a bugzilla
> request [1] based on component (vdsm/ovirt-engine) to get it tracked.
>
> https://bugzilla.redhat.com/enter_bug.cgi?product=oVirt
>
> --
> Cheers
> Douglas
Reading better, for engine now it is ok and it seems that level is
INFO, no DEBUG messages. Good.
But for vdsm/superdsm, my AIO server that for example today has been
powered on without making anything else than keep an idle windows xp
and an idle fedora 19 vm
has these numbers
in 16 running hours
[root at tekkaman vdsm]# grep "2013-12-07" supervdsm.log | wc -l
11357
[root at tekkaman vdsm]# grep "DEBUG::2013-12-07" supervdsm.log | wc -l
11357
so all and only DEBUG type messages, about one every 6 seconds and
about 10MBytes
[root at tekkaman vdsm]# xzcat vdsm.log-20131207.xz vdsm.log.3.xz
vdsm.log.2.xz vdsm.log.1.xz | grep "2013-12-07" | wc -l
236514
[root at tekkaman vdsm]# xzcat vdsm.log-20131207.xz vdsm.log.3.xz
vdsm.log.2.xz vdsm.log.1.xz | grep "DEBUG::2013-12-07" | wc -l
203038
[root at tekkaman vdsm]# xzcat vdsm.log-20131207.xz vdsm.log.3.xz
vdsm.log.2.xz vdsm.log.1.xz |grep "2013-12-07" | awk -F ":" '{print
$3}' | sort | uniq -c
203038 DEBUG
1135 ERROR
31870 INFO
471 WARNING
about 4 debug messages per second
BTW: the ERROR ones are for lines such as
Thread-30::ERROR::2013-12-07
23:04:26,939::sdc::137::Storage.StorageDomainCache::(_findDomain)
looking for unfetched domain 0a8035e6-e41d-40ff-a154-e0a374f264b2
Thread-30::ERROR::2013-12-07
23:04:26,939::sdc::154::Storage.StorageDomainCache::(_findUnfetchedDomain)
looking for domain 0a8035e6-e41d-40ff-a154-e0a374f264b2
I don't know exactly to what they refer as I don't have an sdc disk
and don't know how to solve....
In my opinion it could be ok to move level to INFO for vdsm too, as
already done for engine.
I don't think it is necessary an rfe for this...
If all is ok no problem, but when and if you have a problem it is
cumbersome to surf through all these DEBUG messages to find relevant
information.
Cheers
Gianluca
More information about the Users
mailing list