NSCA strange behaviour

[Cedric Jeanneret]

Hello again

I've made some other tests:

- I changed encryption algo on server01 and client22, restarted nagios&nsca on server01, restarted nagios on client22.
- let it run like that, checking logs for something. As I thought, nsca begins to output lot of error regarding version client and/or encryption method and/or password. Nice.
- I put back the right encryption method on server01 but NOT on client22. I should have seen a pattern like "Received invalid packet".... but nothing.

I forced some status update from client22: 
for i in $(seq 1000); do 
  echo -n 'host  '; 
  /usr/local/bin/submit_ochp $(hostname -f) "UP" "Host is up"; 
  sleep 2; 
done

Nothing. TCPDump shows me traffic, in and out for both hosts...

Last test, I stopped nagios&nsca on server01, removed nsca.dump objects.cache retention.dat files, and start again nsca&nagios....

If we let the fact that all my hosts are "pending", my client22 doesn't push any status... nothing in nsca logs.

Any other idea ? It's like the nsca daemon ignore (without any output) client22 queries. and client22 doesn't know about it.

Best regards,

C.

-- 
Cédric Jeanneret                 |  System Administrator
021 619 10 32                    |  Camptocamp SA
cedric.jeanneret at camptocamp.com  |  PSE-A / EPFL
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <https://www.monitoring-lists.org/archive/users/attachments/20091209/7e6234be/attachment.sig>
-------------- next part --------------
------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
-------------- next part --------------
_______________________________________________
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