Archiving/reporting issues after upgrading to 2.3.0


#1

Piwik is still recording hits, I can see the data inthe database as well as in the ‘visitor log’, ‘keyword’, areas, etc on the Piwik UI BUT the ‘Pages’ (ACTION) widgets/data is not loading.

Also not ALL websites (we have 17) data for June to date is showing under ‘all websites’. (I’m guessing this is because the archiving is not running/reprocessing). Some appear with data, others appear as ‘0’.

I’m not sure if this is all the result of a time-out somewhere or file permissions on the server resulting in time outs.

I can’t find any errors as such. Where is the best place to check.

Lynn


(Matthieu Aubry) #2

Setup cron archiving as explained here: How to Set up Auto-Archiving of Your Reports - Analytics Platform - Matomo
if after 24 hours you still see “no data” for some websites etc. try this: How do I reprocess all websites, all dates and all periods, after initial import of logs? - Analytics Platform - Matomo

if not you will have to re-process data (there is a faq for it)


#3

Thanks Matt. We’re trying to re-archive/re-process but it’s taking hours. It’s been running since 9h30 CEST and is still running on siteid 5 of 17 at 16h34 CEST.

One thing I did find odd after activing the DBstats plugin under ‘Report Tables’ is that the data we are struggling to see in the UI is contained in the blob/archive for June 2014 which seems to have an extremly high row count of 5,583,979 & size of 2.8GB while in general the size blobs is around 642MB with row count of 1,770,941.

Should I just remove the June 2014 archive tables & just run June from scratch even though it takes so terrible long?

thanks
Lynn


#4

At the end of the run we get the attached & piwik is not functioning.

this is in the archive log:

“NFO CoreConsole[2014-07-02 15:51:43] [7efd7] Archived website id = 9, period = month, 14231 visits in last 2 months, 771 visits this month, Time elapsed: 160.535s
ERROR CoreConsole[2014-07-02 16:48:54] [7efd7] Got invalid response from API request: http://mysite/index.php?module=API&method=API.get&idSite=9&period=year&date$
INFO CoreConsole[2014-07-02 16:48:54] [7efd7] Archived website id = 9, period = year, 0 visits in last 2 years, 0 visits this year, Time elapsed: 3430.666s
INFO CoreConsole[2014-07-02 16:48:54] [7efd7] Archived website id = 9, 4 API requests, Time elapsed: 3651.497s [4/12 done]
ERROR CoreConsole[2014-07-02 16:48:56] [7efd7] Got invalid response from API request: http://mysite/index.php?module=API&method=API.get&idSite=10&period=day&date$
INFO CoreConsole[2014-07-02 16:48:56] [7efd7] WARNING: Empty or invalid response ‘’ for website id 10, Time elapsed: 2.104s, skipping
ERROR CoreConsole[2014-07-02 16:48:57] [7efd7] Got invalid response from API request: http://mysite/index.php?module=API&method=API.get&idSite=12&period=day&date$
INFO CoreConsole[2014-07-02 16:48:57] [7efd7] WARNING: Empty or invalid response ‘’ for website id 12, Time elapsed: 0.691s, skipping
ERROR CoreConsole[2014-07-02 16:48:58] [7efd7] Got invalid response from API request: http://mysite/index.php?module=API&method=API.get&idSite=13&period=day&date$
INFO CoreConsole[2014-07-02 16:48:58] [7efd7] WARNING: Empty or invalid response ‘’ for website id 13, Time elapsed: 0.680s, skipping
ERROR CoreConsole[2014-07-02 16:48:58] [7efd7] Got invalid response from API request: http://mysite/index.php?module=API&method=API.get&idSite=16&period=day&date$
INFO CoreConsole[2014-07-02 16:48:59] [7efd7] WARNING: Empty or invalid response ‘’ for website id 16, Time elapsed: 0.655s, skipping
ERROR CoreConsole[2014-07-02 16:48:59] [7efd7] Got invalid response from API request: http://mysite/index.php?module=API&method=API.get&idSite=18&period=day&date$
INFO CoreConsole[2014-07-02 16:48:59] [7efd7] WARNING: Empty or invalid response ‘’ for website id 18, Time elapsed: 0.697s, skipping
ERROR CoreConsole[2014-07-02 16:49:00] [7efd7] Got invalid response from API request: http://mysite/index.php?module=API&method=API.get&idSite=19&period=day&date$
INFO CoreConsole[2014-07-02 16:49:00] [7efd7] WARNING: Empty or invalid response ‘’ for website id 19, Time elapsed: 0.678s, skipping
ERROR CoreConsole[2014-07-02 16:49:01] [7efd7] Got invalid response from API request: http://mysite/index.php?module=API&method=API.get&idSite=20&period=day&date$
INFO CoreConsole[2014-07-02 16:49:01] [7efd7] WARNING: Empty or invalid response ‘’ for website id 20, Time elapsed: 0.556s, skipping
ERROR CoreConsole[2014-07-02 16:49:01] [7efd7] Got invalid response from API request: http://mysite/index.php?module=API&method=API.get&idSite=21&period=day&date$
INFO CoreConsole[2014-07-02 16:49:01] [7efd7] WARNING: Empty or invalid response ‘’ for website id 21, Time elapsed: 0.600s, skipping
INFO CoreConsole[2014-07-02 16:49:01] [7efd7] Done archiving!
INFO CoreConsole[2014-07-02 16:49:01] [7”


#5

In the apache error log:

"


There is an error. Please report the message (Piwik 2.3.0)
and full backtrace in the Piwik forums (please do a Search first as it might h$
Warning:
session_write_close(): write failed: No space left on device (28) in /var/www/libs/Zend/Session.php on line 691</$


Backtrace -->


#0 Piwik\Error::errorHandler(…) called at [:]

#1 session_write_close(…) called at [/var/www/libs/Zend/Session.php:691]

#2 Zend_Session::writeClose(…) called at [:]


There is an error. Please report the message (Piwik 2.3.0) and full backtrace in the Piwik forums (plea[Wed Jul 02 21:54:42 2014] [notice$ [Wed Jul 02 21:57:09 2014] [notice] Apache/2.2.22 (Ubuntu) PHP/5.3.10-1ubuntu3.12 with Suhosin-Patch configured -- resuming normal operations
There is an error. Please report the message (Piwik 2.3.0) and full backtrace in the Piwik forums (please do a Search first as it might h$ Warning: unlink(/var/www/tmp/assets/asset_manager_global_css.css): No such file or directory in /var/www/core/AssetManager/UIAsset/OnDiskUI$

Backtrace -->

#0 Piwik\Error::errorHandler(...) called at [:]
#1 unlink(...) called at [/var/www/core/AssetManager/UIAsset/OnDiskUIAsset.php:61]
#2 Piwik\AssetManager\UIAsset\OnDiskUIAsset->delete(...) called at [/var/www/core/AssetManager.php:369]
#3 Piwik\AssetManager->removeAssets(...) called at [/var/www/core/AssetManager.php:244]
#4 Piwik\AssetManager->removeMergedAssets(...) called at [/var/www/core/Filesystem.php:27]
#5 Piwik\Filesystem::deleteAllCacheOnUpdate(...) called at [/var/www/plugins/Installation/Controller.php:85]
#6 Piwik\Plugins\Installation\Controller->welcome(...) called at [:]
#7 call_user_func_array(...) called at [/var/www/core/FrontController.php:500]
#8 Piwik\FrontController->doDispatch(...) called at [/var/www/core/FrontController.php:85]
#9 Piwik\FrontController->dispatch(...) called at [/var/www/plugins/Installation/Installation.php:87]
#10 Piwik\Plugins\Installation\Installation->dispatch(...) called at [:]
#11 call_user_func_array(...) called at [/var/www/core/EventDispatcher.php:98]
#12 Piwik\EventDispatcher->postEvent(...) called at [/var/www/core/Piwik.php:766]
#13 Piwik\Piwik::postEvent(...) called at [/var/www/core/FrontController.php:301]
#14 Piwik\FrontController->init(...) called at [/var/www/core/dispatch.php:33]
#15 require_once(...) called at [/var/www/index.php:47]



(Matthieu Aubry) #6

@lynn that’s a surprising error. To workaround this problem please try to enable database sessions as explained here:

i think this should fix it!How do I use the database to store session files, instead of storing sessions in files? - Analytics Platform - Matomo


#7

Finally our site is up & running again.

It seems the 2.3.0 & 2.4.0 version needed a huge amount of additonal disk space to reprocess the data only for June (which is strange). We upped our disk size & that seemed to allow the archiving to run correctly.

L