Dashboard issues after updating to 3.12.0

A few days ago I updated Matomo through the web interface.
Everything seemed fine no issues updating, however, after going back to the dashboard the widgets weren’t loading.

Now the dashbaord looks like this. Sometimes certain widgets load i.e Visits in Real-time and Visits Log

EDIT: I just noticed new entires in the php error_log file. Not sure if the errors are related.

[06-Nov-2019 11:37:12 UTC] Error in Matomo: SQLSTATE[08004] [1040] Too many connections
[06-Nov-2019 11:37:12 UTC] Error in Matomo: SQLSTATE[08004] [1040] Too many connections
[06-Nov-2019 11:42:12 UTC] Error in Matomo: SQLSTATE[HY000] [2002] Can't connect to MySQL server on '127.0.0.1' (115)
[06-Nov-2019 11:42:13 UTC] Error in Matomo: SQLSTATE[HY000] [2002] Can't connect to MySQL server on '127.0.0.1' (115)
[06-Nov-2019 11:47:12 UTC] Error in Matomo: SQLSTATE[HY000] [2002] Can't connect to MySQL server on '127.0.0.1' (115)
[06-Nov-2019 11:47:13 UTC] Error in Matomo: SQLSTATE[HY000] [2002] Can't connect to MySQL server on '127.0.0.1' (115)
[06-Nov-2019 11:52:12 UTC] Error in Matomo: SQLSTATE[HY000] [2002] Can't connect to MySQL server on '127.0.0.1' (115)
[06-Nov-2019 11:52:13 UTC] Error in Matomo: SQLSTATE[HY000] [2002] Can't connect to MySQL server on '127.0.0.1' (115)
[06-Nov-2019 12:22:14 UTC] Error in Matomo: SQLSTATE[08004] [1040] Too many connections
[06-Nov-2019 12:22:15 UTC] Error in Matomo: SQLSTATE[08004] [1040] Too many connections
[06-Nov-2019 12:27:14 UTC] Error in Matomo: SQLSTATE[08004] [1040] Too many connections
[06-Nov-2019 12:27:15 UTC] Error in Matomo: SQLSTATE[08004] [1040] Too many connections

EDIT2: Found related errors in the browser console

Hi,

All of these errors in the PHP log come directly from your MySQL server, so I’d start there to make sure it is configured correctly and responding to all requests.

I ended up overwriting the entire Matomo directory with a new matomo.zip install (3.12.0) and copying/keeping my config.ini.php file.
All is working now!

I think that the SQL errors were caused by the bad/incomplete update, but this is just me speculating.

1 Like