From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Sony.onmicrosoft.com; s=selector1-Sony-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=yHa/1qnaz7Ae2ugHOxnwcH2w06fyScT2AirkqNobnJo=; b=H3MuCVztuGW6WFmLYWh/8eHg2DNfhhHagjoL6lG3WSOwUzRn7/rkMoCBkqzciiJLLwuKiYEAXlFAzw/bG02cq/jC+xFKUNPGTCZdzdG57npN0LTkFcXjNHOc6gb6UL5fOQUccUU1hxX2qhWirXTklJ2bkYlpGCAd1uqk4gDj6EQ= From: "Bird, Timothy" Date: Fri, 21 Oct 2016 19:44:19 +0000 Message-ID: Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [Fuego] ssh timeout problem - was RE: [LTSI-dev] Fuego installation List-Id: Mailing list for the Fuego test framework List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Bird, Timothy" , anirudh vasudevan , Daniel Sangorrin Cc: "ltsi-dev@lists.linuxfoundation.org" , "fuego@lists.linuxfoundation.org" > -----Original Message----- > From: ltsi-dev-bounces@lists.linuxfoundation.org [mailto:ltsi-dev- > bounces@lists.linuxfoundation.org] On Behalf Of Bird, Timothy > Sent: Friday, October 21, 2016 12:10 PM > To: anirudh vasudevan > Cc: ltsi-dev@lists.linuxfoundation.org; fuego@lists.linuxfoundation.org > Subject: Re: [LTSI-dev] [Fuego] Fuego installation >=20 >=20 >=20 > > -----Original Message----- > > From: ltsi-dev-bounces@lists.linuxfoundation.org [mailto:ltsi-dev- > > bounces@lists.linuxfoundation.org] On Behalf Of anirudh vasudevan > > Sent: Friday, October 21, 2016 11:52 AM > > To: Bird, Timothy > > Cc: ltsi-dev@lists.linuxfoundation.org; fuego@lists.linuxfoundation.org > > Subject: Re: [LTSI-dev] [Fuego] Fuego installation > > > > Hi Tim, > > > > > > I had already changed the timeout to 45 and ran and found no luck Now I > > tried changing it to 80 and I was left with the same result. > > >=20 > Hmm. I found a reference on the internet to changing the value of UseDNS > on the > target. Can you do the following: >=20 > On your target, in the file /etc/ssh/sshd_config, add a line containing: > UseDNS no >=20 > Then do: "sudo service ssh restart" > on the target. >=20 > Then re-run the test and see if you're still getting the timeout. >=20 > I'm setting up an environment to test this on my side, but it will take a= while. > (I have to reconstruct my setup from the tech showcase.) > But if you could try this out real quick and let me know if it helps, tha= t would > be useful. Just to report back. I am testing a beaglebone black, using it's Ethernet = connection, on a private LAN (no connection to an external network for either the host = or target). I followed those instructions (setting 'UseDNS no') and the running Functio= nal.bc on the board took only 7.7 seconds, as opposed to the 4 minutes and 23 seco= nds it was taking before the change. So, this solves this particular timeout problem for me. Please let me know= if it solves your timeout problem. I believe we should have some "health check" tests in the test suite, to ch= eck a variety of items relating to the target (/proc filesystem availability, s= sh timing test, etc.) and the host/target connection, that would help us ident= ify and cure these problems. Let me know what you think. -- Tim