From: Keith E. <ka...@mi...> - 2005-05-30 00:20:29
|
Hi I've written a check_sensor Nagios plugin that returns performance data for lm_sensors (e.g., fan speeds, temperatures, voltages). I'm just testing it at the moment, and it works fine if the label does not have embedded spaces. However, if there are embedded spaces then no graph is plotted. A simple example - the following is returned, but no graph appears: SENSOR OK: M/B Temp value is 44|'M/B Temp'=44;;;; That seems to be valid performance data according to http://nagiosplug.sourceforge.net/developer-guidelines.html#AEN142, but if it's not please correct me. Otherwise this would appear to be a bug in PerfParse. I'm using Nagios 1.2 and PerfParse V0.105.6. Thanks Keith |
From: Yves <yme...@pe...> - 2005-05-30 08:12:40
|
Hi, If you made no strange things, it looks like a bug. Not respecting http://nagiosplug.sourceforge.net/developer-guidelines.html#AEN142 in the= parsing is a bug in perfparse. Do you have additionnal things in the log to help us in finding and fixin= g that bug ? Yves > Hi > > I've written a check_sensor Nagios plugin that returns performance data > for lm_sensors (e.g., fan speeds, temperatures, voltages). I'm just > testing it at the moment, and it works fine if the label does not have > embedded spaces. However, if there are embedded spaces then no graph is > plotted. > > A simple example - the following is returned, but no graph appears: > > SENSOR OK: M/B Temp value is 44|'M/B Temp'=3D44;;;; > > That seems to be valid performance data according to > http://nagiosplug.sourceforge.net/developer-guidelines.html#AEN142, but > if it's not please correct me. Otherwise this would appear to be a bug > in PerfParse. I'm using Nagios 1.2 and PerfParse V0.105.6. > > Thanks > Keith > > > ------------------------------------------------------- > This SF.Net email is sponsored by Yahoo. > Introducing Yahoo! Search Developer Network - Create apps using Yahoo! > Search APIs Find out how you can build Yahoo! directly into your own > Applications - visit http://developer.yahoo.net/?fr=3Doffad-ysdn-ostg-q= 22005 > _______________________________________________ > 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/ - - Perfparse - http://www.perfparse.org/ - |
From: Keith E. <ke...@mi...> - 2005-05-30 11:07:36
|
Hi Yves Yves wrote: > If you made no strange things, it looks like a bug. Not respecting > http://nagiosplug.sourceforge.net/developer-guidelines.html#AEN142 in > the parsing is a bug in perfparse. I believe that my output conforms to the specification - here's another sample line in case anyone wants to point out where it doesn't conform [:-)]: SENSOR warning: CPU Temp value is 48|'CPU Temp'=48;45;60;30;100 > Do you have additionnal things in the log to help us in finding and > fixing that bug ? I don't think so. I'm using the infamous "Method 4" of piping the output to perfparsed, and the perfparsed log file has nothing of interest: ======================================================================= 2005/05/30 11:54:28 [perfparsed.c:176 26598 ] Perfparsed successfully daemonized (pid=26598) 2005/05/30 11:54:28 [ storage.c:95 26598 ] storage_mysql module successfully loaded 2005/05/30 11:54:29 [ storage.c:264 26602 ] Perfparsed : periodic cleanup 2005/05/30 11:54:29 [clean_tools.c:101 26602 ] Could not open directory '/tmp/perfparse.drop' ======================================================================= Yves, do you have the 'sensors' command on your system? If so, I'll happily send you a copy of my beta check_sensor plugin for you to test if you wish. In fact, I'm happy to make this available to others to test - contact me offlist if you'd like to do so. It's for Linux/BSD/etc systems only, and you will need lm_sensors installed and working. -- Keith Edmunds +---------------------------------------------------------------------+ | Tiger Computing Ltd | Helping businesses make the most of Linux | | "The Linux Company" | http://www.TheLinuxConsultancy.co.uk | +---------------------------------------------------------------------+ |
From: Ben C. <bcl...@pe...> - 2005-05-31 07:40:27
|
Please check nagio.cfg, find this: # ILLEGAL MACRO OUTPUT CHARACTERS illegal_macro_output_chars=`~$&|'"<> Change to: illegal_macro_output_chars=`~$&|"<> Please let us know if this helps. Ben Keith Edmunds wrote: > Hi Yves > > Yves wrote: > >> If you made no strange things, it looks like a bug. Not respecting >> http://nagiosplug.sourceforge.net/developer-guidelines.html#AEN142 in >> the parsing is a bug in perfparse. > > > I believe that my output conforms to the specification - here's another > sample line in case anyone wants to point out where it doesn't conform > [:-)]: > > SENSOR warning: CPU Temp value is 48|'CPU Temp'=48;45;60;30;100 > >> Do you have additionnal things in the log to help us in finding and >> fixing that bug ? > > > I don't think so. I'm using the infamous "Method 4" of piping the output > to perfparsed, and the perfparsed log file has nothing of interest: > > ======================================================================= > 2005/05/30 11:54:28 [perfparsed.c:176 26598 ] Perfparsed successfully > daemonized (pid=26598) > 2005/05/30 11:54:28 [ storage.c:95 26598 ] storage_mysql module > successfully loaded > 2005/05/30 11:54:29 [ storage.c:264 26602 ] Perfparsed : periodic > cleanup > 2005/05/30 11:54:29 [clean_tools.c:101 26602 ] Could not open > directory '/tmp/perfparse.drop' > ======================================================================= > > Yves, do you have the 'sensors' command on your system? If so, I'll > happily send you a copy of my beta check_sensor plugin for you to test > if you wish. > > In fact, I'm happy to make this available to others to test - contact me > offlist if you'd like to do so. It's for Linux/BSD/etc systems only, and > you will need lm_sensors installed and working. > |
From: Keith E. <ke...@mi...> - 2005-05-31 11:53:58
|
Ben Clewett wrote: > Please check nagio.cfg, find this: > > # ILLEGAL MACRO OUTPUT CHARACTERS > illegal_macro_output_chars=`~$&|'"<> > > Change to: > > illegal_macro_output_chars=`~$&|"<> > > Please let us know if this helps. Yes, that fixed the problem, thank you very much. That would seem to indicate that the problem is, in fact, caused by Nagios - would you agree? Many thanks for your suggestion. Keith -- Keith Edmunds +---------------------------------------------------------------------+ | Tiger Computing Ltd | Helping businesses make the most of Linux | | "The Linux Company" | http://www.TheLinuxConsultancy.co.uk | +---------------------------------------------------------------------+ |
From: Yves <yme...@pe...> - 2005-05-31 12:19:20
|
> Ben Clewett wrote: > > Please check nagio.cfg, find this: > > > > # ILLEGAL MACRO OUTPUT CHARACTERS > > illegal_macro_output_chars=3D`~$&|'"<> > > > > Change to: > > > > illegal_macro_output_chars=3D`~$&|"<> > > > > Please let us know if this helps. > > Yes, that fixed the problem, thank you very much. That would seem to > indicate that the problem is, in fact, caused by Nagios - would you agr= ee? Yes. Maybe this should be documented as a Frequently Asked Question ? I suggest here : http://wiki.perfparse.org/tiki-view_faq.php?faqId=3D8 Yves --=20 - Homepage - http://ymettier.free.fr - http://www.logicacmg.com - - GPG key - http://ymettier.free.fr/gpg.txt - - Maitretarot - http://www.nongnu.org/maitretarot/ - - Perfparse - http://www.perfparse.org/ - |
From: Ben C. <be...@ro...> - 2005-05-31 12:42:48
|
Done. Yves wrote: >>Ben Clewett wrote: >> > Please check nagio.cfg, find this: >> > >> > # ILLEGAL MACRO OUTPUT CHARACTERS >> > illegal_macro_output_chars=`~$&|'"<> >> > >> > Change to: >> > >> > illegal_macro_output_chars=`~$&|"<> >> > >> > Please let us know if this helps. >> >>Yes, that fixed the problem, thank you very much. That would seem to >>indicate that the problem is, in fact, caused by Nagios - would you agree? > > > Yes. > Maybe this should be documented as a Frequently Asked Question ? > I suggest here : http://wiki.perfparse.org/tiki-view_faq.php?faqId=8 > > Yves |
From: Keith E. <ke...@mi...> - 2005-05-31 12:32:43
|
Yves wrote: > Maybe this should be documented as a Frequently Asked Question ? > I suggest here : http://wiki.perfparse.org/tiki-view_faq.php?faqId=8 Added (although it hasn't appeared yet). Should this also be reported to Nagios and, if so, who will do that (let's not all assume someone else will do it)? Finally, meant constructively: I find the perfparsed wiki hard to use and hard to find information. I'm a big fan of Wikis; are there any plans to change it at all? -- Keith Edmunds +---------------------------------------------------------------------+ | Tiger Computing Ltd | Helping businesses make the most of Linux | | "The Linux Company" | http://www.TheLinuxConsultancy.co.uk | +---------------------------------------------------------------------+ |
From: Yves <yme...@pe...> - 2005-05-31 13:09:49
|
> Yves wrote: >> Maybe this should be documented as a Frequently Asked Question ? >> I suggest here : http://wiki.perfparse.org/tiki-view_faq.php?faqId=3D8 > > Added (although it hasn't appeared yet). Thanks :) > Should this also be reported to Nagios and, if so, who will do that > (let's not all assume someone else will do it)? Is this a bug in Nagios ? Or only misconfiguration ? If you consider it i= s a bug, there is a mailing-list where some should listen to you : nagios-devel (http://www.nagios.org/support/mailinglists.php) I have no opinion on that one. > Finally, meant constructively: I find the perfparsed wiki hard to use > and hard to find information. I'm a big fan of Wikis; are there any > plans to change it at all? Well, we are all busy, and if you have ideas and time to help, maybe you = want to join the (small) community ? :) Yves --=20 - Homepage - http://ymettier.free.fr - http://www.logicacmg.com - - GPG key - http://ymettier.free.fr/gpg.txt - - Maitretarot - http://www.nongnu.org/maitretarot/ - - Perfparse - http://www.perfparse.org/ - |
From: Flo G. <fl...@bi...> - 2005-05-31 13:12:28
|
On Tue, 31 May 2005, Keith Edmunds wrote: > > Finally, meant constructively: I find the perfparsed wiki hard to use and > hard to find information. I'm a big fan of Wikis; are there any plans to > change it at all? > > -- > Keith Edmunds > Hehe, i wrote parts of the wiki software and i'm writing a php UI for perfparse at the moment. So you'll have to stick with tikiwiki :-) But constructively: once registered to the wiki, you can unassign the modules (boxes) at the left and right bar and then the wiki gets more simple looking. With http://wiki.perfparse.org/tiki-user_assigned_modules.php you then can reassign the modules if you want them back. Flo |
From: Yves <yme...@pe...> - 2005-05-31 13:40:15
|
I changed the subject of the thread... Should this talk move to perfparse-devel or perfparse-devel-int list to a= void the pollution of perfparse-users ? > But constructively: once registered to the wiki, you can unassign the > modules (boxes) at the left and right bar and then the wiki gets more > simple looking. With > http://wiki.perfparse.org/tiki-user_assigned_modules.php > you then can reassign the modules if you want them back. Flo, can you define the default for new users in a way they have the mini= mum boxes and don't get confused with useless boxes ? Then they can add boxes with the = preferences. Maybe Keith can also make interesting comments on how to improve tiki-wik= i ? Maybe Keith can also give some help to make a better-looking web site (we= have www.perfparse.org and wiki.perfparse.org : isn't there one useless ? :) Why do some sites based on wikis (the best example I know is wikipedia) d= o have a nice look and why does wiki.perfparse.org look like a web portal ? :) Well, this is just my opinion, don't take it as more than my opinion :) Yves --=20 - Homepage - http://ymettier.free.fr - http://www.logicacmg.com - - GPG key - http://ymettier.free.fr/gpg.txt - - Maitretarot - http://www.nongnu.org/maitretarot/ - - Perfparse - http://www.perfparse.org/ - |