Your message dated Sun, 12 May 2013 15:44:33 +0200
with message-id <[email protected]>
and subject line not really a bug, closing
has caused the Debian Bug report #706977,
regarding Bug in munin upgrade (aka: perl trigger)
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.)
--
706977: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706977
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: munin
Version: 2.0.6-4
As seen on our IRC channel :
17:29 [Freenode] < pacop:#munin> Hello, I get this when running munin-cron,
any idea please? Can't locate Log/Log4perl.pm in @INC (@INC contains:
/etc/perl
/usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 /usr/lib/perl5
/usr/share/perl5 /usr/lib/perl/5.14 /usr/share/perl/5.14
/usr/local/lib/site_perl .) at
/usr/share/munin/munin-update line 12.
17:29 [Freenode] < pacop:#munin> BEGIN failed--compilation aborted at
/usr/share/munin/munin-update line 12.
17:30 [Freenode] < pacop:#munin> I have upgraded to debian wheezy,
17:30 [Freenode] < pacop:#munin> but I kept all munin config untocuhed
17:31 < Nilshar:#munin> try installing liblog-log4perl-perl
17:32 [Freenode] < pacop:#munin> solved! it was already install, but I have
solved it with dpkg -r munin liblog-log4perl-perl and then reinstalling them
17:32 [Freenode] < pacop:#munin> *thank you!*
17:54 < h01ger:#munin> thats a hack but not a solutin
17:54 < h01ger:#munin> munin-cron, perl trigger, there was something
17:54 < h01ger:#munin> +please file bugs
h01ger, Wish granted.
--
Steve Schnepp
--- End Message ---
--- Begin Message ---
Hi,
I don't think this is a real bug anymore: cron was probably running during the
upgrade at which at some point liblog-log4perl-perl didn't exist for that perl
version while it was required from the cron job. As the cron job is time
scheduled, it simply can happen that somethings is executed to run, which is
broken at that moment.
cheers,
Holger
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
