java.net.UnknownHostException: ip-10-15-80-156: ip-10-15-80-156: unknown error


Samebug tips

When kafka creates new consumers, it simply concatenate the name of your VM to generate the consumer id. So, your VM resolves localhost as the name of your VM, not whatever you had set. To solve, add kafka(or the name of VM) plus address to /etc/hosts


6 months ago
Expert tip

Solutions on the web

Solution icon of github
ip-10-15-80-156: ip-10-15-80-156: unknown error

Solution icon of googlegroups
via Google Groups by soma srikanth, 11 months ago
ip-10-212-142-227: ip-10-212-142-227: unknown error

Solution icon of apache
via samza-dev by Manohar Reddy, 1 year ago
ip-10-252-1-235: ip-10-252-1-235: unknown error

Solution icon of apache
via samza-dev by Navina Ramesh, 1 year ago
ip-10-252-1-235: ip-10-252-1-235: unknown error

Solution icon of github
via GitHub by NareshDealer
, 1 year ago
ip-10-102-0-114: ip-10-102-0-114: unknown error

Solution icon of github
via GitHub by opendedup
, 1 year ago
ip-10-102-0-114: ip-10-102-0-114: unknown error

Solution icon of github
via GitHub by axcesstech
, 11 months ago
ip-10-0-0-111: ip-10-0-0-111: unknown error

Solution icon of github
ip-10-0-63-225: ip-10-0-63-225: unknown error

Solution icon of github
ip-10-29-121-116: ip-10-29-121-116: unknown error

Solution icon of github
ip-10-10-1-151: ip-10-10-1-151

Stack trace

java.net.UnknownHostException: ip-10-15-80-156: ip-10-15-80-156: unknown error
	at java.net.InetAddress.getLocalHost(InetAddress.java:1484)[na:1.8.0_40]
	at org.elasticsearch.common.network.NetworkUtils.<clinit>(NetworkUtils.java:55)[supply-server-0.0.1-SNAPSHOT.jar:na]
	at org.elasticsearch.transport.netty.NettyTransport.createClientBootstrap(NettyTransport.java:350)[supply-server-0.0.1-SNAPSHOT.jar:na]
	at org.elasticsearch.transport.netty.NettyTransport.doStart(NettyTransport.java:250)[supply-server-0.0.1-SNAPSHOT.jar:na]
	at org.elasticsearch.common.component.AbstractLifecycleComponent.start(AbstractLifecycleComponent.java:85)[supply-server-0.0.1-SNAPSHOT.jar:na]
	at org.elasticsearch.transport.TransportService.doStart(TransportService.java:91)[supply-server-0.0.1-SNAPSHOT.jar:na]
	at org.elasticsearch.common.component.AbstractLifecycleComponent.start(AbstractLifecycleComponent.java:85)[supply-server-0.0.1-SNAPSHOT.jar:na]
	at org.elasticsearch.client.transport.TransportClient.<init>(TransportClient.java:189)[supply-server-0.0.1-SNAPSHOT.jar:na]
	at org.elasticsearch.client.transport.TransportClient.<init>(TransportClient.java:123)[supply-server-0.0.1-SNAPSHOT.jar:na]
	at io.dropwizard.elasticsearch.managed.ManagedEsClient.<init>(ManagedEsClient.java:51)[supply-server-0.0.1-SNAPSHOT.jar:na]
	at com.appirio.service.supply.SupplyServerApplication.run(SupplyServerApplication.java:95)[supply-server-0.0.1-SNAPSHOT.jar:na]

Write tip

You have a different solution? A short tip here would help you and many other users who saw this issue last week.

Users with the same issue

5 times, 2 months ago
2 times, 4 months ago
2 times, 10 months ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
10 more bugmates