Using my email-reports with 1.7 results are errors:
Internal Server Error
or error
Fatal error: Out of memory (allocated 24903680) (tried to allocate 2280 bytes) in /homepages/4xxxxx/core/ReportRenderer.php on line 202
or
…piwik/libs/pChart2.1.3/class/pImage.class.php on line 93
if I disable ImageGraph-plugin it works fine - but wihthout grafics in the reports
That’s strange… I don’t get any Report working for a week on this site.
A range leads to the same error.
I’ll try to export the data to a functioning reporting system as a workaround.
However, I’ll check google analytics for this feature (i.e. working reports).
I’ve made that code change, but the timeout still exists (not the memory problem). Fiddling with the report, it seems the Referrers section is causing the problem. If I put everything else in, except this area, the report runs. If I only put this area in, I can not include all the options without the error, but I can individually or in groups. It seems the Keywords/websites report causes the problem, if this helps.
To summarise, I’ve now got the graphing back on, with everything turned on for the report (PDF, tables/graphs for all) minus these reports:
dashboard
keywords
continent
custom
provider
ALL visitor settings
and it works almost instantly. Is there a resource issue in the “Referrers” section?
I’m just trying to recreate the old reports I had on there that I removed, and now I’m finding the report that was just working is not -so it seems intermittent. Have been testing with download rather than emailing, since it’s a pretty simple task attaching the PDF to an email. I don’t think the problem is there.
I’ve now got the graphs back off, and it seems to be outlinks/downloads that are causing the problem
what would be a sensible memory/time out limit? is 500mb/300secs too tight? It seems like a fair bit to me, for this task?
will continue to play with it when I get the time, but for now, with reduced reporting and removed graphics it’s doing a job of sorts.
I find it worrying that it either working within (say) 10 seconds, or fails with timeouts over 300 seconds/out of memory. There’s no middle ground which you’d expect when tweaking the reports chosen?
I don’t see how messing with the ‘period’ will change this
ok great thanks. This is PHP on windows, so that could be doing all sorts different.
I find the different between working/failing so clear cut rather than gradual time increase weird.
is there a general standard for timeout/memory setting within PHP ini, or is this completely custom depending on setup?
my boss has also had trouble going back and doing monthly reports with timeouts -I thought the auto-archiving helped this process? Or does the auto-archiving only digest the visitor log, and not produce any numbers, so to speak?
is there any mySQL mainenance I should be doing? I’m from an MS SQL background and not sure what goes on in the mySQL box!
if I find out anything interesting, I will let you know! thanks
If you setup archive.php it should process all monthly report, so your boss shouldn’t have to wait or experience issue at all.
However, make sure you use this patched archive.php which fixes a bug: http://dev.piwik.org/trac/export/5927/trunk/misc/cron/archive.php
We’re running Piwik on Windows/IIS7 as well.
Maybe that’s the root of the problem.
I use a cron job as well and cannot get any report working (>= 1 Week, dosen’t realy matter which reports).
Sadly I cannot test further right now - I’ve got other projects as well.
But if you need some information (system etc.) to find the error please let me know.