Error Piwik_Db_Schema_Myisam' not found after update

First of all: Thank's for this great piece of software!

However, I get an error after automatic update:

Quote
Fatal error: Class 'Piwik_Db_Schema_Myisam' not found in /var/www/piwik/core/Db/Schema.php on line 139

Edited 2 time(s). Last edit at 02/16/2012 11:01AM by HurlyBurly.

Please upload the file again, you can get it from SVN [dev.piwik.org]

---

Please READ before posting a new topic

Search Piwik Forum & Docs - Piwik FAQ - Piwik Help - Stay tuned on the Piwik Blog. I'm on twitter & on github

New! Help : fund an AWESOME new feature for Piwik (Custom Segmentations Editor + Apply in Real Time!), we need your help!

New: Sponsor a feature or work new plugin. Contact us now with your budget, timeline, and which new feature you would like to fund we will let you know the quote.

I found out that it was an issue with APC.

@matt: thank you, but this did not work.



Edited 1 time(s). Last edit at 02/16/2012 12:28PM by HurlyBurly.

Hi

I have the same problem as this after upgrading to the latest Piwik 1.7.1.

I didn't realise that Innodb was not supported and a few weeks ago the MySQL database was converted from MyISAM to INNODB, however I have now converted it back but I still have this error:

Quote
Fatal error: Class 'Piwik_Db_Schema_Myisam' not found in /web/stats.transitionnetwork.org/piwik/core/Db/Schema.php on line 139

I did want to raise this as a bug on Trac, however I did a password recovery on [dev.piwik.org] but this results in a redirect loop which then prevents one accessing Trac, so I can't. I tried deleting the Trac cookies and also tried in Chrome (which has a better error message than Firefox):

Quote
The webpage at [url]http://dev.piwik.org/trac/prefs/account[/url] has resulted in too many redirects. Clearing your cookies for this site or allowing third-party cookies may fix the problem. If not, it is possibly a server configuration issue and not a problem with your computer.

My concern is that if issue is not a ticket then nobody is going to notice it...?

I'm not sure what to try next...

Chris

It worked for me when I removed APC. Don't ask why, I don't know.

How do you "remove APC"?

Sorry I don't know what APC is...

matt's suggestion above didn't solve the prolem.

I have tried clearing the APC opcode cache and restarting apache and this didn't change anything.

I have just tried running the cron task, this generates the following error:

Starting Piwik reports archiving...


Archiving period = day for idsite = 1...
PHP Fatal error:  Call to undefined method Piwik_Config::getInstance() in /web/stats.transitionnetwork.org/piwi
/Schema/Myisam.php on line 437

Fatal error: Call to undefined method Piwik_Config::getInstance() in /web/stats.transitionnetwork.org/piwik/cor
ma/Myisam.php on line 437

Before I updated the Myisam.php there wasn't this error.

I then switched back to the 1.7.1 Myisam.php and the cron task runs without errors.

Clearing the cache had no effect for me too. I had to remove APC completely and reinstall it. After that, everything was okay.

Quote
HurlyBurly
Clearing the cache had no effect for me too. I had to remove APC completely and reinstall it. After that, everything was okay.

Wow, that worked for me as well!

This step really shouldn't be needed should it...!

I take that back, the dashboad loaded OK once but now it's back to displaying the error the same as in the screenshot above :-(

I have created a ticket for the trac password reset bug #3048 [dev.piwik.org]

And one for this issue #3049 [dev.piwik.org]

Best follow this matter up via trac.

The trac ticket #3049 has been closed with no suggestions about how to debug or fix this problem and I don't have permissions to reopen it:

[dev.piwik.org]

In cc's case, the problem was apc settings. Disabling apc.include_once_override and setting apc.mmap_file_mask = /dev/zero did the trick.

In HurlyBurly's case, I'm guessing apc.stat is off. As a workaround, please turn apc_stat on. (This has some performance impact on the web server, but will be less problematic for the next upgrade.) We do have a fix in the next release to clear the cache after overwriting the files from the new release. Of course, this won't be apparent until the next-next update.

---

Buy me a beer. Show me some love.

Changes in the upcoming release: CHANGES