New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Piwik segmented search with archived data (cron) doesn't show some periods #8436
Comments
I'm not sure if I understand the issue right. It is normal that two different segmented searches result in different data. It depends on the query and data whether it is normal that there is no data or not. Or do you mean when executing the same segmented search multiple times you get a different result? Can you let us know the segments that you use? |
That's a good question, I experience the same issue too. Realtime works fine, archived one is patially lacking data. |
I have no clue how this can happen right now. Maybe someone else does? It would be probably beneficial to get access to a database or to get a dump of a database to debug this issue - if possible. If that's possible for someone, please email us at "hello at piwik.org" and leave a comment here (in case it goes into spam folder) |
Do you monitor archiving logs? Such situation may happen if there were archiving errors in the past (e.g. memory limit and others). It's possible that there are incomplete archives marked as done. There are 2 solutions to confirm:
Hope that helps. |
Okay, increased memory_limit to 2G, dropped data for 2015_02 and launched archiving again, let's see... |
Now it archived fine, how to deal with this situation without reading logs all the time? |
Make sure that you have memory_limit set properly (2G should be fine but it depends on your traffic). You can also set a basic monitoring (even cron job) that will grep the log file searching for errors and send an e-mail if needed. |
Alright, I dropped all tables in MySQL related to archives, re-indexed everything and now the data is there, but I have another problem - whenever I add any new segmented search (e.g. new region) and switch it to use 'pre-processed data' it shows nothing and re-indexing doesn't help, the only solution is to again clear everything and initialize it from scratch. |
I have the same issue here, One solution is to delete the tables, but for large sites this is not really an option. |
@akrus Can you explain exactly the step to reproduce? it seems to work fine for us
@RMastop do you still have this issue? how can we reproduce this? |
Hi @mattab, |
Upgraded now, should I execute full re-index or usual cron job should fix this? |
Maybe wait 24 hours and see if it fixed itself already. If some old data is still not processed, you can re-process it all with the command in: https://piwik.org/faq/log-analytics-tool/faq_17994/ If you are still seeing the issue we'll investigate more and get to the bottom of it... (added |
Hi @mattab, I'm sorry, I'm not allowed to connect to the instance where it happened. Cheers, |
@akrus could you please create a new issue? I will mark this issue as solved for now, but if you still experience this issue in Piwik 2.16.2 or later, please open a new issue and we will investigate! |
I m having similar issues ..i cant see old records |
@XinfinityoO please create a new issue and write down as many details as possible |
I am having a similar issue |
Solution: Run: |
Hi,
I have Piwik running (latest stable version) and real-time segmented search is quite slow. I've changed this to use archived data (cron) and executed full re-archive using 'piwik/console core:archive --url=http://piwik -vv -
-force-all-periods=315576000 --force-all-websites --force-date-last-n=10000'. This took one day to complete, but as I can see on the graphs, e.g. Visits over Time, in one segmented search there is no data between Apr 2014 and Jun 2015 (so I have Mar 2014 and Jul 2015), in another - Jan-Jun 2015 is missing and so on. Why this could happen? Executing console core:archive again doesn't change anything. New days are appearing fine though.
See screenshots attached.
The text was updated successfully, but these errors were encountered: