-
Notifications
You must be signed in to change notification settings - Fork 2k
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
java.lang.IllegalArgumentException: \etc\resolv.conf didn't provide any name servers #2204
Comments
system is win 10 1704 |
thanks for reporting, can you trace the code and understand why UnixResolverDnsServerAddressStreamProvider is used ? |
my system is Windows,but there is a error appear that is \etc\resolv.conf didn't provide any name servers,
|
I'm rather wondering why UnixResolverDnsServerAddressStreamProvider is used at all given that windows is not an unix system |
I have getted used to Windows development |
I'm not saying that :-) , I'm just asking you, if by chance you could debug the source code on your machine to understand why UnixResolverDnsServerAddressStreamProvider is used in your particular case as it does not seem to happen on other windows. |
ok thank you |
@shenzhenMirren have u fixed this? this function is not supposed on windows but i also wonder know to fix this... thanks a lot |
…indows. Motivation: We should not try to use UnixResolverDnsServerAddressStreamProvider when on Windows as it will log some error that will produce noise and may confuse users. Modifications: Just use DefaultDnsServerAddressStreamProvider if windows is used. Result: Less noise in the logs. This was reported in vert.x: eclipse-vertx/vert.x#2204
@vietj @dreamkidd @shenzhenMirren this is a bug in netty: netty/netty#7403 |
@shenzhenMirren @normanmaurer @vietj |
thanks @normanmaurer for the heads-up |
…indows. Motivation: We should not try to use UnixResolverDnsServerAddressStreamProvider when on Windows as it will log some error that will produce noise and may confuse users. Modifications: Just use DefaultDnsServerAddressStreamProvider if windows is used. Result: Less noise in the logs. This was reported in vert.x: eclipse-vertx/vert.x#2204
@dreamkidd I'm using version 3.4.2 now, but to solve this problem, you can use If fat-jar is started, |
…indows. Motivation: We should not try to use UnixResolverDnsServerAddressStreamProvider when on Windows as it will log some error that will produce noise and may confuse users. Modifications: Just use DefaultDnsServerAddressStreamProvider if windows is used. Result: Less noise in the logs. This was reported in vert.x: eclipse-vertx/vert.x#2204
when I use version 3.5 vertx,it always appears
java.lang.IllegalArgumentException: \etc\resolv.conf didn't provide any name servers,my system is Windows ,
so I want to ask reason,why?
`
2017-11-09 17:45:33 --> failed to parse /etc/resolv.conf and/or /etc/resolver
----------------------> at io.netty.util.internal.logging.Slf4JLogger.debug(Slf4JLogger.java:86)
java.lang.IllegalArgumentException: \etc\resolv.conf didn't provide any name servers
at io.netty.resolver.dns.UnixResolverDnsServerAddressStreamProvider.(UnixResolverDnsServerAddressStreamProvider.java:98)
at io.netty.resolver.dns.UnixResolverDnsServerAddressStreamProvider.(UnixResolverDnsServerAddressStreamProvider.java:124)
at io.netty.resolver.dns.UnixResolverDnsServerAddressStreamProvider.parseSilently(UnixResolverDnsServerAddressStreamProvider.java:66)
at io.netty.resolver.dns.DnsServerAddressStreamProviders.(DnsServerAddressStreamProviders.java:28)
at io.netty.resolver.dns.DnsNameResolverBuilder.(DnsNameResolverBuilder.java:54)
at io.vertx.core.impl.resolver.DnsResolverProvider$1$1.newNameResolver(DnsResolverProvider.java:137)
at io.netty.resolver.dns.DnsAddressResolverGroup.newResolver(DnsAddressResolverGroup.java:86)
at io.netty.resolver.dns.DnsAddressResolverGroup.newResolver(DnsAddressResolverGroup.java:73)
at io.netty.resolver.AddressResolverGroup.getResolver(AddressResolverGroup.java:69)
at io.vertx.core.impl.resolver.DnsResolverProvider$1.newResolver(DnsResolverProvider.java:184)
at io.netty.resolver.AddressResolverGroup.getResolver(AddressResolverGroup.java:69)
at io.vertx.core.impl.AddressResolver.resolveHostname(AddressResolver.java:83)
at io.vertx.core.impl.VertxImpl.resolveAddress(VertxImpl.java:766)
at io.vertx.core.net.impl.AsyncResolveConnectHelper.doBind(AsyncResolveConnectHelper.java:87)
at io.vertx.core.http.impl.HttpServerImpl.listen(HttpServerImpl.java:344)
at io.vertx.core.http.impl.HttpServerImpl.listen(HttpServerImpl.java:226)
at verticle.MainVerticle.start(MainVerticle.java:15)
at io.vertx.core.AbstractVerticle.start(AbstractVerticle.java:111)
at io.vertx.core.impl.DeploymentManager.lambda$doDeploy$10(DeploymentManager.java:481)
at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:344)
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:403)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:463)
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
at java.lang.Thread.run(Unknown Source)
`
The text was updated successfully, but these errors were encountered: