FAIL nsca service_limit

[Steve Shipway]

>Jun 29 17:27:47 schumi xinetd[23752]: START: nsca pid=23361 
>from=172.26.192.37 Jun 29 17:27:47 schumi xinetd[23752]: 
>START: nsca pid=23362 from=172.26.192.37 Jun 29 17:27:55 
>schumi xinetd[23752]: FAIL: nsca service_limit 
>from=172.26.192.37 Jun 29 17:27:55 schumi xinetd[23752]: FAIL: 
>nsca service_limit from=172.26.192.37
...
># description: NSCA (Nagios Service Check Acceptor)
>service nsca
>{
>        disable = no
>        flags           = REUSE
>        socket_type     = stream
>        wait            = no
>        user            = nagios
>        group           = nagios
>        server          = /usr/local/nagios/bin/nsca
>        server_args     = -c /usr/local/nagios/var/nsca.cfg --inetd
>        log_on_failure  += USERID
>#       only_from       = 127.0.0.1,172.26.33.68
>        cps             = 500 30
>}

You also want to look at 'instances = ' in the /etc/xinetd.conf (your
default settings).

Looks like you are hitting the instances maximum, rather than the cps
(connections per second limit).

Check that your nsca calls are not actually exiting in a timely manner --
instances normally defaults to 60.  Maybe you're getting a LOT of nsca logs
coming in?  Maybe something is blocking?

Then, you can add 'instances = 200' (for example) to your nsca service
definition to increase the max number of concurrent instances of nsca.

We use 'instances = UNLIMITED' (OK, risky, I know) because of the huge
number of nsca alerts coming in.

Steve



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at 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