<div>hi all,</div> <div> </div> <div>in responce to Mark's comment of:</div> <div>Also, it's not going to hurt, but you don't really need to say "/usr/bin/perl /usr/share/nagios/nagiosgraph/insert.pl" as long as insert.pl is executable and has "#!/usr/bin/perl" as the first line. </div> <div> </div> <div>Acctually it may hurt. There was a thread in the Nagiosplugin Help mailing list this week that discussed this.</div> <div> </div> <div>if the insert.pl is called without the /usr/bin/perl and Embedded Perl is enabled then the Embedded perl will run the script despite the #! on the first line of the script. This may cause the script to not work. likewise with the /usr/bin/perl in the command then it will always use the External Perl. </div> <div> </div> <div>If Embedded Perl was not compiled into the Nagios install, then what you say would be completly true.</div> <div> Tony </div> <div>On 4/13/07, Frost, Mark {PBG} <<a href="mailto:mark.frost1@pepsi.com">mark.frost1@pepsi.com</a>> wrote: <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Michael, I assume you've checked and made sure that no *.rrd files are being generated? Perhaps it is running, but emptying that file out so quickly that you never catch it when it has data in it? I found that was happening to me at one point, but I could see that I was getting new/updated *.rrd files in my rrd directory for nagiosgraph. You could also try running "watch" (if it's available on your platform) to monitor the contents of the perfdata.log file to see if anything ever really does go in there ("watch -d cat perfdata.log"). Also, it's not going to hurt, but you don't really need to say "/usr/bin/perl /usr/share/nagios/nagiosgraph/insert.pl" as long as insert.pl is executable and has "#!/usr/bin/perl" as the first line. Mark -----Original Message----- From: <a href="mailto:nagios-users-bounces@lists.sourceforge.net"> nagios-users-bounces@lists.sourceforge.net</a> [mailto:<a href="mailto:nagios-users-bounces@lists.sourceforge.net">nagios-users-bounces@lists.sourceforge.net</a>] On Behalf Of Weiner, Michael Sent: Friday, April 13, 2007 2:42 PM To: <a href="mailto:nagios-users@lists.sourceforge.net">nagios-users@lists.sourceforge.net</a> Subject: [Nagios-users] perfdata Using Nagios 2.8 and I am not sure what I am doing wrong. Been trying to squeeze out some perfdata in order to test nagiosgraph and I get Nagios to create the file, but it remains empty no matter what occurs. Here are the relevant portions of my nagios.cfg for clarification: nagios.cfg: perfdata_timeout=5 process_performance_data=1 #service_perfdata_command=process-service-perfdata service_perfdata_file=/var/spool/nagios/perfdata.log service_perfdata_file_template=$LASTSERVICECHECK$||$HOSTNAME$||$SERVICED ESC$||$SERVICEOUTPUT$||$SERVICEPERFDATA$ service_perfdata_file_mode=a <-- had this set to w based on a previous email, but that didn't seem to do anything service_perfdata_file_processing_interval=30 service_perfdata_file_processing_command=process-service-perfdata checkcommands.cfg: define command{ command_name process-service-perfdata command_line /usr/bin/perl /usr/share/nagios/nagiosgraph/insert.pl } I just can NOT seem to get anything written to the perfdata.log file although nagios DOES create it upon (re)start. Any thoughts? Michael Weiner | Lead Analyst | Lerner Research Institute Cleveland Clinic | 9500 Euclid Ave. | Cleveland, OH 44195 | (216) 445-6454 Cleveland Clinic is ranked one of the top 3 hospitals in America by U.S.News & World Report. Visit us online at <a href="http://www.clevelandclinic.org">http://www.clevelandclinic.org</a> for a complete listing of our services, staff and locations. Confidentiality Note: This message is intended for use only by the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. Thank you. =================================== ------------------------------------------------------------------------ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash <a href="http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE">http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE </a> V _______________________________________________ Nagios-users mailing list <a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a> <a href="https://lists.sourceforge.net/lists/listinfo/nagios-users"> https://lists.sourceforge.net/lists/listinfo/nagios-users</a> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash <a href="http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV">http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV </a> _______________________________________________ Nagios-users mailing list <a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a> <a href="https://lists.sourceforge.net/lists/listinfo/nagios-users"> https://lists.sourceforge.net/lists/listinfo/nagios-users</a> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null </blockquote></div>