nsca old server with new nsca client

[Albert Shih]

 Le 07/02/2012 à 13:34:21-0800, Mike Lindsey a écrit
> On 2/7/12 12:10 PM, Albert Shih wrote:
> > Hi all,
> > Is there any way I can use a new (2.9.1) client nsca (send_nsca) with old
> > server (2.7.x) ?
> 
> 2.9.1 shouldn't include any backwards incompatible code.  That said, the 

I don't known....All I known is the new version of client don't work (for
me) when the server is the old one. 

I've two nagios server, on one I run the new version of nsca-server and
everything working. On the second from same client with old sever I was
unable to make passive service working. 

> normal cross-version issues have been with newer server, and older 
> client so I'm not sure "old server" has been sufficiently tested with 
> "new client"...
> 
> Is there a particular reason why you can't upgrade your server side?

Well...let's «it's complicated» ;-)

In fact I solve my problem by recompiling on the client the 2.7.2 version
of nsca client. But well...the problem still here...

I can run some test if you like.

The client running FreeBSD 8.2 and the server running Linux Debian. 

Regards.

JAS
-- 
Albert SHIH
DIO batiment 15
Observatoire de Paris
5 Place Jules Janssen
92195 Meudon Cedex
Téléphone : 01 45 07 76 26/06 86 69 95 71
xmpp: jas at obspm.fr
Heure local/Local time:
mar 7 fév 2012 22:45:22 CET

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
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