Andreas, I've just finished the tests :-) The standard configuration doesn't work for me as i told in previous message. So i've tried the send_nsca you provide with the module and it works fine. The only drawback i see (correct me if i'm wrong) is that the module doesn't send performance data for services (so i can't use it for now). What is really cool in my case is that the latency has gone (0.219 sec for now compare to the 5000 sec before). So the problem is solved.
So, for the moment, i'm using the OCP_daemon to handle the oc[hs]p commands (and it seems to just work fine) but i would rather use your module in the long term. The approach is by far more elegant than using performance configuration for the commands. So if you want to go ahead and developp it further, i would gladly help you release a production ready version of it. pnsca would be a must have in large environments like mine. Thanks for you kind help and thanks to Hendrik for pointing me in the right direction. Olivier Jan Andreas Ericsson <[EMAIL PROTECTED]> a écrit : > Olivier, did you get anywhere with this, or haven't you had time to > look at it yet? > > If you want, I could log into the system and see if I can find out > what's wrong. If that's not an option, contact me off-list and I'll > arrange for some faster-feedback medium through which I can better > help you resolve your problems. > > I'm rather anxious to see how the broker module works in such a > large environment :-) > > Andreas Ericsson wrote: >> Olivier JAN wrote: >>> I'm surely missing a point because the master server doesn't >>> receive checks results. i put this line in nagios.cfg without >>> quote. >>> >>> broker_module=/usr/local/nagios/lib/pnsca.so >>> /usr/local/nagios/libexec/send_nsca -H 10.10.10.10 -c >>> /usr/local/nagios/etc/send_nsca.cfg >>> >>> I also tried with quotes without success. Any idea ? >>> >> >> "grep pnsca nagios.log" should produce: >> [1222364357] Event broker module '/usr/local/nagios/lib/pnsca.so' >> initialized successfully. >> >> If you don't have that, decipher the error messages in >> the log until you get it. >> >> If you're already getting that, but it doesn't work >> anyway, you can try using the shipped send_nsca script >> instead of the one on your system. If you change the >> third line of it to say "cat > /tmp/pnsca.out", all the >> host and service check results the module receives from >> Nagios will be dumped to /tmp/pnsca.out (worst case >> scenario, you could actually do >> tail -f /tmp/pnsca.out | send_nsca -f send_nsca.cfg >> and get pretty much the same benefit, but Nagios will >> crash when /tmp/pnsca.out gets larger than 4GB). >> >> It's also a rather good idea to make sure that send_nsca >> is always running (use Nagios and check_procs for this). >> With pnsca in place, you should always have exactly one >> send_nsca process running on your system. If that one dies, >> you need to restart Nagios (until I've got time to add some >> sort of clever process control in the module, anyways). If >> you have too many, something else is going wrong, so you'll >> need to check that up manually. >> >> Thanks for testing, and good luck :) >> > > > -- > Andreas Ericsson [EMAIL PROTECTED] > OP5 AB www.op5.se > Tel: +46 8-230225 Fax: +46 8-230231 ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ 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
