Oops… problem during the request, please try again.

• check that your crontab is actually working by checking that the output is the expected XML from the API calls.
• check your error logs when you have the "oops" error message

Replying to matt:

* check that your crontab is actually working by checking that the output is the expected XML from the API calls.

How do I check that? I am sorry, but I don't know, what is is expected ...

* check your error logs when you have the "oops" error message

apache2/error.log:

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 75 bytes)in /var/www/virtual/counter.hobbyschneiderin.net/htdocs/piwik/modules/ArchiveProcessing/Day.php on line 210

Where does he get the 128MB? It's not from php.ini. php.ini has 256MB for testing, but I don't like it.

Thanks, would be lovely, if it is going to work.

Replying to matt:

* check that your crontab is actually working by checking that the output is the expected XML from the API calls. * check your error logs when you have the "oops" error message

Think I got it. Piwik is running on a dedicated server on which I try the new ispcp control panel.

The php.ini for the domain piwik is running on, is hidden in a special place, which I have overseen.

The responsible php.ini is now set to:

;;;;;;;;;;;;;;;;;;;
; Resource Limits ;
;;;;;;;;;;;;;;;;;;;

max_execution_time = 3600     ; Maximum execution time of each script, in seconds
max_input_time = 120 ; Maximum amount of time each script may spend parsing request data
memory_limit = 512M      ; Maximum amount of memory a script may consume (128MB)

I will wait for a week or two and start changing the memory_limit.

The day he ran out of memory had more than 12.000 visits counted.

Is there a way to calculate the memory_limit needed?

There is no way (yet) to guess the memory usage that will be necessary. However 256M should be enough for most cases.