Xymon Mailing List Archive search

client-local.cfg and xymon-4.3.15

2 messages in this thread

list Dominique Frise · Wed, 05 Feb 2014 16:51:31 +0100 ·
Hi,

We updated our xymon-server from version 4.3.11 to 4.3.15.
The client-local.cfg does not seem to be handled the way it was.

Example :

[linux]
log:/var/log/messages:10240
ignore MARK
trigger Error|error|ERROR

[monk]
log:/var/log/messages:102400
ignore mDNSPlatformSendUDP\sgot\serror\s22
ignore read_data
log:/var/log/logwatch:10240


Which mean that we want to overwrite default linux settings for "monk" 
client.

But there is the resulting content of logfetch.monk.cfg on the client :

[xymon at monk tmp]$ cat logfetch.monk.cfg
log:/var/log/messages:10240
ignore MARK
trigger Error|error|ERROR
log:/var/log/messages:102400
ignore mDNSPlatformSendUDP\sgot\serror\s22
ignore read_data
log:/var/log/logwatch:10240


The default settings are there too !?
Did we missed a patch/advice for this ?

Thanks,

Dominique
list Dominique Frise · Thu, 06 Feb 2014 10:30:13 +0100 ·
I don't agree.
The regexp support should not brake previous configuration.

BTW, the new man-page has not changed regarding the section name :

...
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 - 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  host-
        names.  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 config-
        uration.
...


Dominique

On 02/05/2014 06:22 PM, Galen Johnson wrote:
If I'm not mistaken, the fix to allow regex in client-local.cfg also
will append all matches as a single entity.  If it has several similar
entries, it will munge them together.  Check out the new
client-local.cfg man page.  You might be able to change monk entry to
[host=monk] and see if that returns what you expect.


On Wed, Feb 5, 2014 at 10:51 AM, Dominique Frise
quoted from Dominique Frise
<user-78ab6673b600@xymon.invalid <mailto:user-78ab6673b600@xymon.invalid>> wrote:

    Hi,

    We updated our xymon-server from version 4.3.11 to 4.3.15.
    The client-local.cfg does not seem to be handled the way it was.

    Example :

    [linux]
    log:/var/log/messages:10240
    ignore MARK
    trigger Error|error|ERROR

    [monk]
    log:/var/log/messages:102400
    ignore mDNSPlatformSendUDP\sgot\__serror\s22
    ignore read_data
    log:/var/log/logwatch:10240


    Which mean that we want to overwrite default linux settings for
    "monk" client.

    But there is the resulting content of logfetch.monk.cfg on the client :

    [xymon at monk tmp]$ cat logfetch.monk.cfg
    log:/var/log/messages:10240
    ignore MARK
    trigger Error|error|ERROR
    log:/var/log/messages:102400
    ignore mDNSPlatformSendUDP\sgot\__serror\s22
    ignore read_data
    log:/var/log/logwatch:10240


    The default settings are there too !?
    Did we missed a patch/advice for this ?

    Thanks,

    Dominique
    
    <