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

Resolve 'A thread timer expired 5.xxxxxx seconds ago' issue #2475

Merged
merged 2 commits into from
Oct 5, 2024

Conversation

pqarmitage
Copy link
Collaborator

No description provided.

Setting SO_LINGER causes the close() call to block until the first
of:
1. the ACK of the FIN is received
2. the SO_LINGER timeout expires

Since the SO_LINGER timeout was set to 5 seconds, if the FIN or the
subsequent ACK were lost, then keepalived would block for 5 seconds,
which must not be allowed to happen.

The only TCP sockets that keepalived opens are for TCP_CHECK, HTTP_GET,
SSL_GET, SMTP_CHECK and sending notify emails. For all of these, for
any data that keepalived sends it receives data in response, and so
there is no purpose in using SO_LINGER.

Removing setting SO_LINGER will stop the occasional 'A thread timer
expired 5.1nnnnn seconds ago', as reported in issue acassen#2271.

Signed-off-by: Quentin Armitage <[email protected]>
@pqarmitage pqarmitage merged commit d750f45 into acassen:master Oct 5, 2024
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant