Package: munin Version: 1.2.3-3 Followup-For: Bug #310915
I have seen loads of lock messages when dns records got changed and some hosts would no longer respond to names in the config. I suppose that it could happen if anything delays the cron task so much that the next one is fired before the old one has managed to finish all processing. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (900, 'stable'), (400, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.10-1-686 Locale: LANG=en_GB, [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages munin depends on: ii adduser 3.67 Add and remove users and groups pn libdigest-md5-perl <none> (no description available) ii libhtml-template-perl 2.6-2 HTML::Template : A module for usin ii librrds-perl 1.0.49-1 Time-series data storage and displ pn libtime-hires-perl <none> (no description available) ii perl [libstorable-perl] 5.8.7-3 Larry Wall's Practical Extraction ii perl-modules 5.8.7-3 Core Perl modules ii rrdtool 1.0.49-1 Time-series data storage and displ Versions of packages munin recommends: pn libdate-manip-perl <none> (no description available) ii munin-node 1.2.3-3 network-wide graphing framework (n -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
