Error in Widgets:

[dev-101]

complete message:

The Piwik configuration file couldn't be found and you are trying to access a Piwik page.
   You can install Piwik now
If you installed Piwik before and have some tables in your DB, don't worry, you can reuse the same tables and keep your existing data!

It appears randomly on Keywords, Refferer Websites, Visitor Map and Visitor Browser widgets (sometimes on all 3, sometimes on 2, but always at least in 1 widget with each Dashboard access). I have tried to reduce number of widgets to those 4-5, and removed non-essential ones.

This was (almost) never happening with Piwik 1.12 or 2.2.0 (maybe once or twice on a single widget, IIRC), but after automatic update from 2.2.0 to 2.2.2 (without any errors), this is now a regular occurence.

This issue is old and well-known (according to quick search), and something probably changed in communication with the database since 2.2.0, that now triggers this behaviour frequently (widget, ajax calls, related possibly to sql concurrency settings etc.)
Keywords: Piwik, configuration, file

[mattab]

Thanks for the report. If you go to Settings > System check, do you see any warning there?

[dev-101]

Well, nothing out of ordinary, this is a basic free shared hosting account (also they recently upgraded specs so it is much faster); php 5.4.26 and website has less than 300 page views per month (my visits excluded), so I am using it as a testing ground before deploying things to other sites. Now, same warnings were present in 2.2.0 (and in 1.12), but here they are:

1
File integrity -- this is because of my manual update -- see issue #5026

File size mismatch: piwik/core/Twig.php (expected length: 10465, found: 11172)
File size mismatch: piwik/plugins/Live/templates/_actionsList.twig (expected length: 7713, found: 7848)

(This is NOT the cause of making my hyperlinks all red, and this is NOT the cause of widget bug. Reverted back these 2 files & confirmed it is still happening. )

2
Memory limit 71M
On a high traffic website, the archiving process may require more memory than currently allowed. If necessary, change the memory_limit directive in your php.ini file. After making this change, restart your web server.

3
set_time_limit
On a high traffic website, executing the archiving process may require more time than currently allowed. If necessary, change the max_execution_time directive in your php.ini file.

4
LOAD DATA INFILE

Using LOAD DATA INFILE will greatly speed Piwik's archiving process up. To make it available to Piwik, try updating your PHP & MySQL software and make sure your database user has the FILE privilege.

[dev-101]

Btw, forgot to mention that I have another website with 5x higher visitor traffic, and the very same hosting company/specs, but with 'older' Piwik 2.2.0 and this is never happening.

That is why I am sure it is update to 2.2.2 (or changes I skipped from 2.2.1) is the cause of it.

Regards

[mattab]

That is why I am sure it is update to 2.2.2 (or changes I skipped from 2.2.1) is the cause of it.

Well you can never be sure of things like this. Maybe your host is testing new things on your server, maybe they enabled NFS, or maybe there are dozens of possible things that could go wrong.

This particular bug you are seeing is not a bug in Piwik: piwik just cannot find or read the config file. So it's a web host or maybe config error... good luck for finding it, and feel free to post here any more info or if you find the solution.

[dev-101]

Hi,
ok, I will wait for the next major release and install it from scratch to see how it goes (but, update went without any wornings, though).

In the meantime, I have deleted 2.2.2 and reinstalled 2.2.0 again (thankfully database is compatible, just manually had to switch version fields, since I didn't have the latest backup) and it works again as it should.

Regards Matt

[mattab]

Oh so when you revert code to 2.2.0 it works again all the time? then maybe this is a real regression / bug in 2.2.2. if you have more info please post here, thanks!

[dev-101]

Hi Matt,

Yes, definitely. As I already stated in my comment 3, I do have another website on the very same hosting service, which is a bit more popular, and Piwik 2.2.0 works fine there.

I can only guess that this changes from Piwik 2.2.1 changelog have something to do with it, but my database knowledge is very limited:

Piwik 2.2.1 what's new
#5035 Archiving should trigger limited number of concurrent requests
#4946 import_logs.py fail to populate actions/page tables
#4989 Database is sometimes not initialised correctly after a fresh install

---

Regards