@matomoto opened this Issue on January 2nd 2023
  • Matomo Version: 4.13.0
  • PHP Version: 8.1.13

Oops… there was a problem during the request. Maybe the server had a temporary issue, or maybe you requested a report with too much data. Please try again. If this error occurs repeatedly please contact your Matomo administrator for assistance.

I become this message every time by loading the All Websites dashboard, when i check my matomo stats for the last month. I have ~50 IDs. The visitors are ~0 to ~500 and by one ~3000 per ID. I reload the page with Ctrl+F5. After 10 minutes, the stats are loaded. I think, the server is worked 10 minutes tp generate the stats.

I have a own instance of matomo installed and use it for ~8 years. It is installed on a virtual server webhost account.

  • 64-bit PHP Binary: ✔
  • Memory limit: ✔ 256M
  • PHP INI max_execution_time: 90
  • PHP INI post_max_size: 2048M
  • PHP INI max_input_vars: 1500
  • Curl Version: 7.83.1, OpenSSL/1.0.2k-fips
  • DB Adapter: MYSQLI
  • MySQL Version: 10.3.37-MariaDB
  • Server Info: Apache/2.4.54 (Unix)

The message Oops… there was a problem an the Ctrl#F5 is boring. My idea: Don't make it with the server timeout. Make it with a async fetch() and a setInterval(). Load the page and start the job. When the job is finished, then display the result. Maybe display a wait-jingle on the loading time.

Cronjob: It is not a solution in this case.

@bx80 commented on January 4th 2023 Contributor

Hi @matomoto, thanks for the feedback.

You are probably correct that the server is working away for 10 minutes to generate the statistics. Browser triggered archiving isn't really suitable for large amounts of data which is why a background cronjob is usually recommended so the necessary archives can be generated before they are needed.

An asynchronous check for archive availability would definitely be nicer than have a long running request that times out with an error message :+1: I'll adjust this issue title to reflect this suggestion and assign it for prioritization.

@matomoto commented on January 4th 2023

Thx @bx80
i know the issue with cronjob long ago. Not every matomo user had a free cronjob for that. In many webhost accounts the cronjobs are limited (to 5 or 10) and possible all in use, also no free ... and so one ;)

The waiting time (page) can have a information about a cronjob for faster result displaying. For me, 10 minutes wait is OK instead a cronjob.

Powered by GitHub Issue Mirror