Your message dated Mon, 5 Dec 2011 08:32:26 +0100
with message-id <[email protected]>
and subject line Fixed in 0.9.8
has caused the Debian Bug report #625288,
regarding Disable harmful second timestamp (or make optional).
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
625288: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625288
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libvirt
Version: 0.9.0-1
Severity: normal
I run logcheck with syslog-summary enabled. That allows me to get ONE
line like this, indicating the number of duplicate (in this case 10):
10 stomp dovecot: IMAP(russm): stat(/var/mail/lists/.managers/tmp) failed:
Permission denied (euid=1033(russm) egid=1033(russm) missing +x perm:
/var/mail/lists/.managers)
However, libvirtd includes its own timestamps in its syslog messages, which
completely ruins this:
1 theta libvirtd: 15:33:46.516: error : checkType:2495 :
remoteReadConfigFile: /etc/libvirt/libvirtd.conf: unix_sock_group: invalid
type: got long; expected string#012
1 theta libvirtd: 15:33:46.523: error : checkType:2495 :
remoteReadConfigFile: /etc/libvirt/libvirtd.conf: unix_sock_group: invalid
type: got long; expected string#012
1 theta libvirtd: 15:33:46.530: error : checkType:2495 :
remoteReadConfigFile: /etc/libvirt/libvirtd.conf: unix_sock_group: invalid
type: got long; expected string#012
1 theta libvirtd: 15:33:46.537: error : checkType:2495 :
remoteReadConfigFile: /etc/libvirt/libvirtd.conf: unix_sock_group: invalid
type: got long; expected string#012
1 theta libvirtd: 15:33:46.544: error : checkType:2495 :
remoteReadConfigFile: /etc/libvirt/libvirtd.conf: unix_sock_group: invalid
type: got long; expected string#012
1 theta libvirtd: 15:33:46.551: error : checkType:2495 :
remoteReadConfigFile: /etc/libvirt/libvirtd.conf: unix_sock_group: invalid
type: got long; expected string#012
1 theta libvirtd: 15:33:46.558: error : checkType:2495 :
remoteReadConfigFile: /etc/libvirt/libvirtd.conf: unix_sock_group: invalid
type: got long; expected string#012
1 theta libvirtd: 15:33:46.565: error : checkType:2495 :
remoteReadConfigFile: /etc/libvirt/libvirtd.conf: unix_sock_group: invalid
type: got long; expected string#012
1 theta libvirtd: 15:33:46.572: error : checkType:2495 :
remoteReadConfigFile: /etc/libvirt/libvirtd.conf: unix_sock_group: invalid
type: got long; expected string#012
1 theta libvirtd: 15:33:46.579: error : checkType:2495 :
remoteReadConfigFile: /etc/libvirt/libvirtd.conf: unix_sock_group: invalid
type: got long; expected string#012
1 theta libvirtd: 15:33:46.586: error : checkType:2495 :
remoteReadConfigFile: /etc/libvirt/libvirtd.conf: unix_sock_group: invalid
type: got long; expected string#012
Please remove, or at least make optional, these timestamps. This is analogous
to these smb.conf options:
[global]
# Without these, logserv's syslog-summary(1) fails to merge
# identical smb log entries in logcheck emails.
debug prefix timestamp = no
debug timestamp = no
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Version: libvirt/0.9.8~rc2-1
Hi,
this was fixed in the above upload.
Cheers,
-- Guido
--- End Message ---
