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

Live plug-in user time limit of 18h 12m #2650

Closed
anonymous-matomo-user opened this issue Sep 7, 2011 · 6 comments
Closed

Live plug-in user time limit of 18h 12m #2650

anonymous-matomo-user opened this issue Sep 7, 2011 · 6 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Milestone

Comments

@anonymous-matomo-user
Copy link

I'm operating a few webcam sites where a few unpolite visitors reload the start pages many thousand times. In the 1.5.1 Live! plug-in, I've spotted an unexpected 'visiting time ceiling' of 18 hours 12 minutes. Visits longer then that still seem to be analyzed/processed correctly. It's just the time in the table header that clips.
Keywords: Live plug-in

@mattab
Copy link
Member

mattab commented Sep 10, 2011

Can you please post screenshots of the bug, and also show the log_visit rows for these visitors? Thank you

@anonymous-matomo-user
Copy link
Author

Piwik screenshots of two huge sessions, both erroneously ending after 18h 12m:
[http://www.marienplatz-muenchen.de/optonline_piwik1.png]
[http://www.marienplatz-muenchen.de/optonline_piwik2.png]
Hundreds of similar pages are following after the first ones...

Logfile accross both sessions (and a few more short ones) filtered to that visitor's IP:
[http://www.marienplatz-muenchen.de/optonline_stripped.log]
These are accesses to / only, all child accesses have been stripped.

@anonymous-matomo-user
Copy link
Author

18h 12m 15s equals 65535s - which is exactly (2^16)-1

@mattab
Copy link
Member

mattab commented Sep 13, 2011

OK, I think this is an acceptable bug. Otherwise we could maybe rename it to "More than 18h 12min" ?

@sgiehl
Copy link
Member

sgiehl commented Sep 13, 2011

I guess the problem is the database definition. In the log_visit table the field visit_total_time is a smallint(5). Well, smallint can't store values above 65535. We could change the fieldtype to int, that would fix this problem.

@mattab
Copy link
Member

mattab commented Sep 27, 2011

Sorry, I prefer marking this one as a "known documented display bug" rather than increase the field size to BIGINT which would have performance overhead. It is not common for piwik to track visitors for more than 18h, since it sounds like a bot and we generally exclude bots. in fact maybe this bot should not be tracked via IP exclusion or upcoming user agent exclusion... #2375

@anonymous-matomo-user anonymous-matomo-user added this to the 1.6 Piwik 1.6 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

3 participants