[Nagios-users] Event Handlers

2009-01-15 Thread Morris, Josh
Is there a way to run the an event handler from the web interface? 

Example: When our internet goes down I have an event handler to restart
a service on one of our Linux servers. This works great if the internet
is down for a minute or less. Once I know the internet is back up if it
has been down for more than a minute, I need to run the event handler
again but I don't see anywhere to run the event handler from the web
interface. I am having to remote into the server and reboot this
service.

 

Thanks for your help in advance.

 

Josh Morris

 

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword___
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] Retrieving Data from M.I.B.

2009-01-15 Thread Sean O`Brien
Dear Mailing List,


My question is regarding the check_snmp_int.pl plug-in functionality.

At present the script retrieves network information from the M.I.B.-II and has 
the functionality to output performance 
data in octects on specified devices.
Using, for example:

-Soption: Include speed in performance output in bits/s as 
'interface_name_speed_bps'
-y option : output performance data in % of interface speed


However, is there a plug-in (similar to the one above) that can calculate the 
percentage of interface speeds of Unicast 
and Broadcast packets?



Kind Regards


--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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] Retrieving Data from M.I.B.

2009-01-15 Thread Thomas Guyot-Sionnest
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 15/01/09 06:13 AM, Sean O`Brien wrote:
 Dear Mailing List,
 
 
 My question is regarding the check_snmp_int.pl plug-in functionality.
 
 At present the script retrieves network information from the M.I.B.-II and 
 has the functionality to output performance 
 data in octects on specified devices.
 Using, for example:
 
 -Soption: Include speed in performance output in bits/s as 
 'interface_name_speed_bps'
 -y option : output performance data in % of interface speed
 
 
 However, is there a plug-in (similar to the one above) that can calculate the 
 percentage of interface speeds of Unicast 
 and Broadcast packets?

To calculate percentage, you need a maximum value and you don't have one
for packets. Packet throughput depends mainly on average packet size and
hardware so there's no way it could be shown in percentage.

- --
Thomas
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJbxwW6dZ+Kt5BchYRAiE5AJwJg8dzHwPvd/tuSCQhV1qozw0fLgCg3tHr
1B1BP4bwPBeUVugePeRFkaA=
=mvWn
-END PGP SIGNATURE-

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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] Please help. Problem using check_nrpe and check_mailq

2009-01-15 Thread Sergio Ariel
I stopped Nagios first, and executed from Nagios Server:
check_nrpe -H Postfix Server's IP -t 500 -c check_cola_correo

and the result was the same (NRPE: Command timed out after 60 seconds) 
so, I don't think it's because a nagios.cfg's timeout definition.

Please, what do you think about?





jmose...@corp.xanadoo.com wrote:
 
 
 
 Sergio Ariel sergio.ar...@iris.uh.cu  wrote:
 
 
 I have installed NRPE to check a Postfix Server's mail queue.
 I have changed timeouts in order to obtain what I want.

 In Postfix Server I have declared in nrpe.cfg this:

 command[check_cola_correos]=/usr/local/nagios/libexec/check_mailq -w
 5000 -c 7000 -M postfix -t 450

 and when I run from Nagios Server this:
 check_nrpe -H Postfix Server's IP -t 500 -c check_cola_correo

 I obtain this error message:
 NRPE: Command timed out after 60 seconds

 What can I do?
 I don't know where is this timeout of 60 seconds.

 Thanks
 
 Perhaps the 'service_check_timeout' setting in the main nagios.cfg file?
 
 James
 
 
 

-- 
Sergio Ariel de la Campa Saiz
Administrador Red UH

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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] Please help. Problem using check_nrpe and check_mailq

2009-01-15 Thread jmoseley




Sergio Ariel sergio.ar...@iris.uh.cu  wrote:

I stopped Nagios first, and executed from Nagios Server:
check_nrpe -H Postfix Server's IP -t 500 -c check_cola_correo

and the result was the same (NRPE: Command timed out after 60 seconds)
so, I don't think it's because a nagios.cfg's timeout definition.

Please, what do you think about?

You need to adjust the timeout setting in nagios.cfg on the nagios server
AND adjusting the timeout setting (command_timeout=60) in the nrpe.cfg on
the Postfix server...  Those values will override anything you set in the
command line argument.

James



--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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] Acknowledged by user + Service action url

2009-01-15 Thread Palle L Jensen
Hello,

 

I have 2 problems that I am currently working on.

 

1. In Nagios Web-interface and when someone acknowledges a problem, the
Author (your name) it is pre-populated with Nagios and cannot be changed.
We would like to be able to populate that with operators that acknowledge
the problem.

- I have looked around on settings and permissions but can't find any
solution.

 

2. I wanted to have service action url in the acknowledge notes being sent
to operators from Nagios. The host action url works fine, but for the
service it does not populate the url in the notes.

- Below is how my commands look.

 

In commands.cfg it looks like this:

 

-- For host - and this works with action url: --

notify-host-by-email /usr/bin/printf %b * Nagios Monitoring 3.0.1
*\n\nNotification Type: $NOTIFICATIONTYPE$\n\nDate/Time:
$LONGDATETIME$\n\nHost: $HOSTNAME$\nState: $HOSTSTATE$\nAddress:
$HOSTADDRESS$\nInfo: $HOSTOUTPUT$\n\nOperator: $HOSTACKAUTHOR$\nComment:
$HOSTACKCOMMENT$\nUrl: $HOSTACTIONURL$ | /usr/bin/mail -s **
$NOTIFICATIONTYPE$ Host Alert: $HOSTNAME$ is $HOSTSTATE$ ** $CONTACTEMAIL$

 

Acknowledge note looks like this:

 

* Nagios Monitoring 3.0.1 *

Notification Type: ACKNOWLEDGEMENT

Date/Time: Wed Jan 14 06:58:12 EST 2009

Host: hostname

State: DOWN

Address: 1xx.xx.xxx.xxx

Info: CRITICAL - Host Unreachable (1xx.xx.xxx.xxx)

Operator: nagios

Comment: Server was Microsoft patched and rebooted

Url: http://1xx.xx.xxx.xxx/nagios/cgi-bin/extinfo.cgi?type=1
http://1xx.xx.xxx.xxx/nagios/cgi-bin/extinfo.cgi?type=1host=
host=hostname

 

 

-- For service - this does not work with action url: ---

notify-service-by-email /usr/bin/printf %b * CCO Nagios Monitoring
3.0.1 *\n\nNotification Type: $NOTIFICATIONTYPE$\n\nDate/Time:
$LONGDATETIME$\n\nService: $SERVICEDESC$\nHost: $HOSTALIAS$\nAddress:
$HOSTADDRESS$\nState: $SERVICESTATE$\n\nOperator:
$SERVICEACKAUTHOR$\nComment: $SERVICEACKCOMMENT$\nUrl:
$SERVICEACTIONURL$\nInfo:\n$SERVICEOUTPUT$ | /usr/bin/mail -s **
$NOTIFICATIONTYPE$ Service Alert: $HOSTALIAS$/$SERVICEDESC$ is
$SERVICESTATE$ ** $CONTACTEMAIL$ 

 

Acknowledge note looks like this:

 

* Nagios Monitoring 3.0.1 *

Notification Type: ACKNOWLEDGEMENT

Date/Time: Tue Jan 13 07:38:43 EST 2009

Service: Disk-C

Host: hostname

Address: 1xx.xx.xxx.xxx

State: WARNING

Operator: nagios

Comment: Need to free up space, forwarding to operator x.

Url: 

Info: c:\ - total: 9.77 Gb - used: 9.28 Gb (95%) - free 0.48 Gb (5%)

-

 

 

If anyone has any suggestions for changes that would make the 2 above
problems working it would be greatly appreciated.

 

 

Thanks,

PJ

 

.|.  OS:openSUSE 10.3 - Nagios:3.01 - Plugin 3.11  .|.

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword___
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] Next check time bug?

2009-01-15 Thread James Green
Albrecht,

Can you say if your patches made it into the Nagios build tree? It certainly 
sounds like a good contender.

The first patch fails to apply to the version shipped by Ubuntu 8.10 so either 
I wait for a fixed build in the months to come or I grab the source code with 
your patch applied.

Interestingly my nagios installations again reset the next check time to 
midnight tonight, so we effectively have monitoring 3.5hrsx7d at the moment :( 
Might need to reconfigure in other ways I think.

James

-Original Message-
From: Albrecht Dreß [mailto:albrecht.dr...@arcor.de] 
Sent: 14 January 2009 15:53
To: sosagabr...@gmail.com; James Green
Cc: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] Next check time bug?

 I have the exactly same problem this is my thread [1] but not not 
 replies so far.

No idea if this is related, but I discovered a bug which resulted in 
notifications *never* being sent under certain circumstances, so this smells 
somewhat similar...  You may want to check the diffs from 
http://article.gmane.org/gmane.network.nagios.devel/5910 and see if they 
solve your issue (you have to compile nagios yourself, though, but the diffs 
should also be usable with the 3.0.6 tarball).

Cheers, Albrecht.



Jetzt komfortabel bei Arcor-Digital TV einsteigen: Mehr Happy Ends, mehr 
Herzschmerz, mehr Fernsehen! Erleben Sie 50 digitale TV Programme und optional 
60 Pay TV Sender, einen elektronischen Programmführer mit Movie Star 
Bewertungen von TV Movie. Außerdem, aktuelle Filmhits und spannende Dokus in 
der Arcor-Videothek. Infos unter www.arcor.de/tv

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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] Calendar dates in timeperiods

2009-01-15 Thread nagios
Hi

Specs:
Nagios 3.0.3 
CentOS release 5.2 (Final)

I'm trying to configure a 'vacation' timeperiod so I will not receive alerts
using calendar dates, but once the dates are accepted into nagios, they seem
to go skewiff. 
My config looks like this;

define timeperiod{
timeperiod_name kristian_vacation
alias   Times Kristian is not in the
office.
2009-01-17 - 2009-02-10 00:00-24:00

}

From the web interface, it changes into this;

kristian_vacation   Times Kristian is not in the office.2009--1-17 -
2009-00-10 00:00:00 - 24:00:00

as you can see, the calendar dates change from 
2009-01-17 - 2009-02-10 
to
2009--1-17 - 2009-00-10


Is anybody else seeing the same thing or am I doing something obviously
wrong?


Cheers
Kristian




--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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] Please help. Problem using check_nrpe and check_mailq

2009-01-15 Thread Marc Powell

On Jan 15, 2009, at 8:06 AM, Sergio Ariel wrote:

 I stopped Nagios first, and executed from Nagios Server:
 check_nrpe -H Postfix Server's IP -t 500 -c check_cola_correo

 and the result was the same (NRPE: Command timed out after 60 seconds)
 so, I don't think it's because a nagios.cfg's timeout definition.

 Please, what do you think about?

Does whatever plugin 'check_cola_correo' runs have a timeout? Did you  
increase that?

--
Marc

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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] Acknowledged by user + Service action url {Fraud?}

2009-01-15 Thread Marc Powell

On Jan 15, 2009, at 8:28 AM, Palle L Jensen wrote:

 Hello,

 I have 2 problems that I am currently working on.

 1. In Nagios Web-interface and when someone acknowledges a problem,  
 the Author (your name) it is pre-populated with “Nagios” and cannot  
 be changed. We would like to be able to populate that with operators  
 that acknowledge the problem.
 - I have looked around on settings and permissions but can’t find  
 any solution.

http://nagios.sourceforge.net/docs/3_0/configcgi.html

Lock Author Names

Format: lock_author_names=[0/1]
Example:lock_author_names=1

This option allows you to restrict users from changing the author name  
when submitting comments, acknowledgements, and scheduled downtime  
from the web interface. If this option is enabled, users will be  
unable to change the author name associated with the command request.

 * 0 = Allow users to change author names when submitting commands
 * 1 = Prevent users from changing author names (default)

 2. I wanted to have service action url in the acknowledge notes  
 being sent to operators from Nagios. The host action url works fine,  
 but for the service it does not populate the url in the notes.
 - Below is how my commands look.


 -- For service – this does not work with action url: ---
 notify-service-by-email /usr/bin/printf %b * CCO Nagios  
 Monitoring 3.0.1 *\n\nNotification Type: $NOTIFICATIONTYPE$\n 
 \nDate/Time: $LONGDATETIME$\n\nService: $SERVICEDESC$\nHost:  
 $HOSTALIAS$\nAddress: $HOSTADDRESS$\nState: $SERVICESTATE$\n 
 \nOperator: $SERVICEACKAUTHOR$\nComment: $SERVICEACKCOMMENT$\nUrl:  
 $SERVICEACTIONURL$\nInfo:\n$SERVICEOUTPUT$ | /usr/bin/mail -s **  
 $NOTIFICATIONTYPE$ Service Alert: $HOSTALIAS$/$SERVICEDESC$ is  
 $SERVICESTATE$ ** $CONTACTEMAIL$

It does look like you're using the correct(ly spelled) macro. Are you  
sure that the service definition has action_url specified? Can you  
post it? I'd also enable debug mode in nagios.cfg and see if anything  
interesting showed up.

--
Marc


--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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] Acknowledged by user + Service action url

2009-01-15 Thread Chris Beattie
From: Palle L Jensen [mailto:pall...@gmail.com] 
Sent: Thursday, January 15, 2009 9:28 AM
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] Acknowledged by user + Service action url

1. In Nagios Web-interface and when someone acknowledges a problem, the
Author (your name) it is pre-populated with Nagios and cannot be
changed. We would like to be able to populate that with operators that
acknowledge the problem.

As far as I know, that field is automatically populated through some
alignment of the users being set up as contacts within Nagios, those
contacts being set up in cgi.cfg, and having access set up through
htpasswd.users.  I kept the user name in htpasswd.users the same as the
contact_name in contacts.cfg, and the $NOTIFICATIONAUTHORALIAS$ macro
got correctly set to the user's contact alias (where I put their full
name).

It all worked for me the first time I tried it, so I didn't get any
experience fixing any wrong-ness, though.

Nothing in this message is intended to make or accept and offer or to form a 
contract, except that an attachment that is an image of a contract bearing the 
signature of an officer of our company may be or become a contract. This 
message (including any attachments) is intended only for the use of the 
individual or entity to whom it is addressed. It may contain information that 
is non-public, proprietary, privileged, confidential, and exempt from 
disclosure under applicable law or may constitute as attorney work product. If 
you are not the intended recipient, we hereby notify you that any use, 
dissemination, distribution, or copying of this message is strictly prohibited. 
If you have received this message in error, please notify us immediately by 
telephone and delete this message immediately.

Thank you.

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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] Event Handlers

2009-01-15 Thread Morris, Patrick
 Is there a way to run the an event handler from the web interface? 
 Example: When our internet goes down I have an event handler to restart 
 a service on one of our Linux servers. This works great if the internet 
 is down for a minute or less. Once I know the internet is back up if it 
 has been down for more than a minute, I need to run the event handler 
 again but I don't see anywhere to run the event handler from the web 
 interface. I am having to remote into the server and reboot this service.

No, there is not. Event handlers are only run after service checks.


--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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] What does the flag failure_prediction_enabled

2009-01-15 Thread Michel MAYEN
Hi all,

I use Nagios 3.0.6

I can't find any informations on the flag failure_prediction_enabled
in service definition. What is the effect of this flag ?


Best regards,

Michel MAYEN


--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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_dhcp seems not working

2009-01-15 Thread Christian Iñiguez
Hi Everyone

I have a linux server as dhcp server and it's working very well, and I'd like 
to monitoring it with nrpe plugin and check_dhcp.

The problem here is the outcome of check_dhcp is always: CRITICAL: No 
DHCPOFFERs were received. But the server is working alright.

The command line is: check_dhcp -s serverip -t 30

What am I doing wrong? Any suggest?

Thanks in advance!

__
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ¡gratis! 
Regístrate ya - http://correo.yahoo.com.mx/ 

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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] Acknowledged by user + Service action url{Fraud?}

2009-01-15 Thread Palle L Jensen
Marc,

Thanks for you help!! I am half way there :=)

1.
 http://nagios.sourceforge.net/docs/3_0/configcgi.html
 
 Lock Author Names
 
 Format:   lock_author_names=[0/1]
 Example:  lock_author_names=1

That worked great, Recently was looking for something like this in the
cgi.cfg but never found the commands. I guess I should have looked closer in
the manual (http://nagios.sourceforge.net/docs/3_0/configcgi.html) cause
that made all sense. Adding that to the cgi.cfg worked perfect.

2.
 It does look like you're using the correct(ly spelled) macro. Are you
 sure that the service definition has action_url specified? Can you
 post it? I'd also enable debug mode in nagios.cfg and see if anything
 interesting showed up.

You are right I have been unable to add the action url in the service
definition, due to I have several hostnames for the specific service check.

For example the below DiskE check I have several hosts defined for that
check, how would I go by to replace johndoehost so the link will be
correct?
 
http://1xx.xx.xxx.xxx/nagios/cgi-bin/extinfo.cgi?type=2host=johndoehostser
vice=DiskE


Thanks,
PJ


 -Original Message-
 From: Marc Powell [mailto:m...@ena.com]
 Sent: Thursday, January 15, 2009 10:38 AM
 To: nagios-users Mailinglist
 Subject: Re: [Nagios-users] Acknowledged by user + Service action
 url{Fraud?}
 
 
 On Jan 15, 2009, at 8:28 AM, Palle L Jensen wrote:
 
  Hello,
 
  I have 2 problems that I am currently working on.
 
  1. In Nagios Web-interface and when someone acknowledges a problem,
  the Author (your name) it is pre-populated with Nagios and cannot
  be changed. We would like to be able to populate that with operators
  that acknowledge the problem.
  - I have looked around on settings and permissions but can't find
  any solution.
 
 http://nagios.sourceforge.net/docs/3_0/configcgi.html
 
 Lock Author Names
 
 Format:   lock_author_names=[0/1]
 Example:  lock_author_names=1
 
 This option allows you to restrict users from changing the author name
 when submitting comments, acknowledgements, and scheduled downtime
 from the web interface. If this option is enabled, users will be
 unable to change the author name associated with the command request.
 
  * 0 = Allow users to change author names when submitting commands
  * 1 = Prevent users from changing author names (default)
 
  2. I wanted to have service action url in the acknowledge notes
  being sent to operators from Nagios. The host action url works fine,
  but for the service it does not populate the url in the notes.
  - Below is how my commands look.
 
 
  -- For service - this does not work with action url: ---
  notify-service-by-email /usr/bin/printf %b * CCO Nagios
  Monitoring 3.0.1 *\n\nNotification Type: $NOTIFICATIONTYPE$\n
  \nDate/Time: $LONGDATETIME$\n\nService: $SERVICEDESC$\nHost:
  $HOSTALIAS$\nAddress: $HOSTADDRESS$\nState: $SERVICESTATE$\n
  \nOperator: $SERVICEACKAUTHOR$\nComment: $SERVICEACKCOMMENT$\nUrl:
  $SERVICEACTIONURL$\nInfo:\n$SERVICEOUTPUT$ | /usr/bin/mail -s **
  $NOTIFICATIONTYPE$ Service Alert: $HOSTALIAS$/$SERVICEDESC$ is
  $SERVICESTATE$ ** $CONTACTEMAIL$
 
 It does look like you're using the correct(ly spelled) macro. Are you
 sure that the service definition has action_url specified? Can you
 post it? I'd also enable debug mode in nagios.cfg and see if anything
 interesting showed up.
 
 --
 Marc
 
 
 --
 
 This SF.net email is sponsored by:
 SourcForge Community
 SourceForge wants to tell your story.
 http://p.sf.net/sfu/sf-spreadtheword
 ___
 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:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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_dhcp seems not working

2009-01-15 Thread jmoseley




Christian Iñiguez challenger_jos...@yahoo.com.mx  wrote:

Hi Everyone

I have a linux server as dhcp server and it's working very well, and I'd
like to monitoring it with nrpe plugin and check_dhcp.

The problem here is the outcome of check_dhcp is always: CRITICAL: No
DHCPOFFERs were received. But the server is working alright.

The command line is: check_dhcp -s serverip -t 30

What am I doing wrong? Any suggest?

Thanks in advance!

I have no idea which flavor of DHCP you are running (probably ISC's), but I
don't think you are going to be able to run check_dhcp from the DHCP server
itself.  The DHCP server will see an incoming requeset from itself and
probably block it.  Therefore, using the nrpe method of doing these checks
is a moot point.

If your Nagios server is on the same network as the DHCP server, just run
check_dhcp from the Nagios box.  If you're running Nagios on a different
network than the DHCP server and there is a firewall in between, you'll
probably have to do several things:

1. Open up a hole in the firewall to allow the Nagios server to request a
DHCP address from the DHCP server
2. Have a DHCP relay statement on the router's interface your Nagios server
connects to so it knows to which server to relay the DHCP request to
3. Setup a small DHCP subnet on the DHCP server in the same IP range as the
Nagios server so it can offer a valid IP address

There are probably other methods as well.

James





--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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] Question about using the NSCA addon

2009-01-15 Thread Matthew Tice
I'm interested in using the nsca addon - but only the daemon.  I thought I
could just open an tcp connection to the daemon and send my update manually:

echo 3\t1\tmt-ubuntu\tSMTP Availability\tFAIL\n | netcat nocnag02 5667

I set the value decryption_method=0 in the server config file (because I'm
not doing any encryption on the client end).

Is this possible?  I looked through the source and tried to create the
necessary string - but I'm thinking I'm missing something.  Any ideas?  Feel
free to tell me I'm way off here.

Matt
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword___
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_dhcp seems not working

2009-01-15 Thread Christian Iñiguez
In deed both servers (the dhcp server and nagios server) are in the same subnet 
and there is no firewall between them. From the nagios server I run 
check_nrpe!check_dhcp

And in the side of dhcp server I run the command: check_dhcp -s ip_dhcp_server 
-t 30

Actually I'm running other services like check_load, check_procs, etc. With no 
problems.

Just check_dhcp is not working

My dhcp server is a RHEL 5 with dhcp-3.0.5-3.el5

I hope this help!



- Mensaje original 
De: jmose...@corp.xanadoo.com jmose...@corp.xanadoo.com
Para: Christian Iñiguez challenger_jos...@yahoo.com.mx
CC: nagios-users@lists.sourceforge.net
Enviado: jueves, 15 de enero, 2009 13:06:21
Asunto: Re: [Nagios-users] check_dhcp seems not working





Christian Iñiguez challenger_jos...@yahoo.com.mx  wrote:

Hi Everyone

I have a linux server as dhcp server and it's working very well, and I'd
like to monitoring it with nrpe plugin and check_dhcp.

The problem here is the outcome of check_dhcp is always: CRITICAL: No
DHCPOFFERs were received. But the server is working alright.

The command line is: check_dhcp -s serverip -t 30

What am I doing wrong? Any suggest?

Thanks in advance!

I have no idea which flavor of DHCP you are running (probably ISC's), but I
don't think you are going to be able to run check_dhcp from the DHCP server
itself.  The DHCP server will see an incoming requeset from itself and
probably block it.  Therefore, using the nrpe method of doing these checks
is a moot point.

If your Nagios server is on the same network as the DHCP server, just run
check_dhcp from the Nagios box.  If you're running Nagios on a different
network than the DHCP server and there is a firewall in between, you'll
probably have to do several things:

1. Open up a hole in the firewall to allow the Nagios server to request a
DHCP address from the DHCP server
2. Have a DHCP relay statement on the router's interface your Nagios server
connects to so it knows to which server to relay the DHCP request to
3. Setup a small DHCP subnet on the DHCP server in the same IP range as the
Nagios server so it can offer a valid IP address

There are probably other methods as well.

James

__
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ¡gratis! 
Regístrate ya - http://correo.yahoo.com.mx/ 

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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_dhcp seems not working

2009-01-15 Thread Morris, Patrick
 I have a linux server as dhcp server and it's working very well, and
 I'd like to monitoring it with nrpe plugin and check_dhcp.
 
 The problem here is the outcome of check_dhcp is always: CRITICAL: No
 DHCPOFFERs were received. But the server is working alright.
 
 The command line is: check_dhcp -s serverip -t 30
 
 What am I doing wrong? Any suggest?

This one's come up a billion times or so on the list, but the most likely cause 
of your problem is that the plugin needs to be setuid root.

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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_dhcp seems not working

2009-01-15 Thread Christian Iñiguez
Thanks but actually the plugin is setuid root, and as user root and user nagios 
the outcome is the same =(



- Mensaje original 
De: Morris, Patrick patrick.mor...@hp.com
Para: Christian Iñiguez challenger_jos...@yahoo.com.mx; 
nagios-users@lists.sourceforge.net nagios-users@lists.sourceforge.net
Enviado: jueves, 15 de enero, 2009 13:18:08
Asunto: RE: [Nagios-users] check_dhcp seems not working

 I have a linux server as dhcp server and it's working very well, and
 I'd like to monitoring it with nrpe plugin and check_dhcp.
 
 The problem here is the outcome of check_dhcp is always: CRITICAL: No
 DHCPOFFERs were received. But the server is working alright.
 
 The command line is: check_dhcp -s serverip -t 30
 
 What am I doing wrong? Any suggest?

This one's come up a billion times or so on the list, but the most likely cause 
of your problem is that the plugin needs to be setuid root.


__
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ¡gratis! 
Regístrate ya - http://correo.yahoo.com.mx/ 

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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_dhcp seems not working

2009-01-15 Thread jmoseley


James Moseley




Christian Iñiguez challenger_jos...@yahoo.com.mx  wrote:

In deed both servers (the dhcp server and nagios server) are in the same
subnet and there is no firewall between them. From the nagios server I run
check_nrpe!check_dhcp

And in the side of dhcp server I run the command: check_dhcp -s
ip_dhcp_server -t 30

Actually I'm running other services like check_load, check_procs, etc.
With no problems.

Just check_dhcp is not working

My dhcp server is a RHEL 5 with dhcp-3.0.5-3.el5

In my previous reply, I told you that what you are trying to do above will
*not* work.  Do not try and check your DHCP server from the Nagios server
using check_nrpe and running check_dhcp on the DHCP server itself.

Run check_dhcp directly from the Nagios server.

James





--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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_dhcp seems not working

2009-01-15 Thread Kevin Keane
jmose...@corp.xanadoo.com wrote:


 Christian Iñiguez challenger_jos...@yahoo.com.mx  wrote:

   
 Hi Everyone

 I have a linux server as dhcp server and it's working very well, and I'd
 
 like to monitoring it with nrpe plugin and check_dhcp.
   
 The problem here is the outcome of check_dhcp is always: CRITICAL: No
 
 DHCPOFFERs were received. But the server is working alright.
   
 The command line is: check_dhcp -s serverip -t 30

 What am I doing wrong? Any suggest?

 Thanks in advance!
 

 I have no idea which flavor of DHCP you are running (probably ISC's), but I
 don't think you are going to be able to run check_dhcp from the DHCP server
 itself.  The DHCP server will see an incoming requeset from itself and
 probably block it.  Therefore, using the nrpe method of doing these checks
 is a moot point.

 If your Nagios server is on the same network as the DHCP server, just run
 check_dhcp from the Nagios box.  If you're running Nagios on a different
 network than the DHCP server and there is a firewall in between, you'll
 probably have to do several things:

 1. Open up a hole in the firewall to allow the Nagios server to request a
 DHCP address from the DHCP server
 2. Have a DHCP relay statement on the router's interface your Nagios server
 connects to so it knows to which server to relay the DHCP request to
 3. Setup a small DHCP subnet on the DHCP server in the same IP range as the
 Nagios server so it can offer a valid IP address
I actually have the same problem as Christian, and it does NOT work even 
though Nagios is running on a different box on the same network as the 
DHCP server. In fact, the Nagios box actually gets its IP address from 
the same DHCP server that I would like to monitor (ISC DHCP server 3.0.6 
on a SuSE 10.3). I've seen the same problem before against a Windows 
DHCP server, too, never been able to make check_dhcp work.

check_dhcp -v prints this:

DHCP socket: 3
Hardware address: 00:0c:29:0e:28:4f
DHCPDISCOVER to 255.255.255.255 port 67
DHCPDISCOVER XID: 2138668641 (0x7F797E61)
DHCDISCOVER ciaddr:  0.0.0.0
DHCDISCOVER yiaddr:  0.0.0.0
DHCDISCOVER siaddr:  0.0.0.0
DHCDISCOVER giaddr:  0.0.0.0
send_dhcp_packet result: 548




No (more) data received (nfound: 0)
Result=ERROR
Total responses seen on the wire: 0
Valid responses for this machine: 0
CRITICAL: No DHCPOFFERs were received.

-- 
Kevin Keane
Owner
The NetTech
Find the Uncommon: Expert Solutions for a Network You Never Have to Think About

Office: 866-642-7116
http://www.4nettech.com

This e-mail and attachments, if any, may contain confidential and/or 
proprietary information. Please be advised that the unauthorized use or 
disclosure of the information is strictly prohibited. The information herein is 
intended only for use by the intended recipient(s) named above. If you have 
received this transmission in error, please notify the sender immediately and 
permanently delete the e-mail and any copies, printouts or attachments thereof.


--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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] problem check_dell plugin

2009-01-15 Thread Seth Simmons
I'm having a problem using the dell plugin (from
http://www.itefix.no/i2/check_dell, nothing useful in the forum)

If I run the plugin (as nagios) on the box, it works fine.

$ perl check_dell.pl --storage
DELL STORAGE OK - Controller battery 0:ok  Controller perc 5/i
integrated:ok  Enclosure backplane:ok  virtual disk 0:ok


However, through nagios, it shows (null) and I can't figure out what I'm
doing wrong.

Here are the commands I have:

define command{
command_namecheck_chassis
command_line/usr/bin/perl
/usr/local/nagios/libexec/check_dell.pl --chassis
}

define command{
command_namecheck_storage
command_line/usr/bin/perl
/usr/local/nagios/libexec/check_dell.pl --storage
}



--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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] Acknowledged by user + Service action url

2009-01-15 Thread Marc Powell

On Jan 15, 2009, at 12:51 PM, Palle L Jensen wrote:

 Marc,

 Thanks for you help!! I am half way there :=)

Good deal.

 You are right I have been unable to add the action url in the service
 definition, due to I have several hostnames for the specific service  
 check.

 For example the below DiskE check I have several hosts defined for  
 that
 check, how would I go by to replace johndoehost so the link will be
 correct?

 http://1xx.xx.xxx.xxx/nagios/cgi-bin/extinfo.cgi?type=2host=johndoehostser
 vice=DiskE


http://nagios.sourceforge.net/docs/3_0/macros.html

Macro Substitution - How Macros Work

Before Nagios executes a command, it will replace any macros it finds  
in the command definition with their corresponding values. This macro  
substitution occurs for all types of commands that Nagios executes -  
host and service checks, notifications, event handlers, etc.

Certain macros may themselves contain other macros. These include the  
$HOSTNOTES$, $HOSTNOTESURL$, $HOSTACTIONURL$, $SERVICENOTES$,  
$SERVICENOTESURL$, and $SERVICEACTIONURL$ macros. 

In your case, I expect the following should work --

define service {
...
action_url  
http://1xxx.xx.xxx.xxx/nagios/cgi-bin/extinfo.cgi?type=2host=$HOSTNAME$service=DiskE
...
}

--
Marc

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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_dhcp seems not working

2009-01-15 Thread Christian Iñiguez
I'm sorry, I already understood. But well, I did it like you told me, and I got 
the same outcome

Running the check_dhcp on the nagios server.



- Mensaje original 
De: jmose...@corp.xanadoo.com jmose...@corp.xanadoo.com
Para: Christian Iñiguez challenger_jos...@yahoo.com.mx
CC: nagios-users@lists.sourceforge.net
Enviado: jueves, 15 de enero, 2009 13:25:24
Asunto: Re: [Nagios-users] check_dhcp seems not working



James Moseley




Christian Iñiguez challenger_jos...@yahoo.com.mx  wrote:

In deed both servers (the dhcp server and nagios server) are in the same
subnet and there is no firewall between them. From the nagios server I run
check_nrpe!check_dhcp

And in the side of dhcp server I run the command: check_dhcp -s
ip_dhcp_server -t 30

Actually I'm running other services like check_load, check_procs, etc.
With no problems.

Just check_dhcp is not working

My dhcp server is a RHEL 5 with dhcp-3.0.5-3.el5

In my previous reply, I told you that what you are trying to do above will
*not* work.  Do not try and check your DHCP server from the Nagios server
using check_nrpe and running check_dhcp on the DHCP server itself.

Run check_dhcp directly from the Nagios server.

James

__
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ¡gratis! 
Regístrate ya - http://correo.yahoo.com.mx/ 

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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_dhcp seems not working

2009-01-15 Thread Christian Iñiguez
Exactly Kevin, you are right



- Mensaje original 
De: Kevin Keane subscript...@kkeane.com
CC: nagios-users@lists.sourceforge.net
Enviado: jueves, 15 de enero, 2009 13:39:47
Asunto: Re: [Nagios-users] check_dhcp seems not working

jmose...@corp.xanadoo.com wrote:


 Christian Iñiguez challenger_jos...@yahoo.com.mx  wrote:

  
 Hi Everyone

 I have a linux server as dhcp server and it's working very well, and I'd
    
 like to monitoring it with nrpe plugin and check_dhcp.
  
 The problem here is the outcome of check_dhcp is always: CRITICAL: No
    
 DHCPOFFERs were received. But the server is working alright.
  
 The command line is: check_dhcp -s serverip -t 30

 What am I doing wrong? Any suggest?

 Thanks in advance!
    

 I have no idea which flavor of DHCP you are running (probably ISC's), but I
 don't think you are going to be able to run check_dhcp from the DHCP server
 itself.  The DHCP server will see an incoming requeset from itself and
 probably block it.  Therefore, using the nrpe method of doing these checks
 is a moot point.

 If your Nagios server is on the same network as the DHCP server, just run
 check_dhcp from the Nagios box.  If you're running Nagios on a different
 network than the DHCP server and there is a firewall in between, you'll
 probably have to do several things:

 1. Open up a hole in the firewall to allow the Nagios server to request a
 DHCP address from the DHCP server
 2. Have a DHCP relay statement on the router's interface your Nagios server
 connects to so it knows to which server to relay the DHCP request to
 3. Setup a small DHCP subnet on the DHCP server in the same IP range as the
 Nagios server so it can offer a valid IP address
I actually have the same problem as Christian, and it does NOT work even 
though Nagios is running on a different box on the same network as the 
DHCP server. In fact, the Nagios box actually gets its IP address from 
the same DHCP server that I would like to monitor (ISC DHCP server 3.0.6 
on a SuSE 10.3). I've seen the same problem before against a Windows 
DHCP server, too, never been able to make check_dhcp work.

check_dhcp -v prints this:

DHCP socket: 3
Hardware address: 00:0c:29:0e:28:4f
DHCPDISCOVER to 255.255.255.255 port 67
DHCPDISCOVER XID: 2138668641 (0x7F797E61)
DHCDISCOVER ciaddr:  0.0.0.0
DHCDISCOVER yiaddr:  0.0.0.0
DHCDISCOVER siaddr:  0.0.0.0
DHCDISCOVER giaddr:  0.0.0.0
send_dhcp_packet result: 548




No (more) data received (nfound: 0)
Result=ERROR
Total responses seen on the wire: 0
Valid responses for this machine: 0
CRITICAL: No DHCPOFFERs were received.

-- 
Kevin Keane
Owner
The NetTech
Find the Uncommon: Expert Solutions for a Network You Never Have to Think About

Office: 866-642-7116
http://www.4nettech.com

This e-mail and attachments, if any, may contain confidential and/or 
proprietary information. Please be advised that the unauthorized use or 
disclosure of the information is strictly prohibited. The information herein is 
intended only for use by the intended recipient(s) named above. If you have 
received this transmission in error, please notify the sender immediately and 
permanently delete the e-mail and any copies, printouts or attachments thereof.


--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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


__
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ¡gratis! 
Regístrate ya - http://correo.yahoo.com.mx/ 

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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_dhcp seems not working

2009-01-15 Thread jmoseley
   
 Christian Iñiguez 
 challenger_josep 
 h...@yahoo.com.mxTo 
   Morris, Patrick   
 01/15/2009 01:24  patrick.mor...@hp.com,
 PMnagios-users@lists.sourceforge.net  
cc 
   
   Subject 
   Re: [Nagios-users] check_dhcp seems 
   not working 
   
   
   
   
   
   






Christian Iñiguez challenger_jos...@yahoo.com.mx wrote:

Thanks but actually the plugin is setuid root, and as user root and user
nagios the outcome is the same =(

Christian, Patrick is correct, and something I forgot about.  The
check_dhcp plugin needs to be setuid, which you've indicated it is.

Can you try running check_dhcp directly from the Nagios server though?
With your setup, it doesn't make sense to use check_nrpe when you can query
the DHCP server directly.  And as I've said, I'm not sure you are going to
be able to run check_dhcp from the DHCP server itself, unless you have
multiple interfaces.


Morris, Patrick patrick.mor...@hp.com wrote:


This one's come up a billion times or so on the list, but the most likely
cause of your problem is that the plugin needs to be setuid root.



James


--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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_dhcp seems not working

2009-01-15 Thread Kevin Keane
Christian, actually, your question prompted me to try it again. Turned 
out that it was the firewall software on my Nagios box that blocked the 
DHCP request. As soon as I turned it off, check_dhcp worked. I'm not yet 
sure which ports to open to make it work with the firewall on. So far, I 
tried ports 67 and 68 for both TCP and UDP, but that seems not to be enough.

Christian Iñiguez wrote:
 Exactly Kevin, you are right



 - Mensaje original 
 De: Kevin Keane subscript...@kkeane.com
 CC: nagios-users@lists.sourceforge.net
 Enviado: jueves, 15 de enero, 2009 13:39:47
 Asunto: Re: [Nagios-users] check_dhcp seems not working

 jmose...@corp.xanadoo.com wrote:
   
 Christian Iñiguez challenger_jos...@yahoo.com.mx  wrote:

   
 
 Hi Everyone

 I have a linux server as dhcp server and it's working very well, and I'd
 
   
 like to monitoring it with nrpe plugin and check_dhcp.
   
 
 The problem here is the outcome of check_dhcp is always: CRITICAL: No
 
   
 DHCPOFFERs were received. But the server is working alright.
   
 
 The command line is: check_dhcp -s serverip -t 30

 What am I doing wrong? Any suggest?

 Thanks in advance!
 
   
 I have no idea which flavor of DHCP you are running (probably ISC's), but I
 don't think you are going to be able to run check_dhcp from the DHCP server
 itself.  The DHCP server will see an incoming requeset from itself and
 probably block it.  Therefore, using the nrpe method of doing these checks
 is a moot point.

 If your Nagios server is on the same network as the DHCP server, just run
 check_dhcp from the Nagios box.  If you're running Nagios on a different
 network than the DHCP server and there is a firewall in between, you'll
 probably have to do several things:

 1. Open up a hole in the firewall to allow the Nagios server to request a
 DHCP address from the DHCP server
 2. Have a DHCP relay statement on the router's interface your Nagios server
 connects to so it knows to which server to relay the DHCP request to
 3. Setup a small DHCP subnet on the DHCP server in the same IP range as the
 Nagios server so it can offer a valid IP address
 
 I actually have the same problem as Christian, and it does NOT work even 
 though Nagios is running on a different box on the same network as the 
 DHCP server. In fact, the Nagios box actually gets its IP address from 
 the same DHCP server that I would like to monitor (ISC DHCP server 3.0.6 
 on a SuSE 10.3). I've seen the same problem before against a Windows 
 DHCP server, too, never been able to make check_dhcp work.

 check_dhcp -v prints this:

 DHCP socket: 3
 Hardware address: 00:0c:29:0e:28:4f
 DHCPDISCOVER to 255.255.255.255 port 67
 DHCPDISCOVER XID: 2138668641 (0x7F797E61)
 DHCDISCOVER ciaddr:  0.0.0.0
 DHCDISCOVER yiaddr:  0.0.0.0
 DHCDISCOVER siaddr:  0.0.0.0
 DHCDISCOVER giaddr:  0.0.0.0
 send_dhcp_packet result: 548




 No (more) data received (nfound: 0)
 Result=ERROR
 Total responses seen on the wire: 0
 Valid responses for this machine: 0
 CRITICAL: No DHCPOFFERs were received.

   


-- 
Kevin Keane
Owner
The NetTech
Find the Uncommon: Expert Solutions for a Network You Never Have to Think About

Office: 866-642-7116
http://www.4nettech.com

This e-mail and attachments, if any, may contain confidential and/or 
proprietary information. Please be advised that the unauthorized use or 
disclosure of the information is strictly prohibited. The information herein is 
intended only for use by the intended recipient(s) named above. If you have 
received this transmission in error, please notify the sender immediately and 
permanently delete the e-mail and any copies, printouts or attachments thereof.


--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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] problem check_dell plugin

2009-01-15 Thread Kevin Keane
My guess is that the path environment is different when run under 
Nagios, and check_dell.pl can't find the Dell OpenManage software. I'm 
not sure exactly how it works on Unix, but the Windows version of 
check_dell uses OpenManage to actually do the checking.

Seth Simmons wrote:
 I'm having a problem using the dell plugin (from
 http://www.itefix.no/i2/check_dell, nothing useful in the forum)

 If I run the plugin (as nagios) on the box, it works fine.

 $ perl check_dell.pl --storage
 DELL STORAGE OK - Controller battery 0:ok  Controller perc 5/i
 integrated:ok  Enclosure backplane:ok  virtual disk 0:ok


 However, through nagios, it shows (null) and I can't figure out what I'm
 doing wrong.

 Here are the commands I have:

 define command{
 command_namecheck_chassis
 command_line/usr/bin/perl
 /usr/local/nagios/libexec/check_dell.pl --chassis
 }

 define command{
 command_namecheck_storage
 command_line/usr/bin/perl
 /usr/local/nagios/libexec/check_dell.pl --storage
 }



 --
 This SF.net email is sponsored by:
 SourcForge Community
 SourceForge wants to tell your story.
 http://p.sf.net/sfu/sf-spreadtheword
 ___
 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
   


-- 
Kevin Keane
Owner
The NetTech
Find the Uncommon: Expert Solutions for a Network You Never Have to Think About

Office: 866-642-7116
http://www.4nettech.com

This e-mail and attachments, if any, may contain confidential and/or 
proprietary information. Please be advised that the unauthorized use or 
disclosure of the information is strictly prohibited. The information herein is 
intended only for use by the intended recipient(s) named above. If you have 
received this transmission in error, please notify the sender immediately and 
permanently delete the e-mail and any copies, printouts or attachments thereof.


--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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_dhcp seems not working

2009-01-15 Thread James Miller

Sorry for the top post

  1. Lease Request - The client sends a broadcast requesting an IP address
  2. Lease Offer - The server sends the above information and marks the
 offered address as unavailable. The message sent is a DHCPOFFER
 broadcast message.
  3. Lease Acceptance - The first offer received by the client is
 accepted. The acceptance is sent from the client as a broadcast
 (DHCPREQUEST message) including the IP address of the DNS server
 that sent the accepted offer. Other DHCP servers retract their
 offers and mark the offered address as available and the accepted
 address as unavailable.
  4. Server lease acknowledgement - The server sends a DHCPACK or a
 DHCPNACK if an unavailable address was requested.

All DHCP packets travel as UDP datagrams; all client-sent packets have 
source port 68 and destination port 67; all server-sent packets have 
source port 67 and destination port 68. For example, a server-side 
firewall should allow the following types of packets:


   * Incoming packets from 0.0.0.0 or dhcp-pool to dhcp-ip
   * Incoming packets from any address to 255.255.255.255
   * Outgoing packets from dhcp-ip to dhcp-pool or 255.255.255.255

where dhcp-ip represents any address configured on a DHCP server host 
and dhcp-pool stands for the pool from which a DHCP server assigns 
addresses to clients



Jim





Kevin Keane wrote:
Christian, actually, your question prompted me to try it again. Turned 
out that it was the firewall software on my Nagios box that blocked the 
DHCP request. As soon as I turned it off, check_dhcp worked. I'm not yet 
sure which ports to open to make it work with the firewall on. So far, I 
tried ports 67 and 68 for both TCP and UDP, but that seems not to be enough.


Christian Iñiguez wrote:
  

Exactly Kevin, you are right



- Mensaje original 
De: Kevin Keane subscript...@kkeane.com
CC: nagios-users@lists.sourceforge.net
Enviado: jueves, 15 de enero, 2009 13:39:47
Asunto: Re: [Nagios-users] check_dhcp seems not working

jmose...@corp.xanadoo.com wrote:
  


Christian Iñiguez challenger_jos...@yahoo.com.mx  wrote:

  

  

Hi Everyone

I have a linux server as dhcp server and it's working very well, and I'd

  


like to monitoring it with nrpe plugin and check_dhcp.
  

  

The problem here is the outcome of check_dhcp is always: CRITICAL: No

  


DHCPOFFERs were received. But the server is working alright.
  

  

The command line is: check_dhcp -s serverip -t 30

What am I doing wrong? Any suggest?

Thanks in advance!

  


I have no idea which flavor of DHCP you are running (probably ISC's), but I
don't think you are going to be able to run check_dhcp from the DHCP server
itself.  The DHCP server will see an incoming requeset from itself and
probably block it.  Therefore, using the nrpe method of doing these checks
is a moot point.

If your Nagios server is on the same network as the DHCP server, just run
check_dhcp from the Nagios box.  If you're running Nagios on a different
network than the DHCP server and there is a firewall in between, you'll
probably have to do several things:

1. Open up a hole in the firewall to allow the Nagios server to request a
DHCP address from the DHCP server
2. Have a DHCP relay statement on the router's interface your Nagios server
connects to so it knows to which server to relay the DHCP request to
3. Setup a small DHCP subnet on the DHCP server in the same IP range as the
Nagios server so it can offer a valid IP address

  
I actually have the same problem as Christian, and it does NOT work even 
though Nagios is running on a different box on the same network as the 
DHCP server. In fact, the Nagios box actually gets its IP address from 
the same DHCP server that I would like to monitor (ISC DHCP server 3.0.6 
on a SuSE 10.3). I've seen the same problem before against a Windows 
DHCP server, too, never been able to make check_dhcp work.


check_dhcp -v prints this:

DHCP socket: 3
Hardware address: 00:0c:29:0e:28:4f
DHCPDISCOVER to 255.255.255.255 port 67
DHCPDISCOVER XID: 2138668641 (0x7F797E61)
DHCDISCOVER ciaddr:  0.0.0.0
DHCDISCOVER yiaddr:  0.0.0.0
DHCDISCOVER siaddr:  0.0.0.0
DHCDISCOVER giaddr:  0.0.0.0
send_dhcp_packet result: 548




No (more) data received (nfound: 0)
Result=ERROR
Total responses seen on the wire: 0
Valid responses for this machine: 0
CRITICAL: No DHCPOFFERs were received.

  




  
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword___
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 

Re: [Nagios-users] check_dhcp seems not working

2009-01-15 Thread jmoseley




Kevin Keane subscript...@kkeane.com wrote:

Christian, actually, your question prompted me to try it again. Turned
out that it was the firewall software on my Nagios box that blocked the
DHCP request. As soon as I turned it off, check_dhcp worked. I'm not yet
sure which ports to open to make it work with the firewall on. So far, I
tried ports 67 and 68 for both TCP and UDP, but that seems not to be
enough.

Kevin, that's a really good point.  Christian, do you have iptables running
on either the nagios or DHCP server boxes?

James


--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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_dhcp seems not working

2009-01-15 Thread Holger Weiss
JFTR:

* jmose...@corp.xanadoo.com [2009-01-15 13:06]:
 If you're running Nagios on a different network than the DHCP server and
 there is a firewall in between, you'll probably have to do several things:
 
 1. Open up a hole in the firewall to allow the Nagios server to request a
 DHCP address from the DHCP server
 2. Have a DHCP relay statement on the router's interface your Nagios server
 connects to so it knows to which server to relay the DHCP request to
 3. Setup a small DHCP subnet on the DHCP server in the same IP range as the
 Nagios server so it can offer a valid IP address

For such a setup, step (2) isn't necessary, as check_dhcp will mimic a
DHCP relay if the --unicast option is specified.

Holger

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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_dhcp seems not working

2009-01-15 Thread Holger Weiss
* Christian Iñiguez challenger_jos...@yahoo.com.mx [2009-01-15 10:46]:
 I have a linux server as dhcp server and it's working very well, and
 I'd like to monitoring it with nrpe plugin and check_dhcp.
 
 The problem here is the outcome of check_dhcp is always: CRITICAL: No
 DHCPOFFERs were received. But the server is working alright.

Do you see the request and a reply in the DHCP server's logs?  If so,
could you verify that the server's reply reaches the host running
check_dhcp using tcpdump(8) (e.g., tcpdump -vv port bootps)?

Holger

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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] Next check time bug?

2009-01-15 Thread Albrecht Dreß

Am 15.01.09 15:29 schrieb(en) James Green:
Can you say if your patches made it into the Nagios build tree? It  
certainly sounds like a good contender.


They are in the CVS tree, which according to the Changelog is going to  
be Release 3.1.0...


The first patch fails to apply to the version shipped by Ubuntu 8.10  
so either I wait for a fixed build in the months to come or I grab  
the source code with your patch applied.


IIRC, Ubuntu comes with old versions (I run 8.04 LTS on a Xeon/64 bit  
system, where I found the issue), so I decided to compile it myself  
from sources.  You might try to install from sources into e.g. /opt and  
then symlink the configs to your existing folders, just to check if it  
solves your problem, without breaking the original installation.   
Although the bug I discovered could trigger really strange effects, you  
might actually be hit by something else, so some further tests might be  
really helpful...


Cheers, Albrecht.


pgpq5dFBA15Rh.pgp
Description: PGP signature
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword___
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_dhcp seems not working

2009-01-15 Thread jmoseley




Holger Weiss hol...@cis.fu-berlin.de  wrote:


* jmose...@corp.xanadoo.com [2009-01-15 13:06]:

 2. Have a DHCP relay statement on the router's interface your Nagios
server
 connects to so it knows to which server to relay the DHCP request to

For such a setup, step (2) isn't necessary, as check_dhcp will mimic a
DHCP relay if the --unicast option is specified.

What I meant was you'd have to have an ip helper-address configured.

James


--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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_dhcp seems not working

2009-01-15 Thread Holger Weiss
* jmose...@corp.xanadoo.com [2009-01-15 14:59]:
 Holger Weiss hol...@cis.fu-berlin.de  wrote:
 * jmose...@corp.xanadoo.com [2009-01-15 13:06]:
  2. Have a DHCP relay statement on the router's interface your Nagios server
  connects to so it knows to which server to relay the DHCP request to

 For such a setup, step (2) isn't necessary, as check_dhcp will mimic a
 DHCP relay if the --unicast option is specified.

 What I meant was you'd have to have an ip helper-address configured.

But that's precisely what you don't need if you use check_dhcp's
--unicast option :-)  If you configure an ip helper-address (as
Cisco calls it), the router will relay local DHCP broadcast packets to
the specified remote DHCP server.  check_dhcp --unicast creates the
same sort of unicast packets such a relay would generate.

Holger

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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] problem check_dell plugin

2009-01-15 Thread Brian A. Seklecki

Try:

$ sudo -H -u nagios /usr/bin/perl /usr/local/nagios/libexec/check_dell.pl
--chassis

Otherwise, turn up the debugging in Nagios all the way.

~BAS

On Thu, 15 Jan 2009, Seth Simmons wrote:

 I'm having a problem using the dell plugin (from
 http://www.itefix.no/i2/check_dell, nothing useful in the forum)

 If I run the plugin (as nagios) on the box, it works fine.

 $ perl check_dell.pl --storage
 DELL STORAGE OK - Controller battery 0:ok  Controller perc 5/i
 integrated:ok  Enclosure backplane:ok  virtual disk 0:ok


 However, through nagios, it shows (null) and I can't figure out what I'm
 doing wrong.

 Here are the commands I have:

 define command{
 command_namecheck_chassis
 command_line/usr/bin/perl
 /usr/local/nagios/libexec/check_dell.pl --chassis
 }

 define command{
 command_namecheck_storage
 command_line/usr/bin/perl
 /usr/local/nagios/libexec/check_dell.pl --storage
 }



 --
 This SF.net email is sponsored by:
 SourcForge Community
 SourceForge wants to tell your story.
 http://p.sf.net/sfu/sf-spreadtheword
 ___
 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


l8*
-lava (Brian A. Seklecki - Pittsburgh, PA, USA)
   http://www.spiritual-machines.org/

Show me a young conservative and I'll show you someone with no heart.
Show me an old liberal and I'll show you someone with no brains.
~ Winston Churchill

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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] Windows disk health monitoring with smartmontoolsl/NSClient++?

2009-01-15 Thread Eric Pearce
Thanks for the tip -  I think I'm making some progress, i.e. 

 C:\Program Files\NSClient++nsclient++.exe CheckWMI Select Status from 
Win32_DiskDrive

 \NSClient++.cpp(370) Attempting to start NSCLient++ - 0.3.5.2 2008-09-24 

l \NSClient++.cpp(476) NSCLient++ - 0.3.5.2 2008-09-24 Started! 

l \CheckWMI.cpp(306) |+ 

l \CheckWMI.cpp(307) | Status | 

l \CheckWMI.cpp(308) |+ 

l \CheckWMI.cpp(317) | OK | 

l \CheckWMI.cpp(319) |+ 

l \NSClient++.cpp(530) Attempting to stop NSCLient++ - 0.3.5.2 2008-09-24 

l \NSClient++.cpp(589) NSCLient++ - 0.3.5.2 2008-09-24 Stopped succcessfully 

But I dont' see how to turn this output into something useful for Nagios, i.e. 
OK, WARNING, CRITICAL. It appears that the possible return values for 
Status are one of the following: OK,Error,Degraded,Unknown,Pred Fail, 
Starting, Stopping, Service, Stressed, NonRecover, No Contact or Lost Comm. I 
would be happy with OK resulting in a Nagios OK and anything else being a 
WARNING. Ideally, WARNING followed by the Status output from WMI. Is 
there a way to do this using the  NSClient filter and Max/Min syntax?   

Bonus question: What do you do if you have multiple drives? I don't see any 
obvious way to specify a drive to check.

Thanks 

-e 

  - Original Message - 
  From: Anthony Montibello 
  To: Eric Pearce 
  Cc: nagios-users@lists.sourceforge.net 
  Sent: Wednesday, January 14, 2009 8:58 PM
  Subject: Re: [Nagios-users] Windows disk health monitoring with 
smartmontoolsl/NSClient++?


  USe WMI: 
  the path to the smart data:
  root/Cimv2/Win32_DiskDrive/
  [Instance] -- Status


  Hope this helps
  Tony (Author of NC_Net)

  On Tue, Jan 13, 2009 at 10:49 PM, Eric Pearce epea...@amberpoint.com wrote:

I'd like to get SMART disk health status for Windows machines.  It looks 
like smartctl would work fine on Windows - has someone got it working with 
NSClient++?
I've found some people asking about this in the list archives, but haven't 
found any concrete examples.
All I'm looking for is a basic OK or something bad is going to happen 
soon alert from Nagios.
Thanks
-e




--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword___
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_dhcp seems not working

2009-01-15 Thread jmoseley




Holger Weiss hol...@cis.fu-berlin.de  wrote:

* jmose...@corp.xanadoo.com [2009-01-15 14:59]:
 Holger Weiss hol...@cis.fu-berlin.de  wrote:
 * jmose...@corp.xanadoo.com [2009-01-15 13:06]:
  2. Have a DHCP relay statement on the router's interface your Nagios
server
  connects to so it knows to which server to relay the DHCP request to

 For such a setup, step (2) isn't necessary, as check_dhcp will mimic a
 DHCP relay if the --unicast option is specified.

 What I meant was you'd have to have an ip helper-address configured.

But that's precisely what you don't need if you use check_dhcp's
--unicast option :-)  If you configure an ip helper-address (as
Cisco calls it), the router will relay local DHCP broadcast packets to
the specified remote DHCP server.  check_dhcp --unicast creates the
same sort of unicast packets such a relay would generate.

OK, I've got you now.

Back to the orginal topic.  Christian, another thing to check on the Nagios
server is if you have SELinux enabled.  That could definitely cause
problems with plugins that are SUID root.  If SELinux is enabled, disable
it and try the check_dhcp plugin again.

James



--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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] Problem with check_smtp plugin

2009-01-15 Thread Kaplan, Andrew H.
Hi there --

I recently installed Kyle O'Donnell's HP-UX plugins onto a system running HP-UX
11i v1. All plugins that are in use
appear to be running fine with one exception: check_smtp reports and invalid
hostname/address. 

I checked the arguments associated with the plugin and I manually ran the
following combinations:

./check_smtp -H hostname
./check_smtp -H FQDN
./check_smtp -H IP Address
./check_smtp --hostname=hostname
./check_smtp --hostname=FQDN
./check_smtp --hostname=IP Address

None of the above combinations worked. Does anyone have a solution to this
problem? Thanks. 




The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword___
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] Problem with check_smtp plugin

2009-01-15 Thread jmoseley



Kaplan, Andrew H. ahkap...@partners.org  wrote:

Hi there --


I recently installed Kyle O'Donnell's HP-UX plugins onto a system running
HP-UX 11i v1. All plugins that are in use
appear to be running fine with one exception: check_smtp reports and
invalid hostname/address.


I checked the arguments associated with the plugin and I manually ran the
following combinations:


./check_smtp -H hostname
./check_smtp -H FQDN
./check_smtp -H IP Address
./check_smtp --hostname=hostname
./check_smtp --hostname=FQDN
./check_smtp --hostname=IP Address


None of the above combinations worked. Does anyone have a solution to this
problem? Thanks.


I personally don't know anything about the plugin package you mention, but
have you tried using/installing the official Nagios plugins available at:
http://www.nagios.org/download/download.php


check_smtp works just fine:  check_smtp -H host_name

I assume you've tried running the plugin by itself vs. running it through
Nagios?  If the plugin by itself is throwing errors, you might want to
contact Kyle.

James


--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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] Question about using the NSCA addon

2009-01-15 Thread Anthony Montibello
Hi Matt,

Sorry to let you know your a bit off,

If you review the Source code of NSCA or NRPE
it is NOT expecting a string,
it is expecting a particular formated byte array.
where the begining of the Array is tested for Version# and Timestamps
validation before event thinking about data.

It is quickest to use an existing NSCA clients with NSCA,
I wrote a NSCA Client in C# and it took a lot longer than a day to get it
working.

TOny
(Author of NC_Net)

On Thu, Jan 15, 2009 at 2:13 PM, Matthew Tice mjt...@gmail.com wrote:

 I'm interested in using the nsca addon - but only the daemon.  I thought I
 could just open an tcp connection to the daemon and send my update manually:

 echo 3\t1\tmt-ubuntu\tSMTP Availability\tFAIL\n | netcat nocnag02 5667

 I set the value decryption_method=0 in the server config file (because I'm
 not doing any encryption on the client end).

 Is this possible?  I looked through the source and tried to create the
 necessary string - but I'm thinking I'm missing something.  Any ideas?  Feel
 free to tell me I'm way off here.

 Matt


 --
 This SF.net email is sponsored by:
 SourcForge Community
 SourceForge wants to tell your story.
 http://p.sf.net/sfu/sf-spreadtheword
 ___
 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:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword___
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_dhcp seems not working

2009-01-15 Thread Kevin Keane
Thank you!

In my case, the server-side firewall works without a problem. The server 
does hand out DHCP addresses all the time.

It was the client-side firewall (i.e., the one on the Nagios server) 
that blocked the DHCP request, even though I opened both ports 67 and 68 
for both TCP and UDP. It happened both with broadcast DHCP requests and 
with directed ones (using the -s serverip arg).

Oddly enough, I didn't see anything at all in the firewall log that 
would indicate what was blocked.

James Miller wrote:
 Sorry for the top post

1. Lease Request - The client sends a broadcast requesting an IP
   address
2. Lease Offer - The server sends the above information and marks
   the offered address as unavailable. The message sent is a
   DHCPOFFER broadcast message.
3. Lease Acceptance - The first offer received by the client is
   accepted. The acceptance is sent from the client as a broadcast
   (DHCPREQUEST message) including the IP address of the DNS server
   that sent the accepted offer. Other DHCP servers retract their
   offers and mark the offered address as available and the
   accepted address as unavailable.
4. Server lease acknowledgement - The server sends a DHCPACK or a
   DHCPNACK if an unavailable address was requested.

 All DHCP packets travel as UDP datagrams; all client-sent packets have 
 source port 68 and destination port 67; all server-sent packets have 
 source port 67 and destination port 68. For example, a server-side 
 firewall should allow the following types of packets:

 * Incoming packets from 0.0.0.0 or dhcp-pool to dhcp-ip
 * Incoming packets from any address to 255.255.255.255
 * Outgoing packets from dhcp-ip to dhcp-pool or 255.255.255.255

 where dhcp-ip represents any address configured on a DHCP server host 
 and dhcp-pool stands for the pool from which a DHCP server assigns 
 addresses to clients


 Jim

  


 Kevin Keane wrote:
 Christian, actually, your question prompted me to try it again. Turned 
 out that it was the firewall software on my Nagios box that blocked the 
 DHCP request. As soon as I turned it off, check_dhcp worked. I'm not yet 
 sure which ports to open to make it work with the firewall on. So far, I 
 tried ports 67 and 68 for both TCP and UDP, but that seems not to be enough.

 Christian Iñiguez wrote:
   
 Exactly Kevin, you are right



 - Mensaje original 
 De: Kevin Keane subscript...@kkeane.com
 CC: nagios-users@lists.sourceforge.net
 Enviado: jueves, 15 de enero, 2009 13:39:47
 Asunto: Re: [Nagios-users] check_dhcp seems not working

 jmose...@corp.xanadoo.com wrote:
   
 
 Christian Iñiguez challenger_jos...@yahoo.com.mx  wrote:

   
 
   
 Hi Everyone

 I have a linux server as dhcp server and it's working very well, and I'd
 
   
 
 like to monitoring it with nrpe plugin and check_dhcp.
   
 
   
 The problem here is the outcome of check_dhcp is always: CRITICAL: No
 
   
 
 DHCPOFFERs were received. But the server is working alright.
   
 
   
 The command line is: check_dhcp -s serverip -t 30

 What am I doing wrong? Any suggest?

 Thanks in advance!
 
   
 
 I have no idea which flavor of DHCP you are running (probably ISC's), but I
 don't think you are going to be able to run check_dhcp from the DHCP server
 itself.  The DHCP server will see an incoming requeset from itself and
 probably block it.  Therefore, using the nrpe method of doing these checks
 is a moot point.

 If your Nagios server is on the same network as the DHCP server, just run
 check_dhcp from the Nagios box.  If you're running Nagios on a different
 network than the DHCP server and there is a firewall in between, you'll
 probably have to do several things:

 1. Open up a hole in the firewall to allow the Nagios server to request a
 DHCP address from the DHCP server
 2. Have a DHCP relay statement on the router's interface your Nagios server
 connects to so it knows to which server to relay the DHCP request to
 3. Setup a small DHCP subnet on the DHCP server in the same IP range as the
 Nagios server so it can offer a valid IP address
 
   
 I actually have the same problem as Christian, and it does NOT work even 
 though Nagios is running on a different box on the same network as the 
 DHCP server. In fact, the Nagios box actually gets its IP address from 
 the same DHCP server that I would like to monitor (ISC DHCP server 3.0.6 
 on a SuSE 10.3). I've seen the same problem before against a Windows 
 DHCP server, too, never been able to make check_dhcp work.

 check_dhcp -v prints this:

 DHCP socket: 3
 Hardware address: 00:0c:29:0e:28:4f
 DHCPDISCOVER to 255.255.255.255 port 67
 DHCPDISCOVER XID: 2138668641 (0x7F797E61)
 DHCDISCOVER ciaddr:  0.0.0.0
 DHCDISCOVER yiaddr:  0.0.0.0
 DHCDISCOVER siaddr:  0.0.0.0
 DHCDISCOVER giaddr:  0.0.0.0
 send_dhcp_packet result: 548




 No (more) data received (nfound: 

[Nagios-users] nagios 3.0.6-1 install on OpenSUSE 10.3

2009-01-15 Thread Chris
I downloaded nagios 3.0.6-1 tarball and made an RPM (rpmbuild -ba
/path/to/nagios.spec). I now have the RPMs under
/usr/src/packages/RPMS/i586/. If I run rpm -ivh
nagios-3.0.6-1.i586.rpm I get error:

error: Failed dependencies:
/usr/bin/logger is needed by nagios-3.0.6-1.i586
chkconfig is needed by nagios-3.0.6-1.i586
initscripts is needed by nagios-3.0.6-1.i586

I symlinked /bin/logger to /usr/bin/logger to no avail. chkconfig
installed in /sbin/chkconfig. Couldn't find any RPM for initscripts.

Thanks for any help with resolving this issue.

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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