Menu
▾
▴
perfparse-users — Problems using PerfParse
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(12) |
Jun
(56) |
Jul
(68) |
Aug
(141) |
Sep
(82) |
Oct
(76) |
Nov
(115) |
Dec
(74) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(65) |
Feb
(113) |
Mar
(82) |
Apr
(37) |
May
(44) |
Jun
(22) |
Jul
(12) |
Aug
(3) |
Sep
(17) |
Oct
(11) |
Nov
(23) |
Dec
(1) |
| 2006 |
Jan
(1) |
Feb
(9) |
Mar
(6) |
Apr
(12) |
May
(10) |
Jun
(23) |
Jul
(1) |
Aug
(4) |
Sep
(3) |
Oct
(4) |
Nov
(6) |
Dec
(15) |
| 2007 |
Jan
(17) |
Feb
(14) |
Mar
(20) |
Apr
(7) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(5) |
Oct
(1) |
Nov
|
Dec
(2) |
| 2008 |
Jan
|
Feb
|
Mar
(2) |
Apr
(2) |
May
(6) |
Jun
(5) |
Jul
(13) |
Aug
(2) |
Sep
(16) |
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Sz Z <zsz...@pr...> - 2004-08-18 13:47:42
|
Hi Ben, Thank you for the fast reply. You're right.I'm dud. I made a mistake in the nagios.conf. I corrected that to xpdfile_service_perfdata_template=$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$OUTPUT$\t$SERVICESTATE$\t$PERFDATA$ and it seems resolved the problem. I've new records in the tables. Thanks, Zoli > -----Original Message----- > From: Ben Clewett [mailto:Be...@cl...] > Sent: Wednesday, August 18, 2004 3:15 PM > To: Sz Z > Subject: Re: [Perfparse-users] db insert problem > > > Sz Z, > > My second email on the subject. > > You are using Ping, which I believe currently does not provide any > performance data. (Garry may be able to confirm this for latest > plugins.) You will be unable to get any graphs for this data. > > You should be able to get raw data reports. However the data lines > should include the state (WARN,CRITICAL,OK,UNKNOWN) as the > last field of > the line (where no performance data). If this is not present, then > PerfParse will ignore or drop (?) this line. > > Can you check the format macro in nagios.cfg to ensure it matched that > of the HOWTO: > > xpdfile_service_perfdata_template=$TIMET$\t$HOSTNAME$\t$SERVIC > EDESC$\t$OUTPUT$\t$SERVICESTATE$\t$PERFDATA$ > > If you want latency reports from a server which ping should provide, > then the check_http plugin gives this, and produces good > performance data. > > Ben > > > > > Hi All, > > > > I've compiled and installed the latest release of perfparse > (0.99.08) in > > a gentoo box. I've created the table structure by mysql_create.sql. > > Nagios generate performace log into serviceperf.log and > hostperf.log. > > > > gentoo bin # cat /var/nagios/serviceperf.log > > 1092831013 fs PING PING OK - Packet loss = 0%, > RTA = 0.38 ms > > 1092831063 info_1175/u21 PING PING OK - Packet > loss = 0%, RTA > > = 116.02 ms > > 1092831083 info_1175/u5 PING PING OK - Packet > loss = 0%, RTA > > = 69.46 ms > > > > > > My problem is the follow: > > Perfparse insert nothing to mysql database. > > > > gentoo bin # ./perfparse -r > > Filename: /var/nagios/serviceperf.log > > File open at line 0 and ready to parse: > > > > +---------------------------+ +---------------------------+ > > | Time: 00:00:00 | | New Hosts: 0 | > > | Line in file: 0 | | New Services: 0 | > > | Lines Read: 0 | | New Metrics: 0 | > > | Rate: (line/sec) 0.00 | | Values Recorded: 0 | > > | Metric/line: 0.00 | | Lines Dropped: 0 | > > | SQL Queries: 30 | | Deleted Records: 0 | > > +---------------------------+ +---------------------------+ > > > > I've read the FAQ and mailing list archive too, but unfourtunately I > > wasn't able to find the solution. > > Can anybody help me? > > > > Thanks, > > Zoli > > > > > > > > ------------------------------------------------------- > > SF.Net email is sponsored by Shop4tech.com-Lowest price on > Blank Media > > 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 > > Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. > > http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 > > _______________________________________________ > > Perfparse-users mailing list > > Per...@li... > > https://lists.sourceforge.net/lists/listinfo/perfparse-users > > > > > > > > |
|
From: Yves M. <yme...@li...> - 2004-08-18 13:00:43
|
An idea: is mysql launched with networking enabled ? For example, there is an option "skip-networking" in my configuration fil= e that I have disabled. Is it enabled in your mysql config file ? Yves > Hi All, > > I've compiled and installed the latest release of perfparse (0.99.08) i= n > a gentoo box. I've created the table structure by mysql_create.sql. > Nagios generate performace log into serviceperf.log and hostperf.log. > > gentoo bin # cat /var/nagios/serviceperf.log > 1092831013 fs PING PING OK - Packet loss =3D 0%, RTA =3D 0= .38 ms > 1092831063 info_1175/u21 PING PING OK - Packet loss =3D 0%, R= TA > =3D 116.02 ms > 1092831083 info_1175/u5 PING PING OK - Packet loss =3D 0%, R= TA > =3D 69.46 ms > > > My problem is the follow: > Perfparse insert nothing to mysql database. > > gentoo bin # ./perfparse -r > Filename: /var/nagios/serviceperf.log > File open at line 0 and ready to parse: > > +---------------------------+ +---------------------------+ > | Time: 00:00:00 | | New Hosts: 0 | > | Line in file: 0 | | New Services: 0 | > | Lines Read: 0 | | New Metrics: 0 | > | Rate: (line/sec) 0.00 | | Values Recorded: 0 | > | Metric/line: 0.00 | | Lines Dropped: 0 | > | SQL Queries: 30 | | Deleted Records: 0 | > +---------------------------+ +---------------------------+ > > I've read the FAQ and mailing list archive too, but unfourtunately I > wasn't able to find the solution. > Can anybody help me? > > Thanks, > Zoli > > > > ------------------------------------------------------- > SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media > 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 > Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. > http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 > _______________________________________________ > Perfparse-users mailing list > Per...@li... > https://lists.sourceforge.net/lists/listinfo/perfparse-users > > --=20 - Homepage - http://ymettier.free.fr - http://www.logicacmg.com - - GPG key - http://ymettier.free.fr/gpg.txt - - Maitretarot - http://www.nongnu.org/maitretarot/ - - GTKtalog - http://www.nongnu.org/gtktalog/ - |
|
From: Sz Z <zsz...@pr...> - 2004-08-18 12:49:24
|
Hi All, I've compiled and installed the latest release of perfparse (0.99.08) in a gentoo box. I've created the table structure by mysql_create.sql. Nagios generate performace log into serviceperf.log and hostperf.log. gentoo bin # cat /var/nagios/serviceperf.log 1092831013 fs PING PING OK - Packet loss = 0%, RTA = 0.38 ms 1092831063 info_1175/u21 PING PING OK - Packet loss = 0%, RTA = 116.02 ms 1092831083 info_1175/u5 PING PING OK - Packet loss = 0%, RTA = 69.46 ms My problem is the follow: Perfparse insert nothing to mysql database. gentoo bin # ./perfparse -r Filename: /var/nagios/serviceperf.log File open at line 0 and ready to parse: +---------------------------+ +---------------------------+ | Time: 00:00:00 | | New Hosts: 0 | | Line in file: 0 | | New Services: 0 | | Lines Read: 0 | | New Metrics: 0 | | Rate: (line/sec) 0.00 | | Values Recorded: 0 | | Metric/line: 0.00 | | Lines Dropped: 0 | | SQL Queries: 30 | | Deleted Records: 0 | +---------------------------+ +---------------------------+ I've read the FAQ and mailing list archive too, but unfourtunately I wasn't able to find the solution. Can anybody help me? Thanks, Zoli |
|
From: Sz Z <zsz...@pr...> - 2004-08-18 12:48:42
|
confirm 862078 |
|
From: Ben C. <Be...@cl...> - 2004-08-17 23:09:40
|
Hi Philipp, Can you tell me which version you are now using? My guess is that you need to check the deletion policies through the CGI=20 interface. (Make sure you have set the permissions to view these, look=20 at the perfparse.cfg.example in the latest version.) This is the only=20 place where you define the length of time the data is stored. If you want to reset all your deletion policies to some good starting=20 value, there is an option in perfparse-db-tool to set this. Take a look=20 at the HOWTO for more information. The raw data in perfdata_service_raw is used to archive the raw output=20 from the plugins, both the state and the textual output. This has no=20 connection to the binary data used for the graph. If you want=20 historical information of the state returned by the plugins, this will=20 keep this. There is also a nice 'outage' report showing for each=20 service, how much time this has been in states OK, WARN, CRITICAL and=20 UNKNOWN. Hope this is of some use, Ben Sand Philipp wrote: > Hi, >=20 > I just tried out the perfparse_db_purge, and I don't know what I'm doin= g wrong, but I won't work properly...but without giving error messages... > I simply start it from the command-line e.g. with #./perfparse-db-purge= -n 1 > The the program seems to run and after a while it returns, that it has = deleted some million lines. Looks fine i think. > But when I commect to the Database, and do some selects on the perfdata= _host, or on the perfdata_service_raw, I got a lot of Data which is older= than this 1 day. > Which Data is deleted by the perfparse-db-purge tool?=20 > BTW, does perfdata needs the data in the perfdata_service_raw table, or= can it be deleted after perfparse got its bin-data? > Would be great if you guys could post somethng like which table got whi= ch functions, thanks! >=20 > Regards, > Philipp=20 > =20 >=20 > _____________________________ >=20 > Philipp Sand > OC-CC-TEC-SYS >=20 > SYCOR GmbH > Heinrich-von-Stephan-Stra=DFe 1-5 > D - 37073 G=F6ttingen >=20 > Telefon +49 (0) 551 / 490 - 0 > Telefax +49 (0) 551 / 490 - 232468 >=20 > phi...@sy... > www.sycor.de > ------------------------------------------------ >=20 >=20 >=20 > ************************************************ >=20 > sycor plastics - die neue Branchenl=F6sung f=FCr die Kunststoffindustri= e >=20 > www.sycor-plastics.de >=20 > ************************************************ >=20 >=20 >=20 >=20 > Diese E-Mail ist vertraulich und kann dar=FCber hinaus pers=F6nliche In= formationen beinhalten. Wenn Sie nicht der bestimmungsgem=E4=DFe Empf=E4n= ger sind, l=F6schen Sie bitte die E-Mail und deren Anh=E4nge sofort und b= enachrichtigen Sie uns dar=FCber. Die Firma sycor willigt in keine Vertr=E4= ge oder vertragliche Verpflichtungen ein oder =FCbermittelt rechtsverbind= liche Angebote, die in Form von E-Mail versandt werden, sofern dies nicht= ausdr=FCcklich in schriftlicher Form zwischen den Parteien vereinbart wu= rde. >=20 > This e-mail is confidential and may contain personal and/or privileged = information. If you are not the intended recipient please delete this e-m= ail and all attachments immediately and inform us. The company sycor does= not agree with contracts or contract obligations sent by e-mail, neither= do we transmit legally binding offers by e-mail, unless this is not expr= essly agreed upon between the parties and documented in written form. >=20 >=20 >=20 > ------------------------------------------------------- > SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media > 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 > Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. > http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 > _______________________________________________ > Perfparse-users mailing list > Per...@li... > https://lists.sourceforge.net/lists/listinfo/perfparse-users >=20 |
|
From: Cook, G. <GW...@ma...> - 2004-08-17 23:01:03
|
Thanks Jaap. I've added these to the list on the PP web site. However, I'm considering removing check_fping. I'm looking at the check_fping from last Thursday's CVS, and while perfdata does appear to be included, it does not seem to work. Do you (or anyone else on the list) actually have check_fping working and returning perfdata? If so, can you send me an example of the command that you used to get it to work properly? Did you need to change the code at all to get it working, and if so can you send me a patch? Thanks again. Garry W. Cook, CCNA Network Infrastructure Manager MACTEC, Inc. - http://www.mactec.com/ 303.308.6228 (Office) - 720.220.1862 (Mobile)=20 Jaap Hogenberg wrote: > Garry, >=20 > check_fping > check_dns >=20 > both have performance data. >=20 > Regards, > jaap >=20 >=20 > On Tue, 2004-08-17 at 08:48, Cook, Garry wrote: >> I've updated the PerfParse website (http://perfparse.sf.net/) with >> information regarding plugins. >> There is now a short list that shows plugins which support >> performance data, as well as some patches that I've created to add >> perfdata to plugins that do not yet support it. >>=20 >> If any of you have some spare time, please take a look at this and >> let me know of any plugins that you are aware of that support >> perfdata but are not listed. It would be best to email me here on >> the list, rather than the email address on the site, as I only check >> that about once a week.=20 >>=20 >> If any of you have added perfdata to plugins source code, please let >> me know and I'll be happy to post your patches on the site. >>=20 >> Thanks! >>=20 >> Garry W. Cook, CCNA >> Network Infrastructure Manager >> MACTEC, Inc. - http://www.mactec.com/ >> 303.308.6228 (Office) - 720.220.1862 (Mobile) |
|
From: Cook, G. <GW...@ma...> - 2004-08-17 22:49:01
|
Jon, From looking at the bottom of this thread, it appears as though you did get the correct file. However, I have made changes to further improve the performance data output of check_nt since that first post. Please grab the check_nt.c.patch from the Plugins section of the PerfParse web site (http://perfparse.sf.net/). Once you have the patch, you should apply it to check_nt.c in the Nagios plugins source directory. You should be using at least version 1.4.0alpha plugins, if not the latest CVS. If you need help applying the patch, see the manuals for patch and possibly diff ('man patch' & 'man diff'). Once you've applied the patch to check_nt.c, you should recompile your plugins source using the 'configure' and 'make' commands. Then you can either 'make install' to reinstall all plugins, or simply copy the compiled check_nt binary to your nagios plugins directory (usually /usr/local/nagios/libexec/). -g Jon Lyons wrote: > Garry, I tried the check_nt plugin, however it doesn't > report the performace info..Did I get the right file?? >=20 >=20 > nagios# ./check_nt -H 10.4.1.115 -v MEMUSE -w 10 -c 50 > Memory usage: total:1983.00 Mb - used: 89.27 Mb (5%) - free: 1893.73 > Mb (95%) nagios# ./check_nt -H 10.4.1.115 -p1248 -v CPULOAD -l > 10,80,95,60,80,95,1440,80,95 CPU Load 0% (10 min average) 0% (60 min > average) 0% (1440 min average) nagios# ./check_nt -H 10.4.1.115 -v > MEMUSE -w 10 -c 50 Memory usage: total:1983.00 Mb - used: 89.21 Mb > (4%) - free: 1893.79 Mb (96%) nagios# >=20 >=20 >=20 > --- "Cook, Garry" <GW...@ma...> wrote: >=20 >> First off, I'm sorry for the cross-post, there were several people >> interested in this on different lists. If you're on a list that does >> not allow attachments, contact me off-list and I'll send you a copy >> of the plugin source. >>=20 >> I've added Performance Data to the check_nt plugin >> distributed with >> NSClient and Nagios plugins. A copy of the source is attached, please >> feel free to compile and test (don't forget to >> backup your original >> check_nt plugin). >>=20 >> I'm not a master coder, just a hacker, but I was >> able to make it work >> well for my implementation. >> With that said, if anyone has any problems with it, please let me >> know. But keep in mind that I don't have a lot of >> different systems to compile >> on, so I may not be able to fix it for you. >>=20 >> I've commented the code pretty well, so it should be readily apparent >> where things have been added by me. I have not >> changed the revision >> number, so I'll probably submit this as a patch >> after I have some >> feedback from people. I'm guessing that I should >> submit it to both >> Nagios Plugins devel as well as the NSClient >> developers. If any of you >> reading this are developers of NSClient, please >> contact me off-list and >> I'll be happy to submit this in whatever format your require. >>=20 >> Some notes on this updated plugin: >>=20 >> If checking a windows COUNTER, a definition is >> required in order to >> generate perfdata. >> The definition is usually optional. >>=20 >> The following checks return performance data: >> CPULOAD >> USEDDISKSPACE >> MEMUSE >> COUNTER >>=20 >> The following checks do NOT return performance data: CLIENTVERSION >> UPTIME >> SERVICESTATE >> PROCSTATE >>=20 >> I didn't see a need for, nor an easy way to add, >> performance data for >> the CLIENTVERSION, UPTIME, SERVICESTATE, & PROCSTATE checks. If you >> disagree with my assessment of the need for perfdata with any of >> these, please let me know and maybe I'll try to add that as well. >>=20 >> I have also changed the code for the MEMUSE check, >> as it did not appear >> to give the proper output originally. Please let me know if I've >> borked this somehow, although on my systems it shows output that >> looks good. Alternatively, just look at the code. I've >> documented the change and >> anyone that can compile and install Nagios should >> easily be able to >> change it back and recompile the plugin. >>=20 >> Garry W. Cook, CCNA >> Network Infrastructure Manager >> MACTEC, Inc. - http://www.mactec.com/ >> 303.308.6228 (Office) - 720.220.1862 (Mobile) >>=20 >=20 >> ATTACHMENT part 2 application/octet-stream name=3Dcheck_nt.c Garry W. Cook, CCNA Network Infrastructure Manager MACTEC, Inc. - http://www.mactec.com/ 303.308.6228 (Office) - 720.220.1862 (Mobile) |
|
From: Yves M. <yme...@li...> - 2004-08-17 18:12:12
|
Back from holidays, but many things to do like always after coming back := ) So I answer quick and short. You talk about perfparse-db-purge, so you have a perfparse version higher= than 0.99.03. I don't remember any bug in that tool after 0.99.03. But please tell us w= hat version you are using. > Hi, > > I just tried out the perfparse_db_purge, and I don't know what I'm doin= g wrong, but I > won't work properly...but without giving error messages... > I simply start it from the command-line e.g. with #./perfparse-db-purge= -n 1 > The the program seems to run and after a while it returns, that it has = deleted some > million lines. Looks fine i think. > But when I commect to the Database, and do some selects on the perfdata= _host, or on the > perfdata_service_raw, I got a lot of Data which is older than this 1 da= y. There is something strange. In my version, perfparse-db-purge does not recognize -n option. So no old= data was removed. Use --del-old 1 instead of -n 1 if you want to remove old lines = with 0.99.08. Why did it take so much time ? Because there is a feature that is already= implemented in perfparse-db-purge, but not yet in the CGI. There is a record "is_deleted= " in some tables. They are set as 0. If you set it at 1, it will be purged when run= ning perfparse-db-purge (and all related data, like binary data and raw data i= f you remove a host). This takes some time. > Which Data is deleted by the perfparse-db-purge tool? 1/ some data when there is is_deleted set to 1 2/ old data, older than what you specify to --del-old. > BTW, does perfdata needs the data in the perfdata_service_raw table, or= can it be > deleted after perfparse got its bin-data? Raw data contain the return of the plugin (the message, the state...) Bin data contain the perf data, after the | character in the plugin messa= ge They are independant. Remove what you like. Of course, do it at your own risks, we are not responsible for... :) > Would be great if you guys could post somethng like which table got whi= ch functions, > thanks! Better if there is some document somewhere. Yves > > Regards, > Philipp > > > _____________________________ > > Philipp Sand > OC-CC-TEC-SYS > > SYCOR GmbH > Heinrich-von-Stephan-Stra=DFe 1-5 > D - 37073 G=F6ttingen > > Telefon +49 (0) 551 / 490 - 0 > Telefax +49 (0) 551 / 490 - 232468 > > phi...@sy... > www.sycor.de > ------------------------------------------------ > > > > ************************************************ > > sycor plastics - die neue Branchenl=F6sung f=FCr die Kunststoffindustri= e > > www.sycor-plastics.de > > ************************************************ > > > > > Diese E-Mail ist vertraulich und kann dar=FCber hinaus pers=F6nliche In= formationen > beinhalten. Wenn Sie nicht der bestimmungsgem=E4=DFe Empf=E4nger sind, = l=F6schen Sie bitte die > E-Mail und deren Anh=E4nge sofort und benachrichtigen Sie uns dar=FCber= . Die Firma sycor > willigt in keine Vertr=E4ge oder vertragliche Verpflichtungen ein oder = =FCbermittelt > rechtsverbindliche Angebote, die in Form von E-Mail versandt werden, so= fern dies nicht > ausdr=FCcklich in schriftlicher Form zwischen den Parteien vereinbart w= urde. > > This e-mail is confidential and may contain personal and/or privileged = information. If > you are not the intended recipient please delete this e-mail and all at= tachments > immediately and inform us. The company sycor does not agree with contra= cts or contract > obligations sent by e-mail, neither do we transmit legally binding offe= rs by e-mail, > unless this is not expressly agreed upon between the parties and docume= nted in written > form. > > > > ------------------------------------------------------- > SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media > 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 > Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. > http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 > _______________________________________________ > Perfparse-users mailing list > Per...@li... > https://lists.sourceforge.net/lists/listinfo/perfparse-users > > --=20 - Homepage - http://ymettier.free.fr - http://www.logicacmg.com - - GPG key - http://ymettier.free.fr/gpg.txt - - Maitretarot - http://www.nongnu.org/maitretarot/ - - GTKtalog - http://www.nongnu.org/gtktalog/ - |
|
From: Cook, G. <GW...@ma...> - 2004-08-17 14:41:50
|
OK, I'm going to leave it on the list. As you can see from my output below, it does not work on my system. I'm not sure why I'm getting a WARNING, as the output is lacking anything other than the status and the IP address. Since check_icmp is based upon check_fping, and works for me, I will continue to use it instead. However, for those users that do wish to use check_fping, it appears as though it should work properly based on your feedback. Thanks! $/usr/local/src/nagios/nagios-plugins-HEAD-200408121647/plugins/check_fp ing 10.1.190.1 -w 2,10% -c 3,30% FPING WARNING - 10.1.190.1 $/usr/local/src/nagios/nagios-plugins-HEAD-200408121647/plugins/check_fp ing -H 10.1.190.1 -w 2,10% -c 3,30% FPING WARNING - 10.1.190.1 $/usr/local/src/nagios/nagios-plugins-1.4.0alpha1/plugins/check_fping -H 10.1.190.1 -w 2,10% -c 3,30%=20 FPING WARNING - 10.1.190.1 $/usr/local/src/nagios/nagios-plugins-1.4.0alpha1/plugins/check_fping -H 10.1.45.1 -w 2,10% -c 3,30% =20 FPING WARNING - 10.1.45.1 Garry W. Cook, CCNA Network Infrastructure Manager MACTEC, Inc. - http://www.mactec.com/ 303.308.6228 (Office) - 720.220.1862 (Mobile) Jaap Hogenberg wrote: > Garry, >=20 > It works for me without modification from the 1.4 alpha plugins: >=20 > nagios@gilmore:~/nagios-plugins-1.4.0alpha1/plugins$ ./check_fping -V > check_fping (nagios-plugins 1.4.0alpha1) 1.11 > nagios@gilmore:~/nagios-plugins-1.4.0alpha1/plugins$ ./check_fping -H > 10.1.5.17 -w 2,10% -c 3,30% > FPING OK - 10.1.5.17 (loss=3D0%, rta=3D19.900000 = ms)|loss=3D0%;10;30;0;100 > rta=3D19899us;2000000;3000000;0=20 >=20 > I also had a newer version from cvs , about 2 weeks ago I think: >=20 > nagios@gilmore:/opt/nagios/plugins$ ./check_fping -V > check_fping (nagios-plugins 1.4.0alpha2) 1.13 > nagios@gilmore:/opt/nagios/plugins$ ./check_fping -H > 10.1.5.17 -w 20,10% > -c 30,30% > FPING OK - 10.1.5.17 (loss=3D0%, rta=3D12.100000 = ms)|loss=3D0%;10;30;0;100 > rta=3D0.012100s;0.020000;0.030000;0.000000 >=20 > Both work without modifications althoug one expects the tresholds in > seconds,the other wants ms. The perfdata has different units too. >=20 > Just checked out the latest cvs, check_fping is at version 1.13 >=20 > Hope this explains. I do think the built in help with check_fping > is a bit vaque w.r.t. the format and unit of the treshold parameters. >=20 > Jaap >=20 >=20 > On Tue, 2004-08-17 at 15:52, Cook, Garry wrote: >> Thanks Jaap. I've added these to the list on the PP web site. >> However, I'm considering removing check_fping. I'm looking at the >> check_fping from last Thursday's CVS, and while perfdata does appear >> to be included, it does not seem to work. Do you (or anyone else on >> the list) actually have check_fping working and returning perfdata? >> If so, can you send me an example of the command that you used to >> get it to work properly? Did you need to change the code at all to >> get it working, and if so can you send me a patch? Thanks again. >>=20 >> Garry W. Cook, CCNA >> Network Infrastructure Manager >> MACTEC, Inc. - http://www.mactec.com/ >> 303.308.6228 (Office) - 720.220.1862 (Mobile) >>=20 >> Jaap Hogenberg wrote: >>> Garry, >>>=20 >>> check_fping >>> check_dns >>>=20 >>> both have performance data. >>>=20 >>> Regards, >>> jaap >>>=20 >>>=20 >>> On Tue, 2004-08-17 at 08:48, Cook, Garry wrote: >>>> I've updated the PerfParse website > (http://perfparse.sf.net/) with >>>> information regarding plugins. >>>> There is now a short list that shows plugins which support >>>> performance data, as well as some patches that I've created to add >>>> perfdata to plugins that do not yet support it. >>>>=20 >>>> If any of you have some spare time, please take a look at this and >>>> let me know of any plugins that you are aware of that support >>>> perfdata but are not listed. It would be best to email me here on >>>> the list, rather than the email address on the site, as I only >>>> check that about once a week.=20 >>>>=20 >>>> If any of you have added perfdata to plugins source code, please >>>> let me know and I'll be happy to post your patches on the site. >>>>=20 >>>> Thanks! >>>>=20 >>>> Garry W. Cook, CCNA >>>> Network Infrastructure Manager >>>> MACTEC, Inc. - http://www.mactec.com/ >>>> 303.308.6228 (Office) - 720.220.1862 (Mobile) |
|
From: Sand P. <Phi...@sy...> - 2004-08-17 11:00:30
|
Hi Ben, I'm currently using the latest perfparse version 0.99.08. Together with N= agios 2.0a1 on Fedora Core 2. The deletion policy in the cgi where set to the default values for raw an= d binary data. Which had been 30days before I changed this just a moment = ago :) I thought, that when I use the -n option with the purgetool the deletion = ploicy is overwritten... Though after running the purgetool I still had host definitions in there = which where definitly older than 30 days. Plus after running the purgetool it said, that it deleted a few million l= ines, but when I wanted to check my diskspace with df, nothing changed...= Here's my perfparse.cfg: # Database Authentication DB_User =3D "nagios" DB_Name =3D "nagios" DB_Pass =3D "XXXXXXXXXXX" DB_Host =3D "127.0.0.1" # Performance Data Log Files: Delete_Service_Log =3D "no" Service_Log =3D "/usr/local/nagios/var/serviceperf.log" Delete_Host_Log =3D "No" Host_Log =3D "/usr/local/nagios/var/hostperf.log" # Drop file for lines of log rejected: Drop_File =3D "/tmp/perfparse.drop" # Nagios file containing its PID (Necessary to delete log files) Nagios_Lock =3D "/usr/local/nagios/var/nagios.lock" # Reporting options: # Do not display completion status of perfparse: Be_Silent =3D "no" # Display a report on exit of perfparse: Do_Report =3D "yes" # Lock file for only one perfparse running at the same time Lock_File =3D "/var/lock/perfparse.lock" # misc Dummy_Hostname =3D "dummy" Accept_Odd_Chars_in_Label =3D "no" # Default user permissions in the CGI. Accepted values are (ro|rw|hide) Default_user_permissions_Policy =3D "rw" Default_user_permissions_Host_groups =3D "rw" Regards, Philipp > -----Original Message----- > From: Ben Clewett [mailto:Be...@cl...]=20 > Sent: Tuesday, August 17, 2004 11:33 AM > To: Sand Philipp > Cc: per...@li... > Subject: Re: [Perfparse-users] (no subject) >=20 > Hi Philipp, >=20 > Can you tell me which version you are now using? >=20 > My guess is that you need to check the deletion policies=20 > through the CGI interface. (Make sure you have set the=20 > permissions to view these, look at the perfparse.cfg.example=20 > in the latest version.) This is the only place where you=20 > define the length of time the data is stored. >=20 > If you want to reset all your deletion policies to some good=20 > starting value, there is an option in perfparse-db-tool to=20 > set this. Take a look at the HOWTO for more information. >=20 > The raw data in perfdata_service_raw is used to archive the=20 > raw output from the plugins, both the state and the textual=20 > output. This has no connection to the binary data used for=20 > the graph. If you want historical information of the state=20 > returned by the plugins, this will keep this. There is also=20 > a nice 'outage' report showing for each service, how much=20 > time this has been in states OK, WARN, CRITICAL and UNKNOWN. >=20 > Hope this is of some use, >=20 > Ben >=20 >=20 > Sand Philipp wrote: >=20 > > Hi, > >=20 > > I just tried out the perfparse_db_purge, and I don't know=20 > what I'm doing wrong, but I won't work properly...but without=20 > giving error messages... > > I simply start it from the command-line e.g. with=20 > > #./perfparse-db-purge -n 1 The the program seems to run and=20 > after a while it returns, that it has deleted some million=20 > lines. Looks fine i think. > > But when I commect to the Database, and do some selects on=20 > the perfdata_host, or on the perfdata_service_raw, I got a=20 > lot of Data which is older than this 1 day. > > Which Data is deleted by the perfparse-db-purge tool?=20 > > BTW, does perfdata needs the data in the=20 > perfdata_service_raw table, or can it be deleted after=20 > perfparse got its bin-data? > > Would be great if you guys could post somethng like which=20 > table got which functions, thanks! > >=20 > > Regards, > > Philipp > > =20 > >=20 > > _____________________________ > >=20 > > Philipp Sand > > OC-CC-TEC-SYS > >=20 > > SYCOR GmbH > > Heinrich-von-Stephan-Stra=DFe 1-5 > > D - 37073 G=F6ttingen > >=20 > > Telefon +49 (0) 551 / 490 - 0 > > Telefax +49 (0) 551 / 490 - 232468 > >=20 > > phi...@sy... > > www.sycor.de > > ------------------------------------------------ > >=20 > >=20 > >=20 > > ************************************************ > >=20 > > sycor plastics - die neue Branchenl=F6sung f=FCr die Kunststoffindust= rie > >=20 > > www.sycor-plastics.de > >=20 > > ************************************************ > >=20 > >=20 > >=20 > >=20 > > Diese E-Mail ist vertraulich und kann dar=FCber hinaus=20 > pers=F6nliche Informationen beinhalten. Wenn Sie nicht der=20 > bestimmungsgem=E4=DFe Empf=E4nger sind, l=F6schen Sie bitte die=20 > E-Mail und deren Anh=E4nge sofort und benachrichtigen Sie uns=20 > dar=FCber. Die Firma sycor willigt in keine Vertr=E4ge oder=20 > vertragliche Verpflichtungen ein oder =FCbermittelt=20 > rechtsverbindliche Angebote, die in Form von E-Mail versandt=20 > werden, sofern dies nicht ausdr=FCcklich in schriftlicher Form=20 > zwischen den Parteien vereinbart wurde. > >=20 > > This e-mail is confidential and may contain personal and/or=20 > privileged information. If you are not the intended recipient=20 > please delete this e-mail and all attachments immediately and=20 > inform us. The company sycor does not agree with contracts or=20 > contract obligations sent by e-mail, neither do we transmit=20 > legally binding offers by e-mail, unless this is not=20 > expressly agreed upon between the parties and documented in=20 > written form. > >=20 > >=20 > >=20 > > ------------------------------------------------------- > > SF.Net email is sponsored by Shop4tech.com-Lowest price on=20 > Blank Media=20 > > 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for=20 > only $33 Save=20 > > 50% off Retail on Ink & Toner - Free Shipping and Free Gift. > > http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 > > _______________________________________________ > > Perfparse-users mailing list > > Per...@li... > > https://lists.sourceforge.net/lists/listinfo/perfparse-users > >=20 >=20 >=20 ************************************************ sycor plastics - die neue Branchenl=F6sung f=FCr die Kunststoffindustrie www.sycor-plastics.de ************************************************ Diese E-Mail ist vertraulich und kann dar=FCber hinaus pers=F6nliche Info= rmationen beinhalten. Wenn Sie nicht der bestimmungsgem=E4=DFe Empf=E4nge= r sind, l=F6schen Sie bitte die E-Mail und deren Anh=E4nge sofort und ben= achrichtigen Sie uns dar=FCber. Die Firma sycor willigt in keine Vertr=E4= ge oder vertragliche Verpflichtungen ein oder =FCbermittelt rechtsverbind= liche Angebote, die in Form von E-Mail versandt werden, sofern dies nicht= ausdr=FCcklich in schriftlicher Form zwischen den Parteien vereinbart wu= rde. This e-mail is confidential and may contain personal and/or privileged in= formation. If you are not the intended recipient please delete this e-mai= l and all attachments immediately and inform us. The company sycor does n= ot agree with contracts or contract obligations sent by e-mail, neither d= o we transmit legally binding offers by e-mail, unless this is not expres= sly agreed upon between the parties and documented in written form. |
|
From: Yves M. <yme...@li...> - 2004-08-17 10:49:38
|
Back from holidays, and a lot to do here... Some questions anyway: - is that 0.99.07 ? Do you have those problems with 0.99.08 (or better: 0= .99.08ym3 at http://ymettier.chez.tiscali.fr/perfparse-devel/index.php) - what compiler do you use ? gcc ? I ask this question because I have nev= er seen some of the warning messages. But there is a beginning for anything :) - are you using GNU make ? On a Linux box, the answer is probably yes. On= some other systems, "make -v" can answer. If you are not using GNU make, test if gma= ke (this is GNU make) exist. This question is interesting because if this is the prob= lem, we will have a discussion about supporting only GNU make or not. - are you using the root account to compile ? You should not. Using the r= oot account is dangerous and only "make install" should be done with root permissions. G= ood system administrators also do "make -n install" before and check what will be do= ne. Well, this is not the solution of your problem, but I saw the "#" character at the e= nd that usually mean root ! :) Yves > Is there a deubg option that may give me more > information on solving my compling issue? Not really > sure what the error is...(happends on all versions > since.11 on freebsd 4.10/4.9) > > cgi_intro.c: In function `displayIntro': > cgi_intro.c:48: warning: use of `l' length character > with `f' type character > source=3D'cgi_raw_report.c' > object=3D'perfgraph_cgi-cgi_raw_report.o' libtool=3Dno > depfile=3D'.deps/perfgraph_cgi-cgi_raw_report.Po' > tmpdepfile=3D'.deps/perfgraph_cgi-cgi_raw_report.TPo' > depmode=3Dgcc /bin/sh ../depcomp gcc -DHAVE_CONFIG_H > -I. -I. -I.. -I/usr/local/include/mysql -O -pipe > -D_THREAD_SAFE -I/usr/local/include/glib-2.0 > -I/usr/local/lib/glib-2.0/include -I../libperfparse > '-DSYSCONFDIR=3D"/usr/local/etc"' -g -O2 -Wall -c -o > perfgraph_cgi-cgi_raw_report.o `test -f > 'cgi_raw_report.c' || echo './'`cgi_raw_report.c > cgi_raw_report.c: In function `displayRawHistory': > cgi_raw_report.c:49: syntax error before `int' > cgi_raw_report.c:208: `iStates' undeclared (first use > in this function) > cgi_raw_report.c:208: (Each undeclared identifier is > reported only once > cgi_raw_report.c:208: for each function it appears > in.) > cgi_raw_report.c:310: warning: use of `l' length > character with `f' type character > *** Error code 1 > > Stop in /tmp/perfparse-0.99.07/cgi. > *** Error code 1 > > Stop in /tmp/perfparse-0.99.07. > *** Error code 1 > > Stop in /tmp/perfparse-0.99.07. > stats# ll /usr/local/include/mysql/ > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > > ------------------------------------------------------- > SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media > 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 > Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. > http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 > _______________________________________________ > Perfparse-users mailing list > Per...@li... > https://lists.sourceforge.net/lists/listinfo/perfparse-users > > --=20 - Homepage - http://ymettier.free.fr - http://www.logicacmg.com - - GPG key - http://ymettier.free.fr/gpg.txt - - Maitretarot - http://www.nongnu.org/maitretarot/ - - GTKtalog - http://www.nongnu.org/gtktalog/ - |
|
From: Sand P. <Phi...@sy...> - 2004-08-17 09:18:44
|
Hi, I just tried out the perfparse_db_purge, and I don't know what I'm doing = wrong, but I won't work properly...but without giving error messages... I simply start it from the command-line e.g. with #./perfparse-db-purge -= n 1 The the program seems to run and after a while it returns, that it has de= leted some million lines. Looks fine i think. But when I commect to the Database, and do some selects on the perfdata_h= ost, or on the perfdata_service_raw, I got a lot of Data which is older t= han this 1 day. Which Data is deleted by the perfparse-db-purge tool?=20 BTW, does perfdata needs the data in the perfdata_service_raw table, or c= an it be deleted after perfparse got its bin-data? Would be great if you guys could post somethng like which table got which= functions, thanks! Regards, Philipp=20 =20 _____________________________ Philipp Sand OC-CC-TEC-SYS SYCOR GmbH Heinrich-von-Stephan-Stra=DFe 1-5 D - 37073 G=F6ttingen Telefon +49 (0) 551 / 490 - 0 Telefax +49 (0) 551 / 490 - 232468 phi...@sy... www.sycor.de ------------------------------------------------ ************************************************ sycor plastics - die neue Branchenl=F6sung f=FCr die Kunststoffindustrie www.sycor-plastics.de ************************************************ Diese E-Mail ist vertraulich und kann dar=FCber hinaus pers=F6nliche Info= rmationen beinhalten. Wenn Sie nicht der bestimmungsgem=E4=DFe Empf=E4nge= r sind, l=F6schen Sie bitte die E-Mail und deren Anh=E4nge sofort und ben= achrichtigen Sie uns dar=FCber. Die Firma sycor willigt in keine Vertr=E4= ge oder vertragliche Verpflichtungen ein oder =FCbermittelt rechtsverbind= liche Angebote, die in Form von E-Mail versandt werden, sofern dies nicht= ausdr=FCcklich in schriftlicher Form zwischen den Parteien vereinbart wu= rde. This e-mail is confidential and may contain personal and/or privileged in= formation. If you are not the intended recipient please delete this e-mai= l and all attachments immediately and inform us. The company sycor does n= ot agree with contracts or contract obligations sent by e-mail, neither d= o we transmit legally binding offers by e-mail, unless this is not expres= sly agreed upon between the parties and documented in written form. |
|
From: Cook, G. <GW...@ma...> - 2004-08-17 06:51:39
|
I've updated the PerfParse website (http://perfparse.sf.net/) with information regarding plugins. There is now a short list that shows plugins which support performance data, as well as some patches that I've created to add perfdata to plugins that do not yet support it. If any of you have some spare time, please take a look at this and let me know of any plugins that you are aware of that support perfdata but are not listed. It would be best to email me here on the list, rather than the email address on the site, as I only check that about once a week. If any of you have added perfdata to plugins source code, please let me know and I'll be happy to post your patches on the site. Thanks! Garry W. Cook, CCNA Network Infrastructure Manager MACTEC, Inc. - http://www.mactec.com/ 303.308.6228 (Office) - 720.220.1862 (Mobile)=20 |
|
From: Cook, G. <GW...@ma...> - 2004-08-17 04:05:52
|
'man make' shows that there is indeed a debug option available.
From the make manual:
-d Print debugging information in addition to normal processing. The
debugging information says which files are being
considered for
remaking, which file-times are being compared and with
what
results, which files actually need to be remade, which
implicit
rules are considered and which are applied---everything
interest-
ing about how make decides what to do.
Hopefully this will help you. If not, Ben and Yves are both back from
vacation now, perhaps they can spot the error...
Guys?=20
Garry W. Cook, CCNA
Network Infrastructure Manager
MACTEC, Inc. - http://www.mactec.com/
303.308.6228 (Office) - 720.220.1862 (Mobile)
per...@li... wrote:
> Is there a deubg option that may give me more
> information on solving my compling issue? Not really
> sure what the error is...(happends on all versions
> since.11 on freebsd 4.10/4.9)
>=20
> cgi_intro.c: In function `displayIntro':
> cgi_intro.c:48: warning: use of `l' length character
> with `f' type character
> source=3D'cgi_raw_report.c'
> object=3D'perfgraph_cgi-cgi_raw_report.o' libtool=3Dno
> depfile=3D'.deps/perfgraph_cgi-cgi_raw_report.Po'
> tmpdepfile=3D'.deps/perfgraph_cgi-cgi_raw_report.TPo'
> depmode=3Dgcc /bin/sh ../depcomp gcc -DHAVE_CONFIG_H
> -I. -I. -I.. -I/usr/local/include/mysql -O -pipe
> -D_THREAD_SAFE -I/usr/local/include/glib-2.0
> -I/usr/local/lib/glib-2.0/include -I../libperfparse
> '-DSYSCONFDIR=3D"/usr/local/etc"' -g -O2 -Wall -c -o
> perfgraph_cgi-cgi_raw_report.o `test -f
> 'cgi_raw_report.c' || echo './'`cgi_raw_report.c
> cgi_raw_report.c: In function `displayRawHistory':
> cgi_raw_report.c:49: syntax error before `int'
> cgi_raw_report.c:208: `iStates' undeclared (first use
> in this function)
> cgi_raw_report.c:208: (Each undeclared identifier is
> reported only once
> cgi_raw_report.c:208: for each function it appears
> in.)
> cgi_raw_report.c:310: warning: use of `l' length
> character with `f' type character
> *** Error code 1
>=20
> Stop in /tmp/perfparse-0.99.07/cgi.
> *** Error code 1
>=20
> Stop in /tmp/perfparse-0.99.07.
> *** Error code 1
>=20
> Stop in /tmp/perfparse-0.99.07.
> stats# ll /usr/local/include/mysql/
|
|
From: Jon L. <jly...@ya...> - 2004-08-16 21:29:00
|
Is there a deubg option that may give me more information on solving my compling issue? Not really sure what the error is...(happends on all versions since.11 on freebsd 4.10/4.9) cgi_intro.c: In function `displayIntro': cgi_intro.c:48: warning: use of `l' length character with `f' type character source='cgi_raw_report.c' object='perfgraph_cgi-cgi_raw_report.o' libtool=no depfile='.deps/perfgraph_cgi-cgi_raw_report.Po' tmpdepfile='.deps/perfgraph_cgi-cgi_raw_report.TPo' depmode=gcc /bin/sh ../depcomp gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/include/mysql -O -pipe -D_THREAD_SAFE -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I../libperfparse '-DSYSCONFDIR="/usr/local/etc"' -g -O2 -Wall -c -o perfgraph_cgi-cgi_raw_report.o `test -f 'cgi_raw_report.c' || echo './'`cgi_raw_report.c cgi_raw_report.c: In function `displayRawHistory': cgi_raw_report.c:49: syntax error before `int' cgi_raw_report.c:208: `iStates' undeclared (first use in this function) cgi_raw_report.c:208: (Each undeclared identifier is reported only once cgi_raw_report.c:208: for each function it appears in.) cgi_raw_report.c:310: warning: use of `l' length character with `f' type character *** Error code 1 Stop in /tmp/perfparse-0.99.07/cgi. *** Error code 1 Stop in /tmp/perfparse-0.99.07. *** Error code 1 Stop in /tmp/perfparse-0.99.07. stats# ll /usr/local/include/mysql/ __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: Cook, G. <GW...@ma...> - 2004-08-16 18:21:10
|
I recently distributed check_nt source code and/or a patch to serveral of you. This was intended to add perfdata to the check_nt plugin, which it did. Unfortunately, the USEDDISKSPACE and MEMUSE checks did not output the perfdata correctly, which I did not realize until I fixed the warn/crit PerfParse bug that Ben Clewett found (PerfParse thread =3D = RES: [Perfparse-users] Warn values are not going into database). I've managed to correct my original code, after much pain due to not realizing that 'int / int !=3D float'. Attached is a patch for check_nt.c, which should be applied to the ORIGINAL check_nt.c from the Nagios Plugins version 1.4.0alpha. Enjoy! Garry W. Cook, CCNA Network Infrastructure Manager MACTEC, Inc. - http://www.mactec.com/ 303.308.6228 (Office) - 720.220.1862 (Mobile)=20 |
|
From: Cook, G. <GW...@ma...> - 2004-08-16 12:39:02
|
Barry Weeks wrote: > Hi people >=20 > I wonder if anyone has had any thoughts regarding the compile > error I am > seeing while trying to compile the check_nt plugin with the > perf data hack. > Heres my errors >=20 > Thanks >=20 > #Making all in lib > make[1]: Entering directory > `/usr/local/src/nagios-plugins/nagios-plugins-1.3.1/lib' > make[1]: Nothing to be done for `all'. > make[1]: Leaving directory [snip] Can you download the latest version of the plugins and try compiling the check_nt.c code with those, instead of the old v1.3.1? I would recommend using at least v1.4.0alpha, if not the latest version from CVS. Garry W. Cook, CCNA Network Infrastructure Manager MACTEC, Inc. - http://www.mactec.com/ 303.308.6228 (Office) - 720.220.1862 (Mobile) |
|
From: Barry W. <ba...@if...> - 2004-08-16 09:07:43
|
Hi people I wonder if anyone has had any thoughts regarding the compile error I am seeing while trying to compile the check_nt plugin with the perf data hack. Heres my errors Thanks #Making all in lib make[1]: Entering directory `/usr/local/src/nagios-plugins/nagios-plugins-1.3.1/lib' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/usr/local/src/nagios-plugins/nagios-plugins-1.3.1/lib' Making all in plugins make[1]: Entering directory `/usr/local/src/nagios-plugins/nagios-plugins-1.3.1/plugins' make all-am make[2]: Entering directory `/usr/local/src/nagios-plugins/nagios-plugins-1.3.1/plugins' source='check_nt.c' object='check_nt.o' libtool=no \ depfile='.deps/check_nt.Po' tmpdepfile='.deps/check_nt.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I. -I. -I. -I. -I. -I. -I.. -I../lib -I/usr/inc lude/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 make[2]: Leaving directory `/usr/local/src/nagios-plugins/nagios-plugins-1.3.1/plugins' make[1]: *** [all] Error 2 make[1]: Leaving directory `/usr/local/src/nagios-plugins/nagios-plugins-1.3.1/plugins' make: *** [all-recursive] Error 1 ----- Original Message ----- From: "Cook, Garry" <GW...@ma...> To: "Nate A. Smith" <nat...@di...>; <per...@li...> Sent: Tuesday, August 10, 2004 4:07 PM Subject: RE: [Perfparse-users] Compile Error > Did you send this message to the list as well? It appears as though you > did, but I only saw it come through at my address. Either way, please be > aware that you should always reply to the list, because as I'm about to > prove, I don't have all of the answers... > > Not being the C guru that Ben and Yves appear to be, I couldn't find the > problem based on the output you've provided. Ben and Yves are both on > vacation this week, but perhaps they can spot the issue when they > return, or maybe someone else on the list can help... > > With that said, I did a bit of googling and found other folks out there > with similar errors, on many different Linux distros, when compiling > several different apps. It appears as though this may be an error > related to gcc, possibly because it's a very new version distributed > with Fedora Core2. From what I've read, it may be that the newer gcc and > older autoconf (which creates the configure file) don't play nice > together. > > Is anyone else out there running Nagios and PerfParse on FC2? Seen > errors like this? > > Garry W. Cook, CCNA > Network Infrastructure Manager > MACTEC, Inc. - http://www.mactec.com/ > 303.308.6228 (Office) - 720.220.1862 (Mobile) > > Nate A. Smith wrote: > > -----Original Message----- > > From: Nate A. Smith > > Sent: Tuesday, August 10, 2004 9:08 AM > > To: per...@li... > > Subject: RE: [Perfparse-users] Compile Error > > > > > > Here is my info. I see an error in the compile process, but > > don't know > > how to fix it... > > > > Fedora Core 2 Final > > > > Here is my glib config: > > > > glibc-devel-2.3.3-27 > > glibc-common-2.3.3-27 > > glib2-2.4.0-1 > > glib2-devel-2.4.0-1 > > glibc-kernheaders-2.4-8.44 > > glibc-2.3.3-27 > > glib-1.2.10-12.1.1 > > dbus-glib-0.20-4.1 > > glibc-headers-2.3.3-27 > > glib-devel-1.2.10-12.1.1 > > > > And my config.log: > > > > This file contains any messages produced by compilers while > > running configure, to aid debugging if configure makes a mistake. > > > > It was created by perfparse configure 0.99.08, which was > > generated by GNU Autoconf 2.58. Invocation command line was > > > > $ ./configure > > > > ## --------- ## > > ## Platform. ## > > ## --------- ## > > > > hostname = rdfuxlinux1 > > uname -m = i686 > > uname -r = 2.6.5-1.358 > > uname -s = Linux > > uname -v = #1 Sat May 8 09:04:50 EDT 2004 > > > > /usr/bin/uname -p = unknown > > /bin/uname -X = unknown > > > > /bin/arch = i686 > > /usr/bin/arch -k = unknown > > /usr/convex/getsysinfo = unknown > > hostinfo = unknown > > /bin/machine = unknown > > /usr/bin/oslevel = unknown > > /bin/universe = unknown > > > > PATH: /usr/kerberos/sbin > > PATH: /usr/kerberos/bin > > PATH: /usr/local/sbin > > PATH: /usr/local/bin > > PATH: /sbin > > PATH: /bin > > PATH: /usr/sbin > > PATH: /usr/bin > > PATH: /usr/X11R6/bin > > PATH: /root/bin > > > > > > ## ----------- ## > > ## Core tests. ## > > ## ----------- ## > > > > configure:1551: checking build system type > > configure:1569: result: i686-pc-linux-gnu > > configure:1577: checking host system type > > configure:1591: result: i686-pc-linux-gnu > > configure:1599: checking target system type > > configure:1613: result: i686-pc-linux-gnu > > configure:1641: checking for a BSD-compatible install > > configure:1696: result: /usr/bin/install -c > > configure:1707: checking whether build environment is sane > > configure:1750: result: yes configure:1807: checking for gawk > > configure:1823: found /bin/gawk > > configure:1833: result: gawk > > configure:1843: checking whether make sets $(MAKE) > > configure:1863: result: yes > > configure:2078: checking for gcc > > configure:2094: found /usr/bin/gcc > > configure:2104: result: gcc > > configure:2348: checking for C compiler version > > configure:2351: gcc --version </dev/null >&5 > > gcc (GCC) 3.3.3 20040412 (Red Hat Linux 3.3.3-7) > > Copyright (C) 2003 Free Software Foundation, Inc. > > This is free software; see the source for copying conditions. There > > is NO > > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR > > PURPOSE. > > > > configure:2354: $? = 0 > > configure:2356: gcc -v </dev/null >&5 > > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/specs > > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > > --infodir=/usr/share/info --enable-shared --enable-threads=posix > > --disable-checking --disable-libunwind-exceptions --with-system-zlib > > --enable-__cxa_atexit --host=i386-redhat-linux > > Thread model: posix > > gcc version 3.3.3 20040412 (Red Hat Linux 3.3.3-7) > > configure:2359: $? = 0 > > configure:2361: gcc -V </dev/null >&5 > > gcc: `-V' option must have argument > > configure:2364: $? = 1 > > configure:2387: checking for C compiler default output file name > > configure:2390: gcc conftest.c >&5 > > configure:2393: $? = 0 > > configure:2439: result: a.out > > configure:2444: checking whether the C compiler works > > configure:2450: ./a.out > > configure:2453: $? = 0 > > configure:2470: result: yes > > configure:2477: checking whether we are cross compiling > > configure:2479: result: no configure:2482: checking for suffix of > > executables > > configure:2484: gcc -o conftest conftest.c >&5 > > configure:2487: $? = 0 > > configure:2512: result: > > configure:2518: checking for suffix of object files > > configure:2539: gcc -c conftest.c >&5 > > configure:2542: $? = 0 > > configure:2564: result: o > > configure:2568: checking whether we are using the GNU C compiler > > configure:2592: gcc -c conftest.c >&5 > > configure:2598: $? = 0 > > configure:2602: test -z > > || test ! -s conftest.err > > configure:2605: $? = 0 > > configure:2608: test -s conftest.o > > configure:2611: $? = 0 > > configure:2624: result: yes > > configure:2630: checking whether gcc accepts -g > > configure:2651: gcc -c -g conftest.c >&5 > > configure:2657: $? = 0 > > configure:2661: test -z > > || test ! -s conftest.err > > configure:2664: $? = 0 > > configure:2667: test -s conftest.o > > configure:2670: $? = 0 > > configure:2681: result: yes > > configure:2698: checking for gcc option to accept ANSI C > > configure:2768: gcc -c -g -O2 conftest.c >&5 > > configure:2774: $? = 0 > > configure:2778: test -z > > || test ! -s conftest.err > > configure:2781: $? = 0 > > configure:2784: test -s conftest.o > > configure:2787: $? = 0 > > configure:2805: result: none needed > > configure:2823: gcc -c -g -O2 conftest.c >&5 > > conftest.c:2: error: syntax error before "me" > > configure:2829: $? = 1 > > configure: failed program was: > >> #ifndef __cplusplus > >> choke me > >> #endif > > configure:2973: checking for style of include used by make > > configure:3001: result: GNU configure:3029: checking dependency style > > of gcc > > configure:3119: result: gcc3 > > configure:3136: checking whether make sets $(MAKE) > > configure:3156: result: yes > > configure:3178: checking for a BSD-compatible install > > configure:3233: result: /usr/bin/install -c > > configure:3316: checking for a sed that does not truncate output > > configure:3370: result: /bin/sed > > configure:3373: checking for egrep > > configure:3383: result: grep -E > > configure:3399: checking for ld used by gcc > > configure:3466: result: /usr/bin/ld > > configure:3475: checking if the linker (/usr/bin/ld) is GNU ld > > configure:3490: result: yes configure:3495: checking for /usr/bin/ld > > option to reload object files configure:3502: result: -r > > configure:3511: checking for BSD-compatible nm > > configure:3553: result: /usr/bin/nm -B > > configure:3557: checking whether ln -s works > > configure:3561: result: yes > > configure:3568: checking how to recognise dependent libraries > > configure:3751: result: pass_all > > configure:3965: checking how to run the C preprocessor > > configure:4000: gcc -E conftest.c > > configure:4006: $? = 0 > > configure:4038: gcc -E conftest.c > > conftest.c:11:28: ac_nonexistent.h: No such file or directory > > configure:4044: $? = 1 configure: failed program was: > >> /* confdefs.h. */ > >> > >> #define PACKAGE_NAME "perfparse" > >> #define PACKAGE_TARNAME "perfparse" > >> #define PACKAGE_VERSION "0.99.08" > >> #define PACKAGE_STRING "perfparse 0.99.08" > >> #define PACKAGE_BUGREPORT "per...@cl..." #define PACKAGE > >> "perfparse" #define VERSION "0.99.08" > >> /* end confdefs.h. */ > >> #include <ac_nonexistent.h> > > configure:4083: result: gcc -E > > configure:4107: gcc -E conftest.c > > configure:4113: $? = 0 > > configure:4145: gcc -E conftest.c > > conftest.c:11:28: ac_nonexistent.h: No such file or directory > > configure:4151: $? = 1 configure: failed program was: > >> /* confdefs.h. */ > >> > >> #define PACKAGE_NAME "perfparse" > >> #define PACKAGE_TARNAME "perfparse" > >> #define PACKAGE_VERSION "0.99.08" > >> #define PACKAGE_STRING "perfparse 0.99.08" > >> #define PACKAGE_BUGREPORT "per...@cl..." #define PACKAGE > >> "perfparse" #define VERSION "0.99.08" > >> /* end confdefs.h. */ > >> #include <ac_nonexistent.h> > > configure:4195: checking for ANSI C header files > > configure:4220: gcc -c -g -O2 conftest.c >&5 > > configure:4226: $? = 0 > > configure:4230: test -z > > || test ! -s conftest.err > > configure:4233: $? = 0 > > configure:4236: test -s conftest.o > > configure:4239: $? = 0 > > configure:4325: gcc -o conftest -g -O2 conftest.c >&5 > > configure:4328: $? = 0 configure:4330: ./conftest > > configure:4333: $? = 0 > > configure:4348: result: yes > > configure:4372: checking for sys/types.h > > configure:4388: gcc -c -g -O2 conftest.c >&5 > > configure:4394: $? = 0 > > configure:4398: test -z > > || test ! -s conftest.err > > configure:4401: $? = 0 > > configure:4404: test -s conftest.o > > configure:4407: $? = 0 > > configure:4418: result: yes > > configure:4372: checking for sys/stat.h > > configure:4388: gcc -c -g -O2 conftest.c >&5 > > configure:4394: $? = 0 > > configure:4398: test -z > > || test ! -s conftest.err > > configure:4401: $? = 0 > > configure:4404: test -s conftest.o > > configure:4407: $? = 0 > > configure:4418: result: yes > > configure:4372: checking for stdlib.h > > configure:4388: gcc -c -g -O2 conftest.c >&5 > > configure:4394: $? = 0 > > configure:4398: test -z > > || test ! -s conftest.err > > configure:4401: $? = 0 > > configure:4404: test -s conftest.o > > configure:4407: $? = 0 > > configure:4418: result: yes > > configure:4372: checking for string.h > > configure:4388: gcc -c -g -O2 conftest.c >&5 > > configure:4394: $? = 0 > > configure:4398: test -z > > || test ! -s conftest.err > > configure:4401: $? = 0 > > configure:4404: test -s conftest.o > > configure:4407: $? = 0 > > configure:4418: result: yes > > configure:4372: checking for memory.h > > configure:4388: gcc -c -g -O2 conftest.c >&5 > > configure:4394: $? = 0 > > configure:4398: test -z > > || test ! -s conftest.err > > configure:4401: $? = 0 > > configure:4404: test -s conftest.o > > configure:4407: $? = 0 > > configure:4418: result: yes > > configure:4372: checking for strings.h > > configure:4388: gcc -c -g -O2 conftest.c >&5 > > configure:4394: $? = 0 > > configure:4398: test -z > > || test ! -s conftest.err > > configure:4401: $? = 0 > > configure:4404: test -s conftest.o > > configure:4407: $? = 0 > > configure:4418: result: yes > > configure:4372: checking for inttypes.h > > configure:4388: gcc -c -g -O2 conftest.c >&5 > > configure:4394: $? = 0 > > configure:4398: test -z > > || test ! -s conftest.err > > configure:4401: $? = 0 > > configure:4404: test -s conftest.o > > configure:4407: $? = 0 > > configure:4418: result: yes > > configure:4372: checking for stdint.h > > configure:4388: gcc -c -g -O2 conftest.c >&5 > > configure:4394: $? = 0 > > configure:4398: test -z > > || test ! -s conftest.err > > configure:4401: $? = 0 > > configure:4404: test -s conftest.o > > configure:4407: $? = 0 > > configure:4418: result: yes > > configure:4372: checking for unistd.h > > configure:4388: gcc -c -g -O2 conftest.c >&5 > > configure:4394: $? = 0 > > configure:4398: test -z > > || test ! -s conftest.err > > configure:4401: $? = 0 > > configure:4404: test -s conftest.o > > configure:4407: $? = 0 > > configure:4418: result: yes > > configure:4444: checking dlfcn.h usability > > configure:4456: gcc -c -g -O2 conftest.c >&5 > > configure:4462: $? = 0 > > configure:4466: test -z > > || test ! -s conftest.err > > configure:4469: $? = 0 > > configure:4472: test -s conftest.o > > configure:4475: $? = 0 > > configure:4485: result: yes > > configure:4489: checking dlfcn.h presence > > configure:4499: gcc -E conftest.c > > configure:4505: $? = 0 > > configure:4525: result: yes > > configure:4560: checking for dlfcn.h > > configure:4567: result: yes > > configure:4632: checking for g++ > > configure:4648: found /usr/bin/g++ > > configure:4658: result: g++ > > configure:4674: checking for C++ compiler version > > configure:4677: g++ --version </dev/null >&5 > > g++ (GCC) 3.3.3 20040412 (Red Hat Linux 3.3.3-7) > > Copyright (C) 2003 Free Software Foundation, Inc. > > This is free software; see the source for copying conditions. There > > is NO > > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR > > PURPOSE. > > > > configure:4680: $? = 0 > > configure:4682: g++ -v </dev/null >&5 > > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/specs > > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > > --infodir=/usr/share/info --enable-shared --enable-threads=posix > > --disable-checking --disable-libunwind-exceptions --with-system-zlib > > --enable-__cxa_atexit --host=i386-redhat-linux > > Thread model: posix > > gcc version 3.3.3 20040412 (Red Hat Linux 3.3.3-7) > > configure:4685: $? = 0 > > configure:4687: g++ -V </dev/null >&5 > > g++: `-V' option must have argument > > configure:4690: $? = 1 > > configure:4693: checking whether we are using the GNU C++ compiler > > configure:4717: g++ -c conftest.cc >&5 > > configure:4723: $? = 0 > > configure:4727: test -z > > || test ! -s conftest.err > > configure:4730: $? = 0 > > configure:4733: test -s conftest.o > > configure:4736: $? = 0 > > configure:4749: result: yes > > configure:4755: checking whether g++ accepts -g > > configure:4776: g++ -c -g conftest.cc >&5 > > configure:4782: $? = 0 > > configure:4786: test -z > > || test ! -s conftest.err > > configure:4789: $? = 0 > > configure:4792: test -s conftest.o > > configure:4795: $? = 0 > > configure:4806: result: yes > > configure:4848: g++ -c -g -O2 conftest.cc >&5 > > configure:4854: $? = 0 > > configure:4858: test -z > > || test ! -s conftest.err > > configure:4861: $? = 0 > > configure:4864: test -s conftest.o > > configure:4867: $? = 0 > > configure:4893: g++ -c -g -O2 conftest.cc >&5 > > conftest.cc: In function `int main()': > > conftest.cc:26: error: `exit' undeclared (first use this function) > > conftest.cc:26: error: (Each undeclared identifier is > > reported only once > > for > > each function it appears in.) > > configure:4899: $? = 1 > > configure: failed program was: > >> /* confdefs.h. */ > >> > >> #define PACKAGE_NAME "perfparse" > >> #define PACKAGE_TARNAME "perfparse" > >> #define PACKAGE_VERSION "0.99.08" > >> #define PACKAGE_STRING "perfparse 0.99.08" > >> #define PACKAGE_BUGREPORT "per...@cl..." #define PACKAGE > >> "perfparse" #define VERSION "0.99.08" > >> #define STDC_HEADERS 1 > >> #define HAVE_SYS_TYPES_H 1 > >> #define HAVE_SYS_STAT_H 1 > >> #define HAVE_STDLIB_H 1 > >> #define HAVE_STRING_H 1 > >> #define HAVE_MEMORY_H 1 > >> #define HAVE_STRINGS_H 1 > >> #define HAVE_INTTYPES_H 1 > >> #define HAVE_STDINT_H 1 > >> #define HAVE_UNISTD_H 1 > >> #define HAVE_DLFCN_H 1 > >> /* end confdefs.h. */ > >> > >> int > >> main () > >> { > >> exit (42); > >> ; > >> return 0; > >> } > > configure:4848: g++ -c -g -O2 conftest.cc >&5 > > configure:4854: $? = 0 > > configure:4858: test -z > > || test ! -s conftest.err > > configure:4861: $? = 0 > > configure:4864: test -s conftest.o > > configure:4867: $? = 0 > > configure:4893: g++ -c -g -O2 conftest.cc >&5 > > configure:4899: $? = 0 > > configure:4903: test -z > > || test ! -s conftest.err > > configure:4906: $? = 0 > > configure:4909: test -s conftest.o > > configure:4912: $? = 0 > > configure:4937: checking dependency style of g++ > > configure:5027: result: gcc3 > > configure:5049: checking how to run the C++ preprocessor > > configure:5080: g++ -E conftest.cc > > configure:5086: $? = 0 > > configure:5118: g++ -E conftest.cc > > conftest.cc:25:28: ac_nonexistent.h: No such file or directory > > configure:5124: $? = 1 configure: failed program was: > >> /* confdefs.h. */ > >> > >> #define PACKAGE_NAME "perfparse" > >> #define PACKAGE_TARNAME "perfparse" > >> #define PACKAGE_VERSION "0.99.08" > >> #define PACKAGE_STRING "perfparse 0.99.08" > >> #define PACKAGE_BUGREPORT "per...@cl..." #define PACKAGE > >> "perfparse" #define VERSION "0.99.08" > >> #define STDC_HEADERS 1 > >> #define HAVE_SYS_TYPES_H 1 > >> #define HAVE_SYS_STAT_H 1 > >> #define HAVE_STDLIB_H 1 > >> #define HAVE_STRING_H 1 > >> #define HAVE_MEMORY_H 1 > >> #define HAVE_STRINGS_H 1 > >> #define HAVE_INTTYPES_H 1 > >> #define HAVE_STDINT_H 1 > >> #define HAVE_UNISTD_H 1 > >> #define HAVE_DLFCN_H 1 > >> #ifdef __cplusplus > >> extern "C" void std::exit (int) throw (); using std::exit; #endif > >> /* end confdefs.h. */ > >> #include <ac_nonexistent.h> > > configure:5163: result: g++ -E > > configure:5187: g++ -E conftest.cc > > configure:5193: $? = 0 > > configure:5225: g++ -E conftest.cc > > conftest.cc:25:28: ac_nonexistent.h: No such file or directory > > configure:5231: $? = 1 configure: failed program was: > >> /* confdefs.h. */ > >> > >> #define PACKAGE_NAME "perfparse" > >> #define PACKAGE_TARNAME "perfparse" > >> #define PACKAGE_VERSION "0.99.08" > >> #define PACKAGE_STRING "perfparse 0.99.08" > >> #define PACKAGE_BUGREPORT "per...@cl..." #define PACKAGE > >> "perfparse" #define VERSION "0.99.08" > >> #define STDC_HEADERS 1 > >> #define HAVE_SYS_TYPES_H 1 > >> #define HAVE_SYS_STAT_H 1 > >> #define HAVE_STDLIB_H 1 > >> #define HAVE_STRING_H 1 > >> #define HAVE_MEMORY_H 1 > >> #define HAVE_STRINGS_H 1 > >> #define HAVE_INTTYPES_H 1 > >> #define HAVE_STDINT_H 1 > >> #define HAVE_UNISTD_H 1 > >> #define HAVE_DLFCN_H 1 > >> #ifdef __cplusplus > >> extern "C" void std::exit (int) throw (); using std::exit; #endif > >> /* end confdefs.h. */ > >> #include <ac_nonexistent.h> > > configure:5326: checking for g77 > > configure:5342: found /usr/bin/g77 > > configure:5352: result: g77 > > configure:5370: checking for Fortran 77 compiler version > > configure:5370: g77 --version </dev/null >&5 > > GNU Fortran (GCC) 3.3.3 20040412 (Red Hat Linux 3.3.3-7) > > Copyright (C) 2002 Free Software Foundation, Inc. > > > > GNU Fortran comes with NO WARRANTY, to the extent permitted by law. > > You may redistribute copies of GNU Fortran > > under the terms of the GNU General Public License. > > For more information about these matters, see the file named COPYING > > or type the command `info -f g77 Copying'. > > configure:5373: $? = 0 > > configure:5375: g77 -v </dev/null >&5 > > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/specs > > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > > --infodir=/usr/share/info --enable-shared --enable-threads=posix > > --disable-checking --disable-libunwind-exceptions --with-system-zlib > > --enable-__cxa_atexit --host=i386-redhat-linux > > Thread model: posix > > gcc version 3.3.3 20040412 (Red Hat Linux 3.3.3-7) > > configure:5378: $? = 0 > > configure:5380: g77 -V </dev/null >&5 > > g77: `-V' option must have argument > > configure:5383: $? = 1 > > configure:5391: checking whether we are using the GNU Fortran 77 > > compiler configure:5405: g77 -c conftest.F >&5 > > configure:5411: $? = 0 > > configure:5415: test -z > > || test ! -s conftest.err > > configure:5418: $? = 0 > > configure:5421: test -s conftest.o > > configure:5424: $? = 0 > > configure:5437: result: yes > > configure:5443: checking whether g77 accepts -g > > configure:5455: g77 -c -g conftest.f >&5 > > configure:5461: $? = 0 > > configure:5465: test -z > > || test ! -s conftest.err > > configure:5468: $? = 0 > > configure:5471: test -s conftest.o > > configure:5474: $? = 0 > > configure:5486: result: yes > > configure:5516: checking the maximum length of command line arguments > > configure:5581: result: 32768 configure:5592: checking command to > > parse /usr/bin/nm -B > > output from gcc > > object > > configure:5681: gcc -c -g -O2 conftest.c >&5 > > configure:5684: $? = 0 > > configure:5688: /usr/bin/nm -B conftest.o \| sed -n -e 's/^.*[ > > ]\([ABCDGIRSTW][ABCDGIRSTW]*\)[ ][ > > ]*\(\)\([_A-Za-z][_A-Za-z0-9]*\)$/\1 \2\3 \3/p' \> conftest.nm > > configure:5691: $? = 0 configure:5743: gcc -o conftest -g -O2 > > conftest.c conftstm.o >&5 configure:5746: $? = 0 configure:5784: > > result: ok > > configure:5788: checking for objdir > > configure:5803: result: .libs > > configure:5893: checking for ar > > configure:5909: found /usr/bin/ar > > configure:5920: result: ar > > configure:5973: checking for ranlib > > configure:5989: found /usr/bin/ranlib > > configure:6000: result: ranlib > > configure:6053: checking for strip > > configure:6069: found /usr/bin/strip > > configure:6080: result: strip > > configure:6342: checking if gcc static flag works > > configure:6365: result: yes > > configure:6383: checking if gcc supports -fno-rtti -fno-exceptions > > configure:6404: gcc -c -g -O2 -fno-rtti -fno-exceptions > > conftest.c >&5 > > cc1: warning: "-fno-rtti" is valid for C++ but not for C/ObjC > > configure:6408: $? = 0 configure:6416: result: no > > configure:6431: checking for gcc option to produce PIC > > configure:6608: result: -fPIC configure:6616: checking if gcc PIC > > flag -fPIC works > > configure:6637: gcc -c -g -O2 -fPIC -DPIC conftest.c >&5 > > configure:6641: $? = 0 configure:6649: result: yes > > configure:6673: checking if gcc supports -c -o file.o > > configure:6697: gcc -c -g -O2 -o out/conftest2.o conftest.c >&5 > > configure:6701: $? = 0 configure:6718: result: yes > > configure:6744: checking whether the gcc linker (/usr/bin/ld) > > supports shared libraries configure:7592: result: yes > > configure:7618: checking whether -lc should be explicitly linked in > > configure:7623: gcc -c -g -O2 conftest.c >&5 > > configure:7626: $? = 0 > > configure:7640: gcc -shared conftest.o -v -Wl,-soname -Wl,conftest -o > > conftest 2\>\&1 \| grep -lc \>/dev/null 2\>\&1 > > configure:7643: $? = 0 > > configure:7655: result: no > > configure:7663: checking dynamic linker characteristics > > configure:8203: result: GNU/Linux ld.so > > configure:8207: checking how to hardcode library paths into programs > > configure:8232: result: immediate > > configure:8246: checking whether stripping libraries is possible > > configure:8251: result: yes configure:9081: checking if libtool > > supports shared libraries configure:9083: result: yes configure:9086: > > checking whether to build shared libraries configure:9144: result: > > yes configure:9147: checking whether to build static libraries > > configure:9151: result: yes configure:9243: creating libtool > > configure:9790: checking for ld used by g++ > > configure:9857: result: /usr/bin/ld > > configure:9866: checking if the linker (/usr/bin/ld) is GNU ld > > configure:9881: result: yes configure:9932: checking whether the g++ > > linker (/usr/bin/ld) supports shared libraries configure:10760: > > result: yes > > configure:10778: g++ -c -g -O2 conftest.cc >&5 > > configure:10781: $? = 0 > > configure:10877: checking for g++ option to produce PIC > > configure:11129: result: -fPIC > > configure:11137: checking if g++ PIC flag -fPIC works > > configure:11158: g++ -c -g -O2 -fPIC -DPIC conftest.cc >&5 > > configure:11162: $? = 0 configure:11170: result: yes > > configure:11194: checking if g++ supports -c -o file.o > > configure:11218: g++ -c -g -O2 -o out/conftest2.o conftest.cc >&5 > > configure:11222: $? = 0 configure:11239: result: yes > > configure:11265: checking whether the g++ linker > > (/usr/bin/ld) supports > > shared libraries > > configure:11290: result: yes > > configure:11361: checking dynamic linker characteristics > > configure:11901: result: GNU/Linux ld.so > > configure:11905: checking how to hardcode library paths into programs > > configure:11930: result: immediate > > configure:11944: checking whether stripping libraries is possible > > configure:11949: result: yes configure:13256: checking if libtool > > supports shared libraries configure:13258: result: yes > > configure:13261: checking whether to build shared libraries > > configure:13279: result: yes configure:13282: checking whether to > > build static libraries configure:13286: result: yes configure:13298: > > checking for g77 option to produce PIC configure:13475: result: -fPIC > > configure:13483: checking if g77 PIC flag -fPIC works > > configure:13504: g77 -c -g -O2 -fPIC conftest.f >&5 > > configure:13508: $? = 0 > > configure:13516: result: yes > > configure:13540: checking if g77 supports -c -o file.o > > configure:13564: g77 -c -g -O2 -o out/conftest2.o conftest.f >&5 > > configure:13568: $? = 0 configure:13585: result: yes > > configure:13611: checking whether the g77 linker > > (/usr/bin/ld) supports > > shared libraries > > configure:14439: result: yes > > configure:14510: checking dynamic linker characteristics > > configure:15050: result: GNU/Linux ld.so > > configure:15054: checking how to hardcode library paths into programs > > configure:15079: result: immediate > > configure:15093: checking whether stripping libraries is possible > > configure:15098: result: yes configure:19289: checking for pkg-config > > configure:19307: found /usr/bin/pkg-config > > configure:19320: result: /usr/bin/pkg-config > > configure:19343: checking for GLIB - version >= 2.0.0 > > configure:19462: gcc -o conftest -g -O2 -I/usr/include/glib-2.0 > > -I/usr/lib/glib-2.0/include conftest.c -lglib-2.0 >&5 > > configure:19465: $? = 0 configure:19467: ./conftest > > configure:19470: $? = 0 > > configure:19488: result: yes (version 2.4.0) > > configure:19638: checking for mysql_config > > configure:19657: found /usr/bin/mysql_config > > configure:19670: result: /usr/bin/mysql_config > > configure:19734: checking for ANSI C header files > > configure:19887: result: yes > > configure:19905: checking for stdlib.h > > configure:19910: result: yes > > configure:19905: checking for string.h > > configure:19910: result: yes > > configure:19905: checking for unistd.h > > configure:19910: result: yes > > configure:19914: checking sys/utsname.h usability > > configure:19926: gcc -c -g -O2 conftest.c >&5 > > configure:19932: $? = 0 > > configure:19936: test -z > > || test ! -s conftest.err > > configure:19939: $? = 0 > > configure:19942: test -s conftest.o > > configure:19945: $? = 0 > > configure:19955: result: yes > > configure:19959: checking sys/utsname.h presence > > configure:19969: gcc -E conftest.c > > configure:19975: $? = 0 > > configure:19995: result: yes > > configure:20030: checking for sys/utsname.h > > configure:20037: result: yes > > configure:20052: checking for an ANSI C-conforming const > > configure:20119: gcc -c -g -O2 conftest.c >&5 > > configure:20125: $? = 0 > > configure:20129: test -z > > || test ! -s conftest.err > > configure:20132: $? = 0 > > configure:20135: test -s conftest.o > > configure:20138: $? = 0 > > configure:20149: result: yes > > configure:20159: checking for pid_t > > configure:20183: gcc -c -g -O2 conftest.c >&5 > > configure:20189: $? = 0 > > configure:20193: test -z > > || test ! -s conftest.err > > configure:20196: $? = 0 > > configure:20199: test -s conftest.o > > configure:20202: $? = 0 > > configure:20213: result: yes > > configure:20225: checking whether struct tm is in sys/time.h or time.h > > configure:20248: gcc -c -g -O2 conftest.c >&5 > > configure:20254: $? = 0 > > configure:20258: test -z > > || test ! -s conftest.err > > configure:20261: $? = 0 > > configure:20264: test -s conftest.o > > configure:20267: $? = 0 > > configure:20278: result: time.h > > configure:20295: checking for stdlib.h > > configure:20300: result: yes > > configure:20440: checking for GNU libc compatible malloc > > configure:20469: gcc -o conftest -g -O2 conftest.c >&5 > > configure:20472: $? = 0 configure:20474: ./conftest > > configure:20477: $? = 0 > > configure:20491: result: yes > > configure:20521: checking whether time.h and sys/time.h may both be > > included configure:20546: gcc -c -g -O2 conftest.c >&5 > > configure:20552: $? = 0 > > configure:20556: test -z > > || test ! -s conftest.err > > configure:20559: $? = 0 > > configure:20562: test -s conftest.o > > configure:20565: $? = 0 > > configure:20576: result: yes > > configure:20593: checking for stdlib.h > > configure:20598: result: yes > > configure:20602: checking sys/time.h usability > > configure:20614: gcc -c -g -O2 conftest.c >&5 > > configure:20620: $? = 0 > > configure:20624: test -z > > || test ! -s conftest.err > > configure:20627: $? = 0 > > configure:20630: test -s conftest.o > > configure:20633: $? = 0 > > configure:20643: result: yes > > configure:20647: checking sys/time.h presence > > configure:20657: gcc -E conftest.c > > configure:20663: $? = 0 > > configure:20683: result: yes > > configure:20718: checking for sys/time.h > > configure:20725: result: yes > > configure:20593: checking for unistd.h > > configure:20598: result: yes > > configure:20742: checking for alarm > > configure:20799: gcc -o conftest -g -O2 conftest.c >&5 > > configure:20805: $? = 0 configure:20809: test -z > > || test ! -s conftest.err > > configure:20812: $? = 0 > > configure:20815: test -s conftest > > configure:20818: $? = 0 > > configure:20830: result: yes > > configure:20840: checking for working mktime > > configure:21016: gcc -o conftest -g -O2 conftest.c >&5 > > configure:21019: $? = 0 configure:21021: ./conftest > > configure:21024: $? = 1 > > configure: program exited with status 1 > > configure: failed program was: > >> /* confdefs.h. */ > >> > >> #define PACKAGE_NAME "perfparse" > >> #define PACKAGE_TARNAME "perfparse" > >> #define PACKAGE_VERSION "0.99.08" > >> #define PACKAGE_STRING "perfparse 0.99.08" > >> #define PACKAGE_BUGREPORT "per...@cl..." #define PACKAGE > >> "perfparse" #define VERSION "0.99.08" > >> #define STDC_HEADERS 1 > >> #define HAVE_SYS_TYPES_H 1 > >> #define HAVE_SYS_STAT_H 1 > >> #define HAVE_STDLIB_H 1 > >> #define HAVE_STRING_H 1 > >> #define HAVE_MEMORY_H 1 > >> #define HAVE_STRINGS_H 1 > >> #define HAVE_INTTYPES_H 1 > >> #define HAVE_STDINT_H 1 > >> #define HAVE_UNISTD_H 1 > >> #define HAVE_DLFCN_H 1 > >> #ifdef __cplusplus > >> extern "C" void std::exit (int) throw (); using std::exit; #endif > >> #define USE_DB_MYSQL 1 > >> #define STDC_HEADERS 1 > >> #define HAVE_STDLIB_H 1 > >> #define HAVE_STRING_H 1 > >> #define HAVE_UNISTD_H 1 > >> #define HAVE_SYS_UTSNAME_H 1 > >> #define HAVE_STDLIB_H 1 > >> #define HAVE_MALLOC 1 > >> #define TIME_WITH_SYS_TIME 1 > >> #define HAVE_STDLIB_H 1 > >> #define HAVE_SYS_TIME_H 1 > >> #define HAVE_UNISTD_H 1 > >> #define HAVE_ALARM 1 > >> /* end confdefs.h. */ > >> /* Test program from Paul Eggert and Tony Leneis. */ #if > >> TIME_WITH_SYS_TIME # include <sys/time.h> > >> # include <time.h> > >> #else > >> # if HAVE_SYS_TIME_H > >> # include <sys/time.h> > >> # else > >> # include <time.h> > >> # endif > >> #endif > >> > >> #if HAVE_STDLIB_H > >> # include <stdlib.h> > >> #endif > >> > >> #if HAVE_UNISTD_H > >> # include <unistd.h> > >> #endif > >> > >> #if !HAVE_ALARM > >> # define alarm(X) /* empty */ > >> #endif > >> > >> /* Work around redefinition to rpl_putenv by other config tests. */ > >> #undef putenv > >> > >> static time_t time_t_max; > >> static time_t time_t_min; > >> > >> /* Values we'll use to set the TZ environment variable. */ > >> static char *tz_strings[] = { > >> (char *) 0, "TZ=GMT0", "TZ=JST-9", > >> "TZ=EST+3EDT+2,M10.1.0/00:00:00,M2.3.0/00:00:00" > >> }; > >> #define N_STRINGS (sizeof (tz_strings) / sizeof (tz_strings[0])) > >> > >> /* Fail if mktime fails to convert a date in the spring-forward gap. > >> Based on a problem report from Andreas Jaeger. */ > >> static void > >> spring_forward_gap () > >> { > >> /* glibc (up to about 1998-10-07) failed this test. */ struct tm > >> tm; > >> > >> /* Use the portable POSIX.1 specification > >> "TZ=PST8PDT,M4.1.0,M10.5.0" instead of "TZ=America/Vancouver" > >> in order to detect the bug even on systems that don't support > >> the Olson extension, or > > don't have > > the > >> full zoneinfo tables installed. */ > >> putenv ("TZ=PST8PDT,M4.1.0,M10.5.0"); > >> > >> tm.tm_year = 98; > >> tm.tm_mon = 3; > >> tm.tm_mday = 5; > >> tm.tm_hour = 2; > >> tm.tm_min = 0; > >> tm.tm_sec = 0; > >> tm.tm_isdst = -1; > >> if (mktime (&tm) == (time_t)-1) > >> exit (1); > >> } > >> > >> static void > >> mktime_test1 (now) > >> time_t now; > >> { > >> struct tm *lt; > >> if ((lt = localtime (&now)) && mktime (lt) != now) exit (1); > >> } > >> > >> static void > >> mktime_test (now) > >> time_t now; > >> { > >> mktime_test1 (now); > >> mktime_test1 ((time_t) (time_t_max - now)); > >> mktime_test1 ((time_t) (time_t_min + now)); > >> } > >> > >> static void > >> irix_6_4_bug () > >> { > >> /* Based on code from Ariel Faigon. */ > >> struct tm tm; > >> tm.tm_year = 96; > >> tm.tm_mon = 3; > >> tm.tm_mday = 0; > >> tm.tm_hour = 0; > >> tm.tm_min = 0; > >> tm.tm_sec = 0; > >> tm.tm_isdst = -1; > >> mktime (&tm); > >> if (tm.tm_mon != 2 || tm.tm_mday != 31) > >> exit (1); > >> } > >> > >> static void > >> bigtime_test (j) > >> int j; > >> { > >> struct tm tm; > >> time_t now; > >> tm.tm_year = tm.tm_mon = tm.tm_mday = tm.tm_hour = tm.tm_min = > >> tm.tm_sec = j; now = mktime (&tm); if (now != (time_t) -1) > >> { > >> struct tm *lt = localtime (&now); > >> if (! (lt > >> && lt->tm_year == tm.tm_year > >> && lt->tm_mon == tm.tm_mon > >> && lt->tm_mday == tm.tm_mday > >> && lt->tm_hour == tm.tm_hour > >> && lt->tm_min == tm.tm_min > >> && lt->tm_sec == tm.tm_sec > >> && lt->tm_yday == tm.tm_yday > >> && lt->tm_wday == tm.tm_wday > >> && ((lt->tm_isdst < 0 ? -1 : 0 < lt->tm_isdst) > >> == (tm.tm_isdst < 0 ? -1 : 0 < tm.tm_isdst)))) > >> exit (1); > >> } > >> } > >> > >> int > >> main () > >> { > >> time_t t, delta; > >> int i, j; > >> > >> /* This test makes some buggy mktime implementations loop. > >> Give up after 60 seconds; a mktime slower than that > >> isn't worth using anyway. */ > >> alarm (60); > >> > >> for (time_t_max = 1; 0 < time_t_max; time_t_max *= 2) continue; > >> time_t_max--; > >> if ((time_t) -1 < 0) > >> for (time_t_min = -1; (time_t) (time_t_min * 2) < 0; > > time_t_min *= > > 2) > >> continue; > >> delta = time_t_max / 997; /* a suitable prime number */ > >> for (i = 0; i < N_STRINGS; i++) > >> { > >> if (tz_strings[i]) > >> putenv (tz_strings[i]); > >> > >> for (t = 0; t <= time_t_max - delta; t += delta) > mktime_test > >> (t); mktime_test ((time_t) 1); > >> mktime_test ((time_t) (60 * 60)); > >> mktime_test ((time_t) (60 * 60 * 24)); > >> > >> for (j = 1; 0 < j; j *= 2) > >> bigtime_test (j); > >> bigtime_test (j - 1); > >> } > >> irix_6_4_bug (); > >> spring_forward_gap (); > >> exit (0); > >> } > > configure:21038: result: no > > configure:21059: checking for atexit > > configure:21116: gcc -o conftest -g -O2 conftest.c >&5 > > configure:21122: $? = 0 configure:21126: test -z > > || test ! -s conftest.err > > configure:21129: $? = 0 > > configure:21132: test -s conftest > > configure:21135: $? = 0 > > configure:21147: result: yes > > configure:21059: checking for modf > > configure:21116: gcc -o conftest -g -O2 conftest.c >&5 > > configure:21122: $? = 0 configure:21126: test -z > > || test ! -s conftest.err > > configure:21129: $? = 0 > > configure:21132: test -s conftest > > configure:21135: $? = 0 > > configure:21147: result: yes > > configure:21059: checking for pow > > configure:21116: gcc -o conftest -g -O2 conftest.c >&5 > > /tmp/ccKneePj.o(.text+0x11): In function `main': > > /root/perfparse-0.99.08/conftest.c:80: undefined reference to `pow' > > /tmp/ccKneePj.o(.data+0x0):/root/perfparse-0.99.08/conftest.c:79: > > undefined reference to `pow' collect2: ld returned 1 exit status > > configure:21122: $? = 1 > > configure: failed program was: > >> /* confdefs.h. */ > >> > >> #define PACKAGE_NAME "perfparse" > >> #define PACKAGE_TARNAME "perfparse" > >> #define PACKAGE_VERSION "0.99.08" > >> #define PACKAGE_STRING "perfparse 0.99.08" > >> #define PACKAGE_BUGREPORT "per...@cl..." #define PACKAGE > >> "perfparse" #define VERSION "0.99.08" > >> #define STDC_HEADERS 1 > >> #define HAVE_SYS_TYPES_H 1 > >> #define HAVE_SYS_STAT_H 1 > >> #define HAVE_STDLIB_H 1 > >> #define HAVE_STRING_H 1 > >> #define HAVE_MEMORY_H 1 > >> #define HAVE_STRINGS_H 1 > >> #define HAVE_INTTYPES_H 1 > >> #define HAVE_STDINT_H 1 > >> #define HAVE_UNISTD_H 1 > >> #define HAVE_DLFCN_H 1 > >> #ifdef __cplusplus > >> extern "C" void std::exit (int) throw (); using std::exit; #endif > >> #define USE_DB_MYSQL 1 > >> #define STDC_HEADERS 1 > >> #define HAVE_STDLIB_H 1 > >> #define HAVE_STRING_H 1 > >> #define HAVE_UNISTD_H 1 > >> #define HAVE_SYS_UTSNAME_H 1 > >> #define HAVE_STDLIB_H 1 > >> #define HAVE_MALLOC 1 > >> #define TIME_WITH_SYS_TIME 1 > >> #define HAVE_STDLIB_H 1 > >> #define HAVE_SYS_TIME_H 1 > >> #define HAVE_UNISTD_H 1 > >> #define HAVE_ALARM 1 > >> #define HAVE_ATEXIT 1 > >> #define HAVE_MODF 1 > >> /* end confdefs.h. */ > >> /* Define pow to an innocuous variant, in case <limits.h> declares > >> pow. For example, HP-UX 11i <limits.h> declares gettimeofday. */ > >> #define pow innocuous_pow > >> > >> /* System header to define __stub macros and hopefully few > >> prototypes, which can conflict with char pow (); below. > >> Prefer <limits.h> to <assert.h> if __STDC__ is defined, since > >> <limits.h> exists even on freestanding compilers. */ > >> > >> #ifdef __STDC__ > >> # include <limits.h> > >> #else > >> # include <assert.h> > >> #endif > >> > >> #undef pow > >> > >> /* Override any gcc2 internal prototype to avoid an error. */ > >> #ifdef __cplusplus extern "C" > >> { > >> #endif > >> /* We use char because int might match the return type of a gcc2 > >> builtin and then its argument prototype would still apply. */ > >> char pow (); /* The GNU C library defines this for functions which > >> it implements to always fail with ENOSYS. Some functions are > >> actually named something starting with __ and the normal name is > >> an alias. */ #if defined (__stub_pow) || defined (__stub___pow) > >> choke me > >> #else > >> char (*f) () = pow; > >> #endif > >> #ifdef __cplusplus > >> } > >> #endif > >> > >> int > >> main () > >> { > >> return f != pow; > >> ; > >> return 0; > >> } > > configure:21147: result: no > > configure:21059: checking for strstr > > configure:21116: gcc -o conftest -g -O2 conftest.c >&5 > > conftest.c:64: warning: conflicting types for built-in > > function `strstr' > > configure:21122: $? = 0 > > configure:21126: test -z > > || test ! -s conftest.err > > configure:21129: $? = 0 > > configure:21132: test -s conftest > > configure:21135: $? = 0 > > configure:21147: result: yes > > configure:21059: checking for vasprintf > > configure:21116: gcc -o conftest -g -O2 conftest.c >&5 > > configure:21122: $? = 0 configure:21126: test -z > > || test ! -s conftest.err > > configure:21129: $? = 0 > > configure:21132: test -s conftest > > configure:21135: $? = 0 > > configure:21147: result: yes > > configure:21369: creating ./config.status > > > > ## ---------------------- ## > > ## Running config.status. ## > > ## ---------------------- ## > > > > This file was extended by perfparse config.status 0.99.08, which was > > generated by GNU Autoconf 2.58. Invocation command line was > > > > CONFIG_FILES = > > CONFIG_HEADERS = > > CONFIG_LINKS = > > CONFIG_COMMANDS = > > $ ./config.status > > > > on rdfuxlinux1 > > > > config.status:738: creating Makefile > > config.status:738: creating libperfparse/Makefile > > config.status:738: creating perfparse/Makefile > > config.status:738: creating db_tools/Makefile > > config.status:738: creating cgi/Makefile > > config.status:738: creating images/Makefile > > config.status:738: creating config/Makefile > > config.status:738: creating contrib/Makefile > > config.status:842: creating config.h > > config.status:999: config.h is unchanged > > config.status:1176: executing depfiles commands > > > > ## ---------------- ## > > ## Cache variables. ## > > ## ---------------- ## > > > > ac_cv_build=i686-pc-linux-gnu > > ac_cv_build_alias=i686-pc-linux-gnu > > ac_cv_c_compiler_gnu=yes > > ac_cv_c_const=yes > > ac_cv_cxx_compiler_gnu=yes > > ac_cv_env_CC_set= > > ac_cv_env_CC_value= > > ac_cv_env_CFLAGS_set= > > ac_cv_env_CFLAGS_value= > > ac_cv_env_CPPFLAGS_set= > > ac_cv_env_CPPFLAGS_value= > > ac_cv_env_CPP_set= > > ac_cv_env_CPP_value= > > ac_cv_env_CXXCPP_set= > > ac_cv_env_CXXCPP_value= > > ac_cv_env_CXXFLAGS_set= > > ac_cv_env_CXXFLAGS_value= > > ac_cv_env_CXX_set= > > ac_cv_env_CXX_value= > > ac_cv_env_F77_set= > > ac_cv_env_F77_value= > > ac_cv_env_FFLAGS_set= > > ac_cv_env_FFLAGS_value= > > ac_cv_env_LDFLAGS_set= > > ac_cv_env_LDFLAGS_value= > > ac_cv_env_build_alias_set= > > ac_cv_env_build_alias_value= > > ac_cv_env_host_alias_set= > > ac_cv_env_host_alias_value= > > ac_cv_env_target_alias_set= > > ac_cv_env_target_alias_value= > > ac_cv_exeext= > > ac_cv_f77_compiler_gnu=yes > > ac_cv_func_alarm=yes > > ac_cv_func_atexit=yes > > ac_cv_func_malloc_0_nonnull=yes > > ac_cv_func_modf=yes > > ac_cv_func_pow=no > > ac_cv_func_strstr=yes > > ac_cv_func_vasprintf=yes > > ac_cv_func_working_mktime=no > > ac_cv_header_dlfcn_h=yes > > ac_cv_header_inttypes_h=yes > > ac_cv_header_memory_h=yes > > ac_cv_header_stdc=yes > > ac_cv_header_stdint_h=yes > > ac_cv_header_stdlib_h=yes > > ac_cv_header_string_h=yes > > ac_cv_header_strings_h=yes > > ac_cv_header_sys_stat_h=yes > > ac_cv_header_sys_time_h=yes > > ac_cv_header_sys_types_h=yes > > ac_cv_header_sys_utsname_h=yes > > ac_cv_header_time=yes > > ac_cv_header_unistd_h=yes > > ac_cv_host=i686-pc-linux-gnu > > ac_cv_host_alias=i686-pc-linux-gnu > > ac_cv_objext=o > > ac_cv_path_MYSQL_CONFIG=/usr/bin/mysql_config > > ac_cv_path_PKG_CONFIG=/usr/bin/pkg-config > > ac_cv_path_install='/usr/bin/install -c' > > ac_cv_prog_AWK=gawk > > ac_cv_prog_CPP='gcc -E' > > ac_cv_prog_CXXCPP='g++ -E' > > ac_cv_prog_ac_ct_AR=ar > > ac_cv_prog_ac_ct_CC=gcc > > ac_cv_prog_ac_ct_CXX=g++ > > ac_cv_prog_ac_ct_F77=g77 > > ac_cv_prog_ac_ct_RANLIB=ranlib > > ac_cv_prog_ac_ct_STRIP=strip > > ac_cv_prog_cc_g=yes > > ac_cv_prog_cc_stdc= > > ac_cv_prog_cxx_g=yes > > ac_cv_prog_egrep='grep -E' > > ac_cv_prog_f77_g=yes > > ac_cv_prog_make_make_set=yes > > ac_cv_struct_tm=time.h > > ac_cv_target=i686-pc-linux-gnu > > ac_cv_target_alias=i686-pc-linux-gnu > > ac_cv_type_pid_t=yes > > am_cv_CC_dependencies_compiler_type=gcc3 > > am_cv_CXX_dependencies_compiler_type=gcc3 > > lt_cv_deplibs_check_method=pass_all > > lt_cv_file_magic_cmd='$MAGIC_CMD' > > lt_cv_file_magic_test_file='/lib/libc.so.6 /lib/libc-2.3.3.so' > > lt_cv_ld_reload_flag=-r lt_cv_objdir=.libs > > lt_cv_path_LD=/usr/bin/ld > > lt_cv_path_LDCXX=/usr/bin/ld > > lt_cv_path_NM='/usr/bin/nm -B' > > lt_cv_path_SED=/bin/sed > > lt_cv_prog_compiler_c_o=yes > > lt_cv_prog_compiler_c_o_CXX=yes > > lt_cv_prog_compiler_c_o_F77=yes > > lt_cv_prog_compiler_rtti_exceptions=no > > lt_cv_prog_gnu_ld=yes > > lt_cv_prog_gnu_ldcxx=yes > > lt_cv_sys_global_symbol_pipe='sed -n -e '\''s/^.*[ > > ]\([ABCDGIRSTW][ABCDGIRSTW]*\)[ ][ > > ]*\(\)\([_A-Za-z][_A-Za-z0-9]*\)$/\1 \2\3 \3/p'\''' > > lt_cv_sys_global_symbol_to_c_name_address='sed -n -e '\''s/^: \([^ > > ]*\) $/ {\"\1\", (lt_ptr) 0},/p'\'' -e '\''s/^[BCDEGRST] \([^ ]*\) > > \([^ ]*\)$/ {"\2", (lt_ptr) \&\2},/p'\''' > > lt_cv_sys_global_symbol_to_cdecl='sed -n -e '\''s/^. .* > > \(.*\)$/extern int \1;/p'\''' lt_cv_sys_max_cmd_len=32768 > > lt_lt_cv_prog_compiler_c_o='"yes"' > > lt_lt_cv_prog_compiler_c_o_CXX='"yes"' > > lt_lt_cv_prog_compiler_c_o_F77='"yes"' > > lt_lt_cv_sys_global_symbol_pipe='"sed -n -e '\''s/^.*[ > > ]\\([ABCDGIRSTW][ABCDGIRSTW]*\\)[ ][ > > ]*\\(\\)\\([_A-Za-z][_A-Za-z0-9]*\\)\$/\\1 \\2\\3 \\3/p'\''"' > > lt_lt_cv_sys_global_symbol_to_c_name_address='"sed -n -e '\''s/^: > > \\([^ ]*\\) \$/ {\\\"\\1\\\", (lt_ptr) 0},/p'\'' -e > > '\''s/^[BCDEGRST] \\([^ ]*\\) \\([^ ]*\\)\$/ {\"\\2\", (lt_ptr) > > \\&\\2},/p'\''"' lt_lt_cv_sys_global_symbol_to_cdecl='"sed -n -e > > '\''s/^. .* \\(.*\\)\$/extern int \\1;/p'\''"' > > > > ## ----------------- ## > > ## Output variables. ## > > ## ----------------- ## > > > > ACLOCAL='${SHELL} /root/perfparse-0.99.08/missing --run aclocal-1.8' > > AMDEPBACKSLASH='\' AMDEP_FALSE='#' > > AMDEP_TRUE='' > > AMTAR='${SHELL} /root/perfparse-0.99.08/missing --run tar' > > AR='ar' > > AUTOCONF='${SHELL} /root/perfparse-0.99.08/missing --run autoconf' > > AUTOHEADER='${SHELL} /root/perfparse-0.99.08/missing --run autoheader' > > AUTOMAKE='${SHELL} /root/perfparse-0.99.08/missing --run > > automake-1.8' AWK='gawk' CC='gcc' > > CCDEPMODE='depmode=gcc3' > > CFLAGS='-g -O2 -Wall' > > CPP='gcc -E' > > CPPFLAGS='' > > CXX='g++' > > CXXCPP='g++ -E' > > CXXDEPMODE='depmode=gcc3' > > CXXFLAGS='-g -O2' > > CYGPATH_W='echo' > > DEFS='-DHAVE_CONFIG_H' > > DEPDIR='.deps' > > ECHO='echo' > > ECHO_C='' > > ECHO_N='-n' > > ECHO_T='' > > EGREP='grep -E' > > EXEEXT='' > > F77='g77' > > FFLAGS='-g -O2' > > GD_CFLAGS='-I${GD_DIR}/include' > > GD_LIBS='-L${GD_DIR}/lib -lgd' > > GLIB_CFLAGS='-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include ' > > GLIB_CONFIG='' GLIB_GENMARSHAL='glib-genmarshal' > > GLIB_LIBS='-lglib-2.0 ' > > GLIB_MKENUMS='glib-mkenums' > > GOBJECT_QUERY='gobject-query' > > HTTP_IMAGE_PATH='/nagios/images' > > ICONV_CFLAGS='' > > ICONV_LIBS='' > > INSTALL_DATA='${INSTALL} -m 644' > > INSTALL_PROGRAM='${INSTALL}' > > INSTALL_SCRIPT='${INSTALL}' > > INSTALL_STRIP_PROGRAM='${SHELL} $(install_sh) -c -s' > > INST_CGI_PATH='${exec_prefix}/sbin' > > INST_IMAGE_PATH='${datadir}/perfparse/images' > > LDFLAGS='' > > LIBOBJS=' mktime$U.o' > > LIBS='' > > LIBTOOL='$(SHELL) $(top_builddir)/libtool' > > LN_S='ln -s' > > LTLIBOBJS=' mktime$U.lo' > > MAKEINFO='${SHELL} /root/perfparse-0.99.08/missing --run makeinfo' > > MYSQL_CFLAGS='-I/usr/include/mysql -mcpu=i486 -fno-strength-reduce' > > MYSQL_CONFIG='/usr/bin/mysql_config' > > MYSQL_LIBS='-L/usr/lib/mysql -lmysqlclient -lz -lcrypt -lnsl -lm -lc > > -lnss_files -lnss_dns -lresolv -lc -lnss_files -lnss_dns -lresolv' > > OBJEXT='o' PACKAGE='perfparse' > > PACKAGE_BUGREPORT='per...@cl...' > > PACKAGE_NAME='perfparse' > > PACKAGE_STRING='perfparse 0.99.08' > > PACKAGE_TARNAME='perfparse' > > PACKAGE_VERSION='0.99.08' > > PATH_SEPARATOR=':' > > PKG_CONFIG='/usr/bin/pkg-config' > > RANLIB='ranlib' > > SET_MAKE='' > > SHELL='/bin/sh' > > STRIP='strip' > > VERSION='0.99.08' > > ac_ct_AR='ar' > > ac_ct_CC='gcc' > > ac_ct_CXX='g++' > > ac_ct_F77='g77' > > ac_ct_RANLIB='ranlib' > > ac_ct_STRIP='strip' > > am__fastdepCC_FALSE='#' > > am__fastdepCC_TRUE='' > > am__fastdepCXX_FALSE='#' > > am__fastdepCXX_TRUE='' > > am__include='include' > > am__leading_dot='.' > > am__quote='' > > bindir='${exec_prefix}/bin' > > build='i686-pc-linux-gnu' > > build_alias='' > > build_cpu='i686' > > build_os='linux-gnu' > > build_vendor='pc' > > cgidir='${exec_prefix}/sbin' > > datadir='${prefix}/share' > > exec_prefix='${prefix}' > > host='i686-pc-linux-gnu' > > host_alias='' > > host_cpu='i686' > > host_os='linux-gnu' > > host_vendor='pc' > > includedir='${prefix}/include' > > infodir='${prefix}/info' > > install_sh='/root/perfparse-0.99.08/install-sh' > > libdir='${exec_prefix}/lib' > > libexecdir='${exec_prefix}/libexec' > > localstatedir='${prefix}/var' > > mandir='${prefix}/man' > > mkdir_p='mkdir -p -- .' > > oldincludedir='/usr/include' > > prefix='/usr/local' > > program_transform_name='s,x,x,' > > sbindir='${exec_prefix}/sbin' > > sharedstatedir='${prefix}/com' > > sysconfdir='${prefix}/etc' > > target='i686-pc-linux-gnu' > > target_alias='' > > target_cpu='i686' > > target_os='linux-gnu' > > target_vendor='pc' > > > > ## ----------- ## > > ## confdefs.h. ## > > ## ----------- ## > > > > #define HAVE_ALARM 1 > > #define HAVE_ATEXIT 1 > > #define HAVE_DLFCN_H 1 > > #define HAVE_INTTYPES_H 1 > > #define HAVE_MALLOC 1 > > #define HAVE_MEMORY_H 1 > > #define HAVE_MODF 1 > > #define HAVE_STDINT_H 1 > > #define HAVE_STDLIB_H 1 > > #define HAVE_STDLIB_H 1 > > #define HAVE_STDLIB_H 1 > > #define HAVE_STDLIB_H 1 > > #define HAVE_STRINGS_H 1 > > #define HAVE_STRING_H 1 > > #define HAVE_STRING_H 1 > > #define HAVE_STRSTR 1 > > #define HAVE_SYS_STAT_H 1 > > #define HAVE_SYS_TIME_H 1 > > #define HAVE_SYS_TYPES_H 1 > > #define HAVE_SYS_UTSNAME_H 1 > > #define HAVE_UNISTD_H 1 > > #define HAVE_UNISTD_H 1 > > #define HAVE_UNISTD_H 1 > > #define HAVE_VASPRINTF 1 > > #define HTTP_IMAGE_PATH "/nagios/images" > > #define OS_LINUX "1" > > #define PACKAGE "perfparse" > > #define PACKAGE_BUGREPORT "per...@cl..." > > #define PACKAGE_NAME "perfparse" > > #define PACKAGE_STRING "perfparse 0.99.08" > > #define PACKAGE_TARNAME "perfparse" > > #define PACKAGE_VERSION "0.99.08" > > #define RATE_DISPLAY "1" > > #define STDC_HEADERS 1 > > #define STDC_HEADERS 1 > > #define TIME_WITH_SYS_TIME 1 > > #define USE_DB_MYSQL 1 > > #define VERSION "0.99.08" > > #endif > > #ifdef __cplusplus > > extern "C" void std::exit (int) throw (); using std::exit; > > > > configure: exit 0 > > > > > ------------------------------------------------------- > SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media > 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 > Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. > http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 > _______________________________________________ > Perfparse-users mailing list > Per...@li... > https://lists.sourceforge.net/lists/listinfo/perfparse-users |
|
From: Ben C. <be...@cl...> - 2004-08-13 13:11:23
|
Paulo, Sorry for the delay. I have just got back from holiday and had a chance to look at the code. There is a bug, these values are the wrong way round. If you want to make a change now, please look at the file 'perfparse.c' at line 71. Change: #define TPERFDATA_MIN 0 #define TPERFDATA_MAX 1 #define TPERFDATA_WARN 2 #define TPERFDATA_CRIT 3 #define TPERFDATA_VALUE 4 Into: #define TPERFDATA_MIN 2 #define TPERFDATA_MAX 3 #define TPERFDATA_WARN 0 #define TPERFDATA_CRIT 1 #define TPERFDATA_VALUE 4 And recompile. This is untested. If you can verify that this does fix the problem, it would be helpful. :) I will get a new version when our other developer Yves is back from vacation sometime in next few days. Sorry for problems. Regards, Ben. Paulo Afonso Graner Fessel wrote: > I wasn't at the office today, so I'll try to describe what's happening. > > Here's for example one row of data took from perfdata_service_bin: > > +-----------+---------------------+--------+---------------------+---------+--------+----------+--------+ > | host_name | service_description | metric | ctime | > value | warn | critical | state | > +-----------+---------------------+--------+---------------------+---------+--------+----------+--------+ > | nagioslab | /dev/vg00/rootlv | / | 2004-07-23 14:35:10 | > 4822 | 0 | 10079 | 0 | > +-----------+---------------------+--------+---------------------+---------+--------+----------+--------+ > > On the other hand, take a look at the output of check_disk: > > [root@nagioslab libexec]# ./check_disk -w 15% -c 5% -p / > DISK OK - free space: / 4869 MB (48%);| /=5211MB;8567;9575;0;10079 > > The line recorded at serviceperf.log shows > > 1092398291 nagioslab /dev/vg00/rootlv DISK OK - free > space: / > 4869 MB (48%): OK /=5211MB;8567;9575;0;10079 > Seems that the values that are making into the database are minimum > (0) and maximum (10079) values instead of warning (10064) and critical > (10074) ones. My patched check_nt (that provides also perfdata > information) also provides evidence supporting this: > > [root@nagioslab libexec]# ./check_nt -H 10.4.8.135 -v USEDDISKSPACE -l c > -w 85% -c 95% > c:\ - total: 37.27 Gb - used: 7.31 Gb (20%) - free 29.96 Gb > (80%)|c=7.310GB;31.678;35.404;;37.268 > > Now, the line recorded at the database: > > +------------+---------------------------+--------+---------------------+---------+--------+----------+--------+ > | host_name | service_description | metric | ctime > | value | warn | critical | state | > +------------+---------------------------+--------+---------------------+---------+--------+----------+--------+ > | bradesk150 | Disco C: | c | 2004-07-23 15:09:11 > | 5.909 | 0 | 37.26 | 0 | > +------------+---------------------------+--------+---------------------+---------+--------+----------+--------+ > Again, we see that warn = 0 and critical =- 37.26, when the correct > information should have been warn = 31.68 and critical = 35.40. Also, as > you can see, both plugins provide output in the format you mentioned - > that is, 'label'=value[UOM];[warn];[crit];[min];[max]. > > TIA, > > Paulo Fessel > > "This is not right. This is not even wrong." (Wolfgang Pauli) > > > *Paulo Fessel* > /Administrador de Ambiente e Sistemas UNIX/ *PrimeSys Soluções > Empresariais* > Av. Brig. Faria Lima, 1485 - 13° andar > Torre Norte - Pinheiros > 01451-904 > São Paulo - SP > pau...@pr... <mailto:pau...@pr...> > tel: > fax: > mobile: +55 (11) 3038-6554 > +55 (11) 3038-6508 > +55 (11) 8259-0353 > > > > /Signature powered by Plaxo/ <http://www.plaxo.com/signature> /Want a > signature like this?/ <http://www.plaxo.com/signature> > > /Add me to your address book.../ > <https://www.plaxo.com/add_me?u=8590019246&v0=166225&k0=1601108562> > > > > ------------------------------------------------------------------------ > *De:* Cook, Garry [mailto:GW...@ma...] > *Enviada em:* quinta-feira, 12 de agosto de 2004 12:07 > *Para:* Paulo Afonso Graner Fessel; > per...@li... > *Assunto:* 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'=value[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ções > Empresariais* > Av. Brig. Faria Lima, 1485 - 13° andar > Torre Norte - Pinheiros > 01451-904 > São Paulo - SP > pau...@pr... <mailto:pau...@pr...> > tel: > fax: > mobile: +55 (11) 3038-6554 > +55 (11) 3038-6508 > +55 (11) 8259-0353 > > > > /Signature powered by Plaxo/ <http://www.plaxo.com/signature> > /Want a signature like this?/ <http://www.plaxo.com/signature> > > /Add me to your address book.../ > <https://www.plaxo.com/add_me?u=8590019246&v0=166225&k0=1601108562> > > |
|
From: Barry W. <ba...@if...> - 2004-08-13 10:12:16
|
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... |
|
From: Jaap H. <jaa...@ma...> - 2004-08-13 09:57:55
|
On Thu, 2004-08-12 at 18:10, Cook, Garry wrote: > OK, I'll take a look at it. If I can hack in the perfdata, I will, but > no guarantees. I've looked at some of the plugins that I want perfdata > for (check_snmp for example), and they are a little bit over my head. Same here. I ended up writing a wrapper script to run the plugin and reformat the output for check_snmp. It's a quick and dirty workaround, but let me know if you are interested. Jaap |
|
From: Steve F. <sf...@uc...> - 2004-08-12 21:41:57
|
I had PerfParse running quite nicely, then it stopped working when I turned off the mysql networking using the mysqld --skip-networking command line option. Is there any way to get mysql.sock file/pipe instead of the network interface? Thanks, -Steve ----- Steve Foley Scripps Institution of Oceanography sf...@uc..., (858) 822-3356 |
|
From: Jon L. <jly...@ya...> - 2004-08-12 17:15:27
|
Still can't get perfparse to compile completly, here's
the output from my configure,maybe I'm missing
something obvious, it builds on my Freebsd 5.2
machine, the only difference is that glib is an older
version and something about gcc3..
stats# ./configure
checking build system type... i386-unknown-freebsd4.10
checking host system type... i386-unknown-freebsd4.10
checking target system type...
i386-unknown-freebsd4.10
checking for a BSD-compatible install...
/usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... no
checking for nawk... nawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name...
a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler...
yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none
needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc
checking whether make sets $(MAKE)... (cached) yes
checking for a BSD-compatible install...
/usr/bin/install -c
checking for a sed that does not truncate output...
/usr/bin/sed
checking for egrep... grep -E
checking for ld used by gcc... /usr/libexec/elf/ld
checking if the linker (/usr/libexec/elf/ld) is GNU
ld... yes
checking for /usr/libexec/elf/ld option to reload
object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries...
pass_all
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... no
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler...
yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for f77... f77
checking whether we are using the GNU Fortran 77
compiler... yes
checking whether f77 accepts -g... yes
checking the maximum length of command line
arguments... 16384
checking command to parse /usr/bin/nm -B output from
gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc static flag works... yes
checking if gcc supports -fno-rtti -fno-exceptions...
yes
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/libexec/elf/ld)
supports shared libraries... yes
checking whether -lc should be explicitly linked in...
yes
checking dynamic linker characteristics... freebsd4.10
ld.so
checking how to hardcode library paths into
programs... immediate
checking whether stripping libraries is possible...
yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/libexec/elf/ld
checking if the linker (/usr/libexec/elf/ld) is GNU
ld... yes
checking whether the g++ linker (/usr/libexec/elf/ld)
supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/libexec/elf/ld)
supports shared libraries... yes
checking dynamic linker characteristics... freebsd4.10
ld.so
checking how to hardcode library paths into
programs... immediate
checking whether stripping libraries is possible...
yes
appending configuration tag "F77" to libtool
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for f77 option to produce PIC... -fPIC
checking if f77 PIC flag -fPIC works... yes
checking if f77 supports -c -o file.o... yes
checking whether the f77 linker (/usr/libexec/elf/ld)
supports shared libraries... yes
checking dynamic linker characteristics... freebsd4.10
ld.so
checking how to hardcode library paths into
programs... immediate
checking whether stripping libraries is possible...
yes
checking for pkg-config... /usr/local/bin/pkg-config
checking for GLIB - version >= 2.0.0... yes (version
2.4.0)
Using glib2
Using Mysql
checking for mysql_config...
/usr/local/bin/mysql_config
checking for ANSI C header files... (cached) yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for unistd.h... (cached) yes
checking sys/utsname.h usability... yes
checking sys/utsname.h presence... yes
checking for sys/utsname.h... yes
checking for an ANSI C-conforming const... yes
checking for pid_t... yes
checking whether struct tm is in sys/time.h or
time.h... time.h
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking whether time.h and sys/time.h may both be
included... yes
checking for stdlib.h... (cached) yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking for unistd.h... (cached) yes
checking for alarm... yes
checking for working mktime... no
checking for atexit... yes
checking for modf... yes
checking for pow... no
checking for strstr... yes
checking for vasprintf... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating libperfparse/Makefile
config.status: creating perfparse/Makefile
config.status: creating db_tools/Makefile
config.status: creating cgi/Makefile
config.status: creating images/Makefile
config.status: creating config/Makefile
config.status: creating contrib/Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
*****************************************************
Configuration options:
Prefix: /usr/local
HTTP path for images: /nagios/images
Installation path for images:
${datadir}/perfparse/images
Installation path for CGIs: ${exec_prefix}/sbin
Using glib2.0: 2.4.0
Database support: mysql
*****************************************************
WARNING WARNING WARNING WARNING WARNING WARNING
WARNING
CHANGE SINCE 0.99.04:
PLEASE CHECK THAT xpdfile_service_perfdata_template IN
nagios.cfg
HAS THE FOLLOWING CONTENT:
xpdfile_service_perfdata_template=$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$OUTPUT$\t$SERVICESTATE$\t$PERFDATA$
*****************************************************
__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail
|
|
From: Cook, G. <GW...@ma...> - 2004-08-12 16:32:21
|
This appears to be an add-on to Nagios, which includes a plugin. I've read through the docs a bit, and it looks like the check_traffic plugin gets bandwidth utilization data and stores it in and rrd database, similar to what MRTG does. Then you can graph the data stored in the rrds. I'm not sure why you would add perfdata to the plugin, unless you wanted to run the plugin separate from the rest of the add-on and use something else like perfparse for the graphs. Is this your intent? Either way, I don't use this plugin, so I can't really test it. From what I've seen it looks like it doesn't return output like a normal plugin does. I would contact the check_traffic developers and point them in the direction of the perfdata guidelines at http://nagiosplug.sourceforge.net/developer-guidelines.html#AEN185. Perhaps they can add it in for you. Garry W. Cook, CCNA Network Infrastructure Manager MACTEC, Inc. - http://www.mactec.com/ 303.308.6228 (Office) - 720.220.1862 (Mobile) Nate A. Smith wrote: > I am now getting graphs for memory usage, CPU load, and Disk space. > That's all I need. Here is the link for check_traffic from Nagios > extras page.=20 >=20 > http://nagios.sourceforge.net/download/contrib/misc/check_traffic/ >=20 > Thanks! > Nate >=20 > -----Original Message----- > From: Cook, Garry [mailto:GW...@ma...] > Sent: Thursday, August 12, 2004 11:03 AM > To: Nate A. Smith; per...@li... > Subject: RE: [Perfparse-users] Check_traffic >=20 > Nate A. Smith wrote: >> Does anyone have the check_traffic plugin graphing? >> Thanks so much on the check_nt graphs!! >> All seems to be working!! >>=20 >> Nate Smith >> Disetronic Medical Systems >> IT Support Consultant >=20 > That's great! I'm glad the check_nt plugin is working for you. As you > can see, it does not include perfdata for all of the different windows > checks. Do you check any of the ones that do not have perfdata? Do you > see a need for perfdata for those checks? As I mentioned in > the original > thread, I didn't see the use for perfdata on those, just wondering if > maybe I missed something important. >=20 > As for check_traffic, I'm not familiar with that plugin, and have not > yet been able to locate it in my plugins source or contrib > directories. Where is this plugin source located and what does it do? > I'll check an older source version, I'm currently working from plugins > 1.4.0alpha (CVS). >=20 > Garry W. Cook, CCNA > Network Infrastructure Manager > MACTEC, Inc. - http://www.mactec.com/ > 303.308.6228 (Office) - 720.220.1862 (Mobile) |
|
From: Cook, G. <GW...@ma...> - 2004-08-12 16:17:32
|
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 have = 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 >=20 > Thanks for quick response as always. > I'm using FC1 >=20 > The lines you specifed are as you said they should be but the > setlocale (LC_ALL, ""); line is line 105 not 110. >=20 > Thanks >=20 > 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 database >=20 >=20 >> 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? >>=20 >> setlocale (LC_ALL, ""); >> bindtextdomain (PACKAGE, LOCALEDIR); >> textdomain (PACKAGE); >>=20 >> if(process_arguments(argc,argv)=3D=3DERROR) >> usage(_("Could not parse arguments\n")); >>=20 >> If not, they should. Let me know. Thanks. >>=20 >> Garry W. Cook, CCNA >> Network Infrastructure Manager >> MACTEC, Inc. - http://www.mactec.com/ >> 303.308.6228 (Office) - 720.220.1862 (Mobile) >>=20 >> Barry Weeks wrote: >>> Hi Gary / All >>>=20 >>> check_nt will not compile for me see below >>>=20 >>> 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': =20 >>> 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':=20 >>> 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': =20 >>> 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=20 >>>=20 >>> 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=20 >>>=20 >>>=20 >>> 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'?=20 >>>=20 >>> 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.=20 >>>=20 >>> 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 >>>=20 >>>=20 >>> Hello, folks. >>>=20 >>> 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".=20 >>>=20 >>> 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? >>>=20 >>> []'s >>> Paulo Fessel >>>=20 >>> "This is not right. This is not even wrong." (Wolfgang Pauli) >>>=20 >>> 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 >>>=20 >>>=20 >>>=20 >>>=20 >>> Signature powered by PlaxoWant a signature like this? >>>=20 >>> Add me to your address book... |
34 messages has been excluded from this view by a project administrator.
