You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
a) how did you build the blob / where did you fetched it?
b) macOS version, hw version
c) can you confirm that in current tip issue persists on your setup ?
I was able to figure out that the file /etc/exports is causing the problem.
So did mv /etc/exports to /etc/exports.bak
Once I moved it to /etc/exports.bak it ran without an issue.
I don't know much about networking or why this is causing an issue.
The earlier entries in the /exports.bak file seem to have been created by vagrant
@fantastic-relations issue was that there was a locally running DNS server (ence binding :53) that was blocking corectld from finishing the startup, so no inherent breackage on our side...
So, can you please ping me too on slack to see what your issue after all :-) ?
I've gotten the same error, because I run dnscrypt. I'd like to continue running dnscrypt, while corectld runs too. Is this possible to tell corectld to skip local DNS server (I'm not sure what that would mean)? Edit: in other words, is it possible to make corectld work like it did before I updated (which was also v7, but not sure which minor version).
Also, the error message includes, “Please […] ensure that 'corectld' is running” which is a little disorienting, because the error prints when trying to run corectld. Here's my full error message (maybe helpful for google to index the other parts of the error):
[q@localhost] corectld start -d
[ERROR] Failed to connect to server
Please check your connection settings and ensure that 'corectld' is running.
panic: Failed to connect to server
Please check your connection settings and ensure that 'corectld' is running.
goroutine 1 [running]:
panic(0x4b3f380, 0xc820191780)
/usr/local/Cellar/go/1.6.3/libexec/src/runtime/panic.go:481 +0x3e6
github.com/TheNewNormal/corectl/vendor/github.com/helm/helm/log.Die(0xc82011eee0, 0x69, 0x0, 0x0, 0x0)
/private/tmp/corectl-20160803-63002-1bz84qn/corectl-0.7.15/src/github.com/TheNewNormal/corectl/vendor/github.com/helm/helm/log/log.go:46 +0xe1
main.main()
/private/tmp/corectl-20160803-63002-1bz84qn/corectl-0.7.15/src/github.com/TheNewNormal/corectl/cmd/server/main.go:77 +0x7a
@quinncomendant valid points. just plz forgive me our latency in handling them as i'll be in vacation til beggining of September with very limited connectivity. will be back to you just after i'm back.
Thanks @AntonioMeireles. In the meantime I've reverted to v0.7.0, which still works fine alongside dnscrypt (this is the last version I was using, saved locally by homebrew; I'm not saying it's the only v0.7.x version that works with local DNS).
Perhaps corectld could check if port 53 is already in use, and if so it continues to load but without DNS and displays a warning message what happened. People running a local DNS server (both dnscrypt and dnsmasq are popular amongst Mac coders) can just use corectld directly without configuring it to ignore DNS, and if they need some corectld DNS feature, they only need to stop their local DNS service first before launching corectld. This is easier than providing a DNS on/off switch, but does rely on displaying a useful warning message so the user knows why corectld DNS was enabled/disabled.
I've still been using v0.7.0, which works fine. I have been busy and haven't updated for fear that I'd get stuck with the same issue in a newer version. Do newer versions of corectld include an option to skip local DNS server?
@quinncomendant since 632c249 got merged there should be no more collisions with whatever local dns setup is present as (quoting changelog) since then instead of running our embedded name server on host's port 53 we run it on port 15353 and transparently port-forward via pf it as :53 to the VMs. this should handle most, if not all, of the "corner" cases that our user base has been hitting lately...
Activity
AntonioMeireles commentedon Jul 22, 2016
Hi! some quick questions
a) how did you build the blob / where did you fetched it?
b) macOS version, hw version
c) can you confirm that in current tip issue persists on your setup ?
Thanks in advance!
AntonioMeireles commentedon Jul 22, 2016
ok - translating a) how was your binary built ? homebrew ?
makefrom local git checkout ?AntonioMeireles commentedon Jul 22, 2016
interesting :/. will get back after your issue after my lunch break
AntonioMeireles commentedon Jul 22, 2016
hi again - plz paste here the output of
sysctl machdep.cpu.featuresthanks in advance and for your patience!
AntonioMeireles commentedon Jul 22, 2016
sysctl kern.hv_supportoutput plz ...(context is https://developer.apple.com/library/mac/documentation/DriversKernelHardware/Reference/Hypervisor/index.html :( )
AntonioMeireles commentedon Jul 22, 2016
strange , as it should work then afaict. what timezone are you on ?
AntonioMeireles commentedon Jul 22, 2016
two hrs ahead of me. will ping you monday around your 11.30 am. ok to you ?
AntonioMeireles commentedon Jul 22, 2016
you're welcome! have a great weekend!
drgeb commentedon Jul 22, 2016
I am observing the same thing! Thanks!
I was able to figure out that the file /etc/exports is causing the problem.
So did mv /etc/exports to /etc/exports.bak
Once I moved it to /etc/exports.bak it ran without an issue.
I don't know much about networking or why this is causing an issue.
The earlier entries in the /exports.bak file seem to have been created by vagrant
AntonioMeireles commentedon Jul 25, 2016
@drgeb @fantastic-relations
a quick question - did ever
corectlrun on your setups ?(trying to spot a pattern here as this is not definitivelly a general issue afaict)
also, can one of you ping me at kubernetes slack please in order to try to debug this in an affected setup ?
AntonioMeireles commentedon Jul 25, 2016
@drgeb:
@fantastic-relations issue was that there was a locally running DNS server (ence binding :53) that was blocking
corectldfrom finishing the startup, so no inherent breackage on our side...So, can you please ping me too on slack to see what your issue after all :-) ?
AntonioMeireles commentedon Jul 28, 2016
@drgeb ping (see above)
quinncomendant commentedon Aug 20, 2016
I've gotten the same error, because I run dnscrypt. I'd like to continue running dnscrypt, while corectld runs too. Is this possible to tell corectld to skip local DNS server (I'm not sure what that would mean)? Edit: in other words, is it possible to make corectld work like it did before I updated (which was also v7, but not sure which minor version).
Also, the error message includes, “Please […] ensure that 'corectld' is running” which is a little disorienting, because the error prints when trying to run corectld. Here's my full error message (maybe helpful for google to index the other parts of the error):
AntonioMeireles commentedon Aug 22, 2016
@quinncomendant valid points. just plz forgive me our latency in handling them as i'll be in vacation til beggining of September with very limited connectivity. will be back to you just after i'm back.
once again many thanks for your patience!
quinncomendant commentedon Aug 22, 2016
Thanks @AntonioMeireles. In the meantime I've reverted to v0.7.0, which still works fine alongside dnscrypt (this is the last version I was using, saved locally by homebrew; I'm not saying it's the only v0.7.x version that works with local DNS).
Perhaps corectld could check if port 53 is already in use, and if so it continues to load but without DNS and displays a warning message what happened. People running a local DNS server (both dnscrypt and dnsmasq are popular amongst Mac coders) can just use corectld directly without configuring it to ignore DNS, and if they need some corectld DNS feature, they only need to stop their local DNS service first before launching corectld. This is easier than providing a DNS on/off switch, but does rely on displaying a useful warning message so the user knows why corectld DNS was enabled/disabled.
do not mess with host's dns setup whatever they are
AntonioMeireles commentedon Nov 11, 2016
@quinncomendant is this particular issue still a problem for you ? (sorry latency, and have a great weekend)
quinncomendant commentedon Nov 12, 2016
I've still been using v0.7.0, which works fine. I have been busy and haven't updated for fear that I'd get stuck with the same issue in a newer version. Do newer versions of corectld include an option to skip local DNS server?
AntonioMeireles commentedon Nov 14, 2016
@quinncomendant since 632c249 got merged there should be no more collisions with whatever local dns setup is present as (quoting changelog) since then instead of running our embedded name server on host's port 53 we run it on port 15353 and transparently port-forward via
pfit as :53 to the VMs. this should handle most, if not all, of the "corner" cases that our user base has been hitting lately...Please check if this fully covers your use cases :-)
quinncomendant commentedon Nov 14, 2016
I have updated to version 0.7.18 and it works great. Thank you!
AntonioMeireles commentedon Nov 14, 2016
closing per @quinncomendant's latest feedback.