'Visits Overview' not updating while Visits in Real-time works fine (Matomo 4)
#16689
Comments
|
Thanks for creating this issue and sorry for the trouble @PepijnBoers Could you maybe run this MySQL query and send us the output? select `status`, count(*) from matomo_archive_invalidations group by `status`just created #16690 to add more information to system check so this won't be needed next time. @diosmosis do you have any idea on this? My theory is that maybe some invalidation is stuck in |
mysql> select `status`, count(*) from matomo_archive_invalidations group by `status`;
+--------+----------+
| status | count(*) |
+--------+----------+
| 1 | 2 |
+--------+----------+
1 row in set (0.00 sec) |
|
Thanks a lot @PepijnBoers I think that confirms my theory @diosmosis ? Maybe the one in "progress" failed and was never cleaned up? |
|
For the record: I have the same issue since 4.0.0-rc1. My output for the command above: Let me know if you need some additional information. |
|
Thanks @cadeyrn very appreciated |
|
Hi @cadeyrn would you be able to run |
|
@tsteur that sounds like a possibility, debug logs would be helpful I think. I'll add the |
|
|
fyi there's another report in #16703 @diosmosis might be good to also check if there could be any reason why it fails to remove the invalidation in the first place and why the status = 1 persists. Maybe it's all due to failed archives but maybe there could be also other reasons? @PepijnBoers @cadeyrn @timscha any chance you maybe noticed some DB errors like "server gone away"? (you would likely only notice this if you have the full logs of archiving runs or so). If you don't know out of the box all good and feel free to ignore. |
When I first noticed the issue I tried to manually execute the cron script and indeed I noticed an error in the archiving process. It was caused by the automatic update of the GeoLite2 city database. The URL (without an API key) was no longer working and caused an exception. I changed the URL after that. Maybe that error caused the failure?
Unfortunately I don't know of such errors. I only noticed the LOAD DATA INFILE failed error in my log above. |
|
fyi We'll soon release RC3 which should resume the archiving again. We'll still need to check if we can further prevent this from happening in the first place |
No, MariaDB was fine. I'm using 10.5.7 at the moment. @tsteur: Understand it correctly? RC3 should fixed it? I updated it a few minutes ago, had already some visitors, but no changes to the statistics and graphs. |
Okay, it has not yet arrived as update on my installation but I see RC 3 on the releases page. edit: After the update to RC 3 arrived I can confirm what @timscha said: The issue is still present in RC 3. |
|
Ehm, my Matomo installation said something different. :) |
|
\o chiming in from 4.0.0-RC3 because I just observed the same symptoms and can confirm the issue, maybe I can also help pinpoint the origin with some guidance. Running Also: |
|
Thanks @evilham there should be already a workaround in the latest RC or we might release also another RC today (possible only this next one today includes a fix) @diosmosis if you could today look if there might be any other reasons this might stay on "status= 1" that be great or whether there's maybe something we can do when this happens (when the archive fails) etc. I don't know the details of how it all works right now but be good to check if there might be edge cases where it can be maybe prevented or something. Otherwise I suppose we can close this issue if there's nothing else we can do |
|
Unfortunately also RC4 does not fixed it for me. :( |
same here, the issue is still present. |
|
Any chance you could launch the archiver again? It might need a second run but would have expected this to be fixed directly. @diosmosis there might be still some issue |
I already did this when I wrote my previous comment and now I did it again, but still with no success. Is there anything else I could check? |
|
@cadeyrn can you check the result of this query: |
|
Result:
|
|
@cadeyrn just the one? Interesting, I'll see what I can find, thanks! |
|
I see the issue, it's due to the previous entries still existing. We need to remove @cadeyrn if you run this SQL it should unblock the archiving: cc @tsteur (will remove in an update) |
|
makes sense 👍 |
|
I tried it as well. Result of: I tried the Deleted Query as well, now the statistics and graphs are working again. |
|
works for me as well, thank you! |
|
@diosmosis had a look at the code and can't think of a way this might be triggered except for some archiving is stopped or some fails in a different way. Thought it might possible this error happened because under circumstances the mapping of could move this line to the beginning of the method to delete invalidations first but it shouldn't make any difference https://github.com/matomo-org/matomo/blob/4.0.0-rc4/core/CronArchive.php#L503 so maybe we could close this issue unless you have some ideas why this might happen maybe even if the archiving succeeds. |
|
@tsteur no idea how this might happen if archiving succeeds, but we could put in an extra check after launchArchivingFor or at the end of it that does |
|
@diosmosis we could do this maybe just for 2 months or so to verify the logic works? Then I'd maybe rather remove the overhead maybe once we know it works. Like we could put this logic in a public method in cronArchive, and add a test to |
|
👍 |
|
Can confirm that |
|
Great, I will close this issue for now. Should there still be an issue please let us know. Thanks for your help everyone! |
mattab
added
the
not-in-changelog
Hi,
I'm having some issues with my matomo server since updating to the 4.0.0-rc1 beta. I'm using a crontab to automatically archive my matomo reports. However, the
Visits Overviewstatistics are not updated anymore. TheVisits in Real-timedoes work as intended and shows recent visits. All the system checks succeed and I'm not sure what to look at. I tried deleting thetmpdirectory but it didn't resolve anything.Manually executing the archive command does not show new API requests. Are there some steps I can take to resolve this issue?
matomo_system_check.txt
Thank you,
Pepijn Boers
The text was updated successfully, but these errors were encountered: