Nagiosgraph graphs have gaps

Steve Burton steve at sliderule.demon.co.uk
Mon Dec 8 11:03:28 CET 2008


Steve Burton wrote:
>> Hi Hugo,
>>     
>
>   
>> Thanks for the reply I am also facing the same issue. 
>>     
>
>   
>> As per you suggestion I have gone through the archieve and found one big
>> thread regarding Nagios graph gap.
>>     
>
>   
>> https://sourceforge.net/mailarchive/message.php?msg_id=007301c84e20$4def
>> 0850$98ad38a6 at na.dsmain.com
>>     
>
>   
>> In the thread the working solution as per people is but when I went
>> through the it then found 
>> We need to make change in ngraph.ncfg but in current nagiosgraph there
>> is no such file.
>>     
>
>   
>> Pls guide how to solve graph this gap issue.
>>     
>
>   
>> In my machine heartbeat is 600 sec and perf_file_iterval is 60 sec.
>>     
>
>   
>> thanks
>>     
>
>   
>> ==================================================
>> Hi,
>>     
>
>   
>> the old NagiosGrapher interfaces (network/pipe) can cause huge
>> latency :-(. Thanks to a patch we got there is a new interface type
>> "file". The main advantages of this new interface are:
>> * no gaps any more
>> * no latency caused by NagiosGrapher
>> * restarting NagiosGrapher does not cause any gaps
>>     
>
>   
>> I am sorry but the documentation totally lacks this interface. But below
>> is all you need.
>>     
>
>   
>> Cheers,
>>     
>
>   
>> Gerd
>>     
>
>
>
>
>   
>> =20
>> ngraph.ncfg:
>>     
>
>   
>> interface file
>> perffile_path /dev/shm
>>     
>
>   
>> nagios.cfg:
>>     
>
>   
>> process_performance_data=1
>> service_perfdata_file=/dev//shm/service-perfdata
>> service_perfdata_file_template=$HOSTNAME$\t$SERVICEDESC$\t$SERVICEOUTPUT
>> $\t$SERVICEPERFDATA$\t$TIMET$
>> service_perfdata_file_mode=a
>> service_perfdata_file_processing_interval=60
>>     
>
>   
>> service_perfdata_file_processing_command=3Dprocess-service-perfdata-file
>>     
>
>
>   
>> commands.cfg:
>> define command{
>> command_name process-service-perfdata-file
>> command_line
>> mv /dev/shm/service-perfdata /dev/shm/service-perfdata.$TIMET$
>> }
>> ==================================================
>>     
>
>
>
>   
>> Thanks & Regards
>> Novin Jaiswal
>> Ishi Systems Inc.
>> 201-521-3155(Direct)
>> 732-318-8156(Cell)
>>     
>
>
>
>   
>> -----Original Message-----
>> From: Hugo van der Kooij [mailto:hvdkooij at vanderkooij.org] 
>> Sent: Sunday, November 30, 2008 2:44 AM
>> To: Nagios Users Mailinglist
>> Subject: Re: [Nagios-users] Nagiosgraph graphs have gaps
>>     
>
>   
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>     
>
>   
>> Steve Burton wrote:
>>     
>>> Hi,
>>>
>>> I  have  nagios  3.0.4 running on FreeBSD and I'm using nagiosgraph to
>>> generate  rrd's  on  the  data.  I'm  visualizing  the  data with both
>>> nagiosgraph and drraw.
>>>
>>> My  problem  is that the graphs have gaps so I guessing that the rrd's
>>> are  not  being  updated.  I'm  concentrating  on just one service for
>>> debugging   and   I've  run  the  plugin  (which  I  wrote)  from  the
>>> command-line  many times for a local server and I haven't seen it fail
>>> to  connect  or  report  or to time out. It is as though nagios is not
>>> checking  the service within the heartbeat of the rrd's in question. I
>>> have  set  the service check interval to 5 minutes, which I believe to
>>> be  the  default nagiosgraph step time and the heartbeat is set to the
>>> nagiosgraph default of 600 seconds.
>>>
>>> Can anyone advise me if if this is likely to be the problem and if not
>>> how I can diagnose what is actually going on?
>>>       
>
>   
>> I have put a diagnose on the mailinglist for something that is either
>> the same problem or something similar.
>>     
>
>   
>> The problem is that nagios can send several commands into the pipe at
>> once and the other end will only pick up one of them. So the RRD info is
>> not written. The work around is not to allow Nagios to run things in
>> parallel. But it will severly limit the amount of hosts and services one
>> can check with Nagios.
>>     
>
>   
>> This should have been fixed by using the file interface instead of the
>> named pipe. The file interface was introduced about a year ago or even
>> longer back.
>>     
>
>   
>> Please check the mailinglist archives for more details.
>>     
>
>   
>> Hugo.
>>     
>
> This seems to refer to nagiosgrapher, see:
> http://www.nagiosexchange.org/cgi-bin/pages/Detailed/1659.html
>
> whereas I'm trying to set up nagiosgraph, see:
>
> http://www.nagiosexchange.org/cgi-bin/pages/Detailed/1501.html
>
> Steve.
>
>
> ------------------------------------------------------------------------------
> SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
> The future of the web can't happen without you.  Join us at MIX09 to help
> pave the way to the Next Web now. Learn more and register at
> http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at 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
>
>   
It was me, mea culpa (or as they say in Seattle, my bad).

Everything I tried pointed to Nagios not checking hosts and services on 
a regular basis but I *knew* that it doesn't do that!
Eventually, I looked at my config files.
The first giveaway was in the header  'NAGIOS.CFG - Sample Main Config 
File for Nagios 1.0b6'
Intrigued, I read on and there, buried halfway down, I found 
'max_concurrent_checks=10'. This must have been in there for years and 
it's a tribute to Nagios (and Ethan) that it has been working correctly 
until I imposed the extra load  (another 100 or so services).
I have re-written nagios.cfg and I'm working on the rest of the config.

Sorry, for all the noise and thanks for all the help I received. I have 
certainly learned a lot from this.

Steve.




______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Nagios-users mailing list
Nagios-users at 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





More information about the Users mailing list