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.

Sign up for GitHub

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

Jump to bottom

OTR_CLEAN_AGE default not correctly handled #500

Open
ckrey opened this issue Oct 2, 2024 · 1 comment
Open

OTR_CLEAN_AGE default not correctly handled #500

ckrey opened this issue Oct 2, 2024 · 1 comment
Labels
bug fixed

Comments

@ckrey
Copy link
Member

ckrey commented Oct 2, 2024

Feature introduced with #447 in version 0.9.8

If OTR_CLEAN_AGE is not specified (default = 0) or explicitly set to zero, the cache entries are always considered out of date, which leads to unintended reverse geo queries.

The cache is effectively invalidated 😭
@ckrey ckrey added the bug label Oct 2, 2024
@ckrey
Copy link
Member Author

ckrey commented Oct 2, 2024 •
edited by jpmens
Loading

As a workaround, add the following line to the configuration file (/etc/default/ot-recorder):

OTR_CLEAN_AGE=315360000

and restart ot-recorder

ckrey added a commit that referenced this issue Oct 2, 2024
@ckrey
[FIX] OTR_CLEAN_AGE default not correctly handled #500
76b00e4
@ckrey ckrey added the fixed label Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug fixed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ckrey