Re: [Fuego] ssh timeout problem - was RE: [LTSI-dev] Fuego installation

[anirudh vasudevan <vasuanirudh@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 3375 bytes --]

Hi Tim,

I am still facing the issue. The target is running on Debian distribution,
I did add the UseDNS and also had the target and testing machine on a
private network. Please see the below error I got from the console o/p.



+++ echo 'cmd: echo "Firmware revision:" 4.7.4-IMX6.VAR_R17'
+++ ov_transport_cmd 'echo "Firmware revision:" 4.7.4-IMX6.VAR_R17'
+++ case "$TRANSPORT" in

+++ sshpass -e ssh -o ServerAliveInterval=30000 -o
StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o
ConnectTimeout=30000 -p 22 root@192.168.1.56 'echo "Firmware
revision:" 4.7.4-IMX6.VAR_R17'

ssh: connect to host 192.168.1.56 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 target




Thanks,

Anirudh


On Fri, Oct 21, 2016 at 3:44 PM, Bird, Timothy <Tim.Bird@am.sony.com> wrote:

>
>
> > -----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 <vasuanirudh@gmail.com>
> > Cc: ltsi-dev@lists.linuxfoundation.org; fuego@lists.linuxfoundation.org
> > Subject: Re: [LTSI-dev] [Fuego] Fuego installation
> >
> >
> >
> > > -----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 <Tim.Bird@am.sony.com>
> > > 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.
> > >
> >
> > 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.
>
> 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
> Functional.bc
> on the board took only 7.7 seconds, as opposed to the 4 minutes and 23
> seconds
> 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
> check
> a variety of items relating to the target (/proc filesystem availability,
> ssh
> timing test, etc.) and the host/target connection, that would help us
> identify
> and cure these problems.
>
> Let me know what you think.
>  -- Tim
>
>

[-- Attachment #2: Type: text/html, Size: 4992 bytes --]