Open dieisraels opened 2 years ago
Hi @dieisraels. Sorry to hear you are having issues with the archiving.
Those segments on page urls are known to be a bit memory and time consuming, especially when they are not using an exact match.
Are you using some custom configuration for [General] enable_segments_cache
or enable_segments_subquery_cache
?
No, I have not made any customizations to the above settings. I have made the following (possibly relevant) changes in the [Generic] section:
enabled_periods_UI = "day,week,month,year"
browser_archiving_disabled_enforce = 1
minimum_memory_limit_when_archiving = 4096
force_ssl = 1
datatable_archiving_maximum_rows_subtable_referrers = 500
datatable_archiving_maximum_rows_actions = 1000
datatable_archiving_maximum_rows_subtable_actions = 500
datatable_archiving_maximum_rows_events = 1000
datatable_archiving_maximum_rows_subtable_events = 100
However, the archiving process does not write errors to the PHP log. That is something I can confirm. My instance (4.8.0 on php 8.0.13) also does not log into the error log file. Running
error_log("Test")
creates the log file and writes the log line "Test" to it.
The archiving process occasionally has empty API response over and over again:
The cron process outputs the following error message in that case:
I have increased the log level of Matomo to DEBUG, but there are no log entries for the API requests. I explicitly redirect the PHP error logging to a file. I have additionally checked the logging of PHP errors on the CLI this way and it works. However, the archiving process does not write errors to the PHP log.
It does not always abort the same API requests. At a later time the segmet could be processed.
What are my options for further error analysis? What could be reasons for API requests aborting?
Your Environment