Page 1 of 1

check_mrtgtraf: Unable to process MRTG log file..

Posted: Fri Feb 08, 2013 1:11 pm
by nagios@ios
Hello All,

i have installed nagios-3.4.4
nagios-plugins-1.4.16

but when i configured it to monitor the switch using http://nagios.sourceforge.net/docs/3_0/ ... uters.html

it is giving me this error for bandwidth usuage.

Can some one help me with this?

thanks

Re: check_mrtgtraf: Unable to process MRTG log file..

Posted: Fri Feb 08, 2013 2:09 pm
by nagios@ios
i checked the /var/lib/ and there was no 'mrtg' . So i created directory named 'mrtg' and than created a file name myipaddress_1.log;

After than i run
crontab -e

and place the line ..
*/5 * * * * /usr/bin/env LANG=C /usr/bin/mrtg /etc/mrtg/mymrtg.cfg –logging /var/log/mrtg.log

but still get the same error.
ichecked that myipaddress_1.log file but nothing is being written there. its empty.

Re: check_mrtgtraf: Unable to process MRTG log file..

Posted: Fri Feb 08, 2013 2:35 pm
by slansing
What is the error you are receiving? It doesn't show in your first post.

Re: check_mrtgtraf: Unable to process MRTG log file..

Posted: Fri Feb 08, 2013 2:46 pm
by nagios@ios
check_mrtgtraf: Unable to process MRTG log file

this is the alert message i am getting for the service Port 1 Bandwidth Usage for my Switch.

Re: check_mrtgtraf: Unable to process MRTG log file..

Posted: Sun Feb 10, 2013 5:09 pm
by scottwilkerson
what is the full command you are using?

Re: check_mrtgtraf: Unable to process MRTG log file..

Posted: Mon Feb 11, 2013 6:21 am
by gshergill
Hi nagios@ios,

Please see my post at the following link:

http://support.nagios.com/forum/viewtop ... 97&p=41106

The link http://www.howtoforge.com/forums/archiv ... 48484.html at about post 10 is the solution to this.

Note that you may need to change a few of the commands there to match your setup.

Hope this helps.

Kind Regards,

Gary Shergill

Re: check_mrtgtraf: Unable to process MRTG log file..

Posted: Mon Feb 11, 2013 3:16 pm
by abrist
@nagios@ios: How did gshergill's link work out for you? Has this been resolved?