• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved [Warning] Access denied for user 'monitoring'@'localhost' (using password: YES)

ic3_2k

New Pleskian
Server operating system version
Debian GNU/Linux 10 (buster)
Plesk version and microupdate number
18.0.57 #5
Hello,

I have tons of registers with this user 'monitoring' trying to log onto the mysql...

How can I check where this logging attempts come from? I mean obviously from localhost, as the register itself says, but from what program, cron or whaeteber process or web is doing this...

And as far as I can see, all the monitoring stuff regarding MySQL is in place, I'm using local monitoring.

Thank you all
 
Hi,

Have you tried 360 Monitoring on your server? Do you have agent360 running on you server (`ps ax | grep agent360 | grep -v grep`)? Also you can check agent360 configuration file ("/etc/agent360.ini") for a section about database. If it is agent360 and you don't want to use it, see Uninstalling 360 Monitoring.
 
Back
Top