I am seeing the following log entries after receiving the "Overload Protection is Active Click for details" message. I read the thread at https://https://helpdesk.paessler.com/en/support/solutions/articles/76000041606. The prtgadmin account is valid and I can login with the password. How do I verify a library is owned by a user? 

2015-04-20 13:47:02 127.0.0.1 "user100-prtgadmin" 127.0.0.1 8085 GET /api/table.csv id=0&count=1000&noraw=1&content=sensorxref&columns=objid&filter_basetype=sensor&filter_priority=3&login=prtgadmin&passhash=*** 200 "Mozilla/3.0 (compatible; Indy Library)"
2015-04-20 13:47:10 127.0.0.1 "user100-prtgadmin" 127.0.0.1 8085 GET /api/table.csv id=0&count=1000&noraw=1&content=sensorxref&columns=objid&filter_basetype=sensor&filter_priority=2&login=prtgadmin&passhash=*** 200 "Mozilla/3.0 (compatible; Indy Library)"
2015-04-20 13:47:19 127.0.0.1 "user100-prtgadmin" 127.0.0.1 8085 GET /api/table.csv id=0&count=1000&noraw=1&content=sensorxref&columns=objid&filter_basetype=sensor&filter_priority=1&login=prtgadmin&passhash=*** 200 "Mozilla/3.0 (compatible; Indy Library)"
2015-04-20 13:47:24 127.0.0.1 "anonymous-prtgadmin-login_failed_and_delayed_120_seconds" 127.0.0.1 80 POST /api/getstatus.htm login=prtgadmin&password=***&id=0 200 "Mozilla/5.0 (compatible; PRTG Network Monitor Enterprise Console; Windows)"

Article Comments

Hello,

thank you for your KB-Post. It seem the Enterprise Console (or its Tray Tool) on the PRTG Server host machine, is trying to connect with wrong credentials. Please re-enter the correct Credentials into the connection settings for the Enterprise Console on the PRTG Host.
The failed logins should then stop.

best regards.


Apr, 2015 - Permalink

That resolved the issue. How can I tell it was the Enterprise Console from the logs?


Apr, 2015 - Permalink

It was part of the log entry: "...PRTG Network Monitor Enterprise Console; Windows)""


Apr, 2015 - Permalink

I am having a very similar problem. I was getting failed logins from both my desktop and the PRTG server itself (although the server is identifying itself by actual IP Address, instead of the loopback address). This is causing the overload protection to be active. I solved the problem on my desktop by uninstalling the enterprise console. That is the only thing that worked. However, it does not allow me to do that on the server.

I have tried everything to stop these failed logins. I have used the prtgadmin account and my own account and my admin account in the Enterprise console. They all connect but I still get the failed logins.

I also closed Enterprise Admin and still get it. I unchecked the server and I still get it.

Any help would be appreciated.


Jun, 2015 - Permalink

Do you have any libraries except for the default ones that were created with a user that doesn't exist anymore?


Jun, 2015 - Permalink