Lukas
(Lukas Winkler)
March 23, 2022, 6:39pm
4
This seems a bit similar to
opened 09:23AM - 19 Apr 21 UTC
closed 07:40AM - 26 Apr 21 UTC
answered
## Expected Behavior
Archive cron does not get stuck on Applying queued rearchi… ving...
## Current Behavior
Archive cron gets stuck during "Applying queued rearchiving..." doing queries like and writing nothing else.
`SELECT option_name, option_value FROM `piwik_option` WHERE option_name LIKE '%report_to_invalidate_733_2021-01-29%" `
up to a point where it goes out of memory (we have 28GB of memory).
## Context
We have a very big matomo installation with more than 20K sites tracked.
We recently updated matomo from 3.12 to 4.2.1
## Your Environment
* Matomo Version: 4.2.1
* PHP Version: 7.4
* Server Operating System: Ubuntu
and
opened 09:05AM - 08 Nov 21 UTC
closed 01:52AM - 10 Nov 21 UTC
invalid
Potential Bug
After upgrading matomo from 3.13 to 4.5 then can't process archive. The log stay… s on this page for three days without moving (FYI, I have 36w+ domains on my server), any idea?
INFO [2021-11-08 08:53:46] 30799 ---------------------------
INFO [2021-11-08 08:53:46] 30799 NOTES
INFO [2021-11-08 08:53:46] 30799 - Async process archiving supported, using CliMulti.
INFO [2021-11-08 08:53:46] 30799 - Reports for today will be processed at most every 3600 seconds. You can change this value in Matomo UI > Settings > General Settings.
INFO [2021-11-08 08:53:46] 30799 - Archiving was last executed without error 349 days 0 hours ago
INFO [2021-11-08 08:53:47] 30799 - Will process all 360546 websites
INFO [2021-11-08 08:53:47] 30799 ---------------------------
INFO [2021-11-08 08:53:47] 30799 START
INFO [2021-11-08 08:53:47] 30799 Starting Matomo reports archiving...
DEBUG [2021-11-08 08:53:47] 30799 Applying queued rearchiving...
* Matomo Version:4.5.0
* PHP Version:7.4.21
* Server Operating System:Centos7
.
But in their cases it was caused by a major Matomo upgrade, while you installed a recent Matomo version freshly, right?
I guess the large amout of sites causes this, but nevertheless this query should not be what causes the major slowdown.