[Nagios-users] using multiple templates

2010-07-09 Thread Litwin, Matthew
Are there any consequences to using multiple templates other than that the last 
one defined gets precedence? I would like to have sevice templates the do 
things like define notifications interval separately from escalation path,  
time periods etc

I was thinking of ending up with something like this:

define{
namesome_services
use an_escalation_template
use a_notification_template
use an_action_template

}

Assuming there is no collisions in namespace, this should work, right?

--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
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


[Nagios-users] failover setup help

2010-07-09 Thread Shadhin Rahman
All,
   I have a failover setup with nagios.  I also have ndoUtils setup for
collecting historical data.   My setup is described below.

master server - running nagios and ndoutils collecting data.  The master is
also sending host state and service state  data using nsca to failover
server.  master server has active host check, service check and notification
enabled.

slave server - running nagios and partial ndoutil.  no active checks are
being done in this slave server.  The slave server also has notification
disabled.  nsca daemon is listening for service and host status from master
server.

The problem:  I am facing the problem where acknowledgements and comments
are not up to date in the slave server.  I can possibly  transfer the
retention file to slave server and fix the comments part of the problem.
However I do not know how to get all the acknowledgements transfer to the
slave server.

It would be great if someone can point me to the right direction, how I can
solve the acknowledgement problem I describe above.  Thanks in advance.

-- 
Cordially,
Shadhin Rahman
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first___
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] Nagiosgrapher problem with building graph for particular check_service

2010-07-09 Thread yuris
You are right, I've been changing definition couple of times, and since 
I have not been changing it for some some time (like 30 minutes) rrd 
file was updated on it's own and graph started to work!

So it seems like manual deleting of rrd file is not absolutely 
necessary, it's possible to just wait for some time and it will be 
updated automatically.

Thanks for the help!

--
best regards,
yuris


Marc Powell wrote:
> On Jul 9, 2010, at 7:51 AM, yuris wrote:
>
>   
>> And the problem is that graphs for Milter are not shown, Nagiosgrapher 
>> complains that "some error occured":
>>
>> RRD Error: No DS called 'sec' in 
>> '/var/lib/nagiosgrapher/rrd//457eb765jjf8905k567849c.rrd'
>> 
>
> It seems you may have been modifying the definition at least once. Try 
> deleting the rrd file and allowing it to be recreated based on your current 
> definition.
>
> --
> Marc
> --
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> ___
> 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 Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
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] Nagiosgrapher problem with building graph for particular check_service

2010-07-09 Thread Marc Powell

On Jul 9, 2010, at 7:51 AM, yuris wrote:

> 
> And the problem is that graphs for Milter are not shown, Nagiosgrapher 
> complains that "some error occured":
> 
> RRD Error: No DS called 'sec' in 
> '/var/lib/nagiosgrapher/rrd//457eb765jjf8905k567849c.rrd'

It seems you may have been modifying the definition at least once. Try deleting 
the rrd file and allowing it to be recreated based on your current definition.

--
Marc
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
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


[Nagios-users] Nagiosgrapher problem with building graph for particular check_service

2010-07-09 Thread yuris
Hi all,

I use check_milter which is basically check_tcp with some arguments, it 
gives output like this:

TCP OK - 0.002 second response time on port 
1313|time=0.001912s;;;0.00;10.00

it's very similar to output from check_ldap:

LDAP OK - 0.006 seconds response time|time=0.006278s;;;0.00

I have defined ngraph for check_milter very similar to check_ldap:

define ngraph{
service_name  Milter
graph_perf_regextime=\s*([0-9.]+)
graph_valuesec
graph_units second
graph_legend  response time on port 1313
rrd_plottypeLINE2
rrd_colorff
}

define ngraph{
service_name   LDAP
graph_perf_regextime=\s*([0-9.]+)
graph_valuesec
graph_units seconds
graph_legend  LDAP Response time
rrd_plottypeLINE2
rrd_color 00a000
}

And the problem is that graphs for Milter are not shown, Nagiosgrapher 
complains that "some error occured":

RRD Error: No DS called 'sec' in 
'/var/lib/nagiosgrapher/rrd//457eb765jjf8905k567849c.rrd'

I wonder why "graph_value sec" is ok for LDAP graph but does not suit 
for different service with almost identical output?

and I see no errors in ngraph.log:

2010-07-09 08:32:55 PIPE: node142   Milter  TCP OK - 0.050 second 
response time on port 1313time=0.049644s;;;0.00;10.00n
2010-07-09 08:32:55 VALUES: [node142][Milter]: sec=0.049644
2010-07-09 08:32:55 RRD: rrdtool update 
/var/lib/nagiosgrapher/rrd/node142/4bab581d80135b9823fd2a54001423a4.rrd 
--template=sec N:0.049644

Please help me figure out what's wrong did I do?

--
best regards,
Yuris
Linux System Engineer,
SMTP.com





--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
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


[Nagios-users] Nagios & Tivoli Enterprise Console [TEC]

2010-07-09 Thread Jones, Stuart
Has anyone tried forwarding Nagios host or service alerts to a Tivoli
Enterprise Console [TEC]? If so what methodology did you employee?
 
Typically a host would use postemsg to forward status / event messages
to a TEC.
 
Thx, Stuart
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first___
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