Assuming you're using 4.3.12 here, the --unknownclientsok option to xymond_client should allow it through. If there's another mis-parse, hopefully it would show up in --debug mode :/ (or when given a -USR2 signal)
HTH,
-jc
Sent from my iPad
On Aug 29, 2013, at 5:33 PM, Ralph Mitchell <user-00a5e44c48c0@xymon.invalid> wrote:
I think xymon wants to see a matching section in xymond/xymond_client.c. There's a big switch statement down at the bottom of that file, selecting between the various client functions in xymond/client/*.c. Those files are included into xymond_client.c right above main(). If it hits the end of the switch without matching an OS, it says:
errprintf("No client backend for OS '%s' sent by %s\n", clientos, sender);
That message is probably showing up in the log somewhere.
Ralph Mitchell
On Thu, Aug 29, 2013 at 8:07 PM, Jeremy Laidman <user-71895fb2e44c@xymon.invalid> wrote:On Aug 30, 2013 8:54 AM, "Kevin King" <user-4c6c31ddcab2@xymon.invalid> wrote:
Jeremy, I was using your example of hostname.eagle eagle, that was the problem. I changed it to sunos and it posted fine.
Maybe Xymon just wants to see a matching section in client-local.cfg.
J