Nagios Support Forum

Hi , yeah, i looked at that and was not brave enough to say that it was not being initialized, i have a very low/no skill in C so did not want to point out something, that would surely have been pointed out in NSCAs long history. go figure. thanks for your post. that has cleared up a lot and I am ha...

I will definitely have a look at 2.1.0 over the weekend

leave this open and I will let you know what I find.

Philip

yes, both time zones match. also I have tried from a third host sending to the NSCA daemon and time differences are always the same.

the version is 2.9.2.

I have decided to use NRDP instead of NSCA so I do not necessarily need a resolution to this.

thanks for your response, I am looking at the nsca.c code now. yes it is a debug message, but NSCA drops the package, and the service will then become stale. everytime send_nsca sends to NSCA, it is the exact same time difference,11018287, so I am thinking it is something to do with the setting up o...

I have compiled NSCA with libmcrypt on omnios, an solaris/illumos variant. Whenever NSCA requests are received, NSCA responds with a very large number, such as "Time difference in packet: 11018287". This can be worked around with setting "max_package_age=0" but ideally I would li...