Re: [Nagios-users] Suggestion on SNMP disk space checker

[Joerg Linge]

Am 14.10.2011 um 02:19 schrieb Al:

> I'm open for any suggestions/urlz/code for disk space checking via SNMP.  I'm 
> trying not to do it with NRPE.  Thanks in advance!

http://www.google.com/search?q=nagios+check+snmp+disk
http://nagios.manubulon.com/snmp_storage.html


--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
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] Suggestion on SNMP disk space checker

[Al]

Its to monitor linux fedora/centos/debian systems... mostly, thanks for the 
suggestion!

On Oct 13, 2011, at 9:08 PM, Matthew Jurgens wrote:

> If you are talking about disk space on Windows then take a look at 
> 
> www.edcint.co.nz/checkwmiplus
> 
> This will check Windows disk space (and many other things) without having to 
> install a client/proxy and without having to configure anything related to 
> SNMP as it use WMI.
> 
> On 14/10/2011 11:19 AM, Al wrote:
>> 
>> I'm open for any suggestions/urlz/code for disk space checking via SNMP.  
>> I'm trying not to do it with NRPE.  Thanks in advance!
>> --
>> 
>> -- 
>> Smartmon System Monitoring 
>> www.smartmon.com.au
> --
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2d-oct___
> 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

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct___
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] Suggestion on SNMP disk space checker

[Matthew Jurgens]

If you are talking about disk space on Windows then take a look at

www.edcint.co.nz/checkwmiplus

This will check Windows disk space (and many other things) without 
having to install a client/proxy and without having to configure 
anything related to SNMP as it use WMI.


On 14/10/2011 11:19 AM, Al wrote:

I'm open for any suggestions/urlz/code for disk space checking via SNMP.  I'm 
trying not to do it with NRPE.  Thanks in advance!
--

--
Smartmon System Monitoring 
www.smartmon.com.au 
--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct___
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] Suggestion on SNMP disk space checker

[Al]

I'm open for any suggestions/urlz/code for disk space checking via SNMP.  I'm 
trying not to do it with NRPE.  Thanks in advance!
--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
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] About new release for Nagios

[Yu Watanabe]

Hello Andreas.

Thank you for the reply.

I understood the situation. So, is v 3.2.3 more stable version 
for now?

Thanks,
Yu

Andreas Ericsson さんは書きました:
>On 10/13/2011 07:09 AM, Yu Watanabe wrote:
>> Hello all.
>> 
>> I was curious there will be any new releases coming out in Nagios.
>> I remember there was memory leak in 3.3.1.
>> 
>> Are there any plans for any new releases?
>> 
>
>No, there will never be a new release of Nagios ever again. We've all
>decided to take up knitting and unicorn-breeding instead.
>
>On a more serious note; Ofcourse there will be a new release of Nagios.
>The memory leaks are not very serious and have not yet been merged to
>the Nagios core, so making a new release right now would be stupid. I
>still need more time to fully investigate the pros and cons of the patch
>sent in to handle the memory leak in the notification, for instance. I
>believe the proposed fix either doesn't fix the leak completely or fixes
>it in a bad way that would cause other problems, so I need to run it
>through valgrind a couple of times to first of all see the leak for
>myself and secondly make sure nothing bad happens when the patch is
>applied and there are multiple notifications going out, of which some
>are sent to escalated contacts.
>
>In the meantime, you can restart your Nagios daemon once a year to avoid
>any realworld problems from any potential leaks (although running latest
>svn trunk would fix most of them too, so you could probably get away with
>restarting only ever leapyear or something).
>
>-- 
>Andreas Ericsson   andreas.erics...@op5.se
>OP5 AB www.op5.se
>Tel: +46 8-230225  Fax: +46 8-230231
>
>Considering the successes of the wars on alcohol, poverty, drugs and
>terror, I think we should give some serious thought to declaring war
>on peace.

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
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] Check_tcp - port monitoring best practice

[Deborah Martin]

Hi,

I just wondered what would be the best practice for monitoring ports. 

At the moment we specify 10,20,25 seconds for ok, warning and critical alerts. 
Is that too little - we are seeing a few critical alerts generated and wondered 
if 
increasing the thresholds would be better. 

What does a "socket timeout" generally mean as some of the ports we're 
monitoring are on systems which are idle at the moment. 
Could these be caused by network glitches between the nagios box and the target 
ports - the systems we're monitoring aren't local on the nagios network but in 
different parts of the world. 

I wonder if a local nagios instance would be better to try and reduce "socket 
timeouts" as otherwise people oncall are going to get called out quite a 
lot (?) 


Any input / ideas would be really appreciated. 


Regards,
Deborah 
Complimentary Events and Webinars on In-Memory, Massively Parallel Processing 
and 'In the Cloud' - for more information click here

This e-mail and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you are not the intended recipient, please delete this e-mail immediately. Any 
unauthorised distribution or copying is strictly prohibited. Whilst Kognitio 
endeavours to prevent the transmission of viruses via e-mail, we cannot 
guarantee that any e-mail or attachment is free from computer viruses and you 
are strongly advised to undertake your own anti-virus precautions. Kognitio 
grants no warranties regarding performance, use or quality of any e-mail or 
attachment and undertakes no liability for loss or damage, howsoever caused

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
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] About new release for Nagios

[Andreas Ericsson]

On 10/13/2011 07:09 AM, Yu Watanabe wrote:
> Hello all.
> 
> I was curious there will be any new releases coming out in Nagios.
> I remember there was memory leak in 3.3.1.
> 
> Are there any plans for any new releases?
> 

No, there will never be a new release of Nagios ever again. We've all
decided to take up knitting and unicorn-breeding instead.

On a more serious note; Ofcourse there will be a new release of Nagios.
The memory leaks are not very serious and have not yet been merged to
the Nagios core, so making a new release right now would be stupid. I
still need more time to fully investigate the pros and cons of the patch
sent in to handle the memory leak in the notification, for instance. I
believe the proposed fix either doesn't fix the leak completely or fixes
it in a bad way that would cause other problems, so I need to run it
through valgrind a couple of times to first of all see the leak for
myself and secondly make sure nothing bad happens when the patch is
applied and there are multiple notifications going out, of which some
are sent to escalated contacts.

In the meantime, you can restart your Nagios daemon once a year to avoid
any realworld problems from any potential leaks (although running latest
svn trunk would fix most of them too, so you could probably get away with
restarting only ever leapyear or something).

-- 
Andreas Ericsson   andreas.erics...@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
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] check_http and other response codes

[Jörg Linge]

Am 13.10.2011 um 09:18 schrieb Morty:

> On Wed, Oct 12, 2011 at 11:16:17PM -0500, Frank Bulk wrote:
>> Isn't there some regex matching?
> 
> There is.  But it didn't help me in either case.  check_http
> apparently does an implicit test to make sure it gets a valid response
> code such as 200.  And the regex checking is in content, not headers
> or response code.  So check_http -H $host -S -r 401 still returns a
> warning with a server that requires auth, and check_http -H $host -S
> -j TRACE -r 405 still returns a warning on a server with TRACE
> disabled.
> 
> While reading a different thread on this mailing list, I found Mark
> Thomas's mention of "negate".  That actually did workaround my HTTP
> TRACE problem -- TRACE will cause check_http to return a warning when
> it's disabled and ok when it's enabled, so the following command
> definition will test for HTTP TRACE:
> 
> define command{
>command_namecheck_http_trace
>command_line$USER1$/negate -sw OK -o CRITICAL -c OK -- 
> $USER1$/check_http -j TRACE -f sticky -H $HOSTADDRESS$ -p $ARG1$ $ARG2$
>}
> 
> But IMHO, that's something of a hack.  And it doesn't deal with the 401 issue.

http://nagiosplugins.org/man/check_http

Option -e

-e, --expect=STRING
Comma-delimited list of strings, at least one of them is expected in
the first (status) line of the server response (default: HTTP/1.)
If specified skips all other status line logic (ex: 3xx, 4xx, 5xx 
processing)
--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
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] check_http and other response codes

[Morty]

On Wed, Oct 12, 2011 at 11:16:17PM -0500, Frank Bulk wrote:
> Isn't there some regex matching?

There is.  But it didn't help me in either case.  check_http
apparently does an implicit test to make sure it gets a valid response
code such as 200.  And the regex checking is in content, not headers
or response code.  So check_http -H $host -S -r 401 still returns a
warning with a server that requires auth, and check_http -H $host -S
-j TRACE -r 405 still returns a warning on a server with TRACE
disabled.

While reading a different thread on this mailing list, I found Mark
Thomas's mention of "negate".  That actually did workaround my HTTP
TRACE problem -- TRACE will cause check_http to return a warning when
it's disabled and ok when it's enabled, so the following command
definition will test for HTTP TRACE:

define command{
command_namecheck_http_trace
command_line$USER1$/negate -sw OK -o CRITICAL -c OK -- 
$USER1$/check_http -j TRACE -f sticky -H $HOSTADDRESS$ -p $ARG1$ $ARG2$
}

But IMHO, that's something of a hack.  And it doesn't deal with the 401 issue.

- Morty

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
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