Re: [Nagios-users] benchmark question

2009-12-14 Thread Fulton, David
Do you have another box? I don't know of much of, if any, of an
advantage to running multiple instances. The SMP will usually not help
there because the other cores will be occupied executing plug-ins.  If
you had another box you could go with a distributed environment instead.
Perhaps using SVN to keep record of config changes.

 

From: shadih rahman [mailto:shadhi...@gmail.com] 
Sent: Monday, December 14, 2009 9:54 AM
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] benchmark question

 

List,
   Is there any information as to what is the maximum number of services
one can run on a single box with single instance of Nagios?  I did not
find any concrete data on this.

I am running a single instance of nagios on a quad core 2.5 GHZ machine
with with 4 Gigs of RAM.  

I have total of 7359 service check running on this box.  I have also
ndoutils running on the same box as backend.  

My total service checks is going to five fold very soon with a lot of
nrpe checks.  

Now, my question is should I run multiple instance of nagios on the same
box or a single instance will be able to handle about 3 service
checks?

I already tested a dev environment with multiple instance of nagios with
some hacking to init.d script, it started and monitored fine.  What
would be the preferred method of running nagios, single instance on a
box or multiple instance on a box when we are dealing with high number
of service checks?   

Please comment on this.  Thanks

-- 
Cordially,
Shadhin Rahman



This email and any attachments ("Message") may contain legally privileged 
and/or confidential information.  If you are not the addressee, or if this 
Message has been addressed to you in error, you are not authorized to read, 
copy, or distribute it, and we ask that you please delete it (including all 
copies) and notify the sender by return email.  Delivery of this Message to any 
person other than the intended recipient(s) shall not be deemed a waiver of 
confidentiality and/or a privilege.
--
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
___
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

Re: [Nagios-users] Help - I am unable to send notifications

2008-07-22 Thread Fulton, David

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf 
> Of jonathan williams
> Sent: Tuesday, July 22, 2008 2:36 PM
> To: Marc Powell
> Cc: Nagios User list
> Subject: Re: [Nagios-users] Help - I am unable to send notifications
> 
> 
> On Tue, 2008-07-22 at 11:14 -0700, Marc Powell wrote:
> > 
> > On Jul 22, 2008, at 12:26 PM, jonathan williams wrote:
> > >>
> > 
> > >> Umm..what can I say?  Wow.  OK.. I fixed that in the 
> send_mail.pl 
> > >> file.  Any other steps I need to take once I did that to make it 
> > >> work.
> > >> I did re-run the sed-i command and still get the same error:
> > >
> > 
> > Not unless you experience further errors.
> > 
> > > [EMAIL PROTECTED]:/usr/local/nagios/libexec# sed -i 
> '1s,.*,#!/usr/bin/ 
> > > perl -w,' check_sendmail.pl
> > > sed: can't read check_sendmail.pl: No such file or directory
> > 
> > Ok. sed 101.
> > 
> > sed -i '1s,.*,#!/usr/bin/perl -w,' check_sendmail.pl
> > 
> > The above is a sed 1-liner. It performs an immediate action 
> and then 
> > exits. What action? Let's break it down --
> > 
> > sed : this is the command to be executed -i : this tells 
> sed that it's 
> > going to be editing an existing file 1s : the start of the 
> actual sed 
> > script. This means we're going to be doing 1 substitution
> > .* : this is what we're going to be looking for, essentially any 
> > content on the line #!/usr/bin/perl -w : what the previous 
> match will 
> > be replaced with check_sendmail.pl : The file that sed is 
> going to be 
> > editing
> > 
> > The end result is that sed would replace the entire first 
> line of the 
> > file check_sendmail.pl, located in your current directory, with the 
> > text '#!/usr/bin/perl -w'.
> > 
> > Your confusion is that the filename should have been check_mail.pl, 
> > not check_sendmail.pl.
> > 
> > --
> > Marc
> > 
> 
> 
> Thank you for that breakdown.  
> 
> I am still having the same error in my nagios.log:
> 
> "[1216749581] SERVICE NOTIFICATION:
> nagiosadmin;jwilliamspc;PrintSpooler;OK;service-notify-by-emai
l;Spooler:
> Started
> [1216749581] Warning: Attempting to execute the command 
> "/usr/local/nagios/libexec/send_mail.pl -n "SERVICE RECOVERY" 
-h "jwilliamspc" -s "OK" -a "10.10.113.51" -i "PrintSpooler - > Spooler:
> Started - check_nt!SERVICESTATE!-d SHOWALL -l Spooler" -d "Tue Jul 22
> 10:59:41 PDT 2008" -e "[EMAIL PROTECTED]"" 
> resulted in a return code of 126.  Make sure the script or 
> binary you are trying to execute actually exists..."
> 
> The top line in the send_mail.pl script is indeed 
> "#!/usr/bin/perl -w".
> I am not sure what it does though.  Doesn't the # mean it is remarked?
> I guess my confusion is that there is no such file on my 
> system called check_sendmail.pl or check_mail.pl.  I was 
> unable to locate any of them.
> There is only a check_mailq.  That is why when you state:
> 
> #!/usr/bin/perl -w : what the previous match will be replaced with
> > check_sendmail.pl : The file that sed is going to be editing
> > 
> > The end result is that sed would replace the entire first 
> line of the 
> > file check_sendmail.pl, located in your current directory, with the 
> > text '#!/usr/bin/perl -w'.
> > 
> > Your confusion is that the filename should have been check_mail.pl, 
> > not check_sendmail.pl.
> 
> I get lost.

As Marc broke down the sed line I will break down the line above, the #
character is indeed a comment character, but only to PERL. PERL is not
what tries to load the file initially, the shell tries to load the file
as a compiled program(like /bin/ls is the compiled program that lists
the files in a directory: I ran this on my nagios server as an example):

[EMAIL PROTECTED] nagios]$ file /bin/ls
/bin/ls: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for
GNU/Linux 2.4.0, dynamically linked (uses shared libs), stripped
[EMAIL PROTECTED] nagios]$

But since a PERL script is interpretted and not compiled (technically
that isn't true either but it might as well be), the loader normally
doesn't know what to do with it, so the gods of UNIX decided that the
characters #! Would have special signifigance to the loader at the
beginning of the file. They indicate the program that will interpret the
script. So when the loader sees it it then looks for the /usr/bin/perl
program and execs it with the -w command and the script path so that it
will interpret the script. If /usr/bin/perl does not exist you will have
problems. To verify the existence of it just "ls /usr/bin/perl". Most
systems have it there, but a few do not, instead they keep it in
/usr/local/bin/ so you might need to change that line to
"#!/usr/local/bin/perl -w" instead. But only if it is in that location,
if it isn't you will need to find it. Which may not be so hard since
nagios probably found it when you installed it and if you do a "file *"
in the plugin directory and then type "head " and the name of a perl
script you should see where it really is.

Hope this he

Re: [Nagios-users] Issues with timeperiods

2008-07-22 Thread Fulton, David
BTW, I am running 3.0.3 on a RHEL 5 box on x86_64

David Fulton
Systems Administrator
NUVOX
O:407-835-0470
C:321-246-2238 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf 
> Of Fulton, David
> Sent: Tuesday, July 22, 2008 4:34 PM
> To: nagios-users@lists.sourceforge.net
> Subject: [Nagios-users] Issues with timeperiods
> 
> I was attempting to setup an on call rotation per the 
> directions on the website and have run into a little snag 
> that I am not sure really is a snag. My timeperiods file 
> looks like this:
> 
> define timeperiod{
>   timeperiod_name cbakeroncall
>   alias   Charles Baker on call weeks
>   2008-07-21  00:00-24:00
> }
> # timeperiods.cfg - Config file for Nagios (www.nagios.org) # 
> # Written by Nawui 0.1.5-dev. Manually editing this file is a 
> bad idea since Nawui will # overwrite it. 
> #
> # Exported at 11:54:47 - 01 Apr 2004
> #
> 
> 
> define timeperiod {
>   timeperiod_name 24x7
>   alias   24 Hours A Day, 7 Days A Week
>   sunday  00:00-24:00
>   monday  00:00-24:00
>   tuesday 00:00-24:00
>   wednesday   00:00-24:00
>   thursday00:00-24:00
>   friday  00:00-24:00
>   saturday00:00-24:00
> }
> 
> define timeperiod {
>   timeperiod_name workhours
>   alias   Work hours
>   monday  08:00-18:00
>   tuesday 08:00-18:00
>   wednesday   08:00-18:00
>   thursday08:00-18:00
>   friday  08:00-18:00
> }
> 
> define timeperiod {
>   timeperiod_name nonworkhours
>   alias   Non-Work Hours
>   sunday  00:00-24:00
>   monday  00:00-09:00,17:00-24:00
>   tuesday 00:00-09:00,17:00-24:00
>   wednesday   00:00-09:00,17:00-24:00
>   thursday00:00-09:00,17:00-24:00
>   friday  00:00-09:00,17:00-24:00
>   saturday00:00-24:00
> }
> 
> define timeperiod {
>   timeperiod_name none
>   alias   No Time Is A Good Time
> }
> 
> # This says some guy named Nawui is gonna overwrite this file 
> if I put this here.
> # Well, I'm just that crazy.
> define timeperiod {
>   timeperiod_name non_netapp_maintenance
>   alias   Always except NetApp Maintenance cronjobs
>   sunday  00:00-01:00,05:00-24:00
>   monday  00:00-01:00,05:00-24:00
>   tuesday 00:00-01:00,05:00-24:00
>   wednesday   00:00-01:00,05:00-24:00
>   thursday00:00-01:00,05:00-24:00
>   friday  00:00-01:00,05:00-24:00
>   saturday00:00-01:00,05:00-24:00
> }
> 
> Now, the problem is at the top of the file, if I look at the 
> timeperiods config in the CGI it looks like this:
> 
> Time Periods
> 
> Name  Alias/Description   Exclusions  Days/Dates  Times
> 24x7  24 Hours A Day, 7 Days A Week   sunday  00:00:00 -
> 24:00:00 
>   monday  00:00:00 - 24:00:00 
>   tuesday 00:00:00 - 24:00:00 
>   wednesday   00:00:00 - 24:00:00 
>   thursday00:00:00 - 24:00:00 
>   friday  00:00:00 - 24:00:00 
>   saturday00:00:00 - 24:00:00 
> cbakeroncall  Charles Baker on call weeks 2008-05-21
> 00:00:00 - 24:00:00
> non_netapp_maintenanceAlways except NetApp 
> Maintenance cronjobs
> sunday05:00:00 - 24:00:00, 00:00:00 - 01:00:00 
>   monday  05:00:00 - 24:00:00, 00:00:00 - 01:00:00 
>   tuesday 05:00:00 - 24:00:00, 00:00:00 - 01:00:00 
>   wednesday   05:00:00 - 24:00:00, 00:00:00 - 01:00:00 
>   thursday05:00:00 - 24:00:00, 00:00:00 - 01:00:00 
>   friday  05:00:00 - 24:00:00, 00:00:00 - 01:00:00 
>   saturday05:00:00 - 24:00:00, 00:00:00 - 01:00:00 
> none  No Time Is A Good Time  
> nonworkhours  Non-Work Hours  sunday  00:00:00 - 24:00:00 
>   monday  17:00:00 - 24:00:00, 00:00:00 - 09:00:00 
>   tuesday 17:00:00 - 24:00:00, 00:00:00 - 09:00:00 
>   wednesday   17:00:00 - 24:00:00, 00:00:00 - 09:00:00 
>   thursday17:00:00 - 24:00:00, 00:00:00 - 09:00:00 
>   friday  17:00:00 - 24:00:00, 00:00:00 - 09:00:00 
>   saturday00:00:00 - 24:00:00 
> workhours Work hours  monday  08:00:00 - 18:00:00 
>   tuesday 08:00:00 - 18:00:00 
>   wednesday   08:00:00 - 18:00:00 
>   thursday08:00:00 - 18:00:00 
>   friday  08:00:00 - 18:00:00 
> 
> Notice the date in the config file is 2008-07-21 and the date 
> the CGI repo

[Nagios-users] Issues with timeperiods

2008-07-22 Thread Fulton, David
I was attempting to setup an on call rotation per the directions on the
website and have run into a little snag that I am not sure really is a
snag. My timeperiods file looks like this:

define timeperiod{
timeperiod_name cbakeroncall
alias   Charles Baker on call weeks
2008-07-21  00:00-24:00
}
# timeperiods.cfg - Config file for Nagios (www.nagios.org)
#
# Written by Nawui 0.1.5-dev. Manually editing this file is a bad idea
since Nawui will
# overwrite it. 
#
# Exported at 11:54:47 - 01 Apr 2004
#


define timeperiod {
timeperiod_name 24x7
alias   24 Hours A Day, 7 Days A Week
sunday  00:00-24:00
monday  00:00-24:00
tuesday 00:00-24:00
wednesday   00:00-24:00
thursday00:00-24:00
friday  00:00-24:00
saturday00:00-24:00
}

define timeperiod {
timeperiod_name workhours
alias   Work hours
monday  08:00-18:00
tuesday 08:00-18:00
wednesday   08:00-18:00
thursday08:00-18:00
friday  08:00-18:00
}

define timeperiod {
timeperiod_name nonworkhours
alias   Non-Work Hours
sunday  00:00-24:00
monday  00:00-09:00,17:00-24:00
tuesday 00:00-09:00,17:00-24:00
wednesday   00:00-09:00,17:00-24:00
thursday00:00-09:00,17:00-24:00
friday  00:00-09:00,17:00-24:00
saturday00:00-24:00
}

define timeperiod {
timeperiod_name none
alias   No Time Is A Good Time
}

# This says some guy named Nawui is gonna overwrite this file if I put
this here.
# Well, I'm just that crazy.
define timeperiod {
timeperiod_name non_netapp_maintenance
alias   Always except NetApp Maintenance cronjobs
sunday  00:00-01:00,05:00-24:00
monday  00:00-01:00,05:00-24:00
tuesday 00:00-01:00,05:00-24:00
wednesday   00:00-01:00,05:00-24:00
thursday00:00-01:00,05:00-24:00
friday  00:00-01:00,05:00-24:00
saturday00:00-01:00,05:00-24:00
}

Now, the problem is at the top of the file, if I look at the timeperiods
config in the CGI it looks like this:

Time Periods

NameAlias/Description   Exclusions  Days/Dates  Times
24x724 Hours A Day, 7 Days A Week   sunday  00:00:00 -
24:00:00 
monday  00:00:00 - 24:00:00 
tuesday 00:00:00 - 24:00:00 
wednesday   00:00:00 - 24:00:00 
thursday00:00:00 - 24:00:00 
friday  00:00:00 - 24:00:00 
saturday00:00:00 - 24:00:00 
cbakeroncallCharles Baker on call weeks 2008-05-21
00:00:00 - 24:00:00
non_netapp_maintenance  Always except NetApp Maintenance cronjobs
sunday  05:00:00 - 24:00:00, 00:00:00 - 01:00:00 
monday  05:00:00 - 24:00:00, 00:00:00 - 01:00:00 
tuesday 05:00:00 - 24:00:00, 00:00:00 - 01:00:00 
wednesday   05:00:00 - 24:00:00, 00:00:00 - 01:00:00 
thursday05:00:00 - 24:00:00, 00:00:00 - 01:00:00 
friday  05:00:00 - 24:00:00, 00:00:00 - 01:00:00 
saturday05:00:00 - 24:00:00, 00:00:00 - 01:00:00 
noneNo Time Is A Good Time  
nonworkhoursNon-Work Hours  sunday  00:00:00 - 24:00:00 
monday  17:00:00 - 24:00:00, 00:00:00 - 09:00:00 
tuesday 17:00:00 - 24:00:00, 00:00:00 - 09:00:00 
wednesday   17:00:00 - 24:00:00, 00:00:00 - 09:00:00 
thursday17:00:00 - 24:00:00, 00:00:00 - 09:00:00 
friday  17:00:00 - 24:00:00, 00:00:00 - 09:00:00 
saturday00:00:00 - 24:00:00 
workhours   Work hours  monday  08:00:00 - 18:00:00 
tuesday 08:00:00 - 18:00:00 
wednesday   08:00:00 - 18:00:00 
thursday08:00:00 - 18:00:00 
friday  08:00:00 - 18:00:00 

Notice the date in the config file is 2008-07-21 and the date the CGI
reports is 2008-05-21. So my question is this, is this just a matter of
the CGI being broken and not being able to correctly interpret the
configuration, or is it nagios itself that is broken. If it is just the
CGI I will be perfectly okay with that. If not, I would like to put it
in as a bug.

Thanks

David Fulton
Systems Administrator
NUVOX
O:407-835-0470
C:321-246-2238


This email and any attachments ("Message") may contain legally privileged 
and/or confidential information.  If you are not the addressee, or if this 
Message has been addressed to you in error, you are not authorized to read, 
copy, or distribute it, and we ask that you please delete it (including all 
copies) and notify the sender by return email.  Delivery of this Message to any 
person other than the intended recipient(s) shall not be deemed a waiver of 
confidentiality an

Re: [Nagios-users] Event_handler and check_nrpe

2008-04-10 Thread Fulton, David
I hate to state the obvious, but nrpe usually doesn't have privileges to
start processes. I have a check that I run on remote hosts that requires
root privilege and had to use sudo. I was very restrictive in my sudoers
file to make sure that there were no holes, but it works with no
problems.




From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Hendric
Minassian
Sent: Wednesday, April 09, 2008 6:51 PM
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] Event_handler and check_nrpe


I am trying to use an event_handler to reatrt a process on a
remote server. I use NRPE for this purpose.
The process works fine when I run the full check_nrpe command
from the command line of the Nagios server:
 
#./check_nrpe -H nnn.nn.nnn.nn -c restart_alert_agent_new -a
CRITICAL SOFT 2

However, the restart script on the remote server does not kick
in when the alert is encountered by Nagios itself. Below is the command
defined in misccommands.cfg:
 
define command{
  command_namerestart_alert_agent_new
  command_line/usr/local/nagios/libexec/check_nrpe -H
$HOSTADDRESS$ -c restart_alert_agent_new -a $SERVICESTATE$
$SERVICESTATETYPE$ $SERVICEATTEMPT$
  }
 
As mentioned, the restart script in the remote server works fine
when invoked through the command line on Nagios server (above).
Below is the definition of the service in services.cfg:
 
# Service definition
define service{
use generic-service ; Name
of service template to use
 
host_name   CHOCLX-INTTEST
service_description check_total_procs
is_volatile 0
check_period24x7
max_check_attempts  4
normal_check_interval   5
retry_check_interval2
event_handler_enabled   1
event_handler   restart_alert_agent_new
contact_groups
sun-admins,lawson-admins,egate-admins
notification_interval   240
notification_period 24x7
notification_optionsu,c
notifications_enabled   1
check_command
check_nrpe!check_total_procs
}

 
Thank you for your help.
Hendric Minassian
 


"EMF " made the following annotations.


--
04/09/08, 15:51:44 

This email message and any files transmitted are sent with
confidentiality in mind 
and contain privileged or copyright information. You must not
present
this message to another party without gaining permission from
the 
sender.  If you are not the intended recipient you must not
copy, 
distribute or use this email or the information contained in it 
for any purpose other than to notify Children's Hospital of 
Orange County.  Any views expressed in this message are those of

the sender, except where the sender specifically states them to 
be the views of Children's Hospital of Orange County. If you
have
received this message in error, please notify the sender
immediately, 
and delete this email from your system. We do not guarantee that

this material is free from viruses or any other defects although

due care has been taken to minimize the risk.



==





This email and any attachments ("Message") may contain legally privileged 
and/or confidential information.  If you are not the addressee, or if this 
Message has been addressed to you in error, you are not authorized to read, 
copy, or distribute it, and we ask that you please delete it (including all 
copies) and notify the sender by return email.  Delivery of this Message to any 
person other than the intended recipient(s) shall not be deemed a waiver of 
confidentiality and/or a privilege.
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___
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 w

Re: [Nagios-users] trends.cgi strange problem

2008-04-10 Thread Fulton, David
I don't know if it that particular issue has been addressed but the nagios 2 
series is up to version 2.11. You could try upgrading as it does fix a number 
of bugs in the CGIs relating to status and dates, so it could fix it.

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf 
> Of Livio Zanol Puppim
> Sent: Wednesday, April 09, 2008 4:50 PM
> To: nagios-users@lists.sourceforge.net
> Subject: Re: [Nagios-users] trends.cgi strange problem
> 
> I have checked on avail.cgi and noticed that the data show is 
> "Insufficient Data" and not Host Up data. Why is this 
> happening? What must I do to get the reports to work correctly...
> 
> thanks,
> Lívio Zanol Puppim
> 
> 2008/4/9, Livio Zanol Puppim <[EMAIL PROTECTED]>:
> > Sorry
> >
> >  Nagios 2.6
> >  Debian etch 4.0
> >
> >  2008/4/9, Livio Zanol Puppim <[EMAIL PROTECTED]>:
> >
> > > Hi,
> >  >
> >  >  I was trying to generate some reports using trends.cgi 
> and have found a problem.
> >  >
> >  >  If I change the "end date" to something before "today" the cgi 
> > gives  >  me a wrong report, showing an "always up" report, 
> which is not true.
> >  >
> >  >  I can change the start date to whatever I want, and the problem 
> > don't  >  show up. I can also modify the hours, minutes, or 
> seconds on 
> > the end  >  date and the report shows real data. The problem only 
> > happends when  >  the end date is changed to something diferent (on 
> > day, month or year)  >  then the today date.
> >  >
> >  >  Ex.:
> >  >  If I want to get a report right now, I can go to trends.cgi and 
> > set  >  the end date to something like 04/09/2008 00:01, but cannot 
> > set the  >  end date to something like 04/08/2008 23:59.
> >  >
> >  >  Has anyone see this problem before?
> >  >
> >
> 
> --
> ---
> This SF.net email is sponsored by the 2008 JavaOne(SM) 
> Conference Don't miss this year's exciting event. There's 
> still time to save $100. 
> Use priority code J8TL2D2. 
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java
.sun.com/javaone
> ___
> 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
> 


This email and any attachments ("Message") may contain legally privileged 
and/or confidential information.  If you are not the addressee, or if this 
Message has been addressed to you in error, you are not authorized to read, 
copy, or distribute it, and we ask that you please delete it (including all 
copies) and notify the sender by return email.  Delivery of this Message to any 
person other than the intended recipient(s) shall not be deemed a waiver of 
confidentiality and/or a privilege.

-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
___
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

Re: [Nagios-users] Nagios 2.11 changelog

2008-03-12 Thread Fulton, David
Just click the changelog tag in the latest news section and scroll down.

David Fulton
Systems Administrator
NuVox Communications
"Because Business is on the Line" 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf 
> Of Marc Powell
> Sent: Wednesday, March 12, 2008 11:37 AM
> To: nagios-users@lists.sourceforge.net
> Subject: Re: [Nagios-users] Nagios 2.11 changelog
> 
> 
> 
> > -Original Message-
> > From: [EMAIL PROTECTED] 
> [mailto:nagios-users- 
> > [EMAIL PROTECTED] On Behalf Of Giles Coochey
> > Sent: Wednesday, March 12, 2008 9:16 AM
> > To: nagios-users@lists.sourceforge.net
> > Subject: [Nagios-users] Nagios 2.11 changelog
> > 
> > 
> > I see 2.11 is released...
> > 
> > Has anyone worked out how to get to the Changelog, since the
> Nagios.org
> > site changed the download pages?
> 
> http://www.nagios.org/development/
> 
> --
> Marc 
> 
> --
> ---
> This SF.net email is sponsored by: Microsoft Defy all 
> challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
> ___
> 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
> 


This email and any attachments ("Message") may contain legally privileged 
and/or confidential information.  If you are not the addressee, or if this 
Message has been addressed to you in error, you are not authorized to read, 
copy, or distribute it, and we ask that you please delete it (including all 
copies) and notify the sender by return email.  Delivery of this Message to any 
person other than the intended recipient(s) shall not be deemed a waiver of 
confidentiality and/or a privilege.

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
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


Re: [Nagios-users] configuration directory and file directives ...perplexity (long and boring). [SEC=UNCLASSIFIED]

2007-10-25 Thread Fulton, David
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:nagios-users-

> [EMAIL PROTECTED] On Behalf Of 
> [EMAIL PROTECTED]
> Sent: Wednesday, October 24, 2007 10:07 PM
> To: nagios-users@lists.sourceforge.net
> Subject: Re: [Nagios-users] configuration directory and file 
> directives ...perplexity (long and boring). [SEC=UNCLASSIFIED]
> 
> Dear Tim,
> 
> (Yes, I am the nitwit).
> 
> > -Original Message-
> > Mr Hopcroft,
> >
> > My first reaction was an unqualified "yuk!, what nitwit would even 
> > consider this", then I noticed it was you, and having seen your ever

> > useful posts since the Netsaint 0.0.7 days, I relented. Although 
> > hearing vi called "anachronistic" ruffles a couple of feathers.
> 
> (OT. Have a look at what Rob Pike has been saying about Unix for some 
> years. To an MSCE, vi is .. well I am happy with my original choice of

> words. I am not a Windows admin and am perfectly happy with vi to do 
> my Nagios configuration [or my own home brew semi-automation] but not 
> everyone who likes Nagios likes vi).
> 
> > Notepad isn't?
> > No accounting for taste...
> 
> (OT. For unambitious text mangling it's Ok. How many people depend on 
> vi macros or even conditional substitution ?)
> 
> >
> > I can't actually speak to your specific question, but it just seems 
> > like a scary thought. Better to run samba on the Nagios machine and 
> > let them mount it, and/or SVN. And then there's the GUI method, of 
> > course.
> 
> Good thought but why should they change to suit one application ?
> 
> At this site there are no Unix Sys admin skills (apart from me) and 
> everyone likes Windows. Having the configs on Win means management is 
> happy they are adequately backed up.
> 
> Does cfg_dir=/Some/Path actually work ? and if so, would anyone be so 
> kind as to paste a few lines containing these directives from their 
> nagios.cfg ?
> 
> Here is the problem, adding a cfg_dir to point to a _Unix_ directory 
> like so
> 
> ***
> *** 78,83 
> --- 78,87 
>   # extension) in a particular directory by using the cfg_dir
>   # directive as shown below:
> 
> + cfg_dir=/etc/nagios
> +
> + # cfg_dir=/mnt/dest_smb/coms/NMS/nagios
> +
>   #cfg_dir=/etc/nagios/servers
>   #cfg_dir=/etc/nagios/printers
>   #cfg_dir=/etc/nagios/switches
> [EMAIL PROTECTED] nagios]#
> 
> causes
> 
> [EMAIL PROTECTED] nagios]# nagios -v nagios.cfg
> 
> Nagios 2.9
> Copyright (c) 1999-2007 Ethan Galstad (http://www.nagios.org) Last
> Modified: 04-10-2007
> License: GPL
> 
> Reading configuration data...
> 
> Error: Unexpected token or statement in file '/etc/nagios/cgi.cfg' on 
> line 23.
> 
> ***> One or more problems was encountered while processing the config 
> files...
> 
>  Check your configuration file(s) to ensure that they contain
valid
>  directives and data defintions.  If you are upgrading from a 
> previous
>  version of Nagios, you should be aware that some 
> variables/definitions
>  may have been removed or modified in this version.  Make sure to 
> read
>  the HTML documentation regarding the config files, as well as the
>  Whats New' section to find out what has changed.
> 
> [EMAIL PROTECTED] nagios]#

If you are setting cfg_dir equal to the directory where you store your
main configuration it is part of the problem. The reasons are twofold:
1.  Nagios will try to recursively open the main
configuration file, as you can imagine this would cause issues.

2.  Nagios will open all configuration files that end in
.cfg including ones that it is not supposed to, like cgi.cfg which is
only intended to be read by the cgi programs that the web server runs.

The workaround that I might use for this is to make a subdirectory for
configuration datat and mount your smb filesystem there. It is a
tradeoff though. The windows admins won't be able to modify the main
nagios.cfg file. On the other hand, how often do you change those
options?  The big configuration file changes always happen in the object
definitions. My nagios.cfg file has the following cfg_dir directives in
it:

cfg_dir=/usr/local/etc/nagios/objects/contacts
cfg_dir=/usr/local/etc/nagios/objects/times
cfg_dir=/usr/local/etc/nagios/objects/services
cfg_dir=/usr/local/etc/nagios/objects/templates

cfg_dir=/usr/local/etc/nagios/objects/hosts/firewalls
cfg_dir=/usr/local/etc/nagios/objects/hosts/routers
cfg_dir=/usr/local/etc/nagios/objects/hosts/switches

cfg_dir=/usr/local/etc/nagios/objects/hosts/ironports

cfg_dir=/usr/local/etc/nagios/objects/hosts/unix/freebsd
cfg_dir=/usr/local/etc/nagios/objects/hosts/unix/linux
cfg_dir=/usr/local/etc/nagios/objects/hosts/unix/solaris

cfg_dir=/usr/local/etc/nagios/objects/hosts/windows
cfg_dir=/usr/local/etc/nagios/objects/hosts/vmware
cfg_dir=/usr/local/etc/nagios/objects/hosts/netapp

cfg_dir=/usr/local/etc/nagios/objects/hosts/virtual_services

cfg_dir=/usr/local/etc/nagios/objects/hostgroups
cfg_dir=/usr/local/etc/nagios/objects/serv

Re: [Nagios-users] compile issue for nagios plugins 1.4.10

2007-10-22 Thread Fulton, David
I had a similar problem and had to set LDFLAGS and CFLAGS thusly:

CFLAGS=-I/usr/include/mysql
LDFLAGS=-L/usr/lib/mysql

Aparently the resulting Makefile doesn't check in some of the more standard 
places that configure assumes it does.

-Original Message-
From: Dylan Bouterse [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 22, 2007 1:55 PM
To: Fulton, David; nagios-users@lists.sourceforge.net
Subject: RE: [Nagios-users] compile issue for nagios plugins 1.4.10

I hope this goes back far enough and isn't overkill on the results of my make.


My configure command:
./configure --with-mysql=/usr

config.status: creating po/Makefile
--with-apt-get-command: 
  --with-ping6-command: /bin/ping6 -n -U -w %d -c %d %s
   --with-ping-command: /bin/ping -n -U -w %d -c %d %s
   --with-ipv6: yes
  --with-mysql: /usr/bin/mysql_config
--with-openssl: yes
 --with-gnutls: no
   --with-perl: /usr/bin/perl
 --enable-perl-modules: no
 --with-cgiurl: /nagios/cgi-bin
   --with-trusted-path: /bin:/sbin:/usr/bin:/usr/sbin

Snippet that shows the mysql error

gcc -g -O2 -o check_ide_smart check_ide_smart.o utils.o  
-L/usr/local/src/nagios-plugins-1.4.10/plugins ../lib/libnagiosplug.a 
../gl/libgnu.a
if gcc -DLOCALEDIR=\"/usr/local/nagios/share/locale\" -DHAVE_CONFIG_H -I. -I. 
-I.. -I.. -I../lib -I../gl -I../intl -I/usr/include/ldap  -I/usr/include 
-I/usr/include   -g -O2 -MT check_mysql-check_mysql.o -MD -MP -MF 
".deps/check_mysql-check_mysql.Tpo" -c -o check_mysql-check_mysql.o `test -f 
'check_mysql.c' || echo './'`check_mysql.c; \
then mv -f ".deps/check_mysql-check_mysql.Tpo" 
".deps/check_mysql-check_mysql.Po"; else rm -f 
".deps/check_mysql-check_mysql.Tpo"; exit 1; fi
/bin/sh ../libtool --tag=CC --mode=link gcc  -g -O2  -L. -o check_mysql  
check_mysql-check_mysql.o netutils.o utils.o ../lib/libnagiosplug.a 
../gl/libgnu.a  -lnsl -lresolv  
gcc -g -O2 -o check_mysql check_mysql-check_mysql.o netutils.o utils.o  
-L/usr/local/src/nagios-plugins-1.4.10/plugins ../lib/libnagiosplug.a 
../gl/libgnu.a -lnsl -lresolv
check_mysql-check_mysql.o(.text+0x5d9): In function `main':
/usr/local/src/nagios-plugins-1.4.10/plugins/check_mysql.c:91: undefined 
reference to `mysql_init'
check_mysql-check_mysql.o(.text+0x5ef):/usr/local/src/nagios-plugins-1.4.10/plugins/check_mysql.c:93:
 undefined reference to `mysql_options'
check_mysql-check_mysql.o(.text+0x61d):/usr/local/src/nagios-plugins-1.4.10/plugins/check_mysql.c:96:
 undefined reference to `mysql_real_connect'
check_mysql-check_mysql.o(.text+0x637):/usr/local/src/nagios-plugins-1.4.10/plugins/check_mysql.c:112:
 undefined reference to `mysql_stat'
check_mysql-check_mysql.o(.text+0x653):/usr/local/src/nagios-plugins-1.4.10/plugins/check_mysql.c:115:
 undefined reference to `mysql_error'
check_mysql-check_mysql.o(.text+0x67f):/usr/local/src/nagios-plugins-1.4.10/plugins/check_mysql.c:126:
 undefined reference to `mysql_query'
check_mysql-check_mysql.o(.text+0x699):/usr/local/src/nagios-plugins-1.4.10/plugins/check_mysql.c:133:
 undefined reference to `mysql_store_result'
check_mysql-check_mysql.o(.text+0x6b8):/usr/local/src/nagios-plugins-1.4.10/plugins/check_mysql.c:140:
 undefined reference to `mysql_num_rows'
check_mysql-check_mysql.o(.text+0x6d3):/usr/local/src/nagios-plugins-1.4.10/plugins/check_mysql.c:146:
 undefined reference to `mysql_fetch_row'
check_mysql-check_mysql.o(.text+0x6f3):/usr/local/src/nagios-plugins-1.4.10/plugins/check_mysql.c:153:
 undefined reference to `mysql_field_count'
check_mysql-check_mysql.o(.text+0x72b):/usr/local/src/nagios-plugins-1.4.10/plugins/check_mysql.c:167:
 undefined reference to `mysql_num_fields'
check_mysql-check_mysql.o(.text+0x73d):/usr/local/src/nagios-plugins-1.4.10/plugins/check_mysql.c:168:
 undefined reference to `mysql_fetch_fields'
check_mysql-check_mysql.o(.text+0x80a):/usr/local/src/nagios-plugins-1.4.10/plugins/check_mysql.c:184:
 undefined reference to `mysql_free_result'
check_mysql-check_mysql.o(.text+0x818):/usr/local/src/nagios-plugins-1.4.10/plugins/check_mysql.c:185:
 undefined reference to `mysql_close'
check_mysql-check_mysql.o(.text+0x837):/usr/local/src/nagios-plugins-1.4.10/plugins/check_mysql.c:97:
 undefined reference to `mysql_errno'
check_mysql-check_mysql.o(.text+0x854):/usr/local/src/nagios-plugins-1.4.10/plugins/check_mysql.c:99:
 undefined reference to `mysql_errno'
check_mysql-check_mysql.o(.text+0x86d):/usr/local/src/nagios-plugins-1.4.10/plugins/check_mysql.c:101:
 undefined reference to `mysql_errno'
check_mysql-check_mysql.o(.text+0x88a):/usr/local/src/nagios-plugins-1.4.10/plugins/check_mysql.c:103:
 undefined reference to `mysql_errno'
che

Re: [Nagios-users] check_snmp syntax issue (now compile issuefornagios plugins)

2007-10-22 Thread Fulton, David
Okay, now after reading the message again I understand(Duh). What sort of 
errors are you getting, could you post them so maybe we can help with options.

David Fulton

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fulton, David
Sent: Monday, October 22, 2007 12:47 PM
To: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] check_snmp syntax issue (now compile issuefornagios 
plugins)

Why do you want to skip it? If it finds the mysql libraries and header file it 
will make the check_mysql plugin. This could come in handy later. You never 
know when you will need it and it will be there just in case. If it doesn't 
find it, then it will not build it and no harm done?

David Fulton

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dylan Bouterse
Sent: Monday, October 22, 2007 12:42 PM
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] check_snmp syntax issue (now compile issue fornagios 
plugins)

I am trying to compile the new Nagios plugins 1.4.10 but my make errors with 
mysql errors. What syntax do I use to skip the mysql plugin during compile/make?
--without-PACKAGE   ?
--disable-FEATURE   ?

Dylan

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dylan Bouterse
Sent: Monday, October 22, 2007 12:01 PM
To: Yost, Josh; nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] check_snmp syntax issue

I guess you have a different check_snmp version than I do because I was not 
showing a 2c option for the version. I will investigate that and see if that's 
my issue.

Dylan

From: Yost, Josh [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 22, 2007 12:00 PM
To: Dylan Bouterse; nagios-users@lists.sourceforge.net
Subject: RE: [Nagios-users] check_snmp syntax issue

It looks like the -P switch will tell it which snmp version to use.  again, 
'-h' helps  =)
 
-P, --protocol=[1|2c|3]
    SNMP protocol version
- Josh


From: Dylan Bouterse [mailto:[EMAIL PROTECTED]
Sent: Mon 10/22/2007 10:56 AM
To: Yost, Josh; nagios-users@lists.sourceforge.net
Subject: RE: [Nagios-users] check_snmp syntax issue
That may do it, but I can't get the host to respond using the check_snmp 
plugin. I think it may be a version mismatch. It seems the check_snmp plugin 
only supports SNMP v1 and v3, but not v2c. I cannot snmpget my device with v1 
or v3.

Dylan


From: Yost, Josh [mailto:[EMAIL PROTECTED]
Sent: Monday, October 22, 2007 11:33 AM
To: Dylan Bouterse; nagios-users@lists.sourceforge.net
Subject: RE: [Nagios-users] check_snmp syntax issue

I think the:  --string='SYNC OK'   option would do it.  Try doing a '-h' on 
check_snmp to see all the options.
 
- Josh
 


From: [EMAIL PROTECTED] on behalf of Dylan Bouterse
Sent: Mon 10/22/2007 10:24 AM
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] check_snmp syntax issue
I am trying to get check_snmp working to alert when my GPS sync stops
working on one of my devices. I can execute the snmpget command to get
the string but I'm having no luck in configuring a check_snmp syntax to
return values.


[EMAIL PROTECTED] cfg]# snmpget -v 2c -c community 1.1.20.3
1.3.6.1.4.1.161.19.3.4.4.13.0
SNMPv2-SMI::enterprises.161.19.3.4.4.13.0 = STRING: "SYNC OK"
[EMAIL PROTECTED] cfg]# snmpget -v 2c -c community 1.1.21.3
1.3.6.1.4.1.161.19.3.4.4.13.0
SNMPv2-SMI::enterprises.161.19.3.4.4.13.0 = STRING: "No SYNC"

How would I write the check_snmp command to show OK when "SYNC OK" and
alert critical when the "No SYNC" value is returned?

Dylan

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
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

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
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

Re: [Nagios-users] check_snmp syntax issue (now compile issue fornagios plugins)

2007-10-22 Thread Fulton, David
Why do you want to skip it? If it finds the mysql libraries and header file it 
will make the check_mysql plugin. This could come in handy later. You never 
know when you will need it and it will be there just in case. If it doesn't 
find it, then it will not build it and no harm done?

David Fulton

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dylan Bouterse
Sent: Monday, October 22, 2007 12:42 PM
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] check_snmp syntax issue (now compile issue fornagios 
plugins)

I am trying to compile the new Nagios plugins 1.4.10 but my make errors with 
mysql errors. What syntax do I use to skip the mysql plugin during compile/make?
--without-PACKAGE   ?
--disable-FEATURE   ?

Dylan

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dylan Bouterse
Sent: Monday, October 22, 2007 12:01 PM
To: Yost, Josh; nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] check_snmp syntax issue

I guess you have a different check_snmp version than I do because I was not 
showing a 2c option for the version. I will investigate that and see if that's 
my issue.

Dylan

From: Yost, Josh [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 22, 2007 12:00 PM
To: Dylan Bouterse; nagios-users@lists.sourceforge.net
Subject: RE: [Nagios-users] check_snmp syntax issue

It looks like the -P switch will tell it which snmp version to use.  again, 
'-h' helps  =)
 
-P, --protocol=[1|2c|3]
    SNMP protocol version
- Josh


From: Dylan Bouterse [mailto:[EMAIL PROTECTED]
Sent: Mon 10/22/2007 10:56 AM
To: Yost, Josh; nagios-users@lists.sourceforge.net
Subject: RE: [Nagios-users] check_snmp syntax issue
That may do it, but I can't get the host to respond using the check_snmp 
plugin. I think it may be a version mismatch. It seems the check_snmp plugin 
only supports SNMP v1 and v3, but not v2c. I cannot snmpget my device with v1 
or v3.

Dylan


From: Yost, Josh [mailto:[EMAIL PROTECTED]
Sent: Monday, October 22, 2007 11:33 AM
To: Dylan Bouterse; nagios-users@lists.sourceforge.net
Subject: RE: [Nagios-users] check_snmp syntax issue

I think the:  --string='SYNC OK'   option would do it.  Try doing a '-h' on 
check_snmp to see all the options.
 
- Josh
 


From: [EMAIL PROTECTED] on behalf of Dylan Bouterse
Sent: Mon 10/22/2007 10:24 AM
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] check_snmp syntax issue
I am trying to get check_snmp working to alert when my GPS sync stops
working on one of my devices. I can execute the snmpget command to get
the string but I'm having no luck in configuring a check_snmp syntax to
return values.


[EMAIL PROTECTED] cfg]# snmpget -v 2c -c community 1.1.20.3
1.3.6.1.4.1.161.19.3.4.4.13.0
SNMPv2-SMI::enterprises.161.19.3.4.4.13.0 = STRING: "SYNC OK"
[EMAIL PROTECTED] cfg]# snmpget -v 2c -c community 1.1.21.3
1.3.6.1.4.1.161.19.3.4.4.13.0
SNMPv2-SMI::enterprises.161.19.3.4.4.13.0 = STRING: "No SYNC"

How would I write the check_snmp command to show OK when "SYNC OK" and
alert critical when the "No SYNC" value is returned?

Dylan

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
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

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
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

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please includ

Re: [Nagios-users] Another Nagios Problem.

2007-10-17 Thread Fulton, David
I never said I wouldn't supply the coders with what they need. I would
expect that those who coded it could point me in the right direction. I
have thus far tried changing how I get my data into perfparse and
changing my timeperiods so that there are no overlapping times (i.e.
from 00:00 - 24:00 to 00:00-23:59) since it always happens overnight and
the problem crops up after midnight I have to wait until then to get
more data. Other than that I am using FreeBSD 6.2 with the latest
plugins (1.4.10), nrpe, nsca and perfparse (the performance data is send
to files via a command definition that calls a perl script that writes
it to a file. Perparse picks it up via a cron job that runs every 5
minutes).

The purpose of the nagios-users list is to obtain help when one gets
stuck not to have someone tell them how they should be able to do their
own support. I have set up a complex piece of software and have been
running it since version 3.0b1. To my knowledge, there are only so many
sources of information that I could provide. Nagios doesn't stop,
doesn't run a particular command. It simply starts orphaning check
results after midnight every day. Turning on debugging does not give any
indication as to why. If I truss (strace) the process it immediately
spawns a new copy of itself that consumes all CPU time on whatever CPU
it is running on without returning anything.

-Original Message-
From: Hugo van der Kooij [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 17, 2007 1:44 PM
To: Fulton, David
Subject: Re: [Nagios-users] Another Nagios Problem.

-BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Fulton, David wrote:
> I was simply wondering if anyone else had experienced the same
problem.
> There is nothing in the debug logs to send. Trussing the process
causes
> Nagios to die (no help there). As far as to whether or not this is in
> production environment, I am setting it up so that it is ready upon
the
> release of the full version. Our production Nagios servers are running
> 1.x variants and need serious updating. I did look at the 2.9 version
> but the 3.0bx versions have some really nice features that come in
handy
> in our environment (i.e. the ability to set up on call rotations and
the
> additive inheritance property) and we would like to use it as soon as
> possible (I.E. when 3.0 is released. If you have no guidance to
> contribute I would rather you hadn't emailed me in the first place. I
am
> looking for help, not some holier than thou attitude.

You are asking for help on a test version. If you use that version you
should be able to do your own support unless you can provide concrete
information a coder can use to troubleshoot.

No one knows your setup on the mailinglist. So unless you are explicit
and elaborate there is little to go on. Anyway I suggest you turn to the
developers mailingist for experimental versions. There are the people
who will do the coding.

Hugo.

- --
[EMAIL PROTECTED]   http://hugo.vanderkooij.org/
PGP/GPG? Use: http://hugo.vanderkooij.org/0x58F19981.asc

Bored? Click on http://spamornot.org/ and rate those images.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFHFkneBvzDRVjxmYERAvrKAJ0bKMROOk1K6YRfBw4R8LSEbSf2sACgiWyd
bpDXj5DJcEaaVhkYvYXtOPM=
=t7MO
-END PGP SIGNATURE-

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
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