Re: [Nagios-users] check_ping strange behavior with google

2012-06-07 Thread Cosmin Neagu
You were right. It need to be told to use ipv4 with -4 switch.
Thanks

  Cosmin Neagu
  NOC Team Leader
  Str. I. G. Duca nr. 36
  Otopeni, Judetul Ilfov, 075100 Romania
  www.omnilogic.ro


On 06/07/2012 11:32 PM, Holger Weiß wrote:
> * Travis Runyard  [2012-06-07 13:18]:
>> It does work but I was using google.com which doesn't. Strange because
>> it is pingable but returns network unreachable with check_ping.
> See my initial reply in this thread:
>
> | The hostname www.google.ro now¹ also resolves to an IPv6 address, and
> | check_ping has issues with IPv6 dependending on the ping6(1)
> | implementation used.  These issues will hopefully be fixed in the next
> | release of the Nagios Plugins; until then, "check_ping -4 [...]" should
> | do the trick.
>
> [ http://article.gmane.org/gmane.network.nagios.user/73851 ]
>
> Holger
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> 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

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
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_ping strange behavior with google

2012-06-07 Thread Holger Weiß
* Travis Runyard  [2012-06-07 13:18]:
> It does work but I was using google.com which doesn't. Strange because
> it is pingable but returns network unreachable with check_ping.

See my initial reply in this thread:

| The hostname www.google.ro now¹ also resolves to an IPv6 address, and
| check_ping has issues with IPv6 dependending on the ping6(1)
| implementation used.  These issues will hopefully be fixed in the next
| release of the Nagios Plugins; until then, "check_ping -4 [...]" should
| do the trick.

[ http://article.gmane.org/gmane.network.nagios.user/73851 ]

Holger

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
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_ping strange behavior with google

2012-06-07 Thread Travis Runyard
Hats off to you, Holger. It does work but I was using google.com which
doesn't. Strange because it is pingable but returns network unreachable
with check_ping. Hey at least I learned something today.

On Thu, Jun 7, 2012 at 1:10 PM, Holger Weiß  wrote:

> * Travis Runyard  [2012-06-07 12:47]:
> > Long option and short option achieve the same thing, which requires an IP
> > address. I have tried it out, on two separate nagios boxes, one running
> > Debian, the other, Redhat. Why don't you copy and paste the results from
> > shell to prove me wrong?
>
> $ check_ping -H nagios-plugins.org -w 500,10% -c 750,50%
> PING OK - Packet loss = 0%, RTA = 123.06
> ms|rta=123.056999ms;500.00;750.00;0.00 pl=0%;10;50;0
>
> Holger
>
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> 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
>
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
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_ping strange behavior with google

2012-06-07 Thread Holger Weiß
* Travis Runyard  [2012-06-07 12:47]:
> Long option and short option achieve the same thing, which requires an IP
> address. I have tried it out, on two separate nagios boxes, one running
> Debian, the other, Redhat. Why don't you copy and paste the results from
> shell to prove me wrong?

$ check_ping -H nagios-plugins.org -w 500,10% -c 750,50%
PING OK - Packet loss = 0%, RTA = 123.06 
ms|rta=123.056999ms;500.00;750.00;0.00 pl=0%;10;50;0

Holger

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
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_ping strange behavior with google

2012-06-07 Thread Travis Runyard
Long option and short option achieve the same thing, which requires an IP
address. I have tried it out, on two separate nagios boxes, one running
Debian, the other, Redhat. Why don't you copy and paste the results from
shell to prove me wrong?

On Thu, Jun 7, 2012 at 12:26 PM, Holger Weiß wrote:

> * Travis Runyard  [2012-06-07 09:56]:
> > http://nagiosplugins.org/man/check_ping
> >
> >  = IP address. NOT hostname.
>
> Indeed, "host_address" seems to suggest an IP address.  Then again, the
> long option is called "--hostname" :-)  Anyway, you can specify either
> an IP address or a hostname.  Why don't you simply try it out?
>
> > $HOSTADDRESS$ - Address of the host. This value is taken from the
> > *address* directive in the host definition
>
> You neither have to hand over the $HOSTADDRESS$ to check_ping (you could
> use the $HOSTALIAS$ or whatever you like instead), nor do you have to
> specify an IP address as the "address" of a host.¹  We use only
> hostnames in our Nagios configuration.
>
> Holger
>
> ¹ "Normally, this is an IP address, although it could really be anything
>  you want" -- http://nagios.sf.net/docs/3_0/objectdefinitions.html#host
>
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> 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
>
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
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_ping strange behavior with google

2012-06-07 Thread Holger Weiß
* Travis Runyard  [2012-06-07 09:56]:
> http://nagiosplugins.org/man/check_ping
> 
>  = IP address. NOT hostname.

Indeed, "host_address" seems to suggest an IP address.  Then again, the
long option is called "--hostname" :-)  Anyway, you can specify either
an IP address or a hostname.  Why don't you simply try it out?

> $HOSTADDRESS$ - Address of the host. This value is taken from the
> *address* directive in the host definition

You neither have to hand over the $HOSTADDRESS$ to check_ping (you could
use the $HOSTALIAS$ or whatever you like instead), nor do you have to
specify an IP address as the "address" of a host.¹  We use only
hostnames in our Nagios configuration.

Holger

¹ "Normally, this is an IP address, although it could really be anything
  you want" -- http://nagios.sf.net/docs/3_0/objectdefinitions.html#host

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
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_ping strange behavior with google

2012-06-07 Thread Travis Runyard
http://nagiosplugins.org/man/check_ping

 = IP address. NOT hostname.
$HOSTADDRESS$Address of the host. This value is taken from the
*address* directive
in the host definition
.
On Thu, Jun 7, 2012 at 8:56 AM, Holger Weiß  wrote:

> * Travis Runyard  [2012-06-07 08:39]:
> > The check_ping Nagios plugin does not ping hostnames, only IP addresses.
>
> The check_ping plugin supports hostnames just fine.
>
> > On Wed, Jun 6, 2012 at 11:54 PM, Cosmin Neagu  >wrote:
> > > Starting from yesterday, check_ping is behaving strange for a single
> host.
> > > When giving -H parameter as www.google.ro it gives CRITICAL - Network
> > > Unreachable
> > > But when giving -H parameter as IP address it is working. I have
> checked
> > > and there are no DNS issues
>
> The hostname www.google.ro now¹ also resolves to an IPv6 address, and
> check_ping has issues with IPv6 dependending on the ping6(1)
> implementation used.  These issues will hopefully be fixed in the next
> release of the Nagios Plugins; until then, "check_ping -4 [...]" should
> do the trick.
>
> Holger
>
> ¹ http://en.wikipedia.org/wiki/World_IPv6_Day_and_World_IPv6_Launch_Day
>
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> 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
>
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
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_ping strange behavior with google

2012-06-07 Thread Holger Weiß
* Travis Runyard  [2012-06-07 08:39]:
> The check_ping Nagios plugin does not ping hostnames, only IP addresses.

The check_ping plugin supports hostnames just fine.

> On Wed, Jun 6, 2012 at 11:54 PM, Cosmin Neagu 
> wrote:
> > Starting from yesterday, check_ping is behaving strange for a single host.
> > When giving -H parameter as www.google.ro it gives CRITICAL - Network
> > Unreachable
> > But when giving -H parameter as IP address it is working. I have checked
> > and there are no DNS issues

The hostname www.google.ro now¹ also resolves to an IPv6 address, and
check_ping has issues with IPv6 dependending on the ping6(1)
implementation used.  These issues will hopefully be fixed in the next
release of the Nagios Plugins; until then, "check_ping -4 [...]" should
do the trick.

Holger

¹ http://en.wikipedia.org/wiki/World_IPv6_Day_and_World_IPv6_Launch_Day

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
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_ping strange behavior with google

2012-06-07 Thread Travis Runyard
The check_ping Nagios plugin does not ping hostnames, only IP addresses.

-Travis

On Wed, Jun 6, 2012 at 11:54 PM, Cosmin Neagu wrote:

> Hi nagios users,
>
> Starting from yesterday, check_ping is behaving strange for a single host.
> When giving -H parameter as www.google.ro it gives CRITICAL - Network
> Unreachable
> But when giving -H parameter as IP address it is working. I have checked
> and there are no DNS issues
>
>
> nagios@mon2:/usr/local/nagios/libexec$ ./check_ping -H 173.194.35.159 -w
> 3000.0,80% -c 5000.0,100%
> PING OK - Packet loss = 0%, RTA = 46.97
> ms|rta=46.971001ms;3000.00;5000.00;0.00 pl=0%;80;100;0
> nagios@mon2:/usr/local/nagios/libexec$ ./check_ping -H www.google.ro -w
> 3000.0,80% -c 5000.0,100%
> CRITICAL - Network Unreachable (www.google.ro)
> nagios@mon2:/usr/local/nagios/libexec$ ping www.google.ro
> PING www-cctld.l.google.com (173.194.35.159) 56(84) bytes of data.
> 64 bytes from muc03s01-in-f31.1e100.net (173.194.35.159): icmp_seq=1
> ttl=54 time=46.8 ms
> 64 bytes from muc03s01-in-f31.1e100.net (173.194.35.159): icmp_seq=2
> ttl=54 time=46.8 ms
>
>
> Using nagios 3.2.3
> nagios@mon2:/usr/local/nagios/libexec$ ./check_ping -h
> check_ping v1.4.15 (nagios-plugins 1.4.15)
> Copyright (c) 1999 Ethan Galstad 
>
>
> After a little more search
> Other sites works ok when used with check_ping, but not site containing
> goole is working
>
> nagios@mon2:/usr/local/nagios/libexec$ ./check_ping -H www.google.de -w
> 3000.0,80% -c 5000.0,100%
> CRITICAL - Network Unreachable (www.google.de)
> nagios@mon2:/usr/local/nagios/libexec$ ./check_ping -H www.google.com -w
> 3000.0,80% -c 5000.0,100%
> CRITICAL - Network Unreachable (www.google.com)
> nagios@mon2:/usr/local/nagios/libexec$ ./check_ping -H www.google.it -w
> 3000.0,80% -c 5000.0,100%
> CRITICAL - Network Unreachable (www.google.it)
>
> Any idea why?
>
>
>
>
>
>
> --
>  Cosmin Neagu
>  NOC Team Leader
>  Str. I. G. Duca nr. 36
>  Otopeni, Judetul Ilfov, 075100 Romania
>   www.omnilogic.ro
>
>
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> 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
>
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
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] Disk Partitioning for Nagios

2012-06-07 Thread Victor Sanchez2
Hi Faiz,

the more important things are about database and performace. If you are
going to work with NDOUtils for example and MySQL, the best option is to
create a new and independent mount point depending on the data retention
that you need. Then /var/lib/mysql could be a good option.

For performance, if you are going to work with pnp4nagios for example, a
good option is an independent mount point for /var/lib/pnp4nagios.

And for global configuration, you can create the following for example:

250MB - /boot  (out of the LVM)
LVM
  XXX - swap (depending on your requirements)
  2GB  /tmp
  10GB /usr
  8GB   /var
  4GB   /home (it depends on that you want to do)
  XXX  /opt  (if you don't need more "external" software, probably you
don't need it with a big reserve)
  2GB  /

  50GB  /var/lib/mysql
  30GB  /var/lib/pnp4nagios

Also, if you are going to work with SVN to save the .cfg files versions,
you probably need a new mount point for this to separate it.

This is a example, it depends on each time. If you can, separete the
important things in different mount points and maintain an standard
operating system partitioning.

Best regards,
Víctor.


On 7 June 2012 08:25, Muhamad Faiz  wrote:

>  Hi guys, 
>
> ** **
>
> I’m not sure if this question has been asked before but I can’t find
> anything about this. What is the recommended partitioning scheme in Linux
> (ie Redhat) suitable for Nagios implementation? How much percentage for /,
> 40% for /var or what not. Please advice.
>
> ** **
>
> Thanks.
>
> ** **
>
> - Faiz
>
> ** **
>
> "CONFIDENTIALITY NOTICE: This message and any attachment are confidential
> and may also be privileged. If you are not the intended recipient of this
> e-mail you may not copy, forward, disclose or otherwise use it or any part
> of it in any form whatsoever. If you are not the intended recipient please
> telephone or e-mail the sender and delete this message and any attachment
> from your system."
>
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> 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
>
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
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_ping strange behavior with google

2012-06-07 Thread Cosmin Neagu
Hi nagios users,

Starting from yesterday, check_ping is behaving strange for a single host.
When giving -H parameter as www.google.ro it gives CRITICAL - Network 
Unreachable
But when giving -H parameter as IP address it is working. I have checked 
and there are no DNS issues


nagios@mon2:/usr/local/nagios/libexec$ ./check_ping -H 173.194.35.159 -w 
3000.0,80% -c 5000.0,100%
PING OK - Packet loss = 0%, RTA = 46.97 
ms|rta=46.971001ms;3000.00;5000.00;0.00 pl=0%;80;100;0
nagios@mon2:/usr/local/nagios/libexec$ ./check_ping -H www.google.ro -w 
3000.0,80% -c 5000.0,100%
CRITICAL - Network Unreachable (www.google.ro)
nagios@mon2:/usr/local/nagios/libexec$ ping www.google.ro
PING www-cctld.l.google.com (173.194.35.159) 56(84) bytes of data.
64 bytes from muc03s01-in-f31.1e100.net (173.194.35.159): icmp_seq=1 
ttl=54 time=46.8 ms
64 bytes from muc03s01-in-f31.1e100.net (173.194.35.159): icmp_seq=2 
ttl=54 time=46.8 ms


Using nagios 3.2.3
nagios@mon2:/usr/local/nagios/libexec$ ./check_ping -h
check_ping v1.4.15 (nagios-plugins 1.4.15)
Copyright (c) 1999 Ethan Galstad 


After a little more search
Other sites works ok when used with check_ping, but not site containing 
goole is working

nagios@mon2:/usr/local/nagios/libexec$ ./check_ping -H www.google.de -w 
3000.0,80% -c 5000.0,100%
CRITICAL - Network Unreachable (www.google.de)
nagios@mon2:/usr/local/nagios/libexec$ ./check_ping -H www.google.com -w 
3000.0,80% -c 5000.0,100%
CRITICAL - Network Unreachable (www.google.com)
nagios@mon2:/usr/local/nagios/libexec$ ./check_ping -H www.google.it -w 
3000.0,80% -c 5000.0,100%
CRITICAL - Network Unreachable (www.google.it)

Any idea why?






-- 
  Cosmin Neagu
  NOC Team Leader
  Str. I. G. Duca nr. 36
  Otopeni, Judetul Ilfov, 075100 Romania
   www.omnilogic.ro


--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
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