[Fuego] [LTSI-dev] Fuego installation

Bird, Timothy Tim.Bird at am.sony.com
Fri Oct 21 19:09:58 UTC 2016



> -----Original Message-----
> From: ltsi-dev-bounces at lists.linuxfoundation.org [mailto:ltsi-dev-
> bounces at lists.linuxfoundation.org] On Behalf Of anirudh vasudevan
> Sent: Friday, October 21, 2016 11:52 AM
> To: Bird, Timothy <Tim.Bird at am.sony.com>
> Cc: ltsi-dev at lists.linuxfoundation.org; fuego at 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.
>

Hmm.  I found a reference on the internet to changing the value of UseDNS on the
target.  Can you do the following:

On your target, in the file /etc/ssh/sshd_config, add a line containing:
UseDNS no

Then do: "sudo service ssh restart"
on the target.

Then re-run the test and see if you're still getting the timeout.

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, that would
be useful.

Thanks - and sorry for the problems.

BTW - what target board and Linux distribution are you using?

 -- Tim


> 
> +++ sshpass -e ssh -o ServerAliveInterval=30 -o StrictHostKeyChecking=no -o
> UserKnownHostsFile=/dev/null -o ConnectTimeout=80 -p 22
> root at 10.200.15.192 <mailto:root at 10.200.15.192>  true
> ssh: connect to host 10.200.15.192 port 22: Connection timed out
> +++ abort_job 'Cannot connect to 10.200.15.192 via ssh'
> +++ set +x
> 
> P.S- Both the target and testing machine are on the same network and able
> to ssh from terminal
> Thanks,
> Anirudh
> 
> 
> On Fri, Oct 21, 2016 at 2:09 PM, Bird, Timothy <Tim.Bird at am.sony.com
> <mailto:Tim.Bird at am.sony.com> > wrote:
> 
> 
> 
> 
> 	> -----Original Message-----
> 	> From: anirudh vasudevan [mailto:vasuanirudh at gmail.com
> <mailto:vasuanirudh at gmail.com> ]
> 	> Sent: Thursday, October 20, 2016 9:25 AM
> 	> To: Daniel Sangorrin <daniel.sangorrin at toshiba.co.jp
> <mailto:daniel.sangorrin at toshiba.co.jp> >
> 	> Cc: Bird, Timothy <Tim.Bird at am.sony.com
> <mailto:Tim.Bird at am.sony.com> >;
> 	> fuego at lists.linuxfoundation.org
> <mailto:fuego at lists.linuxfoundation.org> ; ltsi-
> dev at lists.linuxfoundation.org <mailto:ltsi-dev at lists.linuxfoundation.org>
> 	> Subject: Re: [Fuego] [LTSI-dev] Fuego installation
> 	>
> 	> Hi Daniel,
> 	>
> 	>
> 	> I did apply the patch that you sent and did work for an extent now
> am getting
> 	> the below error.
> 	>
> 	> root at 10.200.15.192 <mailto:root at 10.200.15.192>
> <mailto:root at 10.200.15.192 <mailto:root at 10.200.15.192> >  'echo "Firmware
> revision:"
> 	> 4.7.4-IMX6.VAR_R17'
> 	> ssh: connect to host 10.200.15.192 port 22: Connection timed out
> 	> +++ abort_job 'Error while ROOTFS_FWVER command execution on
> target'
> 	> +++ set +x
> 	>
> 	> *** ABORTED ***
> 	>
> 	> Fuego error reason: Error while ROOTFS_FWVER command
> execution on
> 
> 	I have seen lots of timeouts on my boards when running tests as
> well,
> 	but not gotten to the cause of it.  At ELCE, during the demo
> showcase,
> 	the tests were running extremely slowly.  Each ssh connection
> operation
> 	took something like 10 seconds.  During a test, the framework
> connects
> 	many times to the target, so this was causing even a simple test like
> 	Functional.bc to take a few minutes (when it should have taken only
> 	20 or-so seconds).
> 
> 	I haven't gotten to the bottom of this, but it's not consistent on my
> devices.
> 	To work around it, you can increase the timeout for the ssh
> operations, by
> 	editing the lines for ssh in the file (inside the docker container):
> 	/home/jenkins/fuego/engine/overlays/base/base-
> params.fuegoclass.
> 
> 	There are lines like the following:
> 	SSH="sshpass -e ssh -o ServerAliveInterval=30 -o
> StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o
> ConnectTimeout=15 -p $SSH_PORT $LOGIN@"
> 	SCP="sshpass -e scp -o ServerAliveInterval=30 -o
> StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o
> ConnectTimeout=15 -P $SSH_PORT"
> 
> 	Change the value of ConnectTimeout to 30, so the lines read as
> follows:
> 	SSH="sshpass -e ssh -o ServerAliveInterval=30 -o
> StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o
> ConnectTimeout=30 -p $SSH_PORT $LOGIN@"
> 	SCP="sshpass -e scp -o ServerAliveInterval=30 -o
> StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o
> ConnectTimeout=30 -P $SSH_PORT"
> 
> 	This is kind of a hack, and definitely (IMHO) the connection timeout
> should be
> 	added as an easily overridable board-level variable, but it should
> work around
> 	the issue for you for now.
> 
> 	Figuring out what's going on with sshpass or ssh in this circumstance
> is on my
> 	(rather lengthy) list of things to do.
> 	 -- Tim
> 
> 
> 
> 



More information about the Fuego mailing list