Deactivate archiving using the browser trigger in the settings.[/quote]
I’ve already been running Piwik like that for 2 months. I auto-archive every 15 minutes, and this error still happens.
I got the error saying: Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /path/to/piwik/install/core/DataTable/Row.php on line xx.
PHP Version 5.3.2-1ubuntu4.5ppa5~lucid1
I have 32GB of memory installed on the server and 12GB free.
I updated memory_limit in php.ini (there are multiple copies of this file, I changed them all, with one in /etc/php5/cli configured using memory_limit = -1, others are 512MB), the error is still there, not sure what to do to fix that.
Bob, if you’re still getting the “Fatal error: Allowed memory size of 134217728 bytes exhausted”, then the most plausible causes are:
(a) php.ini or .htaccess file where it sets memory_limit = 128M, or
(b) you’re running mod_php under Apache, and haven’t restarted the apache (or httpd) process.
Thanks. Actually there is another php.ini files (it runs mulitple instances of php on the server) that was not updated and was used by this app. It works now, Thanks for your help.
Sure thing, we just move the stats server from a hosting provider to our own server as it experience memory issue there. I will see how the server goes, and may share with all of you in this forum.
With cron task enabled, I’m not able to see monthly and yearly stats
With cron task disabled, I’m got the following error message when I select monthly period :
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 8208 bytes) in /home/xxx/public_html/piwik/core/DataTable.php on line 1022
My trafic is more or less 3000 visit/day and 900.000 pages/month
PHP Version 5.2.17 Linux serveur
memory_limit 128M
I’m on a mutualized server, so I don’t have acces to server configuration files.
I was phpMyVisit user and with the same trafic on the same server I never got a problem
I’m now on a PHP 5.3.8 serveur, with Piwik 1.7 rc1, but still with memory_limit 128M, and the problem is the same : Monthly report does not work.
On the other side, if I select a date range date like for exemple from Jan 2nd to Feb 2nd, it works.
But if I select a date range from Jan 1st to Jan 31, it doesn’t work, because I guess it uses the monthly function in this case.
Is it really impossible to do something in order to have monthly (and yearly) report working on serveur with memory_limit at 128M ?