--- Marc Powell <[EMAIL PROTECTED]> wrote: Hello Marc,
> > > > -----Original Message----- > > From: [EMAIL PROTECTED] > [mailto:nagios-users- > > [EMAIL PROTECTED] On Behalf Of Sumit > malhotra > > Sent: Tuesday, July 18, 2006 12:26 PM > > To: [email protected] > > Subject: [Nagios-users] Nagios - Nsca - OCSP > command Timedout > > > > Hello, > > > > I am using Nagios in a distributed environment > where > > many systems report to a central nagios server via > > NSCA. > > > > Many a times the nsca command(ocsp and oshp > command) > > times out due to low response time from remote > nsca. > > > > As the results submiteed by remote client are not > > received, it causes an alert to be generated. > > (I am using nsca -server in inetd mode.) > > > > > > I have few questions: > > > > 1. Is it possible to set up NSCA -server so that > it > > doesn't time out ? What's the deterministic > parameter? > > is it RAM ? CPU? or NETWORK CHOKING. > > I'd check your inetd config. Are you allowing > sufficient connections and > rate limits for your environment? Here is the xinetd configurations service nsca { flags = REUSE socket_type = stream wait = no user = nagios group = nagios server = /usr/sbin/nsca server_args = -c /etc/nsca.cfg --inetd log_on_failure += USERID instances = 200 disable = no } Also, sometimes nsca goes in adefunct state. I have no clue why ? 3054 ? Rs 0:01 /usr/sbin/xinetd -pidfile /var/run/xinetd.pid -stayalive 21552 ? Zs 0:00 \_ [nsca] <defunct> 21553 ? Zs 0:00 \_ [nsca] <defunct> 21554 ? Zs 0:00 \_ [nsca] <defunct> 21555 ? Ss 0:00 \_ nsca -c /etc/nsca.cfg --inetd 21556 ? Ss 0:00 \_ nsca -c /etc/nsca.cfg --inetd nsca.cfg ------------- server_port=5667 server_address=x.x.x.x nsca_user=nagios nsca_group=nagios debug=0 command_file=/var/lib/nagios2/rw/nagios.cmd aggregate_writes=0 append_to_file=0 max_packet_age=30 password=xxxxxxxxx decryption_method=1 > > > In Normal scenarios I have 90% RAM as free > > Average System Load is 1.5 > > Network of 10MB is available. with only 100 odd > hosts > > to report to ( It's not getting choked either) > > > > 2. Is it possbile to retry sending in 15 seconds > if > > the ochp/ocsp command has timed out ? > > Yes, you could always modify your > submit_check_result script to take > that into account. Nagios doesn't have that > capability itself. The > proper fix however is to determine why the timeouts > are occurring. I'm > able to process 3648 passive checks via NSCA every 5 > minutes running > NSCA as a standalone daemon. That's why I believe > you may need to look > at your (x)inetd.conf. > > -- > Marc > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get > the chance to share your > opinions on IT & business topics through brief > surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Nagios-users mailing list > [email protected] > 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 > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Nagios-users mailing list [email protected] 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
