Tuesday, May 21st 2013, 6:41pm UTC+2

You are not logged in.

  • Login
  • Register

Dear visitor, welcome to Monitoring-Portal.
Although this is a german monitoring forum, please don't hesitate to post in English. Nearly everybody here understands you and will answer in English as well.
If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form to register here or read more information about the registration process. If you are already registered, please login here.

JensT

Beginner

Posts: 20

Number of monitoring servers: 1

Nagios Version: 3.3.1

Distributed monitoring: Nein

Redundant monitoring: Nein

Number of hosts: 187

Number of services: 143

OS: CentOS

Plugin Version: ?

NDO Version: 1

1

Monday, April 16th 2012, 9:00am

check_iftraffic4.pl Server performance

Hey, I'm quite new to Nagios and I have the following problem:



I'm using the check_iftraffic4.pl plugin to monitor some interfaces.

Now i have the following problem.

I'm monitoring about 30 interfaces with the check_iftraffic4.pl plugin. After some time (aprox 1 hour) my server starts having latency problems and getting wrong results.

For example my servers says that there's 90 hosts of 120 hosts down which is totally wrong.



Now I disabled the check_iftraffic4.pl services and there's no problem with my server.



This weekend I monitored 15 interfaces with the plugin and when I see the logs of my server it looks like it works fine.

Now my question is: Am I monitoring to much interfaces with the check_iftraffic4.pl?



Thanks in advance!

bern

Master

Posts: 2,938

Number of monitoring servers: 2-5

Nagios Version: 3.x

Distributed monitoring: Nein

Redundant monitoring: Nein

Number of hosts: 80-200

Number of services: 1400-2000

OS: Linux

Plugin Version: Whatever I can download, patch, or cobble together myself :-)

Other Addons: n2rrd, PNP, livestatus

2

Monday, April 16th 2012, 11:52am

I'm having a bit of trouble to imagine how problems with a service check command could lead to hosts being erroneously pronounced DOWN, and only that. Since you seem to have traced it (to latency effects?), could you elaborate on that? Otherwise, what host check command do you use, and what is it's (textual) output in the error state?

JensT

Beginner

Posts: 20

Number of monitoring servers: 1

Nagios Version: 3.3.1

Distributed monitoring: Nein

Redundant monitoring: Nein

Number of hosts: 187

Number of services: 143

OS: CentOS

Plugin Version: ?

NDO Version: 1

3

Monday, April 16th 2012, 12:14pm

I'm having a bit of trouble to imagine how problems with a service check command could lead to hosts being erroneously pronounced DOWN, and only that. Since you seem to have traced it (to latency effects?), could you elaborate on that? Otherwise, what host check command do you use, and what is it's (textual) output in the error state?


I'm using the check_host_alive check command.



I'm using Fully Automated Nagios. When i check all my interface in the network after some time the webpage says that my server is having latency problems. When these problems occur my servers is very slow and it starts saying hosts are down even if they're up

Now I'm monitoring about 15 interfaces for a few days and I'm not having any problems or errors yet. So I think the check_iftraffic plugin is causing these latency problems.

6uellerBpanda

Intermediate

Posts: 212

Gender: male

Location: Linz

Number of monitoring servers: 1

Nagios Version: 0.0

Icinga Version: 1.7.0

Distributed monitoring: Ja

Redundant monitoring: Nein

Number of hosts: -

Number of services: -

OS: SLES11

Plugin Version: -

NDO Version: -

4

Monday, April 16th 2012, 1:31pm

how long does it take for the check_iftraffic to complete the command ?
please execute plugin on cli.

bern

Master

Posts: 2,938

Number of monitoring servers: 2-5

Nagios Version: 3.x

Distributed monitoring: Nein

Redundant monitoring: Nein

Number of hosts: 80-200

Number of services: 1400-2000

OS: Linux

Plugin Version: Whatever I can download, patch, or cobble together myself :-)

Other Addons: n2rrd, PNP, livestatus

5

Monday, April 16th 2012, 5:31pm

I'm using the check_host_alive check command.
Which, I presume, is ultimately a "ping" command (read: a mechanism completely different from the SNMP used to gather interface statistics). There are no services being erroneously reported as down?

JensT

Beginner

Posts: 20

Number of monitoring servers: 1

Nagios Version: 3.3.1

Distributed monitoring: Nein

Redundant monitoring: Nein

Number of hosts: 187

Number of services: 143

OS: CentOS

Plugin Version: ?

NDO Version: 1

6

Tuesday, April 17th 2012, 9:01am

I'm using the check_host_alive check command.
Which, I presume, is ultimately a "ping" command (read: a mechanism completely different from the SNMP used to gather interface statistics). There are no services being erroneously reported as down?
It's only hosts being erroneously reported as down.

bern

Master

Posts: 2,938

Number of monitoring servers: 2-5

Nagios Version: 3.x

Distributed monitoring: Nein

Redundant monitoring: Nein

Number of hosts: 80-200

Number of services: 1400-2000

OS: Linux

Plugin Version: Whatever I can download, patch, or cobble together myself :-)

Other Addons: n2rrd, PNP, livestatus

7

Tuesday, April 17th 2012, 9:50am

I'm using the check_host_alive check command.
Which, I presume, is ultimately a "ping" command (read: a mechanism completely different from the SNMP used to gather interface statistics). There are no services being erroneously reported as down?
It's only hosts being erroneously reported as down.
As far as the mechanism connecting (probable) cause and effect is concerned - I'm stumped, sorry. :huh: Something FAN specific, possibly.

Please try to continue analysis into the service check, as 6uellerBpanda suggested.

Similar threads