8:56 a.m.
Hi,
While trying to debug a problem we've noticed that the libvirt doen't write logs.
Please noticed that, and chnage the configuration of the libvirtd.conf.
thanks,
Yogev
9:13 a.m.
bug opened https://bugzilla.redhat.com/show_bug.cgi?id=1061753
----- Original Message -----
From: "Yogev Rabl" <yrabl(a)redhat.com>
To: rdo-list(a)redhat.com
Sent: Wednesday, February 5, 2014 4:56:17 PM
Subject: [Rdo-list] libvirtd default configuration
Hi,
While trying to debug a problem we've noticed that the libvirt doen't write logs.
Please noticed that, and chnage the configuration of the libvirtd.conf.
thanks,
Yogev
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
11:45 a.m.
On Wed, Feb 05, 2014 at 10:13:56AM -0500, Yogev Rabl wrote:
This is not a bug.
Even though the configuration looks empty, the *default* log_level is 3,
i.e. warnings and errors, this is redirected to systemd journal (on
systems that are run systemd, and to syslog on older systems). You can
notice this when you invoke:
$ systemctl status libvirtd
libvirtd.service - Virtualization daemon
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled)
Active: active (running) since Wed 2014-02-05 22:45:05 IST; 11s ago
Main PID: 32521 (libvirtd)
CGroup: /system.slice/libvirtd.service
├─ 821 /sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf
└─32521 /usr/sbin/libvirtd
Feb 05 22:45:05 foohost.com systemd[1]: Started Virtualization daemon.
Feb 05 22:45:06 foohost.com dnsmasq[821]: read /etc/hosts - 2 addresses
Feb 05 22:45:06 foohost.com dnsmasq[821]: read
/var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
Feb 05 22:45:06 foohost.com dnsmasq-dhcp[821]: read
/var/lib/libvirt/dnsmasq/default.hostsfile
Furthermore, there's a couple of different ways to enable various log
levels based on filters, etc.
- If you want logs to be redirected to a file, that can be expressed in
/etc/libvirt/libvirtd.conf.
To log _everything_ (this spews LOTS of details, fills up your disk),
add these
log_level = 1
log_outputs = 1:file:/var/tmp/libvirtd.log
to /etc/libvirt/libvirtd.conf, restart libvirtd.
- Alternatively, you can set environment variables (if set, this will
take precedence over values specified in the configuration file):
$ export LIBVIRT_DEBUG=1
$ export LIBVIRT_TRACE=1
More extensive details on logging filters are available here:
http://libvirt.org/logging.html
--
/kashyap
12:23 p.m.
This is a bug since we install with packstack which need to configure
this in the deployment and up until now was configured.
libvirtd log should be created and should be in debug level when
installing with packstack.
If this did not happen - it's a bug and user should not configure it
manually.
Dafna
On 02/05/2014 05:45 PM, Kashyap Chamarthy wrote:
On Wed, Feb 05, 2014 at 10:13:56AM -0500, Yogev Rabl wrote:
> bug opened https://bugzilla.redhat.com/show_bug.cgi?id=1061753
This is not a bug.
Even though the configuration looks empty, the *default* log_level is 3,
i.e. warnings and errors, this is redirected to systemd journal (on
systems that are run systemd, and to syslog on older systems). You can
notice this when you invoke:
$ systemctl status libvirtd
libvirtd.service - Virtualization daemon
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled)
Active: active (running) since Wed 2014-02-05 22:45:05 IST; 11s ago
Main PID: 32521 (libvirtd)
CGroup: /system.slice/libvirtd.service
├─ 821 /sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf
└─32521 /usr/sbin/libvirtd
Feb 05 22:45:05 foohost.com systemd[1]: Started Virtualization daemon.
Feb 05 22:45:06 foohost.com dnsmasq[821]: read /etc/hosts - 2 addresses
Feb 05 22:45:06 foohost.com dnsmasq[821]: read
/var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
Feb 05 22:45:06 foohost.com dnsmasq-dhcp[821]: read
/var/lib/libvirt/dnsmasq/default.hostsfile
Furthermore, there's a couple of different ways to enable various log
levels based on filters, etc.
- If you want logs to be redirected to a file, that can be expressed in
/etc/libvirt/libvirtd.conf.
To log _everything_ (this spews LOTS of details, fills up your disk),
add these
log_level = 1
log_outputs = 1:file:/var/tmp/libvirtd.log
to /etc/libvirt/libvirtd.conf, restart libvirtd.
- Alternatively, you can set environment variables (if set, this will
take precedence over values specified in the configuration file):
$ export LIBVIRT_DEBUG=1
$ export LIBVIRT_TRACE=1
More extensive details on logging filters are available here:
http://libvirt.org/logging.html
--
/kashyap
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
--
Dafna Ron
12:28 p.m.
On 02/05/2014 01:23 PM, Dafna Ron wrote:
This is a bug since we install with packstack which need to
configure
this in the deployment and up until now was configured.
libvirtd log should be created and should be in debug level when
installing with packstack.
If this did not happen - it's a bug and user should not configure it
manually.
libvirtd should never be configured in debug mode by default. Please
see danpb's rationale here:
https://bugzilla.redhat.com/show_bug.cgi?id=1061753#c3
If someone wanted to change packstack to expose a configuration option
to set libvirtd to more verbose logging (but not debug mode) if that
config param is set, that would be fine. But under no circumstances
should it be defaulted to debug enabled.
12:44 p.m.
Perry,
in current setups nothing is logged at all, i.e there is no libvirt log
until we configure the conf file to log something...
And sorry, but I disagree with Dan... working on ovirt for a few years I
can tell you that the libvirt logs are in debug and are simply rotated
and deleted if space is run out or after 30 days.
These are simple debugging tools that admin's need and if someone
decided that they don't need them - that's ok, but our premise should be
that we want to catch events since they cannot always be reproduced...
this is from an ovirt host where log level is debug and logs are rotated:
2014-02-05 17:07:31.556+0000: 31964: debug : virConnectNumOfDomains:1855
: conn=0x7fe7140008c0
2014-02-05 17:07:35.775+0000: 31958: debug : virConnectCompareCPU:17082
: conn=0x7fe7140008c0, xmlDesc=<cpu
match="minimum"><model>Haswell</model><vendor>Intel</vendor></cpu>,
flags=0
2014-02-05 17:07:35.786+0000: 31959: debug : virConnectCompareCPU:17082
: conn=0x7fe7140008c0, xmlDesc=<cpu
match="minimum"><model>athlon</model><vendor>AMD</vendor></cpu>,
flags=0
2014-02-05 17:07:35.787+0000: 31966: debug : virConnectCompareCPU:17082
: conn=0x7fe7140008c0, xmlDesc=<cpu
match="minimum"><model>Nehalem</model><vendor>Intel</vendor></cpu>,
flags=0
2014-02-05 17:07:35.792+0000: 31963: debug : virConnectCompareCPU:17082
: conn=0x7fe7140008c0, xmlDesc=<cpu
match="minimum"><model>Conroe</model><vendor>Intel</vendor></cpu>,
flags=
root@XXX-XXXX ~]# ls -l /var/log/libvirt/
total 34384
-rw-------. 1 root root 14934506 Feb 5 19:07 libvirtd.log
-rw-------. 1 root root 52868 Jan 1 10:40 libvirtd.log.100.xz
-rw-------. 1 root root 150216 Jan 6 08:25 libvirtd.log.10.xz
-rw-------. 1 root root 149048 Jan 6 06:55 libvirtd.log.11.xz
-rw-------. 1 root root 148444 Jan 6 05:25 libvirtd.log.12.xz
-rw-------. 1 root root 149484 Jan 6 03:55 libvirtd.log.13.xz
-rw-------. 1 root root 150536 Jan 6 02:25 libvirtd.log.14.xz
-rw-------. 1 root root 149948 Jan 6 00:55 libvirtd.log.15.xz
-rw-------. 1 root root 148748 Jan 5 23:25 libvirtd.log.16.xz
-rw-------. 1 root root 149548 Jan 5 21:55 libvirtd.log.17.xz
-rw-------. 1 root root 149428 Jan 5 20:25 libvirtd.log.18.xz
-rw-------. 1 root root 149284 Jan 5 18:55 libvirtd.log.19.xz
-rw-------. 1 root root 601460 Jan 23 14:25 libvirtd.log.1.xz
-rw-------. 1 root root 265132 Dec 15 03:48 libvirtd.log-20131215.xz
-rw-------. 1 root root 148028 Jan 3 03:09 libvirtd.log-20140103.xz
-rw-------. 1 root root 148916 Jan 5 17:25 libvirtd.log.20.xz
-rw-------. 1 root root 149680 Jan 5 15:55 libvirtd.log.21.xz
-rw-------. 1 root root 244180 Jan 5 14:25 libvirtd.log.22.xz
-rw-------. 1 root root 164292 Jan 5 13:10 libvirtd.log.23.xz
-rw-------. 1 root root 156920 Jan 5 11:55 libvirtd.log.24.xz
-rw-------. 1 root root 148544 Jan 5 10:40 libvirtd.log.25.xz
-rw-------. 1 root root 149344 Jan 5 09:10 libvirtd.log.26.xz
On 02/05/2014 06:28 PM, Perry Myers wrote:
On 02/05/2014 01:23 PM, Dafna Ron wrote:
> This is a bug since we install with packstack which need to configure
> this in the deployment and up until now was configured.
> libvirtd log should be created and should be in debug level when
> installing with packstack.
> If this did not happen - it's a bug and user should not configure it
> manually.
libvirtd should never be configured in debug mode by default. Please
see danpb's rationale here:
https://bugzilla.redhat.com/show_bug.cgi?id=1061753#c3
If someone wanted to change packstack to expose a configuration option
to set libvirtd to more verbose logging (but not debug mode) if that
config param is set, that would be fine. But under no circumstances
should it be defaulted to debug enabled.
12:56 p.m.
On 02/05/2014 01:44 PM, Dafna Ron wrote:
Perry,
in current setups nothing is logged at all, i.e there is no libvirt log
until we configure the conf file to log something...
See Kashyap's earlier email. By default libvirt logs to syslog with a
default log level of 3, which logs warnings and errors.
If you are seeing no warnings or errors, then that's a good thing and
under normal circumstances should be sufficient.
Increasing the verbosity to log Info (or Debug) should be something the
system administrator CHOOSES to do, not something a tool like packstack
forces you to do.
See my comment on that bug. I fully support making it easy for
packstack to increase the verbosity of libvirt logging, but agree with
Dan and others that increasing it by default is make a decision for
sysadmins when they should be making the decision themselves.
Perry
1:14 p.m.
perhaps we have a misunderstanding... yogev wrote in the bug:
configuration doesn't write logs -> no libvirt log exists :)
libvirtd.conf currently has # for any logging - which means nothing is
logged for libvirt, no debug, info, warn or error will be logged at all
because the logs for libvirt are disabled.
we did have an error where a libvirt domain was killed and I wanted to
look at the libvirt log to see what happened and this is when we found
no log exists...
after we manually changed the libvirtd.conf file a libvirt log was
created and than we also changed the log level to debug so that we can
debug something :)
basically, we can debate the debug log level issue but can we agree that
a log should exist and log erros?
On 02/05/2014 06:56 PM, Perry Myers wrote:
On 02/05/2014 01:44 PM, Dafna Ron wrote:
> Perry,
>
> in current setups nothing is logged at all, i.e there is no libvirt log
> until we configure the conf file to log something...
See Kashyap's earlier email. By default libvirt logs to syslog with a
default log level of 3, which logs warnings and errors.
If you are seeing no warnings or errors, then that's a good thing and
under normal circumstances should be sufficient.
Increasing the verbosity to log Info (or Debug) should be something the
system administrator CHOOSES to do, not something a tool like packstack
forces you to do.
See my comment on that bug. I fully support making it easy for
packstack to increase the verbosity of libvirt logging, but agree with
Dan and others that increasing it by default is make a decision for
sysadmins when they should be making the decision themselves.
Perry
--
Dafna Ron
3:47 p.m.
On Wed, Feb 05, 2014 at 07:14:07PM +0000, Dafna Ron wrote:
perhaps we have a misunderstanding... yogev wrote in the bug:
configuration doesn't write logs -> no libvirt log exists :)
libvirtd.conf currently has # for any logging - which means nothing
is logged for libvirt, no debug, info, warn or error will be logged
at all because the logs for libvirt are disabled.
we did have an error where a libvirt domain was killed and I wanted
to look at the libvirt log to see what happened and this is when we
found no log exists...
after we manually changed the libvirtd.conf file a libvirt log was
created and than we also changed the log level to debug so that we
can debug something :)
Agreed, this can be a little frustrating during full crashes. I noted
some more points in the bug, to keep discussions/questions intact,
further discussions please redirect there.
basically, we can debate the debug log level issue but can we agree
that a log should exist and log erros?
Please note:
- You can do "tail -f foo.log" style monitoring, by default, for
libvirtd service:
$ journalctl -f --unit=libvirtd
So, you should at-least see some kind of errors, warnings there.
- And, Some amount of guest specific logs go --
/var/log/libvirt/qemu/guest.log
On 02/05/2014 06:56 PM, Perry Myers wrote:
>On 02/05/2014 01:44 PM, Dafna Ron wrote:
>>Perry,
>>
>>in current setups nothing is logged at all, i.e there is no libvirt log
>>until we configure the conf file to log something...
>See Kashyap's earlier email. By default libvirt logs to syslog with a
>default log level of 3, which logs warnings and errors.
>
>If you are seeing no warnings or errors, then that's a good thing and
>under normal circumstances should be sufficient.
>
>Increasing the verbosity to log Info (or Debug) should be something the
>system administrator CHOOSES to do, not something a tool like packstack
>forces you to do.
>
>See my comment on that bug. I fully support making it easy for
>packstack to increase the verbosity of libvirt logging, but agree with
>Dan and others that increasing it by default is make a decision for
>sysadmins when they should be making the decision themselves.
>
>Perry
--
Dafna Ron
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
--
/kashyap
3751
days inactive
3751
days old
8 comments
4 participants
participants (4)
-
Dafna Ron -
Kashyap Chamarthy -
Perry Myers -
Yogev Rabl