Skip to content
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

No reports generated for 1 site #13006

Closed
kaplun opened this issue May 29, 2018 · 4 comments
Closed

No reports generated for 1 site #13006

kaplun opened this issue May 29, 2018 · 4 comments
Labels
answered For when a question was asked and we referred to forum or answered it.

Comments

@kaplun
Copy link

kaplun commented May 29, 2018

Hi! I am running import_logs.py in a pipe to continuously import extended Apache logs from 2 websited. One is lighter (1 event/second on average), the second one is more used (200 events/second).

I run core:archive cronjob every hour.

Now: reports do appear for the lighter site, while they do not appear for the heavier one (unless I force by hand core:archive.

I haven't found any particular errors in the log, but I am open to suggestions on how to debug this.

@mattab
Copy link
Member

mattab commented May 31, 2018

Makes sense that you need to run core:archive to get reports to show up.
for a large site, it won' work to "browser trigger archiving" so you'll need to setup the cron. Please check: https://matomo.org/docs/setup-auto-archiving/

@mattab mattab closed this as completed May 31, 2018
@mattab mattab added the answered For when a question was asked and we referred to forum or answered it. label May 31, 2018
@kaplun
Copy link
Author

kaplun commented May 31, 2018

I am using the core:archive. The issue seems to be that the job is so long that it doesn't finish within one hour.
Also it leads to all sorts of memory issues with the DB. I guess this is the reason why it was been killed.

@mattab
Copy link
Member

mattab commented May 31, 2018

@kaplun I understand. We could help you make it work great (we do this for our customers of our on-premises support subscription, see: https://matomo.org/support/ ). Otherwise as a quick workaround, try running the core:archive less often

@kaplun
Copy link
Author

kaplun commented May 31, 2018

Sorry to abuse this ticket: I was wondering: if I rotate my logs after 7 days (to keep DB fit), will it still be possible to have monthly and yearly reports?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
answered For when a question was asked and we referred to forum or answered it.
Projects
None yet
Development

No branches or pull requests

2 participants