mrtg graphs

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Locked
Pikmin
Posts: 80
Joined: Tue Feb 17, 2015 5:32 pm

mrtg graphs

Post by Pikmin »

Hi there
I keep getting these in the mrtg.log file, any chance someone can help me resolve them?

Code: Select all

Use of uninitialized value in concatenation (.) or string at /usr/bin/mrtg line 1326.
Use of uninitialized value in concatenation (.) or string at /usr/bin/mrtg line 1326.
Use of uninitialized value in concatenation (.) or string at /usr/bin/mrtg line 1335.
Use of uninitialized value in concatenation (.) or string at /usr/bin/mrtg line 1335.
Use of uninitialized value in concatenation (.) or string at /usr/bin/mrtg line 1326.
Use of uninitialized value in concatenation (.) or string at /usr/bin/mrtg line 1326.
Use of uninitialized value in concatenation (.) or string at /usr/bin/mrtg line 1335.
Use of uninitialized value in concatenation (.) or string at /usr/bin/mrtg line 1335.
Use of uninitialized value in concatenation (.) or string at /usr/bin/mrtg line 1326.
Use of uninitialized value in concatenation (.) or string at /usr/bin/mrtg line 1326.
Use of uninitialized value in concatenation (.) or string at /usr/bin/mrtg line 1335.
Use of uninitialized value in concatenation (.) or string at /usr/bin/mrtg line 1335.
Also I'm getting mails about this:

2-03-2015 15:00:05, Rateup ERROR: /usr/bin/rateup found that 192.168.100.2_10108's log file time of 1426132803 was great
er than now (1426132802)
ERROR: Let's not do the time warp, again. Logfile unchanged.
12-03-2015 15:00:05, Rateup ERROR: /usr/bin/rateup found that 192.168.100.2_10109's log file time of 1426132803 was great
er than now (1426132802)
ERROR: Let's not do the time warp, again. Logfile unchanged.
12-03-2015 15:00:05, Rateup ERROR: /usr/bin/rateup found that 192.168.100.2_10110's log file time of 1426132803 was great
er than now (1426132802)

I did change the time on the server to use ntp from windows domain, from there I have deleted and regenerated all the log files with cfgmaker and still keep getting those errors
Top
User avatar
Box293
Too Basu
Posts: 5126
Joined: Sun Feb 07, 2010 10:55 pm
Location: Deniliquin, Australia
Contact:
Contact Box293

Re: mrtg graphs

Post by Box293 »

Are you getting any messages about MRTG in /var/spool/mail/root ?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Top
Pikmin
Posts: 80
Joined: Tue Feb 17, 2015 5:32 pm

Re: mrtg graphs

Post by Pikmin »

Hi yes,
This morning I checked and there are 362 messages since yesterday
Top
jolson
Attack Rabbit
Posts: 2560
Joined: Thu Feb 12, 2015 12:40 pm

Re: mrtg graphs

Post by jolson »

Any chance SELinux is running on this box?

Code: Select all

sestatus
If so, try disabling it temporarily and see if that helps:

Code: Select all

setenforce 0
Twits Blog
Show me a man who lives alone and has a perpetually clean kitchen, and 8 times out of 9 I'll show you a man with detestable spiritual qualities.
Top
Pikmin
Posts: 80
Joined: Tue Feb 17, 2015 5:32 pm

Re: mrtg graphs

Post by Pikmin »

Hi there,
SELinux is disabled
Top
User avatar
Box293
Too Basu
Posts: 5126
Joined: Sun Feb 07, 2010 10:55 pm
Location: Deniliquin, Australia
Contact:
Contact Box293

Re: mrtg graphs

Post by Box293 »

Pikmin wrote:Hi yes,
This morning I checked and there are 362 messages since yesterday
Can you please post one of these messages in it's entirety (from /var/spool/mail/root).

With that information I should be able to give you a fix.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Top
Pikmin
Posts: 80
Joined: Tue Feb 17, 2015 5:32 pm

Re: mrtg graphs

Post by Pikmin »

Here you go :)

Code: Select all

From root@localhost.localdomain  Thu Mar 12 16:20:12 2015
Return-Path: <root@localhost.localdomain>
X-Original-To: root
Delivered-To: root@localhost.localdomain
Received: by localhost.localdomain (Postfix, from userid 0)
        id 44CC2388D30; Thu, 12 Mar 2015 16:20:08 +1100 (EST)
From: root@localhost.localdomain (Cron Daemon)
To: root@localhost.localdomain
Subject: Cron <root@localhost> /usr/bin/env /usr/bin/mrtg /etc/mrtg/mrtg.cfg --logging /var/log/mrtg.log
Content-Type: text/plain; charset=UTF-8
Auto-Submitted: auto-generated
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=root>
X-Cron-Env: <USER=root>
Message-Id: <20150312052012.44CC2388D30@localhost.localdomain>
Date: Thu, 12 Mar 2015 16:20:04 +1100 (EST)
Status: O

12-03-2015 16:20:04, Rateup WARNING: /usr/bin/rateup Can't remove 192.168.100.3_100.old updating log file
12-03-2015 16:20:04, Rateup WARNING: /usr/bin/rateup Can't remove 192.168.100.3_10101.old updating log file
12-03-2015 16:20:05, Rateup WARNING: /usr/bin/rateup could not read the primary log file for 192.168.100.1_28
12-03-2015 16:20:05, Rateup ERROR: /usr/bin/rateup found 192.168.100.1_28's log file was corrupt
          or not in sorted order:
time: 1421121600.12-03-2015 16:20:05, Rateup WARNING: /usr/bin/rateup The backup log file for 192.168.100.1_28 was invalid as well

From root@localhost.localdomain  Thu Mar 12 16:20:14 2015
Return-Path: <root@localhost.localdomain>
X-Original-To: root
Delivered-To: root@localhost.localdomain
Received: by localhost.localdomain (Postfix, from userid 0)
        id EABDD388C9E; Thu, 12 Mar 2015 16:20:08 +1100 (EST)
From: root@localhost.localdomain (Cron Daemon)
To: root@localhost.localdomain
Subject: Cron <root@localhost> LANG=C LC_ALL=C /usr/bin/mrtg /etc/mrtg/mrtg.cfg --lock-file /var/lock/mrtg/mrtg_l --confcache-file /var/lib/mrtg/mrtg.ok
Content-Type: text/plain; charset=UTF-8
Auto-Submitted: auto-generated
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=root>
X-Cron-Env: <USER=root>
Message-Id: <20150312052012.EABDD388C9E@localhost.localdomain>
Date: Thu, 12 Mar 2015 16:20:04 +1100 (EST)
Status: O

12-03-2015 16:20:04, Rateup WARNING: /usr/bin/rateup could not read the primary log file for 192.168.100.3_100
12-03-2015 16:20:04, Rateup WARNING: /usr/bin/rateup Can't rename 192.168.100.3_100.log to 192.168.100.3_100.old updating log file
12-03-2015 16:20:04, Rateup WARNING: /usr/bin/rateup could not read the primary log file for 192.168.100.3_10101
12-03-2015 16:20:04, Rateup WARNING: /usr/bin/rateup Can't rename 192.168.100.3_10101.log to 192.168.100.3_10101.old updating log file
12-03-2015 16:20:05, Rateup WARNING: /usr/bin/rateup could not read the primary log file for 192.168.100.1_28
12-03-2015 16:20:05, Rateup ERROR: /usr/bin/rateup found 192.168.100.1_28's log file was corrupt
          or not in sorted order:
time: 1421121600.12-03-2015 16:20:05, Rateup WARNING: /usr/bin/rateup The backup log file for 192.168.100.1_28 was invalid as well
Thursday, 12 March 2015 at 16:20: ERROR: Skipping webupdates because rateup did not return anything sensible
Thursday, 12 March 2015 at 16:20: WARNING: rateup died from Signal 0
 with Exit Value 1 when doing router '192.168.100.1_28'
 Signal was 0, Returncode was 1
12-03-2015 16:20:06, Rateup ERROR: /usr/bin/rateup found that 192.168.100.1_10201's log file time of 1426137603 was greater than now (1
426137602)
ERROR: Let's not do the time warp, again. Logfile unchanged.
12-03-2015 16:20:06, Rateup ERROR: /usr/bin/rateup found that 192.168.100.1_10202's log file time of 1426137603 was greater than now (1
426137602)
ERROR: Let's not do the time warp, again. Logfile unchanged.
12-03-2015 16:20:06, Rateup ERROR: /usr/bin/rateup found that 192.168.100.1_10610's log file time of 1426137603 was greater than now (1
426137602)
ERROR: Let's not do the time warp, again. Logfile unchanged.
12-03-2015 16:20:06, Rateup ERROR: /usr/bin/rateup found that 192.168.100.1_10611's log file time of 1426137603 was greater than now (1
426137602)
ERROR: Let's not do the time warp, again. Logfile unchanged.
Top
User avatar
Box293
Too Basu
Posts: 5126
Joined: Sun Feb 07, 2010 10:55 pm
Location: Deniliquin, Australia
Contact:
Contact Box293

Re: mrtg graphs

Post by Box293 »

In your config file, are these ports valid ports and do you want to collect data on them?

192.168.100.1_28
192.168.100.1_10201
192.168.100.1_10202
192.168.100.1_10610
192.168.100.1_10611

If they are not, simply comment out the lines for each port (it can be 30+ lines).
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Top
Pikmin
Posts: 80
Joined: Tue Feb 17, 2015 5:32 pm

Re: mrtg graphs

Post by Pikmin »

192.168.100.1_28 Vl28 (Vlan28 Virtual Interface)
192.168.100.1_10201 Te1/1/1
192.168.100.1_10202 Te1/1/2
192.168.100.1_10610 Gi2/0/10
192.168.100.1_10611 Gi2/0/10

I would like to monitor vlan28, even though there's very little traffic on it

The others are not connected so I could comment them out
Thank you
Top
User avatar
Box293
Too Basu
Posts: 5126
Joined: Sun Feb 07, 2010 10:55 pm
Location: Deniliquin, Australia
Contact:
Contact Box293

Re: mrtg graphs

Post by Box293 »

First just try commenting out those ports you don't need and observe.

If number 28 persists to be a problem, I would try deleting the file for 192.168.100.1_28 and see if that fixes the problem.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Top
Locked

Return to “Open Source Nagios Projects”