I have a Matomo (5.3.2) running with database in MariaDB.
The CustomReport and CustomAlert plugin is installed.
When accessing the Behaviour → Pages when selected the Year period for 2025 it times out (the generic Oops… message is presented) also tried to call the data api call directly to ensure that it is not using any segments that could cause issue
/index.php?date=2025-01-01&module=Actions&format=html&action=getPageUrls&idSite=2&period=year&showtitle=1
I have verified:
- in database in all matomo_archive_numeric_2025_MM having a “done” row with value = 1 for all periods 1,2,3.
- that matomo_archive_numeric_2025_01 contains archive rows for period 4 including the “done” row with value = 1
- that matomo_archive_blob_2025_01 contains archive rows for period 4.
- looked into matomo.log file if there are any errors related, but none found
In the config.ini.php the browser_archiving_disabled_enforce = 1
I have tried to invalidate the year with:
./console core:invalidate-report-data --sites=2 --dates=2025-01-01,2025-12-31
and run an archive with:
./console core:archive --url=… --force-date-range=2025-01-01,2025-12-31 --force-idsites=2 --force-periods=year
but the issue with timeout still remains.
It feels like Matomo doesn’t find or not using the archived report, instead try to calculate/archive it on the request.
What configuration have I missed or what can I do to make the year report work?
1 post - 1 participant