Thanks for the help , but managed to solve the issue . The problem was that the pnp4 was looking in the wrong place for the rrd data provided by nagios .
Once i fixed the paths - the graph resumed their work. Thanks for the "nudge" . Assaf Guy Waugh wrote: > Hi Assaf, > > Have you restarted nagios lately? > > Have the permissions on the pnp4nagios files (or the directory they > reside in) changed? > > Has anything changed in nagios.cfg that might affect this? > > How are you running pnp4nagios? Synchronous mode, bulk mode or bulk > mode with NPCD? Are the nagios perfdata files being populated > correctly etc.? > > Cheers, > Guy. > > On 9 June 2010 14:14, Assaf Flatto <nag...@flatto.net > <mailto:nag...@flatto.net>> wrote: > > Assaf Flatto wrote: > > Hello All > > > > Not sure this is the right place for this - but since many of us use > > pnp4nagios - i thought i might be able to get some advice , I've > > installed pnp4nagios and it worked well for more then a month , > but now > > it seem it no longer generating graphs for any of the existing > checks. > > > > I can see in the nagios debug file that the pnp script is > executed , > > and hence i was expecting the xml to be generated . > > When i execute the script manually - perl -d > > /usr/local/pnp4nagios/libexec/process_perfdata.pl > <http://process_perfdata.pl/> , i get the following > > perl error output , which is what i think stops my graphs from being > > created. > > > > Anyone ever encountered this issue ? or know whom/where i should > post > > this query at ? > > > > Thanks > > > > Assaf > > > > > > Use of uninitialized value in concatenation (.) or string at > > /usr/local/pnp4nagios/libexec/process_perfdata.pl > <http://process_perfdata.pl/> line 1098. > > at /usr/local/pnp4nagios/libexec/process_perfdata.pl > <http://process_perfdata.pl/> line 1098 > > main::handle_signal('ALRM') called at (eval > > > > 10)[/usr/lib/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/Term/ReadKey.pm:411] > > line 7 > > eval {...} called at (eval > > > > 10)[/usr/lib/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/Term/ReadKey.pm:411] > > line 7 > > Term::ReadKey::ReadKey(0, 'GLOB(0x7aea60)') called at > > /usr/lib/perl5/site_perl/5.8.8/Term/ReadLine/readline.pm > <http://readline.pm/> line 2086 > > readline::rl_getc called at > > /usr/lib/perl5/site_perl/5.8.8/Term/ReadLine/readline.pm > <http://readline.pm/> line 2073 > > readline::getc_with_pending() called at > > /usr/lib/perl5/site_perl/5.8.8/Term/ReadLine/readline.pm > <http://readline.pm/> line 1649 > > readline::readline(' DB<1> ') called at > > /usr/lib/perl5/site_perl/5.8.8/Term/ReadLine/Perl.pm line 11 > > > > > Term::ReadLine::Perl::readline('Term::ReadLine::Perl=ARRAY(0xc242c0)', > > ' DB<1> ') called at /usr/lib/perl5/5.8.8/perl5db.pl > <http://perl5db.pl/> line 6371 > > DB::readline(' DB<1> ') called at > > /usr/lib/perl5/5.8.8/perl5db.pl <http://perl5db.pl/> line 2203 > > DB::DB called at /usr/lib/perl5/5.8.8/perl5db.pl > <http://perl5db.pl/> line 9425 > > DB::fake::at_exit() called at > /usr/lib/perl5/5.8.8/perl5db.pl <http://perl5db.pl/> > > line 8997 > > DB::END() called at > > /usr/local/pnp4nagios/libexec/process_perfdata.pl > <http://process_perfdata.pl/> line 0 > > eval {...} called at > > /usr/local/pnp4nagios/libexec/process_perfdata.pl > <http://process_perfdata.pl/> line 0 > > Use of uninitialized value in concatenation (.) or string at > > /usr/local/pnp4nagios/libexec/process_perfdata.pl > <http://process_perfdata.pl/> line 1098. > > at /usr/local/pnp4nagios/libexec/process_perfdata.pl > <http://process_perfdata.pl/> line 1098 > > main::handle_signal('ALRM') called at (eval > > > > 10)[/usr/lib/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/Term/ReadKey.pm:411] > > line 7 > > eval {...} called at (eval > > > > 10)[/usr/lib/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/Term/ReadKey.pm:411] > > line 7 > > Term::ReadKey::ReadKey(0, 'GLOB(0x7aea60)') called at > > /usr/lib/perl5/site_perl/5.8.8/Term/ReadLine/readline.pm > <http://readline.pm/> line 2086 > > readline::rl_getc called at > > /usr/lib/perl5/site_perl/5.8.8/Term/ReadLine/readline.pm > <http://readline.pm/> line 2073 > > readline::getc_with_pending() called at > > /usr/lib/perl5/site_perl/5.8.8/Term/ReadLine/readline.pm > <http://readline.pm/> line 1649 > > readline::readline(' DB<1> ') called at > > /usr/lib/perl5/site_perl/5.8.8/Term/ReadLine/Perl.pm line 11 > > > > > Term::ReadLine::Perl::readline('Term::ReadLine::Perl=ARRAY(0xc242c0)', > > ' DB<1> ') called at /usr/lib/perl5/5.8.8/perl5db.pl > <http://perl5db.pl/> line 6371 > > DB::readline(' DB<1> ') called at > > /usr/lib/perl5/5.8.8/perl5db.pl <http://perl5db.pl/> line 2203 > > DB::DB called at /usr/lib/perl5/5.8.8/perl5db.pl > <http://perl5db.pl/> line 9425 > > DB::fake::at_exit() called at > /usr/lib/perl5/5.8.8/perl5db.pl <http://perl5db.pl/> > > line 8997 > > DB::END() called at > > /usr/local/pnp4nagios/libexec/process_perfdata.pl > <http://process_perfdata.pl/> line 0 > > eval {...} called at > > /usr/local/pnp4nagios/libexec/process_perfdata.pl > <http://process_perfdata.pl/> line 0 > > > > > Maybe more information that may help in this case - > > the perfdata.log has a repeated entry : > 2010-06-09 10:17:25 [19819] [0] *** TIMEOUT: Timeout after 5 Sec. **** > 2010-06-09 10:17:25 [19819] [0] *** process_perfdata.pl > <http://process_perfdata.pl/> terminated on > signal ALRM > > -- Never,Ever Cut A Deal With a Dragon I am doing a Charity Bike ride On the 27 of June for the Capital to Coast Charity. Please help by Donating http://www.justgiving.com/Lovefilm-capital-to-coast ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null