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

Cronarchiving API error should be stderr and not stdout #13306

Closed
fdellwing opened this issue Aug 17, 2018 · 2 comments
Closed

Cronarchiving API error should be stderr and not stdout #13306

fdellwing opened this issue Aug 17, 2018 · 2 comments
Labels
worksforme The issue cannot be reproduced and things work as intended.

Comments

@fdellwing
Copy link
Contributor

See: https://forum.matomo.org/t/geoip2-libmaxminddb-maxmind-db-reader-php-c-module-performance/29534/12

INFO [2018-08-17 09:39:56] 14195 Error: Got invalid response from API request: ?module=API&method=API.get&idSite=1&period=year&date=last3&format=php&trigger=archivephp. Response was ‘a:2:{s:6:“result”;s:5:“error”;s:7:“message”;s:113:“Mysqli prepare error: Table ‘piwik.piwik_archive_blob_2018_02’ doesn’t exist in engine - caused by plugin Actions”;}’

This should be also written to STDERR instead of only to STDOUT to allow sending it via cron mail.

@mattab
Copy link
Member

mattab commented Aug 17, 2018

In 3.6.0 RC the script will now return an error code of 1. Maybe this would fix the issue for you as well, as it will cause cron emails to be sent

@fdellwing
Copy link
Contributor Author

fdellwing commented Aug 17, 2018

Should be enough to be happy, I think. But need to test it first.

@mattab mattab closed this as completed Dec 24, 2019
@mattab mattab added the worksforme The issue cannot be reproduced and things work as intended. label Dec 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
worksforme The issue cannot be reproduced and things work as intended.
Projects
None yet
Development

No branches or pull requests

2 participants