I have been moved old Piwik server data to another server. Piwik with moved data seems to be work ok and old segments are working fine.
Now I have created simple index.html page to test configurations where tracking code has been set just before end of body.
I have visited yesterday on index.html page one time with IE and two times with Chrome. Visits are tracked which you can see from image.
“All visits” segment on dashboard shows that Visitor browsers are IE and Chrome and number of visits are ok. So this also proves that visits are tracked.
If I create some simple segment like “Device type Is Desktop” just to test configurations then dashboard shows only message: “There is no data for this report.”
Archiving has been set to run hourly:
#!/bin/sh MAILTO="email@example.com" 0 * * * * nginx /usr/bin/php /var/www/piwik/console core:archive --url=http://foo.baz.bar >> /piwik-log/piwik-archive-$(date +\%Y\%m\%d).log 2>> /log/piwik-archive-errors.log
Log files are not containing any errors.
If I run archiving manually like as below then segment start to work but this arching takes about 40 hours with current database (over 20M visits).
./console core:archive --force-all-websites --force-all-periods=315576000 --force-date-last-n=1000 --url=http://foo.baz.bar
Should I always run archiving with --force* attributes when I create new segment or do I have some configuration issue here?
CentOS 6.6, nginx/1.0.15, MariaDB 10.0.17, PHP-FPM 5.3.3, Piwik 2.13.1
browser_archiving_disabled_enforce = 1 enable_create_realtime_segments = 0 enable_browser_archiving_triggering = 0