When using File Content Sensor with regular exception, the sensor results to StackOverflow and PRTGProbe.exe goes down in Services and has to be strated again. An example for the regexp is: ^(?=^.*ERROR)((?!I want to exclude this).)*$
It looks like the problem does not occur with small log files. Only after a specific size. My questions are:
Is the issue known the paessler ? Is there another way to search for a pattern in log-file and exclude some lines with another pattern(s) ?
Article Comments
For example a log file with a size of 186.565 bytes causes the stack overflow.
With the regexp: ^(?=^.*ERROR)*$ the sensor works properly.
Nov, 2017 - Permalink
Works fine for me with a 1MB file containing matching patterns with your original string.
What PRTG version are you actually using?
Kind regards,
Stephan Linke, Tech Support Team
Nov, 2017 - Permalink
Then it may have to do with the actual content of the file. Could you post that here? I won't publish it.
Kind regards,
Stephan Linke, Tech Support Team
Nov, 2017 - Permalink
What specific size are we talking about here? Do other, more simpler patterns actually work properly at that size?
Kind regards,
Stephan Linke, Tech Support Team
Nov, 2017 - Permalink