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

CLI Archiver does not execute record updated component #13017

Closed
tsteur opened this issue May 31, 2018 · 1 comment · Fixed by #13102
Closed

CLI Archiver does not execute record updated component #13017

tsteur opened this issue May 31, 2018 · 1 comment · Fixed by #13102
Assignees
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Milestone

Comments

@tsteur
Copy link
Member

tsteur commented May 31, 2018

When an update is available for Matomo and the files have been update, but the UI hasn't been loaded yet, the archiver shows the following error:

ERROR [2018-05-30 23:51:37] 1842966 Got invalid response from API request: ?module=API&method=API.get&idSite=13320&period=week&date=last3&format=php&trigger=archivephp. Response was 'a:2:{s:6:"result";s:5:"error";s:7:"message";s:160:"Piwik and/or some plugins have been upgraded to a new version. --> Please run the update process first. See documentation: https://matomo.org/docs/update/ ";}'

Even when there is no Update to be executed and it could record the new component version basically.

I totally understand it shouldn't execute any DB updates or other updates, but when there is no update available it should not fail.

Currently, it looks like it is needed to visit the UI afterwards.

@tsteur tsteur added the Bug For errors / faults / flaws / inconsistencies etc. label May 31, 2018
@mattab
Copy link
Member

mattab commented May 31, 2018

@tsteur this is quite important to fix this soon, if i understand correctly. so I set the milestone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants