I´m resending an email sent yersterday that was probably overlooked due
to a lack of indentation.
On Thu, 2014-01-09 at 16:33 +, Dan Kenigsberg wrote:
On Thu, Jan 09, 2014 at 01:39:08PM +, Sven Kieske wrote:
Hi,
I also guess this gets so large because of the loglevels in
On Thu, Jan 9, 2014 at 5:33 PM, Dan Kenigsberg wrote:
The question of how much logging we should keep is a tough one. I, as a
developer, would like to have as much as possible. For long-running busy
systems, it has happened to me that the core bug was spotted in
vdsm.log.67 or so.
However,
On Thu, Jan 09, 2014 at 05:01:12PM +, Karli Sjöberg wrote:
And the rotate policy says:
/etc/logrotate.d/libvirtd
## beginning of configuration section by vdsm
/var/log/libvirt/libvirtd.log {
rotate 100
missingok
copytruncate
size 15M
compress
On Fri, 2014-01-10 at 12:23 +, Dan Kenigsberg wrote:
On Thu, Jan 09, 2014 at 05:01:12PM +, Karli Sjöberg wrote:
And the rotate policy says:
/etc/logrotate.d/libvirtd
## beginning of configuration section by vdsm
/var/log/libvirt/libvirtd.log {
rotate 100
Ah man, now I see it, it´s not rotating the right file, look:
# grep libvirtd /etc/logrotate.d/libvirtd
/var/log/libvirt/libvirtd.log {
# grep libvirtd.log /etc/libvirt/libvirtd.conf
log_outputs=1:file:/var/log/libvirtd.log
Bug?
I would say no - at least for Fedora 19 nodes.
In our
On Fri, Jan 10, 2014 at 2:04 PM, Markus Stockhausen wrote:
Ah man, now I see it, it´s not rotating the right file, look:
# grep libvirtd /etc/logrotate.d/libvirtd
/var/log/libvirt/libvirtd.log {
# grep libvirtd.log /etc/libvirt/libvirtd.conf
log_outputs=1:file:/var/log/libvirtd.log
Bug?
I
I got:
/var/log/libvirt/libvirtd.log
grep libvirtd.log /etc/libvirt/libvirtd.conf
log_outputs=1:file:/var/log/libvirt/libvirtd.log
on my centos 6.4 node
vdsm version as stated in my first mail in this thread.
Am 10.01.2014 14:04, schrieb Markus Stockhausen:
Ah man, now I see it, it´s not
On Fri, 2014-01-10 at 13:24 +, Sven Kieske wrote:
I got:
/var/log/libvirt/libvirtd.log
grep libvirtd.log /etc/libvirt/libvirtd.conf
log_outputs=1:file:/var/log/libvirt/libvirtd.log
on my centos 6.4 node
vdsm version as stated in my first mail in this thread.
Mmm, that´s strange;
On Fri, Jan 10, 2014 at 12:45:09PM +, Karli Sjöberg wrote:
Oh, and here´s the output:
# du -h /var/log/libvirtd.log
1.1G /var/log/libvirtd.log
# /usr/sbin/logrotate -d -v /etc/logrotate.d/libvirtd
reading config file /etc/logrotate.d/libvirtd
reading config info for
Hi!
I just noticed my Hypervisor nodes starting to complain about disks
almost being full. I started investigation and noticed that:
# du -h /var/log/libvirtd.log
100G/var/log/libvirtd.log
And many Hosts system partition had indeed become full:S
Why weren´t the file rotated? Well:
# ls -lah
Hi,
I also guess this gets so large because of the loglevels in
/etc/vdsm/logger.conf
this seems to be the default:
[logger_root]
level=DEBUG
handlers=syslog,logfile
propagate=0
[logger_vds]
level=DEBUG
handlers=syslog,logfile
qualname=vds
propagate=0
[logger_Storage]
level=DEBUG
On Thu, Jan 09, 2014 at 01:39:08PM +, Sven Kieske wrote:
Hi,
I also guess this gets so large because of the loglevels in
/etc/vdsm/logger.conf
this seems to be the default:
[logger_root]
level=DEBUG
handlers=syslog,logfile
propagate=0
[logger_vds]
level=DEBUG
eventually
Från: users-boun...@ovirt.org [users-boun...@ovirt.org] f#246;r Dan Kenigsberg
[dan...@redhat.com]
Skickat: den 9 januari 2014 17:33
Till: Sven Kieske
Kopia: users@ovirt.org
Ämne: Re: [Users] VSDM´s logrotate makes Hosts fill up var eventually
Från: users-boun...@ovirt.org [users-boun...@ovirt.org] f#246;r Dan Kenigsberg
[dan...@redhat.com]
Skickat: den 9 januari 2014 17:33
Till: Sven Kieske
Kopia: users@ovirt.org
Ämne: Re: [Users] VSDM´s logrotate makes Hosts fill up var eventually
On Thu
Hi Karli,
no offense, but, please do use proper quoting (well, any
quoting at all :-) ), I can not see what yoou did write
in your second mail and what's quoted from Dan.
Thank you!
--
Mit freundlichen Grüßen / Regards
Sven Kieske
Systemadministrator
Mittwald CM Service GmbH Co. KG
Hi Dan,
If my opinion is worth, I use logs all the time as my setup is evolving
all the time and have issues quite often, so I rather use space in
logging too much than loose information I need in regular bases.
Regards,
___
Users mailing list
Hi Sven
Skickat från min iPhone
9 jan 2014 kl. 18:23 skrev Sven Kieske s.kie...@mittwald.de:
Hi Karli,
no offense, but, please do use proper quoting (well, any
quoting at all :-) ), I can not see what yoou did write
in your second mail and what's quoted from Dan.
I know, I know, it's
On Jan 9, 2014, at 10:33 AM, Dan Kenigsberg dan...@redhat.com wrote:
The question of how much logging we should keep is a tough one. I, as a
developer, would like to have as much as possible. For long-running busy
systems, it has happened to me that the core bug was spotted in
vdsm.log.67 or
18 matches
Mail list logo
