Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Restart OpenDKIM from time to time #495

Closed
link2xt opened this issue Feb 18, 2025 · 2 comments · Fixed by #498
Closed

Restart OpenDKIM from time to time #495

link2xt opened this issue Feb 18, 2025 · 2 comments · Fixed by #498
Assignees

Comments

@link2xt
Copy link
Contributor

link2xt commented Feb 18, 2025

OpenDKIM leaks memory, reaches 5 GB and keeps growing.

We can set WatchdocSec= (see systemd.service(5)) to restart it from time to time. And need to make sure systemd restarts the service when it is killed by watchdog.

@missytake
Copy link
Contributor

I don't think WatchdocSec= works for us; it would only trigger when opendkim stops responding, and as far as I understood it, functionality doesn't actually deteriorate.

But it seems RuntimeMaxSec= does what we want: https://stackoverflow.com/a/50332245

@adbenitez
Copy link
Contributor

adbenitez commented Feb 19, 2025

WatchdogSec would also work for restarting (I have been using it to restart DC bots every 1h etc) and it is the accepted answer in the linked SO question, but it probably makes sense to use the more modern approach

@missytake missytake self-assigned this Feb 19, 2025
missytake added a commit that referenced this issue Feb 19, 2025
fix #495

The test is not useful for CI, but can help admins figuring out if opendkim is running for longer than 1 day already.
missytake added a commit that referenced this issue Feb 19, 2025
fix #495

The test is not useful for CI, but can help admins figuring out if opendkim is running for longer than 1 day already.
missytake added a commit that referenced this issue Feb 19, 2025
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants