On Sun, January 3, 2016 8:29 pm, Adam Goryachev wrote:
On 03/01/16 12:50, J.C. Cleaver wrote:
Hmm. The only thing that jumps out at me is that the version jump
crosses
the "extcombo" divide... A newer xymonnet sending to an older xymond
might
be sending messages the older one doesn't understand. xymonproxy (4.3.x
at
least) does not recombine into extcombo in any situation, so it wouldn't
be causing it at that point.
Can you send xymonproxy a -USR1 signal to turn on verbosity? That should
indicate what kind of / whether it's getting messages from xymonnet as
expected.
Hi,
This sounds like it could be one (of the many) issues I'm having (but
haven't had time to look into for a while). Is there a simple method to
tell xymonnet to avoid sending "extcombo" messages?
Thanks,
Adam
Unfortunately, no. And with combo generation being pretty low level within
the code, so even setting MAXMSGSPERCOMBO to '1' will just result in an
extcombo-wrapped single message.
It probably should have been called out better within the 4.3.13(?)
Release Notes, but in a distributed infrastructure the central xymond
needs to be updated first.
Regards,
-jc