Backend mysql no longer available

After an upgrade of grafana some settings where no longer taken into account.
Solution on the end of this thread.

After i upgraded grafana to grafana8-8.0.2 and mysql to mariadb105-server-10.5.11, i find in my grafana.log file:
msg=“Connecting to DB” logger=sqlstore dbtype=sqlite3

Here i post my grafana.conf file:

[database]

You can configure the database connection by specifying type, host, name, user and password

as separate properties or as on string using the url properties.

Either “mysql”, “postgres” or “sqlite3”, it’s your choice

type = mysql
dbtype = mysql
host = 127.0.0.1
name =“grafana”
user =“grafana”
password =“grafana”

Can someone please explain what is going on ?

Isn’t a normal behavior not make a functional connection with the explicit specified database or bail out with an error , no ?

With an URL connection string i have a little slitly improvement.
Grafana makes connection with both the sqlite database and both mysql database.

msg=“Connecting to DB” logger=sqlstore dbtype=sqlite3
msg=“Starting DB migrations” logger=migrator
msg=“migrations completed” logger=migrator performed=0 skipped=329 duration=1.847235ms
msg=“Starting plugin search” logger=plugins
msg=“Live Push Gateway initialization” logger=live.push_http
msg=“HTTP Server Listen” logger=http.server address=[::]:3000 protocol=http subUrl= socket=
msg=“Request Completed” logger=context userId=1 orgId=1 uname=admin method=GET path=/api/live/ws status=0 remote_addr=127.0.0.1 time_ms=5 size=0 referer=
msg=“Initialized channel handler” logger=live channel=grafana/dashboard/uid/jBB8LOm7z address=grafana/dashboard/uid/jBB8LOm7z

Zero migrations where performed and not one table of grafana can be found in the mysql database.

Which choices rest me?

After editing grafana.ini , and not grafana.conf the problem was completely fixed.
Great !