I use an filecontentsensor on an Windows 2008 networtshare to montior an mailserver. I got not everytime actial values. Whe I show to the file the content is different to the sensor. Update the sensor dos not change this. If I go to the mailserver an kill the SMB Session by "net session /Delete" all ist fine until any hours.. At 0:00 the mailserver renames the file and recreate the file.

is there an problem or an workaround?

Matthias


Article Comments

Hello,

this appears to be some odditiy in the SMB-Share/Session. Would there be an option to access the target file without going over the SMB-Share? Maybe if its a local folder on a Windows based PC, with a Remote Probe running on it?

best regards.


Feb, 2013 - Permalink

No, the target is not local. Why this happens? Ist the symptom related to the Host or to the client?


Feb, 2013 - Permalink

That's very hard to say. Would a scheduled task (in Windows) be possible, that copies the file to the PRTG Host every minute or every 5 minutes, so that the File-Content sensor can check it locally?


Feb, 2013 - Permalink

That´s hard to do, because I know why but our other admins not...

I do doc this workaround - Its, not fine, but it works...


Feb, 2013 - Permalink

But since one hour, the new sensor dos not update the values, but the filecontent has been changed.

Now i have the logfiles local on the probe and copy them by the mailserver every 5 minutes to the probe. Update the sensor dos nothing. Only when I change sensorsettings, then the value will be updated one time. (switch from regex to text or to regex)


Feb, 2013 - Permalink

None of the filecontentsensors has changed since they scan local files on the probe. I have crosschecked, the filecontent has changed.


Feb, 2013 - Permalink

I have checked.... The timestamp of the logfiles is everytime 00:00 because the will be recreated at 00:00. If I don´t copy the files and transfer them via c:>type file.log >server/share/file1.log all works fine because the hase an changedate every time. Is there an caching issue?


Feb, 2013 - Permalink

The sensor does not cache files. This has to be a cache then on Windows level.


Feb, 2013 - Permalink

Solved - for me - I have modified my linuxscript an add this two lines

printf("\n")
echo PAESSHEND

Since this modificatoins the sensor runs without any problems.

Matthias


Mar, 2013 - Permalink