Hi Tim
On Thu, 23 Jun 2022 at 02:24, POLYAK, TIM P <user-8af0a9b88a73@xymon.invalid> wrote:
I am trying to monitor non-standard logfile with server client-local.cfg
and failing.
Can you explain how it's non-standard? Are you trying to monitor the
contents or the attributes of the file? Would a "log:/var/adm/6800.log"
entry be more suitable for a logfile?
Here is what I tried so far in the client-local.cfg file
[host=hostname]
file:/var/adm/6800.log
and
[hostname]
file:/var/adm/6800.log
The correct format is the latter.
Firstly, note that it can take something like 10 minutes for log/file
monitoring to start reporting due to delays in propagating the config to
the clients, and then for the clients to report back again based on the
config.
What I would do is look in the $XYMONTMP directory on the client (defined
in xymonclient.cfg, often /tmp, /var/tmp or /dev/shm) for the temporary
files created by the client. They will be called logfetch.<hostname>.cfg
and logfetch.<hostname>.status.
The cfg file is essentially just the [hostname] section from the
client-local.cfg, retrieved when the client last reported to the server.
The status file has a line for every "file:" entry in the client-local.cfg
file, and is used to track the logfile position on each run. If you don't
have any "file:" entries in your client-local.cfg file for a server, it
might not have a status file.
So, first see if the cfg file is present. If not, your update to
client-local.cfg might not have been detected by the xymond process on the
Xymon server. Usually it picks this up by itself, but if not, you could
restart xymond and see if that helps (again, wait 10 minutes to see
progress). If the cfg file is present, see if its contents make sense (that
is, match what's in the client-local.cfg file on the server).
J