That is definitely the behavior that I am seeing. /etc/hosts looks fine. Did you figure out how to fix it for all cases?
On Mon, Aug 12, 2013 at 11:17 PM, Chris Riccomini <[email protected]>wrote: > Hey Sriram, > > I have noticed that when I run my work laptop at home without VPN on, it > resolves its hostname to a hostname of criccomi-mn. When I try and ping > that address from the laptop, itself, I get a DNS resolution failure. If I > log into VPN, I can then ping the host as expected. > > I discovered this issue while trying to run YARN locally on my laptop. > When trying to click from the YARN RM site to the AM dashboard for a Samza > job, the page would fail with some socket issue. I discovered that it was > linking to criccomi-mn. Changing to localhost or 127.0.0.1 fixed the issue. > > I believe that the Samza AM and the JmxServer are likely using a similar > method to resolve hostnames for the local machine (InetAddress). JmxServer > does: > > val hostname = InetAddress.getLocalHost.getHostName > > SamzaAppMaster uses: > > val nodeHostString = System.getenv(ApplicationConstants.NM_HOST_ENV) > > I'm willing to bet (but haven't confirmed) that the YARN NM is using > InetAddress as well, and handing that hostname to SamzaAppMaster via the > environment variable. I wonder if this is the behavior you're seeing? > > Cheers, > Chris > > P.S. Might be double checking /etc/hosts as well. > ________________________________________ > From: sriram [[email protected]] > Sent: Monday, August 12, 2013 10:25 PM > To: [email protected] > Subject: Re: build/test failure > > The errors are different though. In my case it is to do with my > environment. This has been happening across projects so it is not specific > to Samza. > > > On Mon, Aug 12, 2013 at 9:50 PM, Tejas Patil <[email protected]> wrote: > > > I too faced problem while building it. But when I triggered the build > again > > on the same checkout, there were no failures and the build was > successful. > > It seems that there is some problem while building for the very first > time. > > Anyways, I have filed SAMZA-10 for this. > > > > https://issues.apache.org/jira/browse/SAMZA-10 > > > > > > On Mon, Aug 12, 2013 at 7:28 PM, Chris Riccomini < > [email protected] > > >wrote: > > > > > Hey Sriram, > > > > > > This sounds like a weird issue with your environment. Can you open the > > > JIRA? Would be good to get a full stack trace as well. > > > > > > I know LI has some funky subnet issues. I'm wondering: are you running > > > this over VPN? If so, it would be good to throw in a println, or debug, > > or > > > turn on test logging, so we can see what hostname is resolved to in > > > JmxServer for this test. > > > > > > Anyway, I think a JIRA is in order. This shouldn't fail. > > > > > > Cheers, > > > Chris > > > ________________________________________ > > > From: Sriram [[email protected]] > > > Sent: Monday, August 12, 2013 7:04 PM > > > To: [email protected] > > > Cc: [email protected] > > > Subject: Re: build/test failure > > > > > > I assumed this was an error during code import to open source. If not, > we > > > can go the JIRA route. > > > > > > On Aug 12, 2013, at 6:38 PM, Jakob Homan <[email protected]> wrote: > > > > > > > Can you go ahead and open a JIRA? Patches are good too. :) > > > > -Jakob > > > > > > > > > > > > On Mon, Aug 12, 2013 at 6:29 PM, sriram <[email protected]> > wrote: > > > > > > > >> I checked out the code from the open source git repo. When I tried > > > building > > > >> it, I get the error below (failed test) - > > > >> > > > >> org.apache.samza.metrics.TestJmxServer > serverStartsUp FAILED > > > >> java.net.UnknownHostException at TestJmxServer.scala:36 > > > >> Caused by: java.net.UnknownHostException at > > > TestJmxServer.scala:36 > > > >> > > > >> 14 tests completed, 1 failed > > > >> :samza-core_2.9.2:test FAILED > > > >> > > > >> FAILURE: Build failed with an exception. > > > >> > > > > > >
