That's great Rafael! Yes, it works. Thank you very much!! Raffaello
Il 20/07/2010 16.23, Rafael Carneiro ha scritto: > Hi Raffaello, > What I have in my opsview.conf and I know it works cause I have a few > service checks that exceed the default 10 secs is: > $overrides = <<'EOF'; > nagios_service_check_timeout=15 > EOF > > That was the only place where I changed it, and it should be applied to all > your monitoring servers (master & slaves) after your next reload. > > Rafael > > > On Tue, Jul 20, 2010 at 3:41 AM, Raffaello Poltronieri - Eutelia SpA < > [email protected]> wrote: > > >> I can't install an agent on ESX servers: the admin of VMWare platform >> wants that server free of any non-vmware software... That's why I >> choosed a simple SNMP query. >> But, anyway, thank you for your advice. My only hope is to try to extend >> timeout >> >> Il 20/07/2010 9.32, [email protected] ha scritto: >> >>> OK >>> >>> So snmp check when run from cli slave is OK. >>> >>> Then either the check on the slave should return the state to the master >>> using NSCA (send_nsca) or the master should initiate the check on the >>> slave using nrpe. I think the last one is simpler to implement. Adapt >>> nrpe.cfg, reload opsview-agent and run the check from the master >>> >>> hth >>> paul >>> >>> >>> >>>> Sorry Paul, I didn't explain. >>>> I receive OK from slave, I can't reach that ESXs from master: master is >>>> in DMZ, slave is in a strictly protected subnet. But it should be in >>>> this way, since master receive check info from slave by NSCA, am I >>>> >> wrong? >> >>>> Il 20/07/2010 9.12, [email protected] ha scritto: >>>> >>>> >>>>> So you have a master and a slave? >>>>> when it is ok, do you mean from slave and master? or just from master? >>>>> >>>>> Thanks >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>> Hi Paul, >>>>>> if I execute the script in CLI it responds with an OK (if ESX is OK, >>>>>> >> of >> >>>>>> course) , usually after 15/20 secs... >>>>>> Thanks >>>>>> R >>>>>> >>>>>> Il 20/07/2010 8.58, [email protected] ha scritto: >>>>>> >>>>>> >>>>>> >>>>>>> Well, that implies the python check does not wait long enough, >>>>>>> therefore >>>>>>> not returning a proper exit code? >>>>>>> >>>>>>> hth >>>>>>> paul >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> Hi Henry, >>>>>>>> well.... it still doesn't work. >>>>>>>> I've a master and a distributed, I modified both nagios.cfg >>>>>>>> service_check_timeout=60 >>>>>>>> >>>>>>>> and on master, added to opsview.conf the line >>>>>>>> $service_check_timeout=60; >>>>>>>> >>>>>>>> (60 is enough, usually the check needs no more than 20, 25 sec) >>>>>>>> reloaded the config... nothing, still (Service Check Timed Out) as >>>>>>>> output. >>>>>>>> >>>>>>>> Have you any other idea for my problem? >>>>>>>> Thank you very much for support! >>>>>>>> >>>>>>>> Il 19/07/2010 17.49, Henry ha scritto: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> Then you're hitting the service_check_timeout of Nagios. I think i >>>>>>>>> remember you're able to override it in opsvie.conf, try adding a >>>>>>>>> line >>>>>>>>> like: >>>>>>>>> service_check_timeout=120 >>>>>>>>> To get a 120 second timeout. And reload your Opsview config. >>>>>>>>> >>>>>>>>> You should also see the timeout pararmter it in the generated >>>>>>>>> nagios.cfg >>>>>>>>> (somwhere at nagios/configs/Master Monitoring Server/nagios.cfg). >>>>>>>>> >>>>>>>>> >>>>>>>>> On Mo, 2010-07-19 at 17:28 +0200, Raffaello Poltronieri - Eutelia >>>>>>>>> SpA >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> My check queries in SNMP protocol: no nrpe. To be honest, I wrote >>>>>>>>>> "my", but just to specify that's a custom check: it is pulled from >>>>>>>>>> a >>>>>>>>>> site: >>>>>>>>>> >>>>>>>>>> >> http://www.matthewjwhite.co.uk/blog/2010/02/09/monitoring-esxi-server-health-using-nagiosopsview/ >> >>>>>>>>>> and it's written in pyton. >>>>>>>>>> It works great, but it needs more than 10 seconds. And, I don't >>>>>>>>>> >> see >> >>>>>>>>>> any option to extend time of timeout... >>>>>>>>>> Thank you for support Henry >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Il 19/07/2010 16.53, Henry ha scritto: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> Then I guess you use NRPE (check_nrpe) for your check. check_nrpe >>>>>>>>>>> features a '-t <timeout>' switch, default is 10 seconds. So you >>>>>>>>>>> have >>>>>>>>>>> to >>>>>>>>>>> edit the service check configuration to include the -t <timeout> >>>>>>>>>>> argument. >>>>>>>>>>> >>>>>>>>>>> On Mo, 2010-07-19 at 16:30 +0200, Raffaello Poltronieri - Eutelia >>>>>>>>>>> SpA >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> No Henry, >>>>>>>>>>>> I'd like Opsview to be "more patient": my check needs more time >>>>>>>>>>>> to >>>>>>>>>>>> perorm a result: as is now, I only receive a "check time out" >>>>>>>>>>>> with >>>>>>>>>>>> a >>>>>>>>>>>> critical sttus in Opsview >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Il 19/07/2010 16.05, Henry ha scritto: >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> You want to speed up your check? >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Opsview-users mailing list >>>>>>>>>>>> [email protected] >>>>>>>>>>>> http://lists.opsview.org/lists/listinfo/opsview-users >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Opsview-users mailing list >>>>>>>>>>> [email protected] >>>>>>>>>>> http://lists.opsview.org/lists/listinfo/opsview-users >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Opsview-users mailing list >>>>>>>>>> [email protected] >>>>>>>>>> http://lists.opsview.org/lists/listinfo/opsview-users >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Opsview-users mailing list >>>>>>>>> [email protected] >>>>>>>>> http://lists.opsview.org/lists/listinfo/opsview-users >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Opsview-users mailing list >>>>>>>> [email protected] >>>>>>>> http://lists.opsview.org/lists/listinfo/opsview-users >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> _______________________________________________ >>>>>>> Opsview-users mailing list >>>>>>> [email protected] >>>>>>> http://lists.opsview.org/lists/listinfo/opsview-users >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> _______________________________________________ >>>>>> Opsview-users mailing list >>>>>> [email protected] >>>>>> http://lists.opsview.org/lists/listinfo/opsview-users >>>>>> >>>>>> >>>>>> >>>>>> >>>>> _______________________________________________ >>>>> Opsview-users mailing list >>>>> [email protected] >>>>> http://lists.opsview.org/lists/listinfo/opsview-users >>>>> >>>>> >>>>> >>>>> >>>> _______________________________________________ >>>> Opsview-users mailing list >>>> [email protected] >>>> http://lists.opsview.org/lists/listinfo/opsview-users >>>> >>>> >>>> >>> _______________________________________________ >>> Opsview-users mailing list >>> [email protected] >>> http://lists.opsview.org/lists/listinfo/opsview-users >>> >>> >>> >> _______________________________________________ >> Opsview-users mailing list >> [email protected] >> http://lists.opsview.org/lists/listinfo/opsview-users >> >> > > > > > > _______________________________________________ > Opsview-users mailing list > [email protected] > http://lists.opsview.org/lists/listinfo/opsview-users >
_______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/lists/listinfo/opsview-users
