Bug 119463 - mrtg cronjob email contain lots of perl errors
mrtg cronjob email contain lots of perl errors
Product: Fedora
Classification: Fedora
Component: mrtg (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Miloslav Trmač
Depends On:
Blocks: 122683
  Show dependency treegraph
Reported: 2004-03-30 13:57 EST by Bernd Bartmann
Modified: 2007-11-30 17:10 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-29 18:12:48 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bernd Bartmann 2004-03-30 13:57:13 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040312

Description of problem:
The default mrtg cronjob sends these error messages each time it is run:

Use of uninitialized value in string at /usr/bin/mrtg line 72.
Empty compile time value given to use lib at /usr/bin/mrtg line 72
Use of uninitialized value in concatenation (.) or string at
/usr/bin/mrtg line 73.
Can't locate MRTG_lib.pm in @INC (@INC contains: /../lib/mrtg2 
/usr/lib/perl5/5.8.3/i386-linux-thread-multi /usr/lib/perl5/5.8.3
+/usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl/5.8.2
/usr/lib/perl5/site_perl/5.8.1 /usr/lib/perl5/site_perl/5.8.0
/usr/lib/perl5/vendor_perl/5.8.3 /usr/lib/perl5/vendor_perl/5.8.2
+/usr/lib/perl5/vendor_perl/5.8.1 /usr/lib/perl5/vendor_perl/5.8.0
/usr/lib/perl5/vendor_perl .) at /usr/bin/mrtg line 78.
BEGIN failed--compilation aborted at /usr/bin/mrtg line 78.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. FC2Test2 everything install
2. wait for mrtg cronjob emails

Additional info:
Comment 1 Need Real Name 2004-04-02 13:09:09 EST
Same for me.
Comment 2 Bernd Bartmann 2004-04-04 13:00:34 EDT
The problem seems to be SELinux related. After reinstalling the system
with SELinux disabled the problem does not appear again.
Comment 3 Warren Togami 2004-05-07 00:16:45 EDT
Any update on this with FC2 latest?
Comment 4 Bernd Bartmann 2004-05-07 03:50:15 EDT
I haven't seen this problem on a default full FC2T3 install anymore.
Comment 5 Miloslav Trmač 2004-09-29 18:12:48 EDT
I haven't seen this with FC3t2 either (even with strict policy).

Note You need to log in before you can comment on or make changes to this bug.