Hi,

I recently added the syslog sensor to my PRTG install. I have one device sending Security Policy logs to it now. The problem is that the Probe Health keeps disconnecting. I think it's anytime i try and search through the syslog data that it causes the probe to fail. Any ideas on how i can troubleshoot what the problem is?

thanks

Article Comments

Does it actually disconnect once you open the message tab? Or just when you search the messages for certain values? Do the messages show up in the tab at all? Is the server running on a virtual machine?

Kind regards,
Stephan Linke, Tech Support Team


Dec, 2017 - Permalink

I'm able to search and get back results, but shortly after it disconnects. The server is running on a virtual machine and only started having issues when i added the syslog sensor. I'm running 827 Sensors but will be cutting that number down. My VM has 8GB of RAM and 4 cpus.

Also, I constantly get warning errors on the probe and then it disconnects. I'm guessing maybe there's some kind or threshold that I'm hitting but i have no idea what that threshold is?

thanks


Dec, 2017 - Permalink

Not really - could you send us a support bundle via Setup | Contact Support after crashing the probe via the sensor click? Can't put my finger on it yet, may be something with the syslog database...

Kind regards,
Stephan Linke, Tech Support Team


Dec, 2017 - Permalink

Hi,

I thought I'd update the thread just in case anybody else is having the same issue. . If I filter for data that exists then the memory issues doesn't happen. If I enter something in any of the fields that doesn't exist then the memory issue happens.

I have a ticket open so I"ll update this thread when i get it fixed.


Dec, 2017 - Permalink