MySQL Issue After Update

So we upgraded last night to the latest version with APT, and now all of our MySQL connections are failing. The error log shows an “login invalid for root@[IP Address]” message, but connecting to the same MySQL server using the command line client and credentials works. Was something changed in the new release that could be breaking this? I did notice I had to re-enter the passwords for our data sources.

Are you intentionally connecting as root? Generally that is a bad idea.

So we upgraded last night to the latest version

Of what?

with APT, and now all of our MySQL connections are failing.

Which versions of MySQL did/do you have?

Which versions of Grafana did/do you have?

The error log shows an “login invalid for root@[IP Address]” message,

You’re telling Grafane to connect to MySQL as root!?

I’d recommend creating a Grafana user in MySQL instead…

but connecting to the same MySQL server using the command line client and
credentials works.

Do you actually need a password to connect to MySQL as root at all?

Was something changed in the new release that could be breaking this?

Tell us which versions you upgraded from and to and someone might be able to
answer that.

I did notice I had to re-enter the passwords for our data sources.

“Sources” plural? How many do you have; are they all MySQL?

Antony.

Originally we were, but even after changing the login, we still had the same issue (this is all inside our network and does not go out to the internet).

I am referring to a Grafana upgrade to version v6.4.4 (092e514) - unfortunately, I don’t have information on the old version number (before upgrade). MySQL is Percona Cluster 5.6.44-86.0-56, but Grafana is connecting via ProxySQL version 5.5.30.

Attempting to use an alternate user does not affect this issue. Root login with our setup does require a password (which I re-entered in initial testing, but still get the same error).

We have three separate MySQL Datasources set up in Grafana - they connect to different databases on the same server setup.

My approach in this situation would be to install tshark or some similar
packet analyser and look at the traffic going to port 3306 on the MySQL server
(or, in this case, the proxy) to see whether Grafana really is presenting the
credentials and asking for the database which you think it is.

Antony.