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

What happens when dnsmasq is restarted? #24

Closed
darron opened this issue Feb 19, 2016 · 3 comments
Closed

What happens when dnsmasq is restarted? #24

darron opened this issue Feb 19, 2016 · 3 comments

Comments

@darron
Copy link
Owner

darron commented Feb 19, 2016

Likely need to protect from stats going negative.

@darron
Copy link
Owner Author

darron commented Feb 19, 2016

Testing some code that is supposed to do this safely.

@darron
Copy link
Owner Author

darron commented Feb 19, 2016

Feb 19 17:39:19 vagrant-ubuntu-trusty-64 goshe[12001]: 2016/02/19 17:39:19 dnsmasq: Negative forwarded queries detected - dnsmasq must have been restarted.
Feb 19 17:39:19 vagrant-ubuntu-trusty-64 goshe[12001]: 2016/02/19 17:39:19 dnsmasq: Forwards: 407
Feb 19 17:39:19 vagrant-ubuntu-trusty-64 goshe[12001]: 2016/02/19 17:39:19 dnsmasq: Negative locally answered queries detected - dnsmasq must have been restarted.
Feb 19 17:39:19 vagrant-ubuntu-trusty-64 goshe[12001]: 2016/02/19 17:39:19 dnsmasq: Locally Answered: 609

Looks like it's working.

@darron darron closed this as completed in bc1a1e8 Feb 19, 2016
@darron
Copy link
Owner Author

darron commented Feb 19, 2016

If dnsmasq is stopped - goshe runs as normal and doesn't crash.

It's because:

  1. We can't find any processes to restart.
  2. The restart code handles that properly and doesn't freak out.
  3. We don't get any stats - but that's OK - we don't have to restart goshe.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant