Re: [Perfparse-users] Warn values are not going into database

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Hi

I copied the plugin into the original plugins source dir and went for the
full on all plugin recompile as per first installation process I used wit=
h
Nagios.

If I leave the orginal check_nt.c in there all compiles fine.

Thanks

Barry

----- Original Message -----=20
From: "Cook, Garry" <GW...@ma...>
To: "Barry Weeks" <ba...@if...>; <per...@li...=
>
Sent: Thursday, August 12, 2004 5:17 PM
Subject: RE: [Perfparse-users] Warn values are not going into database

> Sorry about that, line 105 - 110 is what I meant to type. Damn fingers
have a mind of their own sometimes...
>
> I've not yet compiled or tested on my FC1 box. Don't know when I'll hav=
e
time to do so, maybe next week.
> Did you compile from the nagiosplugins source directory? If not, you
should check the original thread (RE: [Perfparse-users] Added perfdata to
check_nt), there was a post earlier today from Nate Smith. He was having
trouble compiling it on FC2. Philipp Sand replied with some basic
instructions on where to compile the plugin.
>
> HTH
>
> Garry W. Cook, CCNA
> Network Infrastructure Manager
> MACTEC, Inc. - http://www.mactec.com/
> 303.308.6228 (Office) - 720.220.1862 (Mobile)
>
> per...@li... wrote:
> > Hi Garry
> >
> > Thanks for quick response as always.
> > I'm using FC1
> >
> > The lines you specifed are as you said they should be but the
> > setlocale (LC_ALL, ""); line is line 105 not 110.
> >
> > Thanks
> >
> > Barry
> > ----- Original Message -----
> > From: "Cook, Garry" <GW...@ma...>
> > To: "Barry Weeks" <ba...@if...>;
> > <per...@li...>
> > Sent: Thursday, August 12, 2004 4:53 PM
> > Subject: RE: [Perfparse-users] Warn values are not going into databas=
e
> >
> >
> >> That's strange... As I mentioned before, I can't be sure
> > that it will
> > compile properly on all systems, as I only have RH9.0 to test
> > with (and FC1,
> > but haven't really had time to check it out in that environment).
> >> However, I'm wondering if maybe the source code that I sent
> > was somehow
> > corrupted. Do your lines 110 through 115 look like the following?
> >>
> >>   setlocale (LC_ALL, "");
> >>   bindtextdomain (PACKAGE, LOCALEDIR);
> >>   textdomain (PACKAGE);
> >>
> >>   if(process_arguments(argc,argv)=3D=3DERROR)
> >>     usage(_("Could not parse arguments\n"));
> >>
> >> If not, they should. Let me know. Thanks.
> >>
> >> Garry W. Cook, CCNA
> >> Network Infrastructure Manager
> >> MACTEC, Inc. - http://www.mactec.com/
> >> 303.308.6228 (Office) - 720.220.1862 (Mobile)
> >>
> >> Barry Weeks wrote:
> >>> Hi Gary / All
> >>>
> >>> check_nt will not compile for me see below
> >>>
> >>> gcc -DHAVE_CONFIG_H -I. -I. -I. -I. -I. -I. -I. -I. -I.. -I../lib
> >>> -I/usr/include/ldap  -I/usr/include     -g -O2 -c `test -f
> >>> 'check_nt.c' || echo './'`check_nt.c
> >>> check_nt.c: In function `main':
> >>> check_nt.c:105: error: `LC_ALL' undeclared (first use in this
> >>> function) check_nt.c:105: error: (Each undeclared identifier is
> >>> reported only once check_nt.c:105: error: for each function it
> >>> appears in.) check_nt.c:106: error: `LOCALEDIR' undeclared (first
> >>> use in this function) check_nt.c:110: warning: passing arg 1 of
> >>> `usage' makes pointer from integer without a cast check_nt.c:136:
> >>> warning: passing arg 1 of `strlen' makes pointer from integer
> >>> without a cast check_nt.c:136: warning: passing arg 2 of `memcpy'
> >>> makes pointer from integer without a cast check_nt.c:136: warning:
> >>> passing arg 1 of `__strdup' makes pointer from integer without a
> >>> cast check_nt.c:138: warning: passing arg 1 of `strlen' makes
> >>> pointer from integer without a cast check_nt.c:138: warning:
> >>> passing arg 2 of `memcpy' makes pointer from integer without a cast
> >>> check_nt.c:138: warning: passing arg 1 of `__strdup' makes pointer
> >>> from integer without a cast check_nt.c:142: warning: passing arg 1
> >>> of `strlen' makes pointer from integer without a cast
> >>> check_nt.c:142: warning: passing arg 2 of `memcpy' makes pointer
> >>> from integer without a cast check_nt.c:142: warning: passing arg 1
> >>> of `__strdup' makes pointer from integer without a cast
> >>> check_nt.c:143: warning: passing arg 1 of `strlen' makes pointer
> >>> from integer without a cast check_nt.c:143: warning: passing arg 2
> >>> of `memcpy' makes pointer from integer without a cast
> >>> check_nt.c:143: warning: passing arg 1 of `__strdup' makes pointer
> >>> from integer without a cast check_nt.c:177: warning: passing arg 1
> >>> of `strlen' makes pointer from integer without a cast
> >>> check_nt.c:177: warning: passing arg 2 of `memcpy' makes pointer
> >>> from integer without a cast check_nt.c:177: warning: passing arg 1
> >>> of `__strdup' makes pointer from integer without a cast
> >>> check_nt.c:196: warning: passing arg 1 of `strlen' makes pointer
> >>> from integer without a cast check_nt.c:196: warning: passing arg 2
> >>> of `memcpy' makes pointer from integer without a cast
> >>> check_nt.c:196: warning: passing arg 1 of `__strdup' makes pointer
> >>> from integer without a cast check_nt.c:198: warning: passing arg 1
> >>> of `strlen' makes pointer from integer without a cast
> >>> check_nt.c:198: warning: passing arg 2 of `memcpy' makes pointer
> >>> from integer without a cast check_nt.c:198: warning: passing arg 1
> >>> of `__strdup' makes pointer from integer without a cast
> >>> check_nt.c:227: warning: passing arg 1 of `strlen' makes pointer
> >>> from integer without a cast check_nt.c:227: warning: passing arg 2
> >>> of `memcpy' makes pointer from integer without a cast
> >>> check_nt.c:227: warning: passing arg 1 of `__strdup' makes pointer
> >>> from integer without a cast check_nt.c:237: warning: passing arg 1
> >>> of `strlen' makes pointer from integer without a cast
> >>> check_nt.c:237: warning: passing arg 2 of `memcpy' makes pointer
> >>> from integer without a cast check_nt.c:237: warning: passing arg 1
> >>> of `__strdup' makes pointer from integer without a cast
> >>> check_nt.c:276: warning: passing arg 1 of `strlen' makes pointer
> >>> from integer without a cast check_nt.c:276: warning: passing arg 2
> >>> of `memcpy' makes pointer from integer without a cast
> >>> check_nt.c:276: warning: passing arg 1 of `__strdup' makes pointer
> >>> from integer without a cast check_nt.c:312: warning: passing arg 1
> >>> of `strlen' makes pointer from integer without a cast
> >>> check_nt.c:312: warning: passing arg 2 of `memcpy' makes pointer
> >>> from integer without a cast check_nt.c:312: warning: passing arg 1
> >>> of `__strdup' makes pointer from integer without a cast
> >>> check_nt.c:342: warning: passing arg 1 of `usage' makes pointer
> >>> from integer without a cast check_nt.c: In function
> >>> `process_arguments':
> >>> check_nt.c:482: warning: passing arg 1 of `strlen' makes pointer
> >>> from integer without a cast check_nt.c:482: warning: passing arg 2
> >>> of `memcpy' makes pointer from integer without a cast
> >>> check_nt.c:482: warning: passing arg 1 of `__strdup' makes pointer
> >>> from integer without a cast check_nt.c: In function `fetch_data':
> >>> check_nt.c:495: warning: passing arg 1 of `process_tcp_request'
> >>> discards qualifiers from pointer target type
> >>> check_nt.c:495: warning: passing arg 3 of `process_tcp_request'
> >>> discards qualifiers from pointer target type
> >>> check_nt.c: In function `print_help':
> >>> check_nt.c:541: warning: passing arg 1 of `printf' makes pointer
> >>> from integer without a cast check_nt.c:565: warning: passing arg 1
> >>> of `printf' makes pointer from integer without a cast
> >>> check_nt.c:566: warning: passing arg 1 of `printf' makes pointer
> >>> from integer without a cast check_nt.c:569: warning: passing arg 1
> >>> of `printf' makes pointer from integer without a cast
> >>> check_nt.c:572: warning: passing arg 1 of `printf' makes pointer
> >>> from integer without a cast check_nt.c:579: warning: passing arg 1
> >>> of `printf' makes pointer from integer without a cast
> >>> check_nt.c:582: warning: passing arg 1 of `printf' makes pointer
> >>> from integer without a cast check_nt.c:586: warning: passing arg 1
> >>> of `printf' makes pointer from integer without a cast
> >>> check_nt.c:589: warning: passing arg 1 of `printf' makes pointer
> >>> from integer without a cast check_nt.c:595: warning: passing arg 1
> >>> of `printf' makes pointer from integer without a cast
> >>> check_nt.c:598: warning: passing arg 1 of `printf' makes pointer
> >>> from integer without a cast check_nt.c:607: warning: passing arg 1
> >>> of `printf' makes pointer from integer without a cast check_nt.c:
> >>> In function `print_usage':
> >>> check_nt.c:620: warning: passing arg 1 of `printf' makes pointer
> >>> from integer without a cast check_nt.c:623: error: `UT_HLP_VRS'
> >>> undeclared (first use in this function) check_nt.c:623: warning:
> >>> passing arg 1 of `printf' makes pointer from integer without a cast
> >>> make[2]: *** [check_nt.o] Error 1
> >>>
> >>> Any ideas?
> >>> ----- Original Message -----
> >>> From: Cook, Garry
> >>> To: Paulo Afonso Graner Fessel ;
> > per...@li...
> >>> Sent: Thursday, August 12, 2004 4:06 PM
> >>> Subject: RE: [Perfparse-users] Warn values are not going into
> >>> database
> >>>
> >>>
> >>> I'm not sure that I completely understand your question... What do
> >>> you mean by 'I'm not including all fields of performance data on
> >>> plugin output'?
> >>>
> >>> Plugin output of performance data should be in the format
> >>> 'label'=3Dvalue[UOM];[warn];[crit];[min];[max]
> >>> Please see
> >>> http://nagiosplug.sourceforge.net/developer-guidelines.html#AEN185
> >>> for detailed information.
> >>>
> >>> As you can see from the above, some of the variables are optional
> >>> (those enclosed in square brackets). If your performance data does
> >>> not supply the warning and critical values, they will not make it
> >>> into the database. Garry W. Cook, CCNA
> >>> Network Infrastructure Manager
> >>> MACTEC, Inc. - http://www.mactec.com/
> >>> 303.308.6228 (Office) - 720.220.1862 (Mobile)
> >>> -----Original Message-----
> >>> From: per...@li...
> >>> [mailto:per...@li...] On Behalf Of
> >>> Paulo Afonso Graner Fessel Sent: Wednesday, August 11, 2004 2:44 PM
> >>> To: per...@li...
> >>> Subject: [Perfparse-users] Warn values are not going into database
> >>>
> >>>
> >>> Hello, folks.
> >>>
> >>> We have noticed today that perfparse is not inserting the warning
> >>> values into perfdata_service_bin table, only the critical ones. So
> >>> it's impossible to graph threshold lines as warning values are
> >>> always "0".
> >>>
> >>> Does it happen because i'm not including all fields of performance
> >>> data on plugin output? Is it neccessary to include all fields of
> >>> performance values on plugin output?
> >>>
> >>> []'s
> >>> Paulo Fessel
> >>>
> >>> "This is not right. This is not even wrong." (Wolfgang Pauli)
> >>>
> >>> Paulo Fessel
> >>> Administrador de Ambiente e Sistemas UNIX PrimeSys Solu=E7=F5es
> >>> Empresariais Av. Brig. Faria Lima, 1485 - 13=B0 andar
> >>> Torre Norte - Pinheiros
> >>> 01451-904
> >>> S=E3o Paulo - SP
> >>> pau...@pr... tel:
> >>> fax:
> >>> mobile: +55 (11) 3038-6554
> >>> +55 (11) 3038-6508
> >>> +55 (11) 8259-0353
> >>>
> >>>
> >>>
> >>>
> >>> Signature powered by PlaxoWant a signature like this?
> >>>
> >>> Add me to your address book...