On Oct 17, 2018, at 14:46, Timothy Williams <user-1a5482fb085e@xymon.invalid> wrote:
I meant the machine/OS, as some settings are kept in memory and I didn't know (I'm a Windows guy) if restarting the Xymon application by xymonlaunch -restart would have refreshed the memory settings.
However, the Linux manager looked at it and found the issue as missing a slash / at the end of the previous parameter to wrap the line. It never saw the new parameter.
It's now working as designed.
On Tue, Oct 16, 2018 at 11:49 PM Galen Johnson <user-fc632e705d24@xymon.invalid <mailto:user-fc632e705d24@xymon.invalid>> wrote:
By "whole server" I assume you just mean restarting the xymon server (app, not machine)? I usually restart the server but that's because I'm impatient and want immediate gratification for those types of changes. As far as I recall, that shouldn't be required. It also shouldn't hurt to do so since it restarts fairly quickly (at least for my small environment).
=G=
On Tue, Oct 16, 2018 at 3:29 PM Timothy Williams <user-1a5482fb085e@xymon.invalid <mailto:user-1a5482fb085e@xymon.invalid>> wrote:
The [name] section lines are working OK; I am not trying to use regex, just specific hosts to merge with [powershell] defaults.
We are testing by restarting the xymon services, any off chance it needs a whole server reboot?
On Tue, Oct 16, 2018 at 3:21 PM Galen Johnson <user-fc632e705d24@xymon.invalid <mailto:user-fc632e705d24@xymon.invalid>> wrote:
From the client-local.cfg man page:
FILE FORMAT
The file is divided into sections, delimited by "[name]" lines. A section name can be either an operating system identifier - linux, solaris, hp-ux, aix, freebsd, openbsd, netbsd, darwin - a class, or a hostname. When deciding which section to send to a client, Xymon will first look for a section named after the hostname of the client; if such a section does not exist, it will look for a section named by the operating system of the client. So you can configure special configurations for individual hosts, and have a default configuration for all other hosts of a certain type.
It will often be practical to use regular expressions for hostnames. To do this you must use
[host=<expression>]
where <expression> is a Perl-compatible regular expression. The same kind of matching can be done on operating system or host class, using
[os=<expresssion>]
[class=<expression>]
Apart from the section delimiter, the file format is free-form, or rather it is defined by the tools that make use of the configuration.
I just went through this recently so it was fresh in my mind :-).
=G=
On Tue, Oct 16, 2018 at 1:50 PM Thomas Eckert <user-2a86d6cd6326@xymon.invalid <mailto:user-2a86d6cd6326@xymon.invalid>> wrote:
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 <user-1a5482fb085e@xymon.invalid <mailto:user-1a5482fb085e@xymon.invalid>> 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 <mailto: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 <mailto: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 <http://url/>;
Thanks,
Tim Williams
Xymon at xymon.com <
Xymon at xymon.com <