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

archive.sh memory issue with yearly reports, works when archiving months separately #1540

Closed
anonymous-matomo-user opened this issue Jul 31, 2010 · 6 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Milestone

Comments

@anonymous-matomo-user
Copy link

line 75 in archive.sh (from piwik 0.8) reads

for period in day week year; do

but probably should read

for period in day week month year; do

@mattab
Copy link
Member

mattab commented Jul 31, 2010

year processes months

@anonymous-matomo-user
Copy link
Author

well, in my case, it didn't.

first of all, before i added "month" to the for loop, my monthy reports would run into a "maximum memory size exceeded" error, after adding it and running archive.sh again this error disappeared.

secondly, attached are two outputs of archive.sh, one with "month" added an one without, there is a significant difference in the two outputs.

@anonymous-matomo-user
Copy link
Author

Attachment: archive.sh output with month added
archive.sh.output-month

@anonymous-matomo-user
Copy link
Author

Attachment: archive.sh output without month (from distribution .zip)
archive.sh.output-nomonth

@mattab
Copy link
Member

mattab commented Jul 31, 2010

interesting that it helped to run monthly archives first. It actually makes sense. However, I confirm that in a normal use case this is not necessary.

@mattab
Copy link
Member

mattab commented Jul 31, 2010

(In [2837]) Fixes #1540
Thanks for the tip gereon_s

@anonymous-matomo-user anonymous-matomo-user added this to the Piwik 0.9 - Surviving The Wild milestone Jul 8, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Projects
None yet
Development

No branches or pull requests

2 participants