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

Wrong stats after 1.1 upgrade #1939

Closed
anonymous-matomo-user opened this issue Jan 4, 2011 · 17 comments
Closed

Wrong stats after 1.1 upgrade #1939

anonymous-matomo-user opened this issue Jan 4, 2011 · 17 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc. Critical Indicates the severity of an issue is very critical and the issue has a very high priority. duplicate For issues that already existed in our issue tracker and were reported previously.
Milestone

Comments

@anonymous-matomo-user
Copy link

I am using Piwik now since a while and must thank you for those amazing updates (again!).

Unfortunately, after the 1.1 upgrade i get totally confusing visit stats. On a normal day I get around 300-400 visits. Since this morning (i updated at 9:00 a.m.) I already have 900 visits regarding to what Piwik says (its 3:00 p.m. right now). This can't be right. However, g00gle analytics is telling me something completely different than Piwik (the normal 200 visits up to now).

I saw this now in two completely independent installations, so i assume this is a critical bug. Didn't find an open Ticket, so please excuse if this bug is already known - go ahead and delete this one.

@anonymous-matomo-user
Copy link
Author

Attachment: For instance: these visits should be counted as one visitor, right?
Screen shot 2011-01-04 at 3.12.21 PM.png

@anonymous-matomo-user
Copy link
Author

Just as a note to the developers, I've seen at least three more occurences of that in the forums:
http://forum.piwik.org/read.php?2,70446
http://forum.piwik.org/read.php?2,70483
http://forum.piwik.org/read.php?2,70446

@anonymous-matomo-user
Copy link
Author

Sorry for the duplicate, 3rd one should have been this thread http://forum.piwik.org/read.php?5,70445 from the german forum

@robocoder
Copy link
Contributor

I'm looking into it now.

@anonymous-matomo-user
Copy link
Author

Great! Let me know if I can help in any way.

@mattab
Copy link
Member

mattab commented Jan 4, 2011

Are you seeing the wrong count of visits in the Live plugin, or in the actual 'Graph of last visit' widget?

I'm sure there is a bug in the Live widget that shows the same row multiple times, but visits are not counted multiple times.

However if you also see more visits in the 'Graph of last visits' then there is definitely a bug I'm not aware of. Please confirm.

@anonymous-matomo-user
Copy link
Author

Attachment: Graph showing ultra high number of visits
visits-graph.png

@anonymous-matomo-user
Copy link
Author

Attachment: All stats are screwed
piwik-stats-sample.png

@anonymous-matomo-user
Copy link
Author

Attachment: Screenshot of the Live visitors widget
visits-live.png

@anonymous-matomo-user
Copy link
Author

It's definitely more than just the LIVE plugin. See attached Screenshots.

@mattab
Copy link
Member

mattab commented Jan 4, 2011

To all who have the issue AND are seeing non empty IP adresses:

  • can you please email: your Piwik URL, login and password
  • as well as FTP or SSH access to the Piwik files? Please dont worry we dont look at anything else and you can change the passwords when we're done!

The problem is we can't replicate the issue and many beta testers didn't have this issue. So we need direct access to your server to understand what is happening and why.

You can send details to matt att piwik.org

we'll fix this issue as soon as possible

@mattab
Copy link
Member

mattab commented Jan 5, 2011

This is a dup of #1916 - it should only affect a fraction of your visitors, but indeed this can cause visits count to really spike. I added you as CC on the other ticket so you will get notifications.

@anonymous-matomo-user
Copy link
Author

Attachment:
piwik-1.1-bugvisits.jpg

@anonymous-matomo-user
Copy link
Author

I'm sorry to reopen but this issue is not a dup of #1916.
We've got a pretty large install (about 100 websites) and since the yesterday 1.1 update, daily visit counts have tripled for all websites.
You can contact me via email for any access you might need to our DB / files.

This is critical, piwik is nearly unusable as you might guess.

@mattab
Copy link
Member

mattab commented Jan 5, 2011

webapp, is it still bad today? It seems the issue was only temporary (for about 1 day) until the new cookie format settles down.

IF you still experience the issue, you can try the new beta with the fix for #1916: http://builds.piwik.org/piwik-1.1.2b1.zip

@anonymous-matomo-user
Copy link
Author

I'm currently running some tests.
You might be right about the issue being temporary, because :

  • When making fresh visits with a cookie-clean browser, visits are ok
  • Number of visits seem to be "spiking less" today than yesterday (not sure yet about that)
  • Spikes strength seems linked to number of returning visitors
    I'll post more info soon.

Thanks a lot for your answers

@anonymous-matomo-user
Copy link
Author

Sorry for bad formating of previous entry.

After a few hours, it clearly appeared to us the problem was not solving itself. We still had a good number of new visitors not being recorded correctly (ie, being counted one visit for each action)
We did an upgrade to 1.1.2b1 (thanks), and... problem solved instantly ! We can see visit count returning to normal just the minute after the upgrade. Particularly, some random visitor who seemingly kept reloading a page, was counted as a multi-visit before the upgrade, and counted as a single visit after the upgrade, just seconds later.

Congrats for that ; I guess you were right with this ticket being a duplicate of #1916, and maybe ticket #1916 underestimated the number of users being affected. I don't know why we were, but the race condition mentioned by vipsoft in #1916 rings a bell : our piwik server has been experiencing mild slowdowns since yesterday, at the time the issue appeared.

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. Critical Indicates the severity of an issue is very critical and the issue has a very high priority. duplicate For issues that already existed in our issue tracker and were reported previously.
Projects
None yet
Development

No branches or pull requests

3 participants