@anonymous-piwik-user opened this Issue on April 14th 2010


we have set up the autoarchive-feature for high-traffic-sites described here:

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:

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

@anonymous-piwik-user commented on April 26th 2010

Works for me: The archiver script runs fine since 0.5.5 on three Piwik installations with high traffic.

@robocoder commented on April 26th 2010 Contributor

This might be addressed already in the 0.6rc1 release candidate.

@mattab commented on April 30th 2010 Member

This bug was probably fixed in 0.6-rc1. Please update and try this version.

This Issue was closed on April 30th 2010
Powered by GitHub Issue Mirror