-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Setting a very high value for "Delete logs older than (days)" causes archiving issues #20927
Comments
@Starker3 What exactly doesn't work in this case? The output above seems correct. It didn't invalidate any newer data and also didn't invalidate any old data. Did you run core:archive command? |
@sgiehl The issue is that with such a high value for some reason it never invalidates any data. In this specific case the user didn't get any new reports generated for several weeks since setting this. So i.e. there was no report data since the beginning of the month and the above output was shown in the core:archive command. The same was output for each ID Site that was tried to process:
|
A guess would be that such high number overflows somewhere or the date conversion goes back to unsupported date range such as before the start of the unix epoch, causing some (possibly silent) error somewhere, preventing the archiving from running correctly. Another thing I see weird is the "180 days or 365 years" suggestion, probably should be both days. |
Let's simply disallow all values that would be bigger than e.g. 5 years or so. |
It seems that setting an incredibly high value for the option
Delete logs older than (days)
Results in the archiver not being able to invalidate and process reports. For example setting this to
4000000000000
results in:The text was updated successfully, but these errors were encountered: