I have Dell EMC Networker which is generating logs to /nsr/logs folder with raw daemon.raw file and its daemon.txt text file version.
Those files are being rotated periodically to files with the date and time of rotation in its name eg. daemon_180425_085159.raw and daemon_180425_085159.txt.
The deamon.raw file and its corresponding daemon.txt stay with current log, while copied file has previous logs.
Aditionally while files are rotated there is a message in the log file informing of change of the log file, eg "Copy of /nsr/log/daemon.raw to /nsr/logs/daemon_180425_085159.raw was successful, /nst/logs/daemon.raw has been truncated" - the numbers within underscore inform about the date and time of rotation (in this case is 25.04.2018 and 08:51 and 59 sec).
I have set up monitoring of text files with with vRLI using parameter include file set to: daemon.txt; daemon*.txt which allows of monitoring daemon.txt while it is being rotated with copy-truncate mechnism.
Now there is a following problem that I am observing:
Anybody can decipher the cause of the problem from what I have written above? Any ideas?
Thanks
Pawel
The problem was finaly solved after upgrading to the latest Log Insight version 4.6.
What version of vRLI is this and what is your agent version?
Of course, the basic information:-) Sorry for that.
Agent 4.3.0.5052904 and Server 4.5.1.
Any reason your agent isn't up-to-date with your vRLI server version?
Not any serious reason. Just have upgraded server last week, and I am bit cautious since we are monitoring quite a big MS Exchange environment here so just need to approach upgrade carefully. And in the meantime I wanted to prepare for Networker monitoring.
I'd recommend getting that agent upgraded to match the version of your vRLI server instance first. It's a super simple upgrade with extremely low risk, so it shouldn't be an issue.
I will update then and we wll see:-)
Just after the last post I have upgraded LI Agent to the same version as the server.
From then I have not touch anything and just today checked the status:
The appliance is SLES 12SP1 which is supported Linux distribution.
The problem was finaly solved after upgrading to the latest Log Insight version 4.6.