This is what nslookup 127.0.0.1 brings up for me: Server: 172.16.1.2 Address: 172.16.1.2#53
1.0.0.127.in-addr.arpa name = localhost. On Wed, Jun 12, 2013 at 3:54 PM, Chiradeep Vittal < chiradeep.vit...@citrix.com> wrote: > I have the same configuration (Mac OS X Lion) but do not see the issue. > Wonder what > nslookup 127.0.0.1 shows on your host. > > > > On 6/12/13 2:39 PM, "Mike Tutkowski" <mike.tutkow...@solidfire.com> wrote: > > >Ah, too bad. :) > > > >So, it's not a huge deal. I just thought if we already had a solution out > >there that I missed that maybe I could implement it. > > > >I would consider it a low-priority issue. > > > >Thanks! > > > > > >On Wed, Jun 12, 2013 at 3:34 PM, Sheng Yang <sh...@yasker.org> wrote: > > > >> I've added clean, still unable to reproduce. > >> > >> If we can reproduce it in Eclipse, then it would be very easy to track > >>down > >> what's wrong indeed. Otherwise we may need to print debug info > >>everywhere. > >> > >> --Sheng > >> > >> > >> On Wed, Jun 12, 2013 at 2:16 PM, Mike Tutkowski < > >> mike.tutkow...@solidfire.com> wrote: > >> > >> > In my case, I see it when running > >> > > >> > mvn -P developer,systemvm clean install > >> > > >> > from the Terminal in Mac OS X. > >> > > >> > Removing clean seems to give it a better shoot at not halting. > >> > > >> > > >> > On Wed, Jun 12, 2013 at 3:11 PM, Sheng Yang <sh...@yasker.org> wrote: > >> > > >> > > Eclipse didn't complain for me. > >> > > > >> > > BTW: I am using Linux as development environment. > >> > > > >> > > --Sheng > >> > > > >> > > > >> > > On Wed, Jun 12, 2013 at 1:48 PM, Daan Hoogland < > >> > > dhoogl...@schubergphilis.com > >> > > > wrote: > >> > > > >> > > > Macosx? > >> > > > Eclipse? > >> > > > > >> > > > I will try on windows sometime soon (with wireless). > >> > > > > >> > > > -----Original Message----- > >> > > > From: Sheng Yang [mailto:sh...@yasker.org] > >> > > > Sent: woensdag 12 juni 2013 22:37 > >> > > > To: <dev@cloudstack.apache.org> > >> > > > Subject: Re: Test halting build every now and then > >> > > > > >> > > > I tried to look into this, but it's really hard for me to > >>reproduce > >> > > it(I've > >> > > > run the case for 50 times and no show of the issue). > >> > > > > >> > > > The bash command I used is: for i in {1..50}; do mvn > >>-Dtest=NioTest > >> > test > >> > > > -pl utils; done > >> > > > > >> > > > From the log, it looks like server is up but client didn't > >>connect to > >> > the > >> > > > server. The correct log of whole process should be: > >> > > > > >> > > > 2013-06-12 13:30:50,079 INFO [utils.testcase.NioTest] (main:) > >>Test > >> > > > 2013-06-12 13:30:50,103 INFO [utils.nio.NioServer] > >> > > > (NioTestServer-Selector:) NioConnection started and listening on > >> > > > 0.0.0.0/0.0.0.0:7777 > >> > > > 2013-06-12 13:30:50,109 INFO [utils.nio.NioClient] > >> > > > (NioTestServer-Selector:) Connecting to 127.0.0.1:7777 > >> > > > 2013-06-12 13:30:50,351 INFO [utils.testcase.NioTest] > >> > > > (NioTestServer-Handler-1:) Server: Received CONNECT task > >> > > > 2013-06-12 13:30:50,388 INFO [utils.nio.NioClient] > >> > > > (NioTestServer-Selector:) SSL: Handshake done > >> > > > 2013-06-12 13:30:50,389 INFO [utils.nio.NioClient] > >> > > > (NioTestServer-Selector:) Connected to 127.0.0.1:7777 > >> > > > 2013-06-12 13:30:50,389 INFO [utils.testcase.NioTest] > >> > > > (NioTestServer-Handler-1:) Client: Received CONNECT task > >> > > > 2013-06-12 13:30:51,406 INFO [utils.testcase.NioTest] (main:) > >> Client: > >> > > Data > >> > > > sent > >> > > > 2013-06-12 13:30:51,406 INFO [utils.testcase.NioTest] (main:) > >> Client: > >> > > Data > >> > > > sent > >> > > > 2013-06-12 13:30:51,556 INFO [utils.testcase.NioTest] > >> > > > (NioTestServer-Handler-2:) Server: Received DATA task > >> > > > 2013-06-12 13:30:51,597 INFO [utils.testcase.NioTest] > >> > > > (NioTestServer-Handler-3:) Server: Received DATA task > >> > > > 2013-06-12 13:30:51,834 INFO [utils.testcase.NioTest] > >> > > > (NioTestServer-Handler-2:) Verify done. > >> > > > 2013-06-12 13:30:51,856 INFO [utils.testcase.NioTest] > >> > > > (NioTestServer-Handler-3:) Verify done. > >> > > > 2013-06-12 13:30:52,406 INFO [utils.testcase.NioTest] (main:) > >>Client > >> > > > stopped. > >> > > > 2013-06-12 13:30:52,407 INFO [utils.testcase.NioTest] (main:) > >>Server > >> > > > stopped. > >> > > > > >> > > > I've tried wireless network, still unable to reproduce. > >> > > > > >> > > > Is there anything else may affect the reproducibility? I thought > >>it > >> > was a > >> > > > racy issue, but cannot prove it, since client is not up at all in > >> your > >> > > > case. > >> > > > > >> > > > --Sheng > >> > > > > >> > > > > >> > > > > >> > > > On Wed, Jun 12, 2013 at 9:25 AM, Mike Tutkowski < > >> > > > mike.tutkow...@solidfire.com> wrote: > >> > > > > >> > > > > Hi Daan, > >> > > > > > >> > > > > Yeah, now that you remind me, I believe we did talk about a > >> wireless > >> > > > setup > >> > > > > possibly being behind this a while ago. :) > >> > > > > > >> > > > > When I'm working from home, I am on a wireless network. > >> > > > > > >> > > > > In the office, my primary connection is via cable, but I do have > >> > > another > >> > > > > connection to the Internet via wireless. > >> > > > > > >> > > > > It's not the end of the world when this problem occurs. I just > >> CTRL-C > >> > > and > >> > > > > try again, but I thought if someone had a solution that perhaps > >>I > >> > > didn't > >> > > > > see that I could implement it on my side. > >> > > > > > >> > > > > Thanks for your time!! > >> > > > > > >> > > > > > >> > > > > On Wed, Jun 12, 2013 at 1:30 AM, Daan Hoogland < > >> > > > > dhoogl...@schubergphilis.com > >> > > > > > wrote: > >> > > > > > >> > > > > > H Mike, > >> > > > > > > >> > > > > > I had this too, working from my home machine and got some > >>hint on > >> > > this > >> > > > > > list, stating a wireless interface on your machine might be > >>the > >> > > > problem. > >> > > > > I > >> > > > > > haven't been able to pinpoint the culprit yet. What is your > >> setup? > >> > > > > > > >> > > > > > Regards, > >> > > > > > Daan Hoogland > >> > > > > > > >> > > > > > -----Original Message----- > >> > > > > > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] > >> > > > > > Sent: woensdag 12 juni 2013 1:19 > >> > > > > > To: dev@cloudstack.apache.org > >> > > > > > Subject: Re: Test halting build every now and then > >> > > > > > > >> > > > > > Took five tries to get the build over this hump a moment ago. > >> > > > > > > >> > > > > > Any thoughts on what's going on there? > >> > > > > > > >> > > > > > Thanks! > >> > > > > > > >> > > > > > > >> > > > > > On Tue, Jun 4, 2013 at 12:22 PM, Mike Tutkowski < > >> > > > > > mike.tutkow...@solidfire.com> wrote: > >> > > > > > > >> > > > > > > Hi, > >> > > > > > > > >> > > > > > > Does anyone know if there is a way to stop the build from > >>(very > >> > > > often) > >> > > > > > > halting here indefinitely? > >> > > > > > > > >> > > > > > > 2013-06-04 12:19:47,836 INFO [utils.net.NetUtilsTest] > >>(main:) > >> IP > >> > > is > >> > > > > > > 1234:5678::dd3b:e82c:ce6b:fe5c > >> > > > > > > 2013-06-04 12:19:47,839 INFO [utils.net.NetUtilsTest] > >>(main:) > >> IP > >> > > is > >> > > > > > > 1234:5678::814a:9955:e8e2:84f Tests run: 4, Failures: 0, > >> Errors: > >> > 0, > >> > > > > > > Skipped: 0, Time elapsed: 0.085 sec Running > >> > > > > > > com.cloud.utils.StringUtilsTest Tests run: 10, Failures: 0, > >> > Errors: > >> > > > 0, > >> > > > > > > Skipped: 0, Time elapsed: 0.011 sec Running > >> > > > > > > com.cloud.utils.testcase.NioTest > >> > > > > > > 2013-06-04 12:19:47,860 INFO [utils.testcase.NioTest] > >>(main:) > >> > Test > >> > > > > > > 2013-06-04 12:19:47,913 INFO [utils.nio.NioServer] > >> > > > > > > (NioTestServer-Selector:) NioConnection started and > >>listening > >> on > >> > > > > > > 0.0.0.0/0.0.0.0:7777 > >> > > > > > > > >> > > > > > > I usually just wait for this point in the build and if it > >> halts, > >> > > then > >> > > > > > > I CTRL-C and try again. > >> > > > > > > > >> > > > > > > Thanks! > >> > > > > > > > >> > > > > > > -- > >> > > > > > > *Mike Tutkowski* > >> > > > > > > *Senior CloudStack Developer, SolidFire Inc.* > >> > > > > > > e: mike.tutkow...@solidfire.com > >> > > > > > > o: 303.746.7302 > >> > > > > > > Advancing the way the world uses the > >> > > > > > > cloud<http://solidfire.com/solution/overview/?video=play> > >> > > > > > > *(tm)* > >> > > > > > > > >> > > > > > > >> > > > > > > >> > > > > > > >> > > > > > -- > >> > > > > > *Mike Tutkowski* > >> > > > > > *Senior CloudStack Developer, SolidFire Inc.* > >> > > > > > e: mike.tutkow...@solidfire.com > >> > > > > > o: 303.746.7302 > >> > > > > > Advancing the way the world uses the > >> > > > > > cloud<http://solidfire.com/solution/overview/?video=play> > >> > > > > > *(tm)* > >> > > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > -- > >> > > > > *Mike Tutkowski* > >> > > > > *Senior CloudStack Developer, SolidFire Inc.* > >> > > > > e: mike.tutkow...@solidfire.com > >> > > > > o: 303.746.7302 > >> > > > > Advancing the way the world uses the > >> > > > > cloud<http://solidfire.com/solution/overview/?video=play> > >> > > > > *(tm)* > >> > > > > > >> > > > > >> > > > >> > > >> > > >> > > >> > -- > >> > *Mike Tutkowski* > >> > *Senior CloudStack Developer, SolidFire Inc.* > >> > e: mike.tutkow...@solidfire.com > >> > o: 303.746.7302 > >> > Advancing the way the world uses the > >> > cloud<http://solidfire.com/solution/overview/?video=play> > >> > * * > >> > > >> > > > > > > > >-- > >*Mike Tutkowski* > >*Senior CloudStack Developer, SolidFire Inc.* > >e: mike.tutkow...@solidfire.com > >o: 303.746.7302 > >Advancing the way the world uses the > >cloud<http://solidfire.com/solution/overview/?video=play> > >* * > > -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play> *™*
