@cupracer opened this Issue on October 31st 2014

Hi,

in the past I received some error messages during the archive job, like:
"Adding a subtable to the row, but it already has a subtable associated."

I created an issue report for this (#5087) and was referred to #4528.
Today I noticed that there was a code change in Piwik 2.8.3 which may
lead to more information about that issue.

So, after upgrading to Piwik 2.8.3 and during archiving, I noticed a
different error message. Here's the current log output:

ERROR CoreConsole[2014-10-31 08:27:53] [b7241] Got invalid response from API request: http://MYPIWIKURL/index.php?module=API&method=API.get&idSite=33&period=week&date=last248&format=php&token_auth=aa76d97ca3f812780478bbcd298c148d&trigger=archivephp. Response was 'WARN Actions[2014-10-31 08:25:35] [68f71] Row with label '-1' (columns = -1, 197511, 219549, 4355103, 170, 0, 0, , , 23397, 83090, 4682195, 12734, 22444) has already a subtable id=1839 but it was not loaded - overwriting the existing sub-table. a:2:{s:6:"result";s:5:"error";s:7:"message";s:193:"This report has been reprocessed since your last click. To see this error less often, please increase the timeout value in seconds in Settings > General Settings. (error: id 1557 not found).";}'

ERROR CoreConsole[2014-10-31 08:27:53] [b7241] Got invalid response from API request: http://MYPIWIKURL/index.php?module=API&method=API.get&idSite=33&period=week&date=last248&format=php&token_auth=aa76d97ca3f812780478bbcd298c148d&trigger=archivephp. Response was 'WARN Actions[2014-10-31 08:25:35] [68f71] Row with label '-1' (columns = -1, 197511, 219549, 4355103, 170, 0, 0, , , 23397, 83090, 4682195, 12734, 22444) has already a subtable id=1839 but it was not loaded - overwriting the existing sub-table. a:2:{s:6:"result";s:5:"error";s:7:"message";s:193:"This report has been reprocessed since your last click. To see this error less often, please increase the timeout value in seconds in Settings > General Settings. (error: id 1557 not found).";}'

Maybe this new information helps you to understand the cause of this error.
If more information is required, I'm willing to support you.

Thanks in advance!
Thomas

@mattab commented on December 18th 2014 Owner

HI @CupRacer this should be fixed in #3414

This Issue was closed on December 18th 2014
Powered by GitHub Issue Mirror