Xymon Mailing List Archive search

XymonD --merge-clientlocal issues

list Thomas Eckert
Tue, 16 Oct 2018 19:50:40 +0200
Message-Id: <user-a52094142217@xymon.invalid>

That's what works for me. I remember that the correct syntax, in particular with regexes, is slightly different across the config files.

On Oct 16, 2018 19:39, Timothy Williams wrote:
Yes, that's right about tasks.cfg. It had other start parameters, and have added the merge.

Do you think that it needs [host=server1] rather than just [server1]?

Tim


On Tue, Oct 16, 2018 at 1:30 PM Thomas Eckert <user-2a86d6cd6326@xymon.invalid> wrote:
Hi Tim,

for future readers: There is an error in the man page `xymond(8)`: `--merge-clientconfig` in `xymond(8)` is **wrong**. The option `--merge-clientlocal` documented in `client-local.cfg(5)` is correct.
You added this in `tasks.cfg` to the launch of `xymond`, right?

I have this running successfully in a Linux-environment with host-specific (`[host=%www.*]`) and class (`[linux]`)-sections and the sections merge fine.

Cheers
Thomas
On 16 Oct 2018, at 17:40, Timothy Williams <user-1a5482fb085e@xymon.invalid> wrote:

We have set up a new 4.3.28 xymon server, and will be migrating hosts to it in the next few weeks. On it I would like to start to use the --merge-clientlocal command. In testing, Windows powershell clients pick up either the individual host section OR the powershell section, it does not merge. Are there subtleties not in the man-pages that people have found to get it to work? (note that the xymond man-page states to use --merge-clientconfig, but that doesn't work either)

Could it be the section/host headings, or order? I have:

[server1]
file:somefile

[server2]
file:different file

[os=powershell] (also tried [class=powershell] and [powershell] alone)
xymonlogsend
clientversion:2.28:http://url

Thanks,
Tim Williams



Xymon@xymon.com