@Frank_D wrote:
We run the core:archive job every hour. Almost every time I get an Error with some requests:
Done archiving
SUMMARY
Total visits for today across archived websites: 2700
Archived today’s reports for 267 websites
Archived week/month/year for 267 websites
Skipped 572 websites
- 530 skipped because no new visit since the last script execution
- 40 skipped because existing daily reports are less than 3600 seconds old
- 0 skipped because existing week/month/year periods reports are less than 3600 seconds old
- 2 skipped because got an error while querying reporting API
Total API requests: 1064
done: 267/839 32%, 2700 vtoday, 267 wtoday, 267 wperiods, 1064 req, 531532 ms, 6 errors.
Time elapsed: 531.532s
SUMMARY OF ERRORS
Error: Got invalid response from API request: ?module=API&method=API.get&idSite=10055&period=week&date=last2&format=php&trigger=archivephp. The response was empty. This usually means a server error. A solution to this error is generally to increase the value of ‘memory_limit’ in your php.ini file. For more information and the error message please check your web server’s error Log file. As this core:archive command triggers PHP processes over HTTP, you can find the error message in your Matomo’s web server error logs.php memory should be the problem. I get no entry in the Log file.
I also run the misc/cron/archive.php in the browser with the same result.I found some older posts about this problem, but none of them helped me to solve my issue.
Posts: 1
Participants: 1