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
BugFor errors / faults / flaws / inconsistencies etc.MajorIndicates the severity or impact or benefit of an issue is much higher than normal but not critical.wontfixIf you can reproduce this issue, please reopen the issue or create a new one describing it.
If I comment these lines out, the reports will be generated while clicking reports in the webgui of piwik.
Deleting the archive-tables in the database doesn't solve the problem lasting.
Deleting the current archive-table has the following result:
The reports will be generated completely upto the current time with the archive.sh via cron but no new logdates will be added with the next calls of archive.sh
Best Regards Thomas
The text was updated successfully, but these errors were encountered:
BugFor errors / faults / flaws / inconsistencies etc.MajorIndicates the severity or impact or benefit of an issue is much higher than normal but not critical.wontfixIf you can reproduce this issue, please reopen the issue or create a new one describing it.
Hello,
we have set up the autoarchive-feature for high-traffic-sites described here:
http://piwik.org/docs/setup-auto-archiving/
Since the update to 0.5.5 the autoarchiver doesn't work.
/usr/local/bin/bash /var/apache/ourserver/htdocs/misc/cron/archive.sh runs whithout any errors.
Our config.ini.php:
[General]
time_before_today_archive_considered_outdated = 3600
enable_browser_archiving_triggering = false
If I comment these lines out, the reports will be generated while clicking reports in the webgui of piwik.
Deleting the archive-tables in the database doesn't solve the problem lasting.
Deleting the current archive-table has the following result:
The reports will be generated completely upto the current time with the archive.sh via cron but no new logdates will be added with the next calls of archive.sh
Best Regards Thomas
The text was updated successfully, but these errors were encountered: