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
cURL cron auto archive terminates without reason #19675
Comments
This issue has been mentioned on Matomo forums. There might be relevant details there: https://forum.matomo.org/t/curl-based-cron-auto-archive-success-notification/47214/4 |
@JustinFinkelsteinKainos sorry for the late reply, I believe it should always print the keyword |
As @peterhashair mentioned: The archiving should in the end print an info |
@sgiehl As you mentioned, the archiving should complete with 'done' as its last output, but when it's failed, I've not seen anything in our logs to indicate a failure. Is there a "debug" flag that I could set if this fails again? |
The summary should contain either |
Expected Behavior
We have an automated cURL job which calls https://analytics/misc/cron/archive.php?token_auth=X at 5 mins past the hour, every hour to run the auto-archive process and we log the response from the request.
Our script which executes this cURL looks for the strings "Success:ok" or "Finished archiving" to identify that the script has executed correctly; if these are missing or the string "Fatal error" is found, it alerts us.
Yesterday, our script triggered an alert because the cURL completed successfully, but didn't contain the expected "Success" strings we're used to finding.
Current Behavior
Log data from the cURL is returned as follows:
Possible Solution
Can there be some clarification on when this script completes its execution successfully? This seems to have changed across versions without any clear documentation.
Steps to Reproduce (for Bugs)
This one's a bit tricky, but executing the same script should provide you some data
Context
See initial description. One other thing to note is that we've exceeded the licensing on some of our plugins and occasionally see the following show up in our logs:
This looks like Matomo is throwing an (unrelated) error when it shouldn't be.
Your Environment
The text was updated successfully, but these errors were encountered: