check_rrdtraf

[Pili Muñoz Gargallo]

Of course yes, PEBKAC...
i have a new issue:
if i execute the same command from command line  i obtain:
 ./check_rrdtraf -f /var/www/html/cfg/62.81.189.118_1.rrd -c 5000000,5000000
-w 3000000,3000000

./check_rrdtraf: line 248: [: 8,000000: integer expression expected
./check_rrdtraf: line 251: [: 8,000000: integer expression expected
./check_rrdtraf: line 254: [: 8,000000: integer expression expected
./check_rrdtraf: line 263: [: 32,000000: integer expression expected
./check_rrdtraf: line 266: [: 32,000000: integer expression expected
./check_rrdtraf: line 269: [: 32,000000: integer expression expected
(standard_in) 1: parse error
(standard_in) 1: parse error
(standard_in) 1: parse error
(standard_in) 1: parse error
OK - Current BW in: Gbps Out: Gbps(standard_in) 1: parse error
(standard_in) 1: parse error
|in=Gb/s;3000000;5000000 (standard_in) 1: parse error
(standard_in) 1: parse error
out=Gb/s;3000000;5000000

so Is there another problem or it is just me?
Thanks again, and forgive me for these questions: Like i used to say, i am a
student and i am newbie in linux, LAMP servers, Nagios, MRTG, RRDTool.....
and everything you imagine..

Cheers

Pili

2008/2/15, Israel Brewster <israel at frontierflying.com>:
>
>
>
>
> On Feb 14, 2008, at 1:48 PM, Pili Muñoz Gargallo wrote:
>
> hi all,
> thanks for the help. I have been trying several things that you told me.
> I'll give more information. I am monitoring bandwith with MRTG and storing
> datas in rrdtool format.
> If i run command from command line is
>
> ./check_rrdtraf -f ./var/www/html/cfg/62.81.189.118_1.rrd  -l B  -c
> 3000000,3000000 -w 5000000,5000000
>
> ./var/www/html/cfg/62.81.189.118_1.rrd does not exist.
>
> I am graphing with routers2.cgi and it receives values, and if i do :
>
>  rrdtool fetch /var/www/html/cfg/62.81.189.118_1.rrd AVERAGE
> .
> .
> .
>
> 1203025200: 1.3963531752e+05 8.2446477796e+04
> 1203025500: 1.3719540269e+05 1.0068914358e+05
> 1203025800: 1.3673972419e+05 1.0818787703e+05
> 1203026100: 1.3729848910e+05 1.1104579469e+05
> 1203026400: 1.3708077389e+05 1.1129381874e+05
> 1203026700: 1.3590177194e+05 1.1081213980e+05
> 1203027000: 3.1652589163e+05 2.5986265329e+05
> 1203027300: 3.8436060720e+05 3.1651678017e+05
> 1203027600: 1.4309192557e+05 1.1708320591e+05
> 1203027900: nan nan
> 1203028200: nan nan
>
> i see it is storing values...
> what is wrong? I had read check_rrdtraf help and i have included -l B
> option to indicate that data are bits...but it is still not working
>
>
> As Marc pointed out in his response, having the ./var instead of /var in
> the path to the .rrd file is wrong. you want /var WITHOUT the period. Also,
> note that the -l switch only affects the display of the output. It is not
> needed in normal operation, unless you really want to see the output as bits
> rather than Kb, Mb, etc. The plugin will auto-choose the best option based
> on the data if you leave this switch out. But the main problem is the period
> before that slash. Remove it, and it should work.
>
> -----------------------------------------------
> Israel Brewster
> Computer Support Technician
> Frontier Flying Service Inc.
> 5245 Airport Industrial Rd
> Fairbanks, AK 99709
> (907) 450-7250 x293
> -----------------------------------------------
>
>
> I obtain now:
> OK - Current BW in: bps Out: bps
>
> any more ideas?
> Thank you again for your patience!!!
>
> Pili
>
>
> 2008/2/13, Israel Brewster <israel at frontierflying.com>:
> >
> > On Feb 13, 2008, at 6:34 AM, Marc Powell wrote:
> > >> -----Original Message-----
> > >> From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-
> > >> users-
> > >> bounces at lists.sourceforge.net] On Behalf Of Pili Muñoz Gargallo
> > >> Sent: Wednesday, February 13, 2008 7:23 AM
> > >> To: nagios-users at lists.sourceforge.net
> > >> Subject: [Nagios-users] check_rrdtraf
> > >>
> > >> Hi
> > >> i am trying to measure bandwith using check_rrd
> > >
> > > When asking about plugins that don't come with the distribution it's
> > > helpful to include where you obtained the plugin so everyone knows
> > > which check_rrd (or check_rrdtraf as the case may be) you're talking
> > > about.
> >
> >
> > That would be (partly) my plugin, obtained from Nagiosexchange.org,
> > most likely :)
> >
> >
> > >> i use  the command:
> > >> $USER1$/check_rrdtraf -f ./var/www/html/cfg/$HOSTADRESS$_1.rrd  -l
> > >> b -vv -
> > >> c $ARG1$ -w $ARG2$
> > >
> > > You meant $HOSTADDRESS$ here, right?
> >
> >
> > And did you really want that period before the /var ?
> >
> > >
> > >
> > >> and in the service i give it the next arguments:
> > >> !3000000,3000000!5000000,5000000
> > >>
> > >> i have read about it several times, and it doesn't work how i espect:
> > >> it returns me an OK value, but it doesn't tell me the present BW...
> > >> Am i missing something?
> > >>
> > >
> > > When you run the above command as the nagios user from the command
> > > line, does the first line of output match what you're seeing in the
> > > GUI? I expect it starts with the word 'Using'. What is the -vv flag
> > > causing to happen when the program is run (hint, run check_rrdtraf --
> > > help to find out)?
> >
> >
> > The -vv is an issue, although there could be a couple of others (see
> > previous comments about the formating of the file string in the
> > command). As that flag gives a lot of debugging output, and nagios
> > only displays the first line of output, I wouldn't expect it to show
> > the traffic values with this switch in there. What I would expect
> > nagios to be showing is something along the lines of "Using RRD File: /
> > var/www/html/cfg/$HOSTADRESS$_1.rrd" (I think that's the first line of
> > debugging output I put in there), with $HOSTADDRESS$ replaced  with
> > the applicable value. Try without the -vv and see what happens.
> >
> > -----------------------------------------------
> >
> > Israel Brewster
> > Computer Support Technician
> > Frontier Flying Service Inc.
> > 5245 Airport Industrial Rd
> > Fairbanks, AK 99709
> > (907) 450-7250 x293
> > -----------------------------------------------
> >
> > >
> > >
> > > --
> > > Marc
> > >
> > >
> > >
> > >
> > -------------------------------------------------------------------------
> > > This SF.net email is sponsored by: Microsoft
> > > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > > _______________________________________________
> > > Nagios-users mailing list
> > > Nagios-users at lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/nagios-users
> > > ::: Please include Nagios version, plugin version (-v) and OS when
> > > reporting any issue.
> > > ::: Messages without supporting info will risk being sent to /dev/null
> >
> >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > Nagios-users mailing list
> > Nagios-users at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/nagios-users
> > ::: Please include Nagios version, plugin version (-v) and OS when
> > reporting any issue.
> > ::: Messages without supporting info will risk being sent to /dev/null
> >
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20080215/c558b20c/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null