You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you can see, there is a repetitive pattern, and results are totally wrong. I compared with results for individual days:
2014-03-11: I can't have any results here, the page didn't exist yet
2014-03-13: result is correct
2014-03-14: result is correct
2014-03-15: result is correct
2014-03-16: result is the exact copy of the 14th, and it is incorrect, we got only 3 visits
2014-03-17: result is the exact copy of the 13th, which is incorrect, we got 16 visits
2014-03-18: result is the exact copy of the 14th, but we got only 9 visitors.
Finally, when I try to make this request on a bigger date range (from 01-01-2014 to 18-03-2014) I got this response:
can you still reproduce this issue? I tried to reproduce it many times but couldn't.
In case you can still reproduce it: Is it possible for you to provide as access to your FTP (where your Piwik files are) and access to your Piwik web interface? A user with view permission would be enough. Otherwise I cannot solve this issue.
I just upgraded to 2.2.2 and the yes, the problem remains, except that in the case of big date range, I get a clear memory exhausted error:
Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 88 bytes) in /var/www/analytics/htdocs/core/Archive/DataTableFactory.php on line 205
{"result":"error","message":"Allowed memory size of 268435456 bytes exhausted (tried to allocate 88 bytes)"}
It's on a production server so it's a bit touchy to give an FTP access to it. How can I PM you?
In e57984d: refs #4872 this should fix getPageUrl returns same results for several day when a range is used. Waiting to see which tests fail. In this case date always equaled to "2014-03-11,2014-03-18" for each subtable/day
Here is the request:
Here is the results:
As you can see, there is a repetitive pattern, and results are totally wrong. I compared with results for individual days:
2014-03-11: I can't have any results here, the page didn't exist yet
2014-03-13: result is correct
2014-03-14: result is correct
2014-03-15: result is correct
2014-03-16: result is the exact copy of the 14th, and it is incorrect, we got only 3 visits
2014-03-17: result is the exact copy of the 13th, which is incorrect, we got 16 visits
2014-03-18: result is the exact copy of the 14th, but we got only 9 visitors.
Finally, when I try to make this request on a bigger date range (from 01-01-2014 to 18-03-2014) I got this response:
(extract of the end of the response):
"nb_hits_with_time_generation":135,"min_time_generation":"0.001","max_time_generation":"5.299","entry_nb_uniq_visitors":"9","entry_nb_visits":"9","entry_nb_actions":"50","entry_sum_visit_length":"9530","entry_bounce_count":"6","exit_nb_uniq_visitors":"12","exit_nb_visits":"13","avg_time_on_page":365,"bounce_rate":"67%","exit_rate":"39%","avg_time_generation":0.833,"url":"MQN0+.=G9Q!dX=vN[Vq/~v{)Yuv)7oR}0,z6%AMrk!(-jn/y\V='7
GQhArFIuaPl- 04lG#P(vl?mlDn.rN
dF1eOL4 (Cc04%sh/WzZy%
Mc^^I3s8#]ARH
G{I don't know if it's part of the same bug, but I get the same error or kind of pattern described above with all actions.getPageUrl requests.
The text was updated successfully, but these errors were encountered: