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

Error: ENOENT, open '/etc/resolv.conf' #36

Open
omarvelous opened this issue Oct 3, 2014 · 7 comments
Open

Error: ENOENT, open '/etc/resolv.conf' #36

omarvelous opened this issue Oct 3, 2014 · 7 comments

Comments

@omarvelous
Copy link

This has happened randomly 3 times now, where Katon will just fail to work. Usually I do a npm uninstall and re-install and it's all good and dandy. However the last time, I just started it up, and it started working again.

This is the error that re-occures in the daemon.log

3 Oct 09:37:56 - �[31m[daemon] �[39mStart
3 Oct 09:37:56 - �[31m[daemon] �[39mLoading procs
3 Oct 09:37:56 - �[36m[procs ] �[39mAdd �[90mrealty�[39m
3 Oct 09:37:56 - �[36m[procs ] �[39mAdd �[90mroommates�[39m
3 Oct 09:37:56 - �[36m[procs ] �[39mAdd �[90mtruck�[39m
3 Oct 09:37:56 - �[31m[daemon] �[39mStarting DNS server on port 13375
3 Oct 09:37:56 - �[31m[daemon] �[39mStarting katon server on port 31000
3 Oct 09:37:56 - �[31m[daemon] �[39mDNS server started
3 Oct 09:37:56 - �[31m[daemon] �[39mKaton server started

/usr/local/lib/node_modules/katon/node_modules/native-dns/lib/platform.js:166
      throw err;
            ^
Error: ENOENT, open '/etc/resolv.conf'
@typicode
Copy link
Owner

typicode commented Oct 4, 2014

Thanks for the report, seems to be an issue with native-dns.
tjfontaine/node-dns#63

@typicode
Copy link
Owner

typicode commented Oct 6, 2014

A new version of native-dns has just been published and should fix this issue :)
I've updated katon with it (v0.6.3), should be ok now.

@typicode typicode closed this as completed Oct 8, 2014
@typicode
Copy link
Owner

typicode commented Oct 8, 2014

Still having the issue if WiFi is off. Reopening the issue.

@typicode typicode reopened this Oct 8, 2014
@typicode
Copy link
Owner

typicode commented Oct 8, 2014

I've switched to another dns server and released 0.6.5 should be ok now.

@davej
Copy link

davej commented Sep 30, 2015

Still getting this issue. @typicode it looks like you've switched back to native-dns and away from dnsjack is this intentional?

@typicode
Copy link
Owner

@davej hmm... good question, I don't really remember the all story but there was this problem: #44

In the end @assaf fixed the issue by customizing the DNS response. So I guess it's one reason native-dns is used and switching to dnsjack would be complicated.

I'm reopening the issue.

BTW, if you find a way to reproduce just let me know.

@typicode typicode reopened this Oct 12, 2015
@davej
Copy link

davej commented Oct 12, 2015

To reproduce it I just have to use katon without a network connection (i.e. turn off wifi and plug out ethernet). I changed the dependency to point to this fork https://github.com/silverwind/node-dns/ and that fixed it for me.

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

No branches or pull requests

3 participants