Many thanks to Arpit for observing an extra newline in the dumped
/etc/hosts:

127.0.0.1       localhost

   asf900.ygridcore.net       *asf900*


would anyone who has administrator access please help to take a look?

Specifically, the above  should be

127.0.0.1       localhost asf900.ygridcore.net    *asf900*


It would be good to look at all hosts here
https://builds.apache.org/computer/H<idx>/

(https://builds.apache.org/computer/H0/,
https://builds.apache.org/computer/H01/ ...)

because they might have same issue.

Thanks a lot.

--Yongjun





On Thu, Jul 24, 2014 at 8:22 PM, Yongjun Zhang <yzh...@cloudera.com> wrote:

> HI,
>
> I did a test run which dumped /etc/hosts and reported hostname info:
>
> YJD */etc/hosts* contents:
>
>
> 127.0.0.1     localhost
>
>    asf900.ygridcore.net       *asf900*
>
>  # The following lines are desirable for IPv6 capable hosts
>
> ::1     localhost ip6-localhost ip6-loopback
>
> ff02::1 ip6-allnodes
>
> ff02::2 ip6-allrouters
>
>  YJD *hostname* contents:
>
> asf900
>
>
> (see HADOOP-10888
>
> https://builds.apache.org/job/PreCommit-HADOOP-Build/4362//testReport/,
>
> the host is Slave H0 (Build slave for Hadoop project builds : 
> asf900.gq1.ygridcore.net)
>
> )
>
>
> I see hostname "asf900" in "127.0.0.1" row for IPv4  but I don't see it in 
> the "::1" row for IPv6 in /etc/hosts file. I wonder if adding "asf900" as an 
> entry to "::1" row would make it work. The method stuck at is 
> java.net.Inet4AddressImpl.getLocalHostName (IPv4) though.
>
>>
> Thanks.
>
> --Yongjun
>
> On Wed, Jul 23, 2014 at 10:14 PM, Yongjun Zhang <yzh...@cloudera.com>
> wrote:
>
>> Thanks Arpit for throwing this discussion as part of HADOOP-10888
>> investigation! It's a good guess of Arpit's about possible missing
>> /etc/hosts entry.
>>
>> Please feel free to comment in HADOOP-10888 so information can be
>> centralized there.
>>
>> Best regards,
>>
>> --Yongjun
>>
>>
>>
>> On Wed, Jul 23, 2014 at 9:07 PM, Arpit Agarwal <aagar...@hortonworks.com>
>> wrote:
>>
>>> Can someone with administrator access to the Jenkins VMs please take a
>>> look
>>> at the /etc/hosts configuration?
>>>
>>> TestIPC often fails in Jenkins runs due to a timeout in
>>> InetAddress.getLocalHost. Most likely a missing entry in /etc/hosts for
>>> the
>>> system hostname.
>>>
>>> e.g.
>>>
>>> https://builds.apache.org/job/PreCommit-HADOOP-Build/4352//testReport/org.apache.hadoop.ipc/TestIPC/testRetryProxy/
>>>
>>>
>>> https://builds.apache.org/job/PreCommit-HADOOP-Build/4355/testReport/org.apache.hadoop.ipc/TestIPC/testRetryProxy/
>>>
>>>
>>> https://builds.apache.org/job/PreCommit-HADOOP-Build/4347/testReport/org.apache.hadoop.ipc/TestIPC/testRetryProxy/
>>>
>>> java.lang.Exception: test timed out after 300000 milliseconds
>>>   at java.net.Inet4AddressImpl.getLocalHostName(Native Method)
>>>   at java.net.InetAddress.getLocalHost(InetAddress.java:1374)
>>>   at org.apache.hadoop.net.NetUtils.getConnectAddress(NetUtils.java:372)
>>>   at org.apache.hadoop.net.NetUtils.getConnectAddress(NetUtils.java:359)
>>>   at
>>>
>>> org.apache.hadoop.ipc.TestIPC$TestInvocationHandler.invoke(TestIPC.java:212)
>>>   at org.apache.hadoop.ipc.$Proxy11.dummyRun(Unknown Source)
>>>   at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
>>>   at
>>>
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>   at java.lang.reflect.Method.invoke(Method.java:597)
>>>   at
>>>
>>> org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:186)
>>>   at
>>>
>>> org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:101)
>>>   at org.apache.hadoop.ipc.$Proxy11.dummyRun(Unknown Source)
>>>   at org.apache.hadoop.ipc.TestIPC.testRetryProxy(TestIPC.java:1060)
>>>
>>> Thanks,
>>> Arpit
>>>
>>> --
>>> CONFIDENTIALITY NOTICE
>>> NOTICE: This message is intended for the use of the individual or entity
>>> to
>>> which it is addressed and may contain information that is confidential,
>>> privileged and exempt from disclosure under applicable law. If the reader
>>> of this message is not the intended recipient, you are hereby notified
>>> that
>>> any printing, copying, dissemination, distribution, disclosure or
>>> forwarding of this communication is strictly prohibited. If you have
>>> received this communication in error, please contact the sender
>>> immediately
>>> and delete it from your system. Thank You.
>>>
>>
>>
>

Reply via email to