Hi,
After upgrading to 4.2.1 I get a 500 error.
Plus this:
Files were found in your Matomo, but we didn’t expect them.
–> Please delete these files to prevent errors. <–
File to delete: php-fpm.core
What can I do to solve all this?
1 post - 1 participant
I started a fresh installation of 4.2.1 and after the system check I got a 500 error.
Also this:
Files were found in your Matomo, but we didn’t expect them.
–> Please delete these files to prevent errors. <–
File to delete: php-fpm.core
I deleted the file, backed in the browser, reloaded the page, and got the same message to delete the file.
Deleted the file, clicked Next to go to database setup, blank screen.
I think there is something worng wih Matomo verion 4.2.1.
8 posts - 2 participants
Hello i am installing matomo on a server configure with apache2.4 + php-fpm 7.4.6, i can do the installation normally but when i access to the home page after install not load, here are the logs:
error_log - apache:
[:error] [pid 5456:tid 140071686305344] client denied by server configuration: matomo/plugins/CoreHome/angularjs/notification/notification.directive.html
the above line mean while i am on the website stay spamming.
same on the webtools
This is on console
Error: [$templateRequest:tpload] [http://errors.angularjs.org/1.8.2/$templateRequest/tpload?p0…ctive.html%3Fcb%3Df55c49ccade6e2502941fa488f7db90d&p1=-1&p2=](http://errors.angularjs.org/1.8.2/$templateRequest/tpload?p0=plugins%2FCoreHome%2Fangularjs%2Fnotification%2Fnotification.directive.html%3Fcb%3Df55c49ccade6e2502941fa488f7db90d&p1=-1&p2=)
F https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:102
g https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:265
k https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:236
$digest https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:248
$apply https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:251
k https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:202
v https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:208
onabort https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:209
Pg https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:209
s https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:204
b https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:202
k https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:236
$digest https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:248
$apply https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:251
k https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:202
v https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:208
onload https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:208
Pg https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:208
s https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:204
b https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:202
k https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:236
$digest https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:248
$apply https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:251
k https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:202
v https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:208
onload https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:208
Pg https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:208
s https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:204
b https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:202
k https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:236
$digest https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:248
$apply https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:251
k https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:202
v https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:208
onload https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:208
Pg https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:208
s https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:204
b https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:202
k https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:236
$digest https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:248
$apply https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:251
k https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:202
v https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:208
onload https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:208
Pg https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:208
s https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:204
b https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:202
k https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:236
$digest https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:248
$apply https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:251
k https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:202
v https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:208
onload https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:208
Pg https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:208
s https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:204
b https://analytics2.example.com/index.php?module=Proxy&action=getCoreJs&cb=f55c49ccade6e2502941fa488f7db90d:202
1 post - 1 participant
I get the following error in Google Lighthouse
Any idea what I can do to get it solved?
6 posts - 2 participants
Hi Colleagues,
I’ve been using Matomo library for quite some time now and I recently implemented bulkTracking using the library. I wanted to set an interval for which duration the events will be queued and the bulk request will be sent after this interval.
I got to know that setRequestQueueInterval() can be used to set the queue interval. However, it doesn’t work like an interval but rather like inactivity time after which request is fired.
What I mean here is - If I set the timeout to be 15 seconds and if I start using the application at 4:00:00 pm and used it continuously for 1 minute, I expect that at the end of my 1 min activity, there should be 4 requests fired. However, there’s no request fired at all. Rather, there’s 1 request fired at 4:01:15 pm, i.e., after 15 seconds of inactivity from 4:01:00 pm.
is this a bug? How do I achieve my requirement? Kindly let me know. Thank you.
1 post - 1 participant
Last week we updated to 4.2.0. After that we were missing tens of millions visits. Something went terribly wrong with our data!
First of all
After upgrade:
Updating to 4.2.1 did not resolve the problem
I had no other option then to restore the backup we made before update, we are now missing a couple of days which is not a big deal. However some day we’ll need to update again, not looking forward to do 
I could have reprocessed reports from July onward but even new reports were messed up. Besides I could not reprocess older 2020 reports because we don’t have the raw data. And I really needed the 2020 reports.
I don’t really expect any solution here but you never know, maybe someone is experiencing something similar after updated to 4.2.0
3 posts - 2 participants
Hi… i am using Piwik 2.16.1… all data shows zero for the last month Feb 2021 alone… how can it be resolved…
3 posts - 3 participants
`[04-Mar-2021 22:36:47 UTC] Error in Matomo (tracker): Error query: SQLSTATE[22003]: Numeric value out of range: 1264 Out of range value for column 'time_transfer' at row 1 In query: INSERT INTO matomo2_log_link_visit_action (idvisit, idsite, idvisitor, idaction_url, idaction_url_ref, idaction_name_ref, server_time, idpageview, pageview_position, time_spent_ref_action, time_dom_processing, time_network, time_server, time_transfer, idaction_name) VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) Parameters: array ( 0 => '2135890', 1 => 45, 2 => '��vD�T2�', 3 => '481013', 4 => NULL, 5 => '1169110', 6 => '2021-03-04 22:36:47', 7 => 'BYIgWZ', 8 => 12, 9 => 952, 10 => 3216, 11 => 0, 12 => 90, 13 => 1612737866801, 14 => '1105093', )`
Scaring… because some time ago started like this… My matomo is going crazy... graphs are wrong or zero
1 post - 1 participant
Hello,
I logged in to my matomo site recently and was told to do an update from 3.x to 4.2.1. I followed the automatic procedure and it took a few minutes and completed. However, once this was done I seem to be missing all of the past analytic data for all of my sites.
I looked at other topics on this and did the manual update steps, but still nothing has come back. It only seems to be tracking data from the update forward.
A look in the database indicates that there are archive tables names something like “mt51_archive_blob_2018_01”. Is there a way to get this data back in to portal?
1 post - 1 participant
After setting up, I added some websites to try things out.
Today I had to spend hours searching figuring out how to remove those sites from the list.
There was just zero traces of anything remotely looking like a delete function anywhere.
The only things I found in the forums and help texts, suggested I had to run SQL-code to delete anything.
Turns out the only way to get the UI to a state where you can delete sites,
is to click a link marked…
“Add a new website” !
And that also seems to be the only way to reveal any of the sub-sections to the “All Websites”-part of the UI, and large parts of the rest of navigation of the entire admin UI.
You have to first initiate the process of adding a new website, then cancel that action, and then you can get to that part of the UI.
This:
/matomo/index.php?module=SitesManager
…seems to be the only page where you can view a list of the sites, with delete-buttons for each.
But there is no way to get to that page directly from anywhere.
Am I missing something here, or is that just really bad UI-design?
4 posts - 2 participants
I had setup matomo on AWS with Bitnami AMI
My application frontend is on WordPress & behind CDN, load balancer with 3 app server.
I can check real-time logs but when i compare them with load balancer access logs it is completely different.
Example-
An access log of loadbalancer hits for 6th march 2021 showing 1203874
Matomo Total Visit 30983 & pageviews 46284
Both are very different, even not closer, how can i identified them, also how can i check my setup is correct or not.
1 post - 1 participant
Hi everyone,
Currently, Matomo supports the comparison of segments up to 5, but is there a way to unlock this? For example to allow the comparison up to 10.
Thanks for your help,
1 post - 1 participant
Hi All,
I came across a really strange bug on the queued tracking piece which has really got me confused about how this all works. Current documentation is seriously lacking so its hard to get the full picture.
I have set my queue to have 2 workers, one queue has cleared down very quickly, but the other hasn’t
I now have nearly 3 million in queue one and hardly any in the other.
Please help - this ended up locking my redis db and i cant seem to write to the db at all! This has probably been going on for a while.
Is there a way to delete down all data (or bulk upload) to clear this down asap?
I’m on matomo 4.0
Cheers
Steve
1 post - 1 participant
Hello,
Let’s see if someone can help me. I am carrying out the process of updating the version 3.5.1 of Matomo to the latest version that they have released, version 4.2.1. As in other updates I have followed the documentation on how to update, launching the command ./console core: update. After a few hours, I have the following output on the screen, indicating that Matomo has been updated correctly but that there are errors trying to launch the ALTER TABLE statement:
* /var/www/educacion/cau_ce/estadisticasweb_test/core/Columns/Updater.php:
Error trying to execute the migration 'ALTER TABLE `piwik_log_visit` MODIFY COLUMN `visitor_count_visits` INT(11) UNSIGNED NOT NULL DEFAULT 0, MODIFY COLUMN `visit_total_interactions` MEDIUMINT UNSIGNED DEFAULT 0, MODIFY COLUMN `referer_name` VARCHAR(255) NULL, MODIFY COLUMN `referer_url` VARCHAR(1500) NULL, MODIFY COLUMN `config_browser_name` VARCHAR(40) NULL, ADD COLUMN `config_client_type` TINYINT( 1 ) NULL DEFAULT NULL, MODIFY COLUMN `location_region` char(3) DEFAULT NULL, MODIFY COLUMN `location_region` char(3) DEFAULT NULL;'.
The error was: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'location_region' in 'piwik_log_visit'
* /var/www/educacion/cau_ce/estadisticasweb_test/core/Columns/Updater.php:
Error trying to execute the migration 'ALTER TABLE `piwik_log_visit` MODIFY COLUMN `visitor_count_visits` INT(11) UNSIGNED NOT NULL DEFAULT 0, MODIFY COLUMN `visit_total_interactions` MEDIUMINT UNSIGNED DEFAULT 0, MODIFY COLUMN `referer_name` VARCHAR(255) NULL, MODIFY COLUMN `referer_url` VARCHAR(1500) NULL, MODIFY COLUMN `config_browser_name` VARCHAR(40) NULL, ADD COLUMN `config_client_type` TINYINT( 1 ) NULL DEFAULT NULL, MODIFY COLUMN `location_region` char(3) DEFAULT NULL, MODIFY COLUMN `location_region` char(3) DEFAULT NULL;'.
The error was: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'location_region' in 'piwik_log_visit'
* /var/www/educacion/cau_ce/estadisticasweb_test/core/Columns/Updater.php:
Error trying to execute the migration 'ALTER TABLE `piwik_log_visit` MODIFY COLUMN `visitor_count_visits` INT(11) UNSIGNED NOT NULL DEFAULT 0, MODIFY COLUMN `visit_total_interactions` MEDIUMINT UNSIGNED DEFAULT 0, MODIFY COLUMN `referer_name` VARCHAR(255) NULL, MODIFY COLUMN `referer_url` VARCHAR(1500) NULL, MODIFY COLUMN `config_browser_name` VARCHAR(40) NULL, ADD COLUMN `config_client_type` TINYINT( 1 ) NULL DEFAULT NULL, MODIFY COLUMN `location_region` char(3) DEFAULT NULL, MODIFY COLUMN `location_region` char(3) DEFAULT NULL;'.
The error was: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'location_region' in 'piwik_log_visit'
The update completed successfuly, however there were issues during the process. Please read the above descriptions for details. For further help:
* Check the [ Matomo FAQ ] which explains most common errors during update.
* Ask your system administrator - they may be able to help you with the error which is most likely related to your server or MySQL setup.
Matomo has been successfully updated!
When I access the URL where I have Matomo deployed via the web, I get the attached screen also in this thread, where it says that the database is out-of-date.
What’s going wrong? How can I solve this problem?
Thank you very much in advance
1 post - 1 participant
Hello, The log is full of warning like this Trying to add two strings in DataTable\Row::sumRowArray: 0 + Chrome 79.0 for column browser in row # ['idSite' => 20, 'idVisit' => 65611, 'visitIp' => 0, 'visitorId' => 0, 'lastActionDateTime' => 0, 'siteName' => 0, 'userId' => , 'deviceType' => 0, 'deviceTypeIcon' => 0, 'deviceModel' => 0, 'operatingSystem' => 0, 'operatingSystemIcon' => 0, 'browserFamilyDescription' => 0, 'browser' => 0, 'browserIcon' => 0, 'country' => 0, 'countryFlag' => 0, 'region' => , 'label' => -2] [] [idsubtable = ]<br /> Can you please advise how to prevent this from happening. It occurs for all different columns, not just browser.
1 post - 1 participant
Any idea how I can restart it? (everything else is working fine and well tracked)
thanks!
1 post - 1 participant
Hello,
I have created several new segments, but only new data appears in the segments. If I test the segment to a previous time period, I get hits from the visitor log. The segments are not live, but are processed by the archive cron. I have already invalidated all data of the segment by plugin and called the cron manually (https://matomo.org/faq/how-to/faq_59/):
./console core:archive --force-all-websites --url=YOUR_MATOMO_URL_HERE
Still, no previous data appears in the segments. Neither for single days nor the complete months. I am using the latest Matomo version 4.2.1, what am I doing wrong? Or are the data only prepared in larger time intervals?
Thanks for help.
1 post - 1 participant
Our goal, for clarity - Keep the roll-up, optimize so we don’t need >1G of memory to archive it, if at all possible.
I’m wondering if memory_limit 1G+ is to be expected for this kind of configuration/traffic, or if there’s something we could be doing better? We are looking into moving to more powerful hosting that allows us to push the memory_limit above 1G, but want to make sure it’s necessary first.
The problem - Our archiving script runs as a cron job once every hour (UI triggering disabled) and it errors out pretty much every time due to hitting the 1G PHP memory_limit. (According to logs it is definitely using 1G, not loading the wrong config file or something like that.) Our hosting doesn’t allow us to increase above 1G.
Matomo config/traffic info - Our Matomo instance isn’t particularly “high-traffic” (We get ~ 70k-80k pageviews per month). BUT, archiving always fails on the same site, a “roll-up” of 17 sites that contribute nearly all of our traffic. (We track 65 sites total, many of them dev sites, those 17 contribute ~95% of those ~70k-80k pageviews.) And the same period, “year.” No other sites/periods have memory issues archiving w/ memory_limit=1G.
Other factors that may be contributing:
We have tons of custom reports, this roll-up has 19. (10 available to all sites, 9 specifically for the roll-up.) Many use custom variables.
We’ve been running Matomo 1.5 yrs now & our DB has 45.8G of data. This seems odd, according to this Matomo article we should be well under that w/ <2 mill pageviews total, <1G??
Many of our URLs are searches and we don’t currently ignore any search params. (Our “Pageviews - URLs” report for the roll-up is huuuge) Would this make a difference?
Any ideas? Things we can investigate, look into, etc., am I onto something with the bullets above? Thanks in advance!
1 post - 1 participant
Hi there,
I have set up email reports in Matomo - one weekly and one daily. However, they just aren’t sending. I’ve even clicked the Send Report Now link and nothing is being sent. I am included in the email so I know they aren’t being sent out. This is crucial for stakeholder management and I can’t see an obvious reason why they’re not sending.
Thanks in advance.
4 posts - 3 participants
The stats on Wordpress work fine but when I go to the reporting dashboard there is nothing there other than the navigation and the blue header. I saw another post similar to this but didn’t really understand the instructions.
Sara
4 posts - 2 participants
