Matomo does not track after migration

General questions
1

hi, i downloaded the matomo_old DB from a matomo and then added the DB to the newly installed matomo.
After that i just edited config.ini.php to read from matomo_old instead from matomo.
All runs fine, but the new matomo is not tracking.

Here are the differences in the system checks:

####SetupCron-ManagingprocessesviaCLI:  
1. OLD MATOMO: notsupported(optional)(Reasons:Unknown)learnmore
2. NEW MATOMO: ✔Ok

####LastSuccessfulArchivingCompletion:  
1. OLD MATOMO: notsupported(optional)(Reasons:Unknown)learnmore
2. NEW MATOMO: ✔Thearchivingprocesscompletedsuccessfully00:00:25ago.

####Databaseabilities:  
1. OLD MATOMO:✔LOADDATAINFILE  

2. NEW MATOMO:⚠Warning:LOADDATAINFILE<br/>Hint:UsingLOADDATAINFILEbyupdatingyourPHPandMySQLsoftwareandensuringyourdatabaseuserhastheFILEprivilegespeedsupMatomo'sarchivingprocessalot.<br/>YoushouldfixthisproblemifyourMatomoservertrackshigh-trafficwebsites(e.g.over100,000pagespermonth).<br/><strong>Error:</strong>LOADDATAINFILEfailed...Errorwas:<br/>Try#1:LOADDATAINFILE:SQLSTATE[HY000]:Generalerror:1290TheMySQLserverisrunningwiththe--secure-file-privoptionsoitcannotexecutethisstatement,<br/>Try#2:LOADDATALOCALINFILE:SQLSTATE[42000]:Syntaxerrororaccessviolation:3948Loadinglocaldataisdisabled;thismustbeenabledonboththeclientandserversides[42000]<br/>Troubleshooting:FAQonmatomo.org

####PHP_BINARY: 
1. OLD MATOMO: /opt/cpanel/ea-php82/root/usr/bin/php-cgi
2. NEW MATOMO: /usr/sbin/php-fpm8.2

####PHPSAPI:    
1. OLD MATOMO: cgi-fcgi
2. NEW MATOMO: ⚠Warning:fpm-fcgi<br><br>PHPFPMwillignore.htaccessrulesfor.phpfiles.ToensurethatsensitivefilescannotbeaccesseddirectlyitisrecommendedtoexcludecertaindirectoriesfrombeinghandledbyPHPFPM.Formoreinformationpleaseseetheofficialnginxserverconfiguration

####PHPINIpost_max_size:    
1. OLD MATOMO: 20M
2. NEW MATOMO: 8M

####PHPINImax_input_vars:   
1. OLD MATOMO: 5000
2. NEW MATOMO: 1000

####CurlVersion:    
1. OLD MATOMO: 8.1.2,OpenSSL/1.1.1u
2. NEW MATOMO: 7.68.0,OpenSSL/1.1.1f

####MySQLVersion:   
10.6.14-MariaDB-log     8.0.34

####ServerInfo: 
1. OLD MATOMO: Apache
2. NEW MATOMO: Warning:nginx/1.24.0<br><br>Toensurethatsensitivefilescannotbeaccesseddirectlyitisrecommendedtoconfigureyourwebservertorestrictaccesstocertaindirectories.Formoreinformationpleaseseetheofficialnginxserverconfiguration

####UserAgent:  
1. OLD MATOMO: Mozilla/5.0(WindowsNT10.0;Win64;x64;rv:109.0)Gecko/20100101Firefox/115.0
2. NEW MATOMO: Mozilla/5.0(WindowsNT10.0;Win64;x64)AppleWebKit/537.36(KHTML,likeGecko)Chrome/113.0.0.0Safari/537.36OPR/99.0.0.0
2

Hi @mbmg
Is the new Matomo version the same as the old one?
Can you check in the Matomo error log file if you see anything?

3

Stumbled upon this with this problem.

IF you are using Tag Manager, you must create a NEW version for each container. The migration DOES NOT create the js files, so your tracking code is calling a js file that doesn’t exist in your new install. Only discovered this after seeing a bunch of errors in my error log. Creating a new blank version and publishing fixed it.

Might be something worthy of adding to the migration FAQ.

1 Like