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

Jump to bottom

Database corruption #2597

Closed
anonymous-matomo-user opened this issue Jul 29, 2011 · 3 comments
Closed

Database corruption #2597

anonymous-matomo-user opened this issue Jul 29, 2011 · 3 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. worksforme The issue cannot be reproduced and things work as intended.
Milestone
1.6

Comments

@anonymous-matomo-user
Copy link

I have piwik that watch 3 sections of my site. It's SamyGO but cannot write full name due your spam filters

"Submission rejected as potential spam (Content contained these blacklisted patterns: tv)" (actually dot tv)

Anyway I have subdomains and watching statistics as a 3 different site: www wiki forum

Today I looked and saw that there is 0 people come at 28/07/2011 day to my "WEB" (www.) but when I look into detail I can see that people available at "visitor log", referrers page etc...

Also got error on "engagement" at that day.
like on #2587

I believe some database corruption occurs.
Also piwik db snapshot shrinks to 6.1MB(29/07/2011) from 9.2MB(28/07/2011) (compressed sizes)...

Weird part is, there is no problems for my forum and wiki sections statistics. If you need data, I can send my database snapshot...

Also if there is a way to repair parts from my backed up database snapshot?

Thanks
@robocoder
Copy link
Contributor

Because the session handler no longer blocks, browser-based archiving is likely to trigger the archive processing concurrency issue mentioned in #987.

Please switch to either cron-based archiving, or in core/Session.php, remove 'files' from the array, changing:

                if(in_array($currentSaveHandler, array('user', 'mm', 'files')))

to:

                if(in_array($currentSaveHandler, array('user', 'mm')))

This should resolve the archiving processing concurrency issues.

Then truncate/drop your piwik_archive_blob_* and piwik_archive_numeric_* tables, so that Piwik can regenerate them.

@robocoder
Copy link
Contributor

(In [5052]) fixes #2602, fixes #2574, refs #2548, refs #2597

@robocoder
Copy link
Contributor

(In [5065]) fixes #2548, refs #2597 - use advisory locks

@anonymous-matomo-user anonymous-matomo-user added this to the 1.6 Piwik 1.6 milestone Jul 8, 2014
@robocoder robocoder mentioned this issue Jul 31, 2011
Closed
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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. worksforme The issue cannot be reproduced and things work as intended.
Projects
None yet
Milestone
1.6
Development

No branches or pull requests
3 participants
@mattab @robocoder @anonymous-matomo-user