[Nagios-users] oracle 9i tablespace monitoring

[Nicholas Magers]

We are using oracle 9i. Can anyone recommend a process to monitor the
tablespace so that it includes the auto extensible space? I'm in charge
of monitoring not the Oracle databases so I could get more details if
required.


***
This message is intended for the addressee named and may contain confidential 
information. If you are not the intended recipient, please delete it and notify 
the sender. 

Views expressed in this message are those of the individual sender, and are not 
necessarily the views of the Department of  Lands.

This email message has been swept by MIMEsweeper for the presence of computer 
viruses.
***
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null

[Nagios-users] Notification Macros to Determine How Long Last State Duration

[Larry Low]

Here is what I'm trying to figure out how to do.  I'm pretty sure with the 
current Nagios variables available this is not possible (3.0).

I have a perl script that is executed for notifications.  On notifications that 
are triggered from state changes I would like to print out how long the service 
was in a previous state before this new state occurred.

Example:

A) State is OK for 10 minutes (10 checks of ok separated by 1 minute)
B) State changes to CRITICAL
C) Notification triggered

LASTSERVICESTATECHANGE will be current time
LASTSERVICEOK will be 1 minute ago
LASTSERVICESTATE will be OK
LASTSERVICESTATECRITICAL will be current time

I'm thinking the problem is that LASTSERVICESTATECHANGE should be 10 minutes 
since LASTSERVICESTATE is OK.  Bug or misinterpretation of macro?

Thoughts?  Suggestions?


Larry Low
4150 N Drinkwater Blvd., 5th Floor
Scottsdale, AZ  85251
Office: 480.385.7045
E-mail: [EMAIL PROTECTED]'

Telesphere Networks, Inc



-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null

Re: [Nagios-users] Dual-port monitoring

[Cook, Garry]

Well, maybe you can use check_cluster as the host check? It sounds logical to 
me, but I've never used that check so I'm not really sure.
Also, check_icmp has the ability to PING multiple addresses. Perhaps using this 
as your host check against both IPs would give you the results you're looking 
for...

Thanks,
Garry

From: Israel Brewster [mailto:[EMAIL PROTECTED]
Sent: Monday, March 17, 2008 2:37 PM
To: Cook, Garry
Cc: Nagios Users Mailinglist
Subject: Re: [Nagios-users] Dual-port monitoring

On Mar 17, 2008, at 12:06 PM, Cook, Garry wrote:


Yes, check_ifstatus is a service associated with the hosts. It checks 
interfaces only. The host check is a check_icmp against the host address, which 
is the loopback. If any of the interfaces are down, check_ifstatus will report 
this, but the host does not show as down as long as the loopback responds to a 
PING, which it will if any of the interfaces are up.

Ok, I see what you are saying, and it does sound as though it would work as I 
desire. Unfortunately, for the device in question, it doesn't look as though 
this will be an option, as I don't think I can use loopback addresses 
(primarily Linksys RV082 devices). Thanks anyway.

---
Israel Brewster
Computer Support Technician
Frontier Flying Service Inc.
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7250 x293
---

Thanks,
Garry

From: Israel Brewster [mailto:[EMAIL PROTECTED]
Sent: Monday, March 17, 2008 1:46 PM
To: Cook, Garry
Cc: Nagios Users Mailinglist
Subject: Re: [Nagios-users] Dual-port monitoring

On Mar 17, 2008, at 11:03 AM, Cook, Garry wrote:



Do you have the ability to use loopback addresses on these devices? If so, that 
would be used as the host address, and then you could use other checks for the 
interfaces. For instance, all of my Cisco routers have a loopback setup. I then 
use 'check_ifstatus' to check the individual interfaces.

Thanks,
Garry


I assume the check_ifstatus for the interfaces are services associated with the 
host? If so, then what do you use for your host check? How do you get the host 
to show as down if all the interfaces are down, but not if one or both (or 
more, if you have more than two, although that is not the case with any of our 
devices) are up?

---
Israel Brewster
Computer Support Technician
Frontier Flying Service Inc.
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7250 x293
---

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On 
Behalf Of Israel Brewster
Sent: Monday, March 17, 2008 12:41 PM
To: Nagios Users Mailinglist
Subject: Re: [Nagios-users] Dual-port monitoring

On Mar 17, 2008, at 9:03 AM, Gary Every wrote:




In your services file:

define service {
  use   generic-service
  name  Ping
  host_namemulti_homed_server_name
  service_description   Ping Second IFace
  check_command check_ping2!10.1.1.100!3000,10%!1,20%
  contact_groupsUnix
}

for your checkcommands:

define command{
command_namecheck_ping2
command_line/usr/lib/nagios/plugins/check_ping -H $ARG1$ -w $ARG2$ 
-c $ARG3$ -p 5
}


check_ping2 adds the first ARG as the ip address that you want monitored - This 
means that the HOSTNAME will remain the same, but a diff interface will be 
checked.




Thanks for the response. If I understand your reply correctly, though, this 
just adds a second service for the host, with a separate IP from that specified 
in the host directive. it does not, however, allow me to monitor the HOST on 
two separate IP's, taking into account that if either interface is up, the host 
is up. Perhaps my question wasn't quite clear enough. Take, for example, the 
following situation:

host a has two network interfaces: a primary with an IP of 10.1.1.100 and a 
secondary with an IP of 10.1.1.101.
Host a can be reached through either interface.
Host a has its host address defined as the primary of 10.1.1.100, with a check 
command of check_ping
Host a also has a service defined as above, checking the secondary interface 
(10.1.1.101)

If the secondary interface goes down, then everything is fine: nagios notices 
that the service for the secondary interface is critical, checks the host on 
the primary, sees that as being fine, and sends an alert about the service 
(secondary port), while leaving the host in an OK state. This is exactly as it 
should be.

However, now imagine that the primary interface goes down instead. Nagios 
attempts to check the host on the primary interface, which also fails (sicne 
the interface is down), and therefore nagios alerts that the host is down, and 
any devices behind it are unreachable. This, however, is incorrect-since the 
secondary interface is still connected and fully functional, the host and 
everything behind it is st

Re: [Nagios-users] Dual-port monitoring

[Israel Brewster]

On Mar 17, 2008, at 12:06 PM, Cook, Garry wrote:

Yes, check_ifstatus is a service associated with the hosts. It  
checks interfaces only. The host check is a check_icmp against the  
host address, which is the loopback. If any of the interfaces are  
down, check_ifstatus will report this, but the host does not show as  
down as long as the loopback responds to a PING, which it will if  
any of the interfaces are up.


Ok, I see what you are saying, and it does sound as though it would  
work as I desire. Unfortunately, for the device in question, it  
doesn't look as though this will be an option, as I don't think I can  
use loopback addresses (primarily Linksys RV082 devices). Thanks anyway.


---
Israel Brewster
Computer Support Technician
Frontier Flying Service Inc.
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7250 x293
---


Thanks,
Garry

From: Israel Brewster [mailto:[EMAIL PROTECTED]
Sent: Monday, March 17, 2008 1:46 PM
To: Cook, Garry
Cc: Nagios Users Mailinglist
Subject: Re: [Nagios-users] Dual-port monitoring

On Mar 17, 2008, at 11:03 AM, Cook, Garry wrote:


Do you have the ability to use loopback addresses on these devices?  
If so, that would be used as the host address, and then you could  
use other checks for the interfaces. For instance, all of my Cisco  
routers have a loopback setup. I then use ‘check_ifstatus’ to check  
the individual interfaces.


Thanks,
Garry


I assume the check_ifstatus for the interfaces are services  
associated with the host? If so, then what do you use for your host  
check? How do you get the host to show as down if all the interfaces  
are down, but not if one or both (or more, if you have more than  
two, although that is not the case with any of our devices) are up?


---
Israel Brewster
Computer Support Technician
Frontier Flying Service Inc.
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7250 x293
---

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
] On Behalf Of Israel Brewster

Sent: Monday, March 17, 2008 12:41 PM
To: Nagios Users Mailinglist
Subject: Re: [Nagios-users] Dual-port monitoring

On Mar 17, 2008, at 9:03 AM, Gary Every wrote:



In your services file:

define service {
  use   generic-service
  name  Ping
  host_namemulti_homed_server_name
  service_description   Ping Second IFace
  check_command check_ping2!10.1.1.100!3000,10%!1,20%
  contact_groupsUnix
}

for your checkcommands:

define command{
command_namecheck_ping2
command_line/usr/lib/nagios/plugins/check_ping -H $ARG1$  
-w $ARG2$ -c $ARG3$ -p 5

}


check_ping2 adds the first ARG as the ip address that you want  
monitored - This means that the HOSTNAME will remain the same, but a  
diff interface will be checked.




Thanks for the response. If I understand your reply correctly,  
though, this just adds a second service for the host, with a  
separate IP from that specified in the host directive. it does not,  
however, allow me to monitor the HOST on two separate IP's, taking  
into account that if either interface is up, the host is up. Perhaps  
my question wasn't quite clear enough. Take, for example, the  
following situation:


host a has two network interfaces: a primary with an IP of  
10.1.1.100 and a secondary with an IP of 10.1.1.101.

Host a can be reached through either interface.
Host a has its host address defined as the primary of 10.1.1.100,  
with a check command of check_ping
Host a also has a service defined as above, checking the secondary  
interface (10.1.1.101)


If the secondary interface goes down, then everything is fine:  
nagios notices that the service for the secondary interface is  
critical, checks the host on the primary, sees that as being fine,  
and sends an alert about the service (secondary port), while leaving  
the host in an OK state. This is exactly as it should be.


However, now imagine that the primary interface goes down instead.  
Nagios attempts to check the host on the primary interface, which  
also fails (sicne the interface is down), and therefore nagios  
alerts that the host is down, and any devices behind it are  
unreachable. This, however, is incorrect-since the secondary  
interface is still connected and fully functional, the host and  
everything behind it is still up and reachable. What I want is a  
situation where Nagios will send me an alert if either interface of  
a host is down, but only consider the host to be down if BOTH  
interfaces on the host are down. As I explained in my original  
posting, I have considered a couple of options that may accomplish  
this, but neither seems as elegant as I would like. Thanks for any  
thoughts!


---
Israel Brewster
Computer Support Tec

Re: [Nagios-users] Dual-port monitoring

[Israel Brewster]

On Mar 17, 2008, at 12:00 PM, Marcel wrote:

If you would have a round-robin dns setup to reach that particular  
host, you would be fine tweaking a check_host_alive command with  
high lost percentage, but still reachable. But you will rely on dns  
name resolution to do that.


Right, unfortunately we aren't set up quite that fancy. We simply have  
two seperate DNS entries for the two ports, and when we can't reach  
the device on  one, we go on the other. The dual connections are more  
for outgoing traffic than incoming, such that devices behind the  
device will still have a route to the outside world should one route  
die (load balancing and failover), but nagios is on the outside  
looking in.


---
Israel Brewster
Computer Support Technician
Frontier Flying Service Inc.
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7250 x293
---



HTH,
Marcel

On Mon, Mar 17, 2008 at 4:45 PM, Israel Brewster <[EMAIL PROTECTED] 
> wrote:

On Mar 17, 2008, at 11:03 AM, Cook, Garry wrote:

Do you have the ability to use loopback addresses on these devices?  
If so, that would be used as the host address, and then you could  
use other checks for the interfaces. For instance, all of my Cisco  
routers have a loopback setup. I then use 'check_ifstatus' to check  
the individual interfaces.


Thanks,
Garry



I assume the check_ifstatus for the interfaces are services  
associated with the host? If so, then what do you use for your host  
check? How do you get the host to show as down if all the interfaces  
are down, but not if one or both (or more, if you have more than  
two, although that is not the case with any of our devices) are up?


---
Israel Brewster
Computer Support Technician
Frontier Flying Service Inc.
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7250 x293
---

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
] On Behalf Of Israel Brewster

Sent: Monday, March 17, 2008 12:41 PM
To: Nagios Users Mailinglist
Subject: Re: [Nagios-users] Dual-port monitoring

On Mar 17, 2008, at 9:03 AM, Gary Every wrote:


In your services file:

define service {
  use   generic-service
  name  Ping
  host_namemulti_homed_server_name
  service_description   Ping Second IFace
  check_command check_ping2!10.1.1.100!3000,10%!1,20%
  contact_groupsUnix
}

for your checkcommands:

define command{
command_namecheck_ping2
command_line/usr/lib/nagios/plugins/check_ping -H  
$ARG1$ -w $ARG2$ -c $ARG3$ -p 5

}


check_ping2 adds the first ARG as the ip address that you want  
monitored - This means that the HOSTNAME will remain the same, but  
a diff interface will be checked.



Thanks for the response. If I understand your reply correctly,  
though, this just adds a second service for the host, with a  
separate IP from that specified in the host directive. it does not,  
however, allow me to monitor the HOST on two separate IP's, taking  
into account that if either interface is up, the host is up.  
Perhaps my question wasn't quite clear enough. Take, for example,  
the following situation:


host a has two network interfaces: a primary with an IP of  
10.1.1.100 and a secondary with an IP of 10.1.1.101.

Host a can be reached through either interface.
Host a has its host address defined as the primary of 10.1.1.100,  
with a check command of check_ping
Host a also has a service defined as above, checking the secondary  
interface (10.1.1.101)


If the secondary interface goes down, then everything is fine:  
nagios notices that the service for the secondary interface is  
critical, checks the host on the primary, sees that as being fine,  
and sends an alert about the service (secondary port), while  
leaving the host in an OK state. This is exactly as it should be.


However, now imagine that the primary interface goes down instead.  
Nagios attempts to check the host on the primary interface, which  
also fails (sicne the interface is down), and therefore nagios  
alerts that the host is down, and any devices behind it are  
unreachable. This, however, is incorrect-since the secondary  
interface is still connected and fully functional, the host and  
everything behind it is still up and reachable. What I want is a  
situation where Nagios will send me an alert if either interface of  
a host is down, but only consider the host to be down if BOTH  
interfaces on the host are down. As I explained in my original  
posting, I have considered a couple of options that may accomplish  
this, but neither seems as elegant as I would like. Thanks for any  
thoughts!


---
Israel Brewster
Computer Support Technician
Frontier Flying Service Inc.
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-72

Re: [Nagios-users] Dual-port monitoring

[Cook, Garry]

Yes, check_ifstatus is a service associated with the hosts. It checks 
interfaces only. The host check is a check_icmp against the host address, which 
is the loopback. If any of the interfaces are down, check_ifstatus will report 
this, but the host does not show as down as long as the loopback responds to a 
PING, which it will if any of the interfaces are up.

Thanks,
Garry

From: Israel Brewster [mailto:[EMAIL PROTECTED]
Sent: Monday, March 17, 2008 1:46 PM
To: Cook, Garry
Cc: Nagios Users Mailinglist
Subject: Re: [Nagios-users] Dual-port monitoring

On Mar 17, 2008, at 11:03 AM, Cook, Garry wrote:


Do you have the ability to use loopback addresses on these devices? If so, that 
would be used as the host address, and then you could use other checks for the 
interfaces. For instance, all of my Cisco routers have a loopback setup. I then 
use 'check_ifstatus' to check the individual interfaces.

Thanks,
Garry


I assume the check_ifstatus for the interfaces are services associated with the 
host? If so, then what do you use for your host check? How do you get the host 
to show as down if all the interfaces are down, but not if one or both (or 
more, if you have more than two, although that is not the case with any of our 
devices) are up?

---
Israel Brewster
Computer Support Technician
Frontier Flying Service Inc.
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7250 x293
---

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On 
Behalf Of Israel Brewster
Sent: Monday, March 17, 2008 12:41 PM
To: Nagios Users Mailinglist
Subject: Re: [Nagios-users] Dual-port monitoring

On Mar 17, 2008, at 9:03 AM, Gary Every wrote:



In your services file:

define service {
  use   generic-service
  name  Ping
  host_namemulti_homed_server_name
  service_description   Ping Second IFace
  check_command check_ping2!10.1.1.100!3000,10%!1,20%
  contact_groupsUnix
}

for your checkcommands:

define command{
command_namecheck_ping2
command_line/usr/lib/nagios/plugins/check_ping -H $ARG1$ -w $ARG2$ 
-c $ARG3$ -p 5
}


check_ping2 adds the first ARG as the ip address that you want monitored - This 
means that the HOSTNAME will remain the same, but a diff interface will be 
checked.



Thanks for the response. If I understand your reply correctly, though, this 
just adds a second service for the host, with a separate IP from that specified 
in the host directive. it does not, however, allow me to monitor the HOST on 
two separate IP's, taking into account that if either interface is up, the host 
is up. Perhaps my question wasn't quite clear enough. Take, for example, the 
following situation:

host a has two network interfaces: a primary with an IP of 10.1.1.100 and a 
secondary with an IP of 10.1.1.101.
Host a can be reached through either interface.
Host a has its host address defined as the primary of 10.1.1.100, with a check 
command of check_ping
Host a also has a service defined as above, checking the secondary interface 
(10.1.1.101)

If the secondary interface goes down, then everything is fine: nagios notices 
that the service for the secondary interface is critical, checks the host on 
the primary, sees that as being fine, and sends an alert about the service 
(secondary port), while leaving the host in an OK state. This is exactly as it 
should be.

However, now imagine that the primary interface goes down instead. Nagios 
attempts to check the host on the primary interface, which also fails (sicne 
the interface is down), and therefore nagios alerts that the host is down, and 
any devices behind it are unreachable. This, however, is incorrect-since the 
secondary interface is still connected and fully functional, the host and 
everything behind it is still up and reachable. What I want is a situation 
where Nagios will send me an alert if either interface of a host is down, but 
only consider the host to be down if BOTH interfaces on the host are down. As I 
explained in my original posting, I have considered a couple of options that 
may accomplish this, but neither seems as elegant as I would like. Thanks for 
any thoughts!

---
Israel Brewster
Computer Support Technician
Frontier Flying Service Inc.
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7250 x293
---

On Mon, Mar 17, 2008 at 9:38 AM, Israel Brewster <[EMAIL 
PROTECTED]> wrote:
I have a number of devices on my network that have dual-interfaces
such that either one can go down, but the device itself, and all the
devices behind it (in the case of a router) is still up and reachable.
What is the best way to set up monitoring of such devices, considering
that as far as I can tell you can only assign one IP per host? I have
l

Re: [Nagios-users] Dual-port monitoring

[Marcel]

If you would have a round-robin dns setup to reach that particular host, you
would be fine tweaking a check_host_alive command with high lost percentage,
but still reachable. But you will rely on dns name resolution to do that.

HTH,
Marcel

On Mon, Mar 17, 2008 at 4:45 PM, Israel Brewster <[EMAIL PROTECTED]>
wrote:

> On Mar 17, 2008, at 11:03 AM, Cook, Garry wrote:
>
> Do you have the ability to use loopback addresses on these devices? If so,
> that would be used as the host address, and then you could use other checks
> for the interfaces. For instance, all of my Cisco routers have a loopback
> setup. I then use 'check_ifstatus' to check the individual interfaces.
>
> Thanks,
> Garry
>
>
>
> I assume the check_ifstatus for the interfaces are services associated
> with the host? If so, then what do you use for your host check? How do you
> get the host to show as down if all the interfaces are down, but not if one
> or both (or more, if you have more than two, although that is not the case
> with any of our devices) are up?
>
> ---
> Israel Brewster
> Computer Support Technician
> Frontier Flying Service Inc.
> 5245 Airport Industrial Rd
> Fairbanks, AK 99709
> (907) 450-7250 x293
> ---
>
> *From:* [EMAIL PROTECTED] [
> mailto:[EMAIL PROTECTED]<[EMAIL PROTECTED]>
> ] *On Behalf Of *Israel Brewster
> *Sent:* Monday, March 17, 2008 12:41 PM
> *To:* Nagios Users Mailinglist
> *Subject:* Re: [Nagios-users] Dual-port monitoring
>
> On Mar 17, 2008, at 9:03 AM, Gary Every wrote:
>
>
> In your services file:
>
> define service {
>   use   generic-service
>   name  Ping
>   host_namemulti_homed_server_name
>   service_description   Ping Second IFace
>   check_command check_ping2!10.1.1.100!3000,10%!1,20%
>   contact_groupsUnix
> }
>
> for your checkcommands:
>
> define command{
> command_namecheck_ping2
> command_line/usr/lib/nagios/plugins/check_ping -H $ARG1$ -w
> $ARG2$ -c $ARG3$ -p 5
> }
>
>
> check_ping2 adds the first ARG as the ip address that you want monitored -
> This means that the HOSTNAME will remain the same, but a diff interface will
> be checked.
>
>
> Thanks for the response. If I understand your reply correctly, though,
> this just adds a second service for the host, with a separate IP from that
> specified in the host directive. it does not, however, allow me to monitor
> the HOST on two separate IP's, taking into account that if either interface
> is up, the host is up. Perhaps my question wasn't quite clear enough. Take,
> for example, the following situation:
>
> host a has two network interfaces: a primary with an IP of 10.1.1.100 and
> a secondary with an IP of 10.1.1.101.
> Host a can be reached through either interface.
> Host a has its host address defined as the primary of 10.1.1.100, with a
> check command of check_ping
> Host a also has a service defined as above, checking the secondary
> interface (10.1.1.101)
>
> If the secondary interface goes down, then everything is fine: nagios
> notices that the service for the secondary interface is critical, checks the
> host on the primary, sees that as being fine, and sends an alert about the
> service (secondary port), while leaving the host in an OK state. This is
> exactly as it should be.
>
> However, now imagine that the primary interface goes down instead. Nagios
> attempts to check the host on the primary interface, which also fails (sicne
> the interface is down), and therefore nagios alerts that the host is down,
> and any devices behind it are unreachable. This, however, is incorrect-since
> the secondary interface is still connected and fully functional, the host
> and everything behind it is still up and reachable. What I want is a
> situation where Nagios will send me an alert if either interface of a host
> is down, but only consider the host to be down if BOTH interfaces on the
> host are down. As I explained in my original posting, I have considered a
> couple of options that may accomplish this, but neither seems as elegant as
> I would like. Thanks for any thoughts!
>
> ---
> Israel Brewster
> Computer Support Technician
> Frontier Flying Service Inc.
> 5245 Airport Industrial Rd
> Fairbanks, AK 99709
> (907) 450-7250 x293
> ---
>
>
> On Mon, Mar 17, 2008 at 9:38 AM, Israel Brewster <
> [EMAIL PROTECTED]> wrote:
> I have a number of devices on my network that have dual-interfaces
> such that either one can go down, but the device itself, and all the
> devices behind it (in the case of a router) is still up and reachable.
> What is the best way to set up monitoring of such devices, considering
> that as far as I can tell you can only assign one IP per host? I have
> looked at check_cluster, but if that is the best method I am unsure of
> the best way of imple

Re: [Nagios-users] Dual-port monitoring

[Israel Brewster]

On Mar 17, 2008, at 11:03 AM, Cook, Garry wrote:

Do you have the ability to use loopback addresses on these devices?  
If so, that would be used as the host address, and then you could  
use other checks for the interfaces. For instance, all of my Cisco  
routers have a loopback setup. I then use ‘check_ifstatus’ to check  
the individual interfaces.


Thanks,
Garry



I assume the check_ifstatus for the interfaces are services associated  
with the host? If so, then what do you use for your host check? How do  
you get the host to show as down if all the interfaces are down, but  
not if one or both (or more, if you have more than two, although that  
is not the case with any of our devices) are up?


---
Israel Brewster
Computer Support Technician
Frontier Flying Service Inc.
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7250 x293
---

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
] On Behalf Of Israel Brewster

Sent: Monday, March 17, 2008 12:41 PM
To: Nagios Users Mailinglist
Subject: Re: [Nagios-users] Dual-port monitoring

On Mar 17, 2008, at 9:03 AM, Gary Every wrote:


In your services file:

define service {
  use   generic-service
  name  Ping
  host_namemulti_homed_server_name
  service_description   Ping Second IFace
  check_command check_ping2!10.1.1.100!3000,10%!1,20%
  contact_groupsUnix
}

for your checkcommands:

define command{
command_namecheck_ping2
command_line/usr/lib/nagios/plugins/check_ping -H $ARG1$  
-w $ARG2$ -c $ARG3$ -p 5

}


check_ping2 adds the first ARG as the ip address that you want  
monitored - This means that the HOSTNAME will remain the same, but a  
diff interface will be checked.



Thanks for the response. If I understand your reply correctly,  
though, this just adds a second service for the host, with a  
separate IP from that specified in the host directive. it does not,  
however, allow me to monitor the HOST on two separate IP's, taking  
into account that if either interface is up, the host is up. Perhaps  
my question wasn't quite clear enough. Take, for example, the  
following situation:


host a has two network interfaces: a primary with an IP of  
10.1.1.100 and a secondary with an IP of 10.1.1.101.

Host a can be reached through either interface.
Host a has its host address defined as the primary of 10.1.1.100,  
with a check command of check_ping
Host a also has a service defined as above, checking the secondary  
interface (10.1.1.101)


If the secondary interface goes down, then everything is fine:  
nagios notices that the service for the secondary interface is  
critical, checks the host on the primary, sees that as being fine,  
and sends an alert about the service (secondary port), while leaving  
the host in an OK state. This is exactly as it should be.


However, now imagine that the primary interface goes down instead.  
Nagios attempts to check the host on the primary interface, which  
also fails (sicne the interface is down), and therefore nagios  
alerts that the host is down, and any devices behind it are  
unreachable. This, however, is incorrect-since the secondary  
interface is still connected and fully functional, the host and  
everything behind it is still up and reachable. What I want is a  
situation where Nagios will send me an alert if either interface of  
a host is down, but only consider the host to be down if BOTH  
interfaces on the host are down. As I explained in my original  
posting, I have considered a couple of options that may accomplish  
this, but neither seems as elegant as I would like. Thanks for any  
thoughts!


---
Israel Brewster
Computer Support Technician
Frontier Flying Service Inc.
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7250 x293
---

On Mon, Mar 17, 2008 at 9:38 AM, Israel Brewster <[EMAIL PROTECTED] 
> wrote:

I have a number of devices on my network that have dual-interfaces
such that either one can go down, but the device itself, and all the
devices behind it (in the case of a router) is still up and reachable.
What is the best way to set up monitoring of such devices, considering
that as far as I can tell you can only assign one IP per host? I have
looked at check_cluster, but if that is the best method I am unsure of
the best way of implementing it. Things I have thought of:

1) Create two "dummy" hosts which are the two ports, and then a third
host with a check command of check_cluster that looks at those two
dummy hosts. This seems overly complicated, not to mention cluttering
up my configs and nagios interface with three hosts where there is
really only one.

2) Simply monitor the two ports as two separate hosts. This could
work, but again clutters things up with multiple hosts where only one
ex

Re: [Nagios-users] Nagios Config Script

[Nair]

Sure.

I need to monitor CPU/MEM/HDD/Application etc on a Data Center Environment 
having more than 200 Servers right now and it keeps on adding. 

I need to automate Nagios *.cfg file creation and updation. Say i will mention 
all system IPs and services, contact , contact group etc in a tab seperated 
text file and a script should take care of file creation and updation.

Could not find much details NACE and not good at scripting :(

Can you give some ideas, how to go ahead on this.

Thanks,

Nair.




On Thu, 13 Mar 2008 Russell Adams wrote :
>Care to elaborate on your requirements? I'd be happy to give you some
>ideas where NACE might help.
>
>Thanks.
>
>On Thu, Mar 13, 2008 at 12:26:15AM -, Nair wrote:
> > Hi friends,
> >
> > I got to monitor my data centre with Nagios.
> >
> > Please share your thoughts on automated *.cfg file creation.
> >
> > Thank you,
> >
> > Manu.
> >
>
> > -
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
> > ___
> > Nagios-users mailing list
> > Nagios-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/nagios-users
> > ::: Please include Nagios version, plugin version (-v) and OS when 
> > reporting any issue.
> > ::: Messages without supporting info will risk being sent to /dev/null
>
>
>--
>Russell Adams[EMAIL PROTECTED]
>
>PGP Key ID: 0x1160DCB3   http://www.adamsinfoserv.com/
>
>Fingerprint:1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3
>
>-
>This SF.net email is sponsored by: Microsoft
>Defy all challenges. Microsoft(R) Visual Studio 2008.
>http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
>___
>Nagios-users mailing list
>Nagios-users@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/nagios-users
>::: Please include Nagios version, plugin version (-v) and OS when reporting 
>any issue.
>::: Messages without supporting info will risk being sent to /dev/null


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null

[Nagios-users] Unwanted re-notifications

[Israel Brewster]

I have a service that keeps sending me notifications of the fact that  
it is critical every half hour or so, even though the notification  
interval for the service is set to zero. In this particular case, the  
port that is being monitored is temporarily disabled, so there is no  
chance that the service is coming up briefly and then going back down,  
thus triggering the notification. Looking at the nagios page for the  
service, I notice, however that it says "Current Notification Number:  
7", which would imply (to me at least) that re-notification is  
enabled. What am I missing here? how can I get it to stop sending me  
messages? I can, of course, acknowledge the down state, or put it in  
scheduled downtime, but I don't want it to send more than the initial  
notification regardless. Thanks!

The service definition is as follows:

define service{
 use generic service
 host_name   ffsbrw-rtr00
 service_description WAN 2
 notification_interval   0
 check_command   check_custom_ping!xx.xxx.xxx.xxx! 
1200.0,20%!1600.0,50%
 normal_check_interval   1
 max_check_attempts  5
 servicegroups   Satelite Services
 notification_optionsu,c,r
 }

and generic service (which this inherits from) as such (yes, much came  
from the sample files):

define service{
 namegeneric service ; The 'name'  
of this service template
 active_checks_enabled   1   ; Active service  
checks are enabled
 passive_checks_enabled  1   ; Passive service  
checks are enabled/accepted
 parallelize_check   1   ; Active service  
checks should be parallelized (disabling this can lead to major  
performance problems)
 obsess_over_service 1   ; We should obsess  
over this service (if necessary)
 check_freshness 0   ; Default is to NOT  
check service 'freshness'
 notifications_enabled   1   ; Service  
notifications are not enabled
 event_handler_enabled   1   ; Service event  
handler is enabled
 flap_detection_enabled  1   ; Flap detection is  
enabled
 failure_prediction_enabled  1   ; Failure prediction  
is enabled
 process_perf_data   1   ; Process performance  
data
 retain_status_information   1   ; Retain status  
information across program restarts
 retain_nonstatus_information1   ; Retain non-status  
information across program restarts
 is_volatile 0
 check_period24x7
 max_check_attempts  3
 normal_check_interval   5
 retry_check_interval1
 contact_groups  admins2
 notification_optionsn
 notification_interval   0
 notification_period 24x7
 servicegroups   z Ping Services
 register0   ; DONT REGISTER THIS  
DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE!
 }


---
Israel Brewster
Computer Support Technician
Frontier Flying Service Inc.
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7250 x293
---



-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null

Re: [Nagios-users] Dual-port monitoring

[Cook, Garry]

Do you have the ability to use loopback addresses on these devices? If so, that 
would be used as the host address, and then you could use other checks for the 
interfaces. For instance, all of my Cisco routers have a loopback setup. I then 
use 'check_ifstatus' to check the individual interfaces.

Thanks,
Garry

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Israel Brewster
Sent: Monday, March 17, 2008 12:41 PM
To: Nagios Users Mailinglist
Subject: Re: [Nagios-users] Dual-port monitoring

On Mar 17, 2008, at 9:03 AM, Gary Every wrote:


In your services file:

define service {
  use   generic-service
  name  Ping
  host_namemulti_homed_server_name
  service_description   Ping Second IFace
  check_command check_ping2!10.1.1.100!3000,10%!1,20%
  contact_groupsUnix
}

for your checkcommands:

define command{
command_namecheck_ping2
command_line/usr/lib/nagios/plugins/check_ping -H $ARG1$ -w $ARG2$ 
-c $ARG3$ -p 5
}


check_ping2 adds the first ARG as the ip address that you want monitored - This 
means that the HOSTNAME will remain the same, but a diff interface will be 
checked.


Thanks for the response. If I understand your reply correctly, though, this 
just adds a second service for the host, with a separate IP from that specified 
in the host directive. it does not, however, allow me to monitor the HOST on 
two separate IP's, taking into account that if either interface is up, the host 
is up. Perhaps my question wasn't quite clear enough. Take, for example, the 
following situation:

host a has two network interfaces: a primary with an IP of 10.1.1.100 and a 
secondary with an IP of 10.1.1.101.
Host a can be reached through either interface.
Host a has its host address defined as the primary of 10.1.1.100, with a check 
command of check_ping
Host a also has a service defined as above, checking the secondary interface 
(10.1.1.101)

If the secondary interface goes down, then everything is fine: nagios notices 
that the service for the secondary interface is critical, checks the host on 
the primary, sees that as being fine, and sends an alert about the service 
(secondary port), while leaving the host in an OK state. This is exactly as it 
should be.

However, now imagine that the primary interface goes down instead. Nagios 
attempts to check the host on the primary interface, which also fails (sicne 
the interface is down), and therefore nagios alerts that the host is down, and 
any devices behind it are unreachable. This, however, is incorrect-since the 
secondary interface is still connected and fully functional, the host and 
everything behind it is still up and reachable. What I want is a situation 
where Nagios will send me an alert if either interface of a host is down, but 
only consider the host to be down if BOTH interfaces on the host are down. As I 
explained in my original posting, I have considered a couple of options that 
may accomplish this, but neither seems as elegant as I would like. Thanks for 
any thoughts!

---
Israel Brewster
Computer Support Technician
Frontier Flying Service Inc.
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7250 x293
---

On Mon, Mar 17, 2008 at 9:38 AM, Israel Brewster <[EMAIL 
PROTECTED]> wrote:
I have a number of devices on my network that have dual-interfaces
such that either one can go down, but the device itself, and all the
devices behind it (in the case of a router) is still up and reachable.
What is the best way to set up monitoring of such devices, considering
that as far as I can tell you can only assign one IP per host? I have
looked at check_cluster, but if that is the best method I am unsure of
the best way of implementing it. Things I have thought of:

1) Create two "dummy" hosts which are the two ports, and then a third
host with a check command of check_cluster that looks at those two
dummy hosts. This seems overly complicated, not to mention cluttering
up my configs and nagios interface with three hosts where there is
really only one.

2) Simply monitor the two ports as two separate hosts. This could
work, but again clutters things up with multiple hosts where only one
exists, and adds the requirement of multi-parenting any child devices,
which can get ugly, especially in a graphical representation of the
network.

I have read http://nagios.sourceforge.net/docs/2_0/clusters.html, but
that doesn't seem to apply, at least not directly, in that it refers
either to situations where you have redundant services on one or more
hosts (perhaps that is sort of what I want?) or to where you have
multiple redundant hosts, but not to the situation where you have one
host offering one service over two ports. The main problem with that
doc, though, is that the cluster is always a service, which wouldn't
work in my situation, as

Re: [Nagios-users] Dual-port monitoring

[Israel Brewster]

On Mar 17, 2008, at 9:03 AM, Gary Every wrote:


In your services file:

define service {
  use   generic-service
  name  Ping
  host_namemulti_homed_server_name
  service_description   Ping Second IFace
  check_command check_ping2!10.1.1.100!3000,10%!1,20%
  contact_groupsUnix
}

for your checkcommands:

define command{
command_namecheck_ping2
command_line/usr/lib/nagios/plugins/check_ping -H $ARG1$  
-w $ARG2$ -c $ARG3$ -p 5

}


check_ping2 adds the first ARG as the ip address that you want  
monitored - This means that the HOSTNAME will remain the same, but a  
diff interface will be checked.


Thanks for the response. If I understand your reply correctly, though,  
this just adds a second service for the host, with a separate IP from  
that specified in the host directive. it does not, however, allow me  
to monitor the HOST on two separate IP's, taking into account that if  
either interface is up, the host is up. Perhaps my question wasn't  
quite clear enough. Take, for example, the following situation:


host a has two network interfaces: a primary with an IP of 10.1.1.100  
and a secondary with an IP of 10.1.1.101.

Host a can be reached through either interface.
Host a has its host address defined as the primary of 10.1.1.100, with  
a check command of check_ping
Host a also has a service defined as above, checking the secondary  
interface (10.1.1.101)


If the secondary interface goes down, then everything is fine: nagios  
notices that the service for the secondary interface is critical,  
checks the host on the primary, sees that as being fine, and sends an  
alert about the service (secondary port), while leaving the host in an  
OK state. This is exactly as it should be.


However, now imagine that the primary interface goes down instead.  
Nagios attempts to check the host on the primary interface, which also  
fails (sicne the interface is down), and therefore nagios alerts that  
the host is down, and any devices behind it are unreachable. This,  
however, is incorrect-since the secondary interface is still connected  
and fully functional, the host and everything behind it is still up  
and reachable. What I want is a situation where Nagios will send me an  
alert if either interface of a host is down, but only consider the  
host to be down if BOTH interfaces on the host are down. As I  
explained in my original posting, I have considered a couple of  
options that may accomplish this, but neither seems as elegant as I  
would like. Thanks for any thoughts!


---
Israel Brewster
Computer Support Technician
Frontier Flying Service Inc.
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7250 x293
---



On Mon, Mar 17, 2008 at 9:38 AM, Israel Brewster <[EMAIL PROTECTED] 
> wrote:

I have a number of devices on my network that have dual-interfaces
such that either one can go down, but the device itself, and all the
devices behind it (in the case of a router) is still up and reachable.
What is the best way to set up monitoring of such devices, considering
that as far as I can tell you can only assign one IP per host? I have
looked at check_cluster, but if that is the best method I am unsure of
the best way of implementing it. Things I have thought of:

1) Create two "dummy" hosts which are the two ports, and then a third
host with a check command of check_cluster that looks at those two
dummy hosts. This seems overly complicated, not to mention cluttering
up my configs and nagios interface with three hosts where there is
really only one.

2) Simply monitor the two ports as two separate hosts. This could
work, but again clutters things up with multiple hosts where only one
exists, and adds the requirement of multi-parenting any child devices,
which can get ugly, especially in a graphical representation of the
network.

I have read http://nagios.sourceforge.net/docs/2_0/clusters.html, but
that doesn't seem to apply, at least not directly, in that it refers
either to situations where you have redundant services on one or more
hosts (perhaps that is sort of what I want?) or to where you have
multiple redundant hosts, but not to the situation where you have one
host offering one service over two ports. The main problem with that
doc, though, is that the cluster is always a service, which wouldn't
work in my situation, as the host itself is a cluster. Any thoughts?
Thanks.
---
Israel Brewster
Computer Support Technician
Frontier Flying Service Inc.
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7250 x293
---



-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012

Re: [Nagios-users] Bad Stylesheet Links

[Laack,Jacob C]

I've found what might be the area of intrigue.  This code is in the 
cgi/cgiutils.c file of the 3.0 source:

else if(!strcmp(var,"url_html_path")){

strncpy(url_html_path,val,sizeof(url_html_path));
url_html_path[sizeof(url_html_path)-1]='\x0';

strip(url_html_path);
if(url_html_path[strlen(url_html_path)-1]!='/' && 
(strlen(url_html_path) < sizeof(url_html_path)-1))
strcat(url_html_path,"/");
...

snprintf(url_stylesheets_path,sizeof(url_stylesheets_path),"%sstylesheets/",url_html_path);

url_stylesheets_path[sizeof(url_stylesheets_path)-1]='\x0';

I believe this is where the path to the stylesheets and images originates.  
Here's the same area in the 2.9 source:

else if(strstr(input,"url_html_path=")==input){
temp_buffer=strtok(input,"=");
temp_buffer=strtok(NULL,"\n");


strncpy(url_html_path,(temp_buffer==NULL)?"":temp_buffer,sizeof(url_html_path));
url_html_path[sizeof(url_html_path)-1]='\x0';

strip(url_html_path);
if(url_html_path[strlen(url_html_path)-1]!='/' && 
(strlen(url_html_path) < sizeof(url_html_path)-1))
strcat(url_html_path,"/");
...

snprintf(url_stylesheets_path,sizeof(url_stylesheets_path),"%sstylesheets/",url_html_path);

url_stylesheets_path[sizeof(url_stylesheets_path)-1]='\x0';

It would seem the steps to determine the url_html_path have changed.  I've 
found that this post...

http://article.gmane.org/gmane.network.nagios.user/48457/

...which suggests this has been a problem for others (should have looked before 
I posted...for shame).  Any idea why the first doesn't work and the second does?

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Laack,Jacob C
Sent: Monday, March 17, 2008 12:25 PM
To: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] Bad Stylesheet Links

I've noticed that several other paths are "bad" as well.  The img tags on the 
Service Detail page are written with 'up.gif' rather than '/images/up.gif'.

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Laack,Jacob C
Sent: Monday, March 17, 2008 12:11 PM
To: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] Bad Stylesheet Links

I did the same compile and setup on my Fedora laptop and the stylesheet links 
on this machine do this...


...How does the configure/make/install/config determine the stylesheet 
directory (url_stylesheets_path)?  How can I get it to work properly/better 
again?

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Laack,Jacob C
Sent: Monday, March 17, 2008 10:51 AM
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] (no subject)

All-
I've compiled nagios 3.0 on my RHEL 5 64-bit machine.  I have the daemon 
compiled...

./configure \
--prefix=/usr/local/nagios \
--with-cgiurl=/cgi-bin \
--with-htmurl= \
--with-nagios-user=nagios \
--with-nagios-group=nagios \
--with-command-group=nagioscmd \
--enable-embedded-perl \
--with-perlcache

...and running with the sample configs.  I have configured my apache Virtual 
Server myself like so...


RewriteEngine off
Options Indexes FollowSymLinks
AllowOverride None
Order allow,deny
Allow from all



ServerAdmin [EMAIL PROTECTED]
DocumentRoot /usr/local/nagios/share
ServerName nagiosnew.alegent.org
ErrorLog logs/nagios_log
CustomLog logs/nagios_log common
ScriptAlias /cgi-bin/ "/usr/local/nagios/sbin/"


...I can access the page fine and the CGIs work as well.  However, all the 
pages generated by the CGIs have this in their head...




..which is making them all appear rather ugly.  Is there an option to specify 
the stylesheet URL?  Did I do something else wrong?  Thanks.

Jake Laack
Alegent Health, Open Systems Engineer
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null

Re: [Nagios-users] Bad Stylesheet Links

[Laack,Jacob C]

If I remove that line from the configure, nagios will expect that the site is 
nagiosnew.alegent.org/nagios/ when it's really nagiosnew.alegent.org.  I've set 
that option to...

--with-htmurl=/

...and that doesn't work either.

-Original Message-
From: Ben O'Hara [mailto:[EMAIL PROTECTED]
Sent: Monday, March 17, 2008 12:43 PM
To: Laack,Jacob C
Subject: Re: [Nagios-users] Bad Stylesheet Links

On Mon, Mar 17, 2008 at 5:25 PM, Laack,Jacob C <[EMAIL PROTECTED]> wrote:
>
>
>
>
> I've noticed that several other paths are "bad" as well.  The img tags on
> the Service Detail page are written with 'up.gif' rather than
> '/images/up.gif'.
>

Its compiled with --with-htmurl= i'd make clean and configure
again without this flag and rebuild

Ben

--
If voting changed anything, they'd make it illegal



-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null

Re: [Nagios-users] Bad Stylesheet Links

[Laack,Jacob C]

I've noticed that several other paths are "bad" as well.  The img tags on the 
Service Detail page are written with 'up.gif' rather than '/images/up.gif'.

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Laack,Jacob C
Sent: Monday, March 17, 2008 12:11 PM
To: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] Bad Stylesheet Links

I did the same compile and setup on my Fedora laptop and the stylesheet links 
on this machine do this...


...How does the configure/make/install/config determine the stylesheet 
directory (url_stylesheets_path)?  How can I get it to work properly/better 
again?

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Laack,Jacob C
Sent: Monday, March 17, 2008 10:51 AM
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] (no subject)

All-
I've compiled nagios 3.0 on my RHEL 5 64-bit machine.  I have the daemon 
compiled...

./configure \
--prefix=/usr/local/nagios \
--with-cgiurl=/cgi-bin \
--with-htmurl= \
--with-nagios-user=nagios \
--with-nagios-group=nagios \
--with-command-group=nagioscmd \
--enable-embedded-perl \
--with-perlcache

...and running with the sample configs.  I have configured my apache Virtual 
Server myself like so...


RewriteEngine off
Options Indexes FollowSymLinks
AllowOverride None
Order allow,deny
Allow from all



ServerAdmin [EMAIL PROTECTED]
DocumentRoot /usr/local/nagios/share
ServerName nagiosnew.alegent.org
ErrorLog logs/nagios_log
CustomLog logs/nagios_log common
ScriptAlias /cgi-bin/ "/usr/local/nagios/sbin/"


...I can access the page fine and the CGIs work as well.  However, all the 
pages generated by the CGIs have this in their head...




..which is making them all appear rather ugly.  Is there an option to specify 
the stylesheet URL?  Did I do something else wrong?  Thanks.

Jake Laack
Alegent Health, Open Systems Engineer
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null

[Nagios-users] Nagios report

[Fabiano Martins]

Hi,

I would like to know if anyone know some interesting tool to give
nagios availability report to users that have to know about their
hosts.

I've used a perl script already (nagios-reporter), from nagios
exchange that provide these reports trought email but the format is
not easy to understand and the presentation is not good for custumers.

I'm looking for two ways of giving reporting access to the custumers.

One is trought an email with the information, and the other one should
be an user interface that the custumers can go there and check for.

Any idea will be welcome

Regards,

Fabiano Martins

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null

Re: [Nagios-users] Bad Stylesheet Links

[Laack,Jacob C]

I did the same compile and setup on my Fedora laptop and the stylesheet links 
on this machine do this...


...How does the configure/make/install/config determine the stylesheet 
directory (url_stylesheets_path)?  How can I get it to work properly/better 
again?

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Laack,Jacob C
Sent: Monday, March 17, 2008 10:51 AM
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] (no subject)

All-
I've compiled nagios 3.0 on my RHEL 5 64-bit machine.  I have the daemon 
compiled...

./configure \
--prefix=/usr/local/nagios \
--with-cgiurl=/cgi-bin \
--with-htmurl= \
--with-nagios-user=nagios \
--with-nagios-group=nagios \
--with-command-group=nagioscmd \
--enable-embedded-perl \
--with-perlcache

...and running with the sample configs.  I have configured my apache Virtual 
Server myself like so...


RewriteEngine off
Options Indexes FollowSymLinks
AllowOverride None
Order allow,deny
Allow from all



ServerAdmin [EMAIL PROTECTED]
DocumentRoot /usr/local/nagios/share
ServerName nagiosnew.alegent.org
ErrorLog logs/nagios_log
CustomLog logs/nagios_log common
ScriptAlias /cgi-bin/ "/usr/local/nagios/sbin/"


...I can access the page fine and the CGIs work as well.  However, all the 
pages generated by the CGIs have this in their head...




..which is making them all appear rather ugly.  Is there an option to specify 
the stylesheet URL?  Did I do something else wrong?  Thanks.

Jake Laack
Alegent Health, Open Systems Engineer
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null

[Nagios-users] Dual-port monitoring

[Israel Brewster]

I have a number of devices on my network that have dual-interfaces  
such that either one can go down, but the device itself, and all the  
devices behind it (in the case of a router) is still up and reachable.  
What is the best way to set up monitoring of such devices, considering  
that as far as I can tell you can only assign one IP per host? I have  
looked at check_cluster, but if that is the best method I am unsure of  
the best way of implementing it. Things I have thought of:

1) Create two "dummy" hosts which are the two ports, and then a third  
host with a check command of check_cluster that looks at those two  
dummy hosts. This seems overly complicated, not to mention cluttering  
up my configs and nagios interface with three hosts where there is  
really only one.

2) Simply monitor the two ports as two separate hosts. This could  
work, but again clutters things up with multiple hosts where only one  
exists, and adds the requirement of multi-parenting any child devices,  
which can get ugly, especially in a graphical representation of the  
network.

I have read http://nagios.sourceforge.net/docs/2_0/clusters.html, but  
that doesn't seem to apply, at least not directly, in that it refers  
either to situations where you have redundant services on one or more  
hosts (perhaps that is sort of what I want?) or to where you have  
multiple redundant hosts, but not to the situation where you have one  
host offering one service over two ports. The main problem with that  
doc, though, is that the cluster is always a service, which wouldn't  
work in my situation, as the host itself is a cluster. Any thoughts?  
Thanks.
---
Israel Brewster
Computer Support Technician
Frontier Flying Service Inc.
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7250 x293
---



-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null

Re: [Nagios-users] (no subject)

[Gary Every]

Guess I forgot the link ;-[

http://www.nagiosexchange.org/Image_Packs.75.0.html?&tx_netnagext_pi1%5Bp_view%5D=252


On Mon, Mar 17, 2008 at 8:50 AM, Laack,Jacob C <[EMAIL PROTECTED]> wrote:

>  All-
>
> I've compiled nagios 3.0 on my RHEL 5 64-bit machine.  I have the daemon
> compiled…
>
>
>
> ./configure \
>
> --prefix=/usr/local/nagios \
>
> --with-cgiurl=/cgi-bin \
>
> --with-htmurl= \
>
> --with-nagios-user=nagios \
>
> --with-nagios-group=nagios \
>
> --with-command-group=nagioscmd \
>
> --enable-embedded-perl \
>
> --with-perlcache
>
>
>
> …and running with the sample configs.  I have configured my apache Virtual
> Server myself like so…
>
>
>
> 
>
> RewriteEngine off
>
> Options Indexes FollowSymLinks
>
> AllowOverride None
>
> Order allow,deny
>
> Allow from all
>
> 
>
>
>
> 
>
> ServerAdmin [EMAIL PROTECTED]
>
> DocumentRoot /usr/local/nagios/share
>
> ServerName nagiosnew.alegent.org
>
> ErrorLog logs/nagios_log
>
> CustomLog logs/nagios_log common
>
> ScriptAlias /cgi-bin/ "/usr/local/nagios/sbin/"
>
> 
>
>
>
> …I can access the page fine and the CGIs work as well.  However, all the
> pages generated by the CGIs have this in their head…
>
>
>
> 
>
> 
>
>
>
> ..which is making them all appear rather ugly.  Is there an option to
> specify the stylesheet URL?  Did I do something else wrong?  Thanks.
>
>
>
> Jake Laack
>
> Alegent Health, Open Systems Engineer
>
> -
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
> ___
> Nagios-users mailing list
> Nagios-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS when
> reporting any issue.
> ::: Messages without supporting info will risk being sent to /dev/null
>



-- 
Gary Every
"Pay it Forward!"
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null

[Nagios-users] (no subject)

[Laack,Jacob C]

All-
I've compiled nagios 3.0 on my RHEL 5 64-bit machine.  I have the daemon 
compiled...

./configure \
--prefix=/usr/local/nagios \
--with-cgiurl=/cgi-bin \
--with-htmurl= \
--with-nagios-user=nagios \
--with-nagios-group=nagios \
--with-command-group=nagioscmd \
--enable-embedded-perl \
--with-perlcache

...and running with the sample configs.  I have configured my apache Virtual 
Server myself like so...


RewriteEngine off
Options Indexes FollowSymLinks
AllowOverride None
Order allow,deny
Allow from all



ServerAdmin [EMAIL PROTECTED]
DocumentRoot /usr/local/nagios/share
ServerName nagiosnew.alegent.org
ErrorLog logs/nagios_log
CustomLog logs/nagios_log common
ScriptAlias /cgi-bin/ "/usr/local/nagios/sbin/"


...I can access the page fine and the CGIs work as well.  However, all the 
pages generated by the CGIs have this in their head...




..which is making them all appear rather ugly.  Is there an option to specify 
the stylesheet URL?  Did I do something else wrong?  Thanks.

Jake Laack
Alegent Health, Open Systems Engineer
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null

Re: [Nagios-users] Nagios-users Digest, Vol 22, Issue 28

[Carlo Alberto Bedogni]

Hi Tom, and all

i have solved with the check_http plugin , it's work very fine ..:)

the plugin check_apache.pl come with the package  nagios-plugins.x86_64
1.4.11-1.el5.rf from the rpmforge repository

thank all !!

On Sun, Mar 16, 2008 at 8:21 PM, <[EMAIL PROTECTED]>
wrote:

> Send Nagios-users mailing list submissions to
>nagios-users@lists.sourceforge.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
>https://lists.sourceforge.net/lists/listinfo/nagios-users
> or, via email, send a message with subject or body 'help' to
>[EMAIL PROTECTED]
>
> You can reach the person managing the list at
>[EMAIL PROTECTED]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Nagios-users digest..."
>
>
> Today's Topics:
>
>   1. Re: setup check_apache.pl (Tom Throckmorton)
>
>
> --
>
> Message: 1
> Date: Sat, 15 Mar 2008 15:44:28 -0400
> From: Tom Throckmorton <[EMAIL PROTECTED]>
> Subject: Re: [Nagios-users] setup check_apache.pl
> To: Carlo Alberto Bedogni <[EMAIL PROTECTED]>
> Cc: nagios-users@lists.sourceforge.net
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=us-ascii
>
> On Mar 15 10:57, Carlo Alberto Bedogni wrote:
> > hi all
> >
> > i have nagios 2.10 on centos 5 , i'm trying to install check_apache.pl
> but
> > give me a error 127 .
> >
> > check_apache.pl is locate in /usr/lib64/nagios/plugins/contrib/
> >
> > in /etc/nagios/localhost.cfg i have add this lines :
> >
> > define service{
> >use  local-service ; Name of
> > service template to use
> >host_namelocalhost
> >service_description  Check apache
> >check_commandcheck_apache.pl
> >}
> >
> >
> > and in /etc/nagios/command.cfg this lines:
> >
> > # 'check_apache.pl' command definition
> > define command{
> > command_namecheck_apache.pl
> > command_line$USER1$/check_apache.pl -H $HOSTADDRESS$
> > }
>
> Carlo,
>
> Assuming you have $USER1$ set to /usr/lib64/nagios/plugins/, then you need
> to
> change that command_line to:
>
> > command_line$USER1$/contrib/check_apache.pl -H $HOSTADDRESS$
>
> Regardless, I think this plugin isn't going to do what you want - it's
> very
> old, and doesn't work against Apache 2.x, which is the default on CentOS
> 5.  If
> you think checking via mod_status is really what you want/need, then
> someone
> updated this script a while ago to work with 2.x:
>
> http://readlist.com/lists/lists.sourceforge.net/nagios-users/0/320.html
>
> ...are you really just looking to make sure your local Apache instance is
> alive?  Have you tried check_http?
>
> > the plugin check-apache come with a standard rpm for centos...
>
> Out of curiosity - which rpm are you using and from where?
>
> Cheers,
>
> -tt
>
> --
> Tom Throckmorton
> OIT - CSI
> Duke University
>
>
>
> --
>
> -
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
>
> --
>
> ___
> Nagios-users mailing list
> Nagios-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
>
>
> End of Nagios-users Digest, Vol 22, Issue 28
> 
>
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null

Re: [Nagios-users] upgrade to 3.0, new service stuck at pending

[Heiko]

Hi Marc,

well, youre tip did not work directly, but sometime last weekend it
did check, but when I add another service the same happens again.
The time passes but the check never did get run.

What can can be wrong else?


cheers

On Fri, Mar 14, 2008 at 6:20 PM, Marc Powell <[EMAIL PROTECTED]> wrote:
>
>
>  > -Original Message-
>  > From: [EMAIL PROTECTED] [mailto:nagios-users-
>  > [EMAIL PROTECTED] On Behalf Of rupert
>  > Sent: Friday, March 14, 2008 12:10 PM
>  > To: nagios-users@lists.sourceforge.net
>  > Subject: [Nagios-users] upgrade to 3.0, new service stuck at pending
>  >
>
>
>  > define service{
>  > host_name   backend-A1, backend-B1
>  > service_description MYSQL
>  > check_command   check_mysql!monitoring
>  > max_check_attempts  3
>  > normal_check_interval   1
>  > retry_check_interval3
>  > check_period24x7
>  > notification_interval   120
>  > notification_period 24x7
>  > notification_optionsw,u,c,r,f
>  > contact_groups  noc
>  > }
>  >
>  > I checked all the file permissions and it looks fine, there are no
>  > other entries in the logfiles.
>
>  I don't know off the top of my head what the default is (I assume 0),
>  but you don't explicitly state 'active_checks_enabled 1'.
>
>  --
>  Marc
>
>  -
>  This SF.net email is sponsored by: Microsoft
>  Defy all challenges. Microsoft(R) Visual Studio 2008.
>  http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
>  ___
>  Nagios-users mailing list
>  Nagios-users@lists.sourceforge.net
>  https://lists.sourceforge.net/lists/listinfo/nagios-users
>  ::: Please include Nagios version, plugin version (-v) and OS when reporting 
> any issue.
>  ::: Messages without supporting info will risk being sent to /dev/null
>

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null

[Nagios-users] NSCA processes hanging around

[Gareth Watson]

Hello,

Over time I notice a number (a large number, ~500) of nsca processes
hanging around. I used netstat to see what they were up to and they
where all in the TIME_WAIT status.

Reading on the internet I think I understand what this means. Linux is
not closing the socket as it is waiting for any delayed traffic on the
network to appear. I have no problem with this as my first thought would
be that I will see a slow shift in the process numbers as sockets are
eventually closed and opened by new requests. This is not, however, the
behaviour I observed! The processes would wait indefinitely.

Now, clutching at straws I think I have managed to fix the problem. I
removed the REUSE flag from the nsca xinetd configuration:

# default: on
# description: NSCA
service nsca
{

#Commented out the line below in the vain hope it would fix nsca's wagon

#FLAGS = REUSE 
socket_type = stream 
wait = no 
user = nagios 
group = nagios 
server = /usr/local/nagios/bin/nsca 
server_args = -c /usr/local/nagios/etc/nsca.cfg --inetd log_on_failure
+= USERID 
disable = no 
}

Again some research on the net has told me a little bit about the REUSE
flag but I wanted to gather the opinions from those with much more
knowledge than I. Therefore, can anyone tell me if this is a reasonable
thing to do? Have I made a grievous error without even knowing? Has
anyone else experienced this behaviour?

I really appreciate anyone who has taken the time to read this and would
love some feedback if you get the chance.

Many thanks, 

Gareth Watson


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null

Re: [Nagios-users] Sending notifications via SMS+mobile phone

[Gareth Watson]

We use that terminal at our workplace.  I have been using SMSLink very 
successfully for the past 12 months.  

I did have to play with the source code to get it working just how we wanted.  
However, the developer tells me that the changes I have made are now included 
in the new version.  I would take a look at that if you want an easy way to get 
this working:

http://smslink.sourceforge.net/

Once configured and installed all we needed to do was create a notification 
command like this:

define command{
  command_name  notify-by-sms
  command_line echo -e 
"$SERVICEDESC$\r$HOSTNAME$\r$SERVICESTATE$\r$SERVICEOUTPUT$" | 
/usr/local/bin/sendsms -d $CONTACTPAGER$ -Q -f'-' localhost 2>/dev/null
}

Works a treat for us.  Plus we like the fact that we can also send SMSs to this 
software.  This means that, in theory at least, our engineers could acknowledge 
a problem or get a status report from Nagios by texting the SMS modem.  We have 
yet to implement this but it was a big selling point for our installation.

I hope this helps,

Gareth.



From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dennis Hünseler
Sent: 17 March 2008 08:02
To: Meylikhov
Cc: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] Sending notifications via SMS+mobile phone


Meylikhov schrieb: 

Hi!
Do you use this one - Siemens TC35i Terminal -
http://www.warburtech.com/gsm/tc35i.terminal/ ? 

-Original Message-
From: Sander Klein [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 14, 2008 1:38 PM
To: Meylikhov
Cc: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] Sending notifications via SMS+mobile phone

Hi,

I use the siemens tc35i gsm modem and think it's great. Just hook it up 
to your COM port, install smstool (which is in debian) create the 
configfile, make a script to send sms and go

It's really easy.

Greets,

Sander

Meylikhov wrote:
  

Hello, everybody!

Can anyone assist me in solving the following task: I need 
nagios to 
send SMS via mobile phone connected to COM port. Are there are 
such 
possibilities in nagios and are there any plugins that support 
sending 
sms via mobile phone? I found only one plugin (NAGIOSMS: 




http://www.nagiosexchange.org/Notifications.35.0.html?&tx_netnagext_pi1[p_vi
ew]=619 
  

)that is currently supports sending notifications via mobile 
phone but 
I even can't imagine how to connect mobile phone to my Linux 
Debian 
4.0 server (2.6.18-6-686). Maybe someone already has configured 
notifications send via mobile phone and can suggest me what 
mobile 
phone to buy? I also need any help (suggestions,links, 
documentation, 
etc) in connecting mobile phone to my Linux Debian 4.0 server.

My system:

Nagios server: Linux Debian 4.0 server 2.6.18-6-686

Nagios: nagios-3.0b5

Nagios plugins: nagios-plugins-1.4.11

NRPE: nrpe-2.10

Thank you!





-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/



___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS 
when


reporting any issue. 
  

::: Messages without supporting info will risk being sent to 
/dev/null





-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/list

Re: [Nagios-users] Sending notifications via SMS+mobile phone

[Dennis Hünseler]

Meylikhov schrieb:

Hi!
Do you use this one - Siemens TC35i Terminal -
http://www.warburtech.com/gsm/tc35i.terminal/ ? 


-Original Message-
From: Sander Klein [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 14, 2008 1:38 PM

To: Meylikhov
Cc: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] Sending notifications via SMS+mobile phone

Hi,

I use the siemens tc35i gsm modem and think it's great. Just hook it up 
to your COM port, install smstool (which is in debian) create the 
configfile, make a script to send sms and go


It's really easy.

Greets,

Sander

Meylikhov wrote:
  

Hello, everybody!

Can anyone assist me in solving the following task: I need nagios to 
send SMS via mobile phone connected to COM port. Are there are such 
possibilities in nagios and are there any plugins that support sending 
sms via mobile phone? I found only one plugin (NAGIOSMS: 



http://www.nagiosexchange.org/Notifications.35.0.html?&tx_netnagext_pi1[p_vi
ew]=619 
  
)that is currently supports sending notifications via mobile phone but 
I even can't imagine how to connect mobile phone to my Linux Debian 
4.0 server (2.6.18-6-686). Maybe someone already has configured 
notifications send via mobile phone and can suggest me what mobile 
phone to buy? I also need any help (suggestions,links, documentation, 
etc) in connecting mobile phone to my Linux Debian 4.0 server.


My system:

Nagios server: Linux Debian 4.0 server 2.6.18-6-686

Nagios: nagios-3.0b5

Nagios plugins: nagios-plugins-1.4.11

NRPE: nrpe-2.10

Thank you!



-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/


___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when

reporting any issue. 
  

::: Messages without supporting info will risk being sent to /dev/null




-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null


  

Hey, this is the right one. You can also use the Siemens MC35
Works also great with smstool. Used it in several companies...

Regards, Dennis
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null

Re: [Nagios-users] Sending notifications via SMS+mobile phone

[Sander Klein]

Hi,

Meylikhov wrote:
> Hi!
> Do you use this one - Siemens TC35i Terminal -
> http://www.warburtech.com/gsm/tc35i.terminal/ ? 
>   
Indeed, that's the one. I bought it with the starter kit. Which was nice 
for me because it comes with a reasonable antenna. I don't have very 
good GSM signal in my server room.

Regards,

Sander

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null

Re: [Nagios-users] Sending notifications via SMS+mobile phone

[Meylikhov]

Hi!
Do you use this one - Siemens TC35i Terminal -
http://www.warburtech.com/gsm/tc35i.terminal/ ? 

-Original Message-
From: Sander Klein [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 14, 2008 1:38 PM
To: Meylikhov
Cc: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] Sending notifications via SMS+mobile phone

Hi,

I use the siemens tc35i gsm modem and think it's great. Just hook it up 
to your COM port, install smstool (which is in debian) create the 
configfile, make a script to send sms and go

It's really easy.

Greets,

Sander

Meylikhov wrote:
>
> Hello, everybody!
>
> Can anyone assist me in solving the following task: I need nagios to 
> send SMS via mobile phone connected to COM port. Are there are such 
> possibilities in nagios and are there any plugins that support sending 
> sms via mobile phone? I found only one plugin (NAGIOSMS: 
>
http://www.nagiosexchange.org/Notifications.35.0.html?&tx_netnagext_pi1[p_vi
ew]=619 
> )that is currently supports sending notifications via mobile phone but 
> I even can't imagine how to connect mobile phone to my Linux Debian 
> 4.0 server (2.6.18-6-686). Maybe someone already has configured 
> notifications send via mobile phone and can suggest me what mobile 
> phone to buy? I also need any help (suggestions,links, documentation, 
> etc) in connecting mobile phone to my Linux Debian 4.0 server.
>
> My system:
>
> Nagios server: Linux Debian 4.0 server 2.6.18-6-686
>
> Nagios: nagios-3.0b5
>
> Nagios plugins: nagios-plugins-1.4.11
>
> NRPE: nrpe-2.10
>
> Thank you!
>
> 
>
> -
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
> 
>
> ___
> Nagios-users mailing list
> Nagios-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS when
reporting any issue. 
> ::: Messages without supporting info will risk being sent to /dev/null


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null