How to setup msgs and file column ? 🔗 link

Hi,

I am looking for some help due to a problem with the msgs and file column.
For some reason I do not get any entry in the msgs or file column. Mainly having no msgs is really a problem for me.

On the client (RH Linux 5, XYMON client 4.2.2) in localclient.cfg I have:

                                :
DEFAULT
                                :
                                :
        FILE /var/log/messages SIZE>0 MTIME<600 yellow

        LOG /var/log/messages WARNING COLOR=yellow
        LOG /var/log/messages ERROR COLOR=red
                                :
                                :


On the server (XYMON version 4.3.4, running on Solaris 10) in client_local.cfg I have:
  :
  :
[linux]
log:/var/log/messages:10240
ignore MARK
  :
  :
[servername]
log:/var/log/messages:10240
trigger WARNING|ERROR
  :
  :

I checked that the client has access rights to read the /var/log/messages file.

On the Webpage I get only "The client did not report any logfile data"

Is there anything I miss ? Or do msgs work only in the centralized mode ?

Thanks for any help.

                Thomas

On Wed, Oct 12, 2011 at 12:17 AM,  <user-acae49b2b4e6@xymon.invalid> wrote:

Or do msgs work only in the centralized mode ?

By default, msgs only works in centralized mode, and you define the
parameters in client-local.cfg on the server (as you have done).  For
non-centralized mode, you must add "--local" into clientlaunch.cfg
after "xymonclient.sh".

Are you unable to use centralized mode for some reason?  I can't tell
if you're trying non-centralized mode because centralized mode is not
working, or because of some other reason.

Assuming you'd want to get centralized mode to work, have a look for
the logfetch tempfile in $XYMONTMP (which is /tmp for me).  The file
will be called "logfetch.name-of-server.cfg".  Check that the content
looks OK (same as the matching [servername] stanza from
client-local.cfg), and check that the timestamp is within 10 minutes.
[There's also a logfetch.name-of-server.status file that might contain
clues.  Not sure of the format, so dunno how useful.]

If the logfetch tempfile is OK, try running logfetch against it and
see what it shows.  Something like this:

  sudo -u xymon /usr/lib/xymon/client/bin/logfetch
/tmp/logfetch.`uname -n`.cfg /tmp/test.status

It should show output for each entry in the .cfg file.

Cheers
Jeremy

Hi Jeremy,

sorry for my late reply. you really helped me a lot.
 
I made some tests in the mean time and well, I modified some clients for 
the centralized mode. 
In fact all client installations that I have were configured/compiled with 
local mode. 
So, I took out the "--local" in the clientlaunch.cfg file, restarted the 
client,  and configured the rest as you said in analysis.cfg on the 
server.

Now I get the message files (at least those that were readable, but that 
is another problem) on the WebPage.

Is taking out the "--local" enough in order to switch clients to 
centralized mode ?

The problem I have now is that in analysis.cfg  I have configured PROC and 
PORT, but the server column for these servers keep saying "No checks 
defined".

Maybe you have also an idea for that.

Thomas F. Weber

From:   Jeremy Laidman <user-71895fb2e44c@xymon.invalid>
To:     user-acae49b2b4e6@xymon.invalid
Cc:     Xymon mailinglist <xymon at xymon.com>
Date:   10/14/2011 01:27
Subject:        Re: [Xymon] How to setup msgs and file column ?


On Wed, Oct 12, 2011 at 12:17 AM,  <user-acae49b2b4e6@xymon.invalid> wrote:

By default, msgs only works in centralized mode, and you define the
parameters in client-local.cfg on the server (as you have done).  For
non-centralized mode, you must add "--local" into clientlaunch.cfg
after "xymonclient.sh".

Are you unable to use centralized mode for some reason?  I can't tell
if you're trying non-centralized mode because centralized mode is not
working, or because of some other reason.

Assuming you'd want to get centralized mode to work, have a look for
the logfetch tempfile in $XYMONTMP (which is /tmp for me).  The file
will be called "logfetch.name-of-server.cfg".  Check that the content
looks OK (same as the matching [servername] stanza from
client-local.cfg), and check that the timestamp is within 10 minutes.
[There's also a logfetch.name-of-server.status file that might contain
clues.  Not sure of the format, so dunno how useful.]

If the logfetch tempfile is OK, try running logfetch against it and
see what it shows.  Something like this:

  sudo -u xymon /usr/lib/xymon/client/bin/logfetch
/tmp/logfetch.`uname -n`.cfg /tmp/test.status

It should show output for each entry in the .cfg file.

Cheers
Jeremy

DISCLAIMER: 
This e-mail contains proprietary information some or all of which may be legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the author by replying to this e-mail. If you are not the intended recipient you must not use, disclose, distribute, copy, print, or rely on this e-mail.

On Tue, Oct 18, 2011 at 11:32 PM,  <user-acae49b2b4e6@xymon.invalid> wrote:

I think so, but not sure.  The server needs to be running
"xymond_client" to process the data, so check for this in tasks.cfg
(in the [clientdata] section).

This is often caused by invalid PORT and PROC definitions in
analysis.cfg.  I would double-check these.  Not sure where parse
errors will show up, but I'm guessing it will be in clientdata.log.

Cheers
Jeremy