My company start to use piwik for some time by now and everything is working as smooth as silk except the archive part.
We have try a cron with a wget to the url of archive.php and call the piwik console directly from a cron job. The both gave the sometimes the same output no matter what memory_limit configuration in php:
Have floowed some solutions found on this board and on some blogues but none of them seems to work nor the increse of memory_limit in php.ini configuration (by now we are using 2048M and the value on the error keep on show the 805306368 bytes).
Now we are running the cron passing the memory_limit value but it seems that in the recurrent requests made by the piwik console this variable is not passed to it. For exemple the first request is
please make the change of memory limit in the PHP config file if you can. Otherwise we could forward the parameters to the CLI, for this feel free to create issue on our issue tracker: Issues · matomo-org/piwik · GitHub
Hi Matt thanks for your response.
I can change of memory limit in the PHP config file and I’ve made it but no matter what the value that I put in memory_limit, piwik keeps me saying the same memory value in the error message: 805306368 bytes. And this is the strange part of it no matter if I put 128M or 2048M…
/etc/php5/apache2/php.ini is for the PHP plugin used by Apache. This is the one you need to edit for changes to be applied for your Apache setup. do you have this on your particular setup?
I have no /etc/php5/apache2/php.ini.
In my setup there’s only one php.ini availabla and is in /etc/php53. Verify that is the one in use by apache, using php_info.
My question is that no matter what memory_limit I put piwik archive always return the same memory value 805306368 bytes as I said before. Thus my suggested solution may not work because even I call archive trough console it seems to make a web request to /index.php?module=API&method=API.get&idSite=3&period=week&date=last8&format=php&token_auth=3f5caeexed3ccb8351c93f2cb1c1e1a0&trigger=archivephp wich make no difference beteween console and wget cron configuration. If you have memory problems with wget cron you will get it as well in console cron configuration.
lesjokolat, No we use our own CMS and entirely separated from piwik install thus different SO and configurations too.
matt, Yes I have restarted apache after php.ini changes.
The weird part is the value that appears in the message because it seems that php was using the 2048M configured but when the 2048M was exceded it keeps on showing the wrong memory value of 805306368 bytes in the error log output. And that was the reason of my post. Unfounded seems now
Dispite that on the debugging tasks discovered that the console make some http requests. It was good that the console cron call don’t make any http request to proccess statistics since you can pass memory_limit to the command line that is going to be “lost” when the http request is made. And passing the memory_limit to console make possible to change this only when running the piwik cron tasks and keep a “logical value” in apache default configuration.
lesjokolat think not. The php configuration already have a value for timezone.
We’ve simply update the php engine to the latest release 5.4.16 and now the error was gone with the exact configuration / php.ini used before…
Can’t tell for shure where the problem was
