Re: [Nagios-users] problem with nsca
Marc Powell wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:nagios-users- [EMAIL PROTECTED] On Behalf Of basile au siris Sent: Tuesday, February 14, 2006 8:29 AM To: nagios-users@lists.sourceforge.net Subject: [Nagios-users] problem with nsca i install nagios and nsca on Fedora core 4 after a short time i have many process nsca and it seems it never decrease idea ? Make sure you have proper permissions on the external command file (per the documentation on External Commands) Yes . Make sure that Nagios is set to check for external commands frequently enough (command_check_interval). every 15 s Try turning on NSCA debug and watch your messages log file for interesting output. just have nsca logs from checks and nsca : handling connection If you have SELinux enabled, make sure that it's not interfering with NSCA's ability to write to the external command file; look for 'avc denied' messages related to the command file in /var/log/messages. selinux is disable and in one hour i have 600 nsca process what can i do thanks basile -- Marc --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd___ 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: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
[Nagios-users] problem with nsca
i install nagios and nsca on Fedora core 4 after a short time i have many process nsca and it seems it never decrease idea ? thanks basile --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 ___ 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] nsca / distributed monitoring result problem
hi
maybe i have the same problem
i have distributed monitoring and the central server sometimes freeze
and i just
have to reboot it ( electric )
i suspect nsca ( or hardware problem ) because sometimes i note there
are many ( 50 )
nsca process and if i restart it all become normal again
hope we solve our problem
basile
Chris Goosen wrote:
Hello all..
I am running my nagios central server on an HP 2.4ghz with 512mb ram.
At present, I am monitoring 65 hosts with approx. 400 services.
After a reboot, everything works perfectly, but the longer my server
runs, the more sluggish it gets and eventually the nsca processes
consume all the memory and the server stops responding. What also
happens it that I start getting hosts that are reported as down even
though they have the correct ping response.. the error says “PLUGIN
TIMED OUT after 10 seconds”
Here is an example of what I mean:
Host State Information
Host Status:
DOWN
Status Information:
CRITICAL - Plugin timed out after 10 seconds
Last Status Check:
01-16-2006 12:06:28
Status Data Age:
0d 0h 2m 57s
Last State Change:
01-16-2006 10:20:44
Current State Duration:
0d 1h 48m 41s
Last Host Notification:
01-16-2006 10:20:44
Current Notification Number:
2
Is This Host Flapping?
N/A
OK 01-16-2006 12:05:47 63d 19h 30m 59s 1/3 PING OK - Packet loss = 0%,
RTA = 0.42 ms
I assume that these are related and that the lack of memory caused
this problem, would an upgrade to from nagios 1.2 to nagios 1.3 fix
this? If so, what is the best way to perform that upgrade?
my /etc/xinetd.d/nsca file :
# default: on
# description: NSCA
service nsca
{
flags = REUSE
socket_type = stream
wait = no
user = nagios
group = nagios
server = /usr/sbin/nsca
server_args = -c /home/e-smith/nagios/nsca.cfg --inetd
cps = 9000 30
instances = UNLIMITED
log_on_failure += USERID
disable = no
only_from = ip1, ip2, ip3, etc..
}
command_check_interval= -1
System info:
SME server 6.01 (2.4.20-18.7, i686)
Perl v5.6.1
Apache/1.3.27
Nagios 1.2
Any advice would be great… thanks.
Chris
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] problem check_traceroute
it s not round robin problem i thinks it s router problem because i have same error on many routers on the route i try with 72.14.238.124 , 64.233.175.246 and i have same error why is there -- sometimes between two ip address ? it seems to failed the first time there is -- basile Tedman Eng wrote: You'll want to traceroute by IP rather than by name. Google uses DNS round robin, so each time you traceroute, you'll get a different IP, and likely a different path. You may also want to notify Google that you're using their resources for your automated tests. -Original Message----- From: basile au siris [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 11, 2006 2:54 AM To: nagios-users@lists.sourceforge.net Subject: [Nagios-users] problem check_traceroute hi i do check_traceroute -r and obtain a route i do check_traceroute -R this route and have errors can someone explain me what it means ? here are logs ./check_traceroute.pl -r -H www.google.fr Ok. Traceroute to host "www.google.fr" via route "195.220.107.253-195.221.127.97-195.221.127.110-193.51.181.102 -193.51.180.158--193.51.179.1--193.51.179.34-194.68.129.242-80 .231.79.42-80.231.64.25--80.231.66.4-80.231.66.50-72.14.238.12 8-72.14.238.119-64.233.175.246-66.249.94.46-66.249.94.54-66.24 9.93.99". ./check_traceroute.pl -R "195.220.107.253-195.221.127.97-195.221.127.110-193.51.181.102 -193.51.180.158--193.51.179.1--193.51.179.34-194.68.129.242-80 .231.79.42-80.231.64.25--80.231.66.4-80.231.66.50-72.14.238.12 8-72.14.238.119-64.233.175.246-66.249.94.46-66.249.94.54-66.24 9.93.99" -H www.google.fr Failed. Last 2 routers () repeated, "195.220.107.253-195.221.127.97-195.221.127.110-193.51.181.102 -193.51.180.158--". traceroute to www.l.google.com (66.249.93.99), 30 hops max, 38 byte packets 1 XX-MSFC-1 (195.220.107.253) 1.064 ms 0.802 ms 0.776 ms 2 cr-odeon.rap.prd.fr (195.221.127.97) 1.898 ms 1.653 ms 1.357 ms 3 195.221.127.110 (195.221.127.110) 2.153 ms 2.075 ms 1.569 ms 4 jussieu-g0-1-165.cssi.renater.fr (193.51.181.102) 1.639 ms 2.288 ms 1.532 ms 5 nri-c-pos2-0.cssi.renater.fr (193.51.180.158) 2.181 ms 1.914 ms 2.421 ms MPLS Label=273 CoS=5 TTL=1 S=0 6 nri-a-gi1-0-0-11.cssi.renater.fr (193.51.179.1) 3.028 ms 2.687 ms 2.550 ms MPLS Label=27 CoS=5 TTL=1 S=0 7 193.51.179.34 (193.51.179.34) 2.596 ms 1.934 ms 1.573 ms 8 TELEGLOBE-FRANCE-INTERNATIONAL.sfinx.tm.fr (194.68.129.242) 2.810 ms 2.464 ms 2.751 ms 9 if-8-0.core1.PG1-Paris.teleglobe.net (80.231.79.42) 2.369 ms 2.647 ms 3.451 ms 10 if-6-0.core1.FR1-Frankfurt.teleglobe.net (80.231.64.25) 12.886 ms 12.652 ms 12.210 ms MPLS Label=17 CoS=5 TTL=1 S=0 11 Vlan2.msfc1.FR1-Frankfurt.teleglobe.net (80.231.66.4) 12.801 ms 13.139 ms 12.335 ms 12 Vlan108.msfc1.FR1-Frankfurt.teleglobe.net (80.231.66.50) 12.124 ms 12.111 ms 14.045 ms 13 72.14.238.128 (72.14.238.128) 13.207 ms 12.388 ms 72.14.238.124 (72.14.238.124) 12.277 ms 14 72.14.238.119 (72.14.238.119) 16.894 ms 16.596 ms 16.491 ms 15 64.233.175.246 (64.233.175.246) 20.153 ms 18.976 ms 18.996 ms 16 66.249.94.46 (66.249.94.46) 21.722 ms 19.380 ms 216.239.43.42 (216.239.43.42) 19.112 ms 17 66.249.94.54 (66.249.94.54) 30.050 ms 24.097 ms 30.946 ms 18 66.249.93.99 (66.249.93.99) 19.916 ms 20.407 ms 19.316 ms thanks basile --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ 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: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
[Nagios-users] problem check_traceroute
hi i do check_traceroute -r and obtain a route i do check_traceroute -R this route and have errors can someone explain me what it means ? here are logs ./check_traceroute.pl -r -H www.google.fr Ok. Traceroute to host "www.google.fr" via route "195.220.107.253-195.221.127.97-195.221.127.110-193.51.181.102-193.51.180.158--193.51.179.1--193.51.179.34-194.68.129.242-80.231.79.42-80.231.64.25--80.231.66.4-80.231.66.50-72.14.238.128-72.14.238.119-64.233.175.246-66.249.94.46-66.249.94.54-66.249.93.99". ./check_traceroute.pl -R "195.220.107.253-195.221.127.97-195.221.127.110-193.51.181.102-193.51.180.158--193.51.179.1--193.51.179.34-194.68.129.242-80.231.79.42-80.231.64.25--80.231.66.4-80.231.66.50-72.14.238.128-72.14.238.119-64.233.175.246-66.249.94.46-66.249.94.54-66.249.93.99" -H www.google.fr Failed. Last 2 routers () repeated, "195.220.107.253-195.221.127.97-195.221.127.110-193.51.181.102-193.51.180.158--". traceroute to www.l.google.com (66.249.93.99), 30 hops max, 38 byte packets 1 XX-MSFC-1 (195.220.107.253) 1.064 ms 0.802 ms 0.776 ms 2 cr-odeon.rap.prd.fr (195.221.127.97) 1.898 ms 1.653 ms 1.357 ms 3 195.221.127.110 (195.221.127.110) 2.153 ms 2.075 ms 1.569 ms 4 jussieu-g0-1-165.cssi.renater.fr (193.51.181.102) 1.639 ms 2.288 ms 1.532 ms 5 nri-c-pos2-0.cssi.renater.fr (193.51.180.158) 2.181 ms 1.914 ms 2.421 ms MPLS Label=273 CoS=5 TTL=1 S=0 6 nri-a-gi1-0-0-11.cssi.renater.fr (193.51.179.1) 3.028 ms 2.687 ms 2.550 ms MPLS Label=27 CoS=5 TTL=1 S=0 7 193.51.179.34 (193.51.179.34) 2.596 ms 1.934 ms 1.573 ms 8 TELEGLOBE-FRANCE-INTERNATIONAL.sfinx.tm.fr (194.68.129.242) 2.810 ms 2.464 ms 2.751 ms 9 if-8-0.core1.PG1-Paris.teleglobe.net (80.231.79.42) 2.369 ms 2.647 ms 3.451 ms 10 if-6-0.core1.FR1-Frankfurt.teleglobe.net (80.231.64.25) 12.886 ms 12.652 ms 12.210 ms MPLS Label=17 CoS=5 TTL=1 S=0 11 Vlan2.msfc1.FR1-Frankfurt.teleglobe.net (80.231.66.4) 12.801 ms 13.139 ms 12.335 ms 12 Vlan108.msfc1.FR1-Frankfurt.teleglobe.net (80.231.66.50) 12.124 ms 12.111 ms 14.045 ms 13 72.14.238.128 (72.14.238.128) 13.207 ms 12.388 ms 72.14.238.124 (72.14.238.124) 12.277 ms 14 72.14.238.119 (72.14.238.119) 16.894 ms 16.596 ms 16.491 ms 15 64.233.175.246 (64.233.175.246) 20.153 ms 18.976 ms 18.996 ms 16 66.249.94.46 (66.249.94.46) 21.722 ms 19.380 ms 216.239.43.42 (216.239.43.42) 19.112 ms 17 66.249.94.54 (66.249.94.54) 30.050 ms 24.097 ms 30.946 ms 18 66.249.93.99 (66.249.93.99) 19.916 ms 20.407 ms 19.316 ms thanks basile --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ 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
