Your message dated Tue, 12 Feb 2008 18:44:17 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#465422: munin: runs wild and overwrites random files
on the system
has caused the Debian Bug report #465422,
regarding munin: runs wild and overwrites random files on the system
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.)
--
465422: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465422
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: munin
Version: 1.2.5-1
Severity: critical
Tags: security
Justification: causes serious data loss
Munin recently ran amok on my backup/log-server. It dumped its RRD files
on top of random files in the root-filesystem. Fortunately mostly in
/usr/share/doc/
I have experienced bug #310915 as well as the occational excessive
cpu-usage. None of these seemed to be worse than annoyances though.
Today however, it clobbered /usr/share/backuppc/lib/BackupPC/Lib.pm
which obviously broke my backups.
All clobbered files end up with their original name but owner/group as
munin/munin. It even replaced /usr/share/doc/libneon25/ (a directory)
with an RRD-file of the same name but munin/munin as owner/group.
Filesystem : ext3
Munin version was : 1.2.5-1
# uname -a
Linux vaagen 2.6.18-5-xen-686 #1 SMP Mon Dec 24 20:49:58 UTC 2007 i686
GNU/Linux
Since the server is a production-machine I've uninstalled munin, but
I'll be happy to provide whatever other information I can.
The other machines that have been running munin-node only, with various
plugins have not suffered the same problems.
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-xen-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages munin depends on:
ii adduser 3.102 Add and remove users and groups
pn libdigest-md5-perl <none> (no description available)
pn libhtml-template-perl <none> (no description available)
pn librrds-perl <none> (no description available)
pn libtime-hires-perl <none> (no description available)
ii perl [libstorable-perl] 5.8.8-7etch1 Larry Wall's Practical Extraction
ii perl-modules 5.8.8-7etch1 Core Perl modules
pn rrdtool <none> (no description available)
Versions of packages munin recommends:
pn libdate-manip-perl <none> (no description available)
pn munin-node <none> (no description available)
--- End Message ---
--- Begin Message ---
On Tue, Feb 12, 2008 at 04:11:14PM +0100, Ole-Morten Duesund wrote:
> There was indeed a filesystem corruption - however, fsck only found
> problems with the files munin had touched.
That was my experience with my case of file syystem corruption. The first
damage was quite specific. The first indication was that
/var/lib/dpkg/available contained a lot of syslog data. The second, a few
days later, was rather more serious, and I needed to restore from backup to
recover my /var.
Closing this bug report. I hope you don't see any more filesystem
corruption, but make sure your backups are restorable in any case. :D
--
Stig
signature.asc
Description: Digital signature
--- End Message ---
