-
Notifications
You must be signed in to change notification settings - Fork 5
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
dnsmasq Pod locks on infra-ops server #503
Comments
Happened before Resorted to the same non-fix as before: |
and again |
Happened again ~ 7th July |
Happened again Friday 23rd July |
Happened again, between 7th and 9th Aug |
Happened again ~17th Aug |
Happened again ~11th Sept |
Happened again ~14th Sept |
Happened ~ 20th Sept |
After time
dnsmasq
becomes unresponsive on the infra-ops server.Direct requests to the DNS service timeout:
Booting
dnsmasq
with aSIGHUP
signal doesn't solve the problem.Restarting the Pod on the infra-ops server makes it go away.
Direct requests to the DNS service work fine:
The text was updated successfully, but these errors were encountered: