FAFT Test: connection refused by DUT.

[Martin Yan]

As Server starts to perform test item, it shows,

18:40:51 INFO | autoserv| Started XMLRPC server on host 192.168.1.18, pid = 8966

18:40:51 INFO | autoserv| Full tunnel command: /usr/bin/ssh -a -x -n -N -q -L 36087:localhost:9990 -o Protocol=2 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=900 -o ServerAliveCountMax=3 -o ConnectionAttempts=4 -l root -p 22 192.168.1.18

18:40:51 INFO | autoserv| Started ssh tunnel, local = 36087 remote = 9990, pid = 612

18:40:51 INFO | autoserv| Waiting 120 seconds for XMLRPC server to start.

18:40:51 INFO | autoserv| <class 'socket.error'>([Errno 111] Connection refused: "<RPCProxy '192.168.1.18:9990'> (localhost:36087)")

18:40:51 INFO | autoserv| Retrying in 0.796286 seconds...

18:40:52 INFO | autoserv| <class 'socket.error'>([Errno 104] Connection reset by peer: "<RPCProxy '192.168.1.18:9990'> (localhost:36087)")

18:40:52 INFO | autoserv| Retrying in 0.777513 seconds...

18:40:53 INFO | autoserv| <class 'socket.error'>([Errno 104] Connection reset by peer: "<RPCProxy '192.168.1.18:9990'> (localhost:36087)")

18:40:53 INFO | autoserv| Retrying in 0.963274 seconds...

18:40:54 INFO | autoserv| <class 'socket.error'>([Errno 104] Connection reset by peer: "<RPCProxy '192.168.1.18:9990'> (localhost:36087)")

18:40:54 INFO | autoserv| Retrying in 1.253809 seconds...

18:40:55 INFO | autoserv| <class 'socket.error'>([Errno 104] Connection reset by peer: "<RPCProxy '192.168.1.18:9990'> (localhost:36087)")

18:40:55 INFO | autoserv| Retrying in 0.592433 seconds...

But able to verify connection Via ssh (IP is 192.168.1.18):

(cr) ((5fba239...)) pfw1@MP1 ~/trunk/src/scripts $ ssh ro...@192.168.1.18

Password: 

localhost ~ # exit

logout

Connection to 192.168.1.18 closed.

(cr) ((5fba239...)) pfw1@MP1 ~/trunk/src/scripts $ ssh -q root@dut exit; echo $?

255

Sound simple and straight, but not working, any helpful advice?

[Jeremy Bettis]

I had something similar happen when for some reason python was deleted from my DUT.   I think I would look at the /tmp/test_that_results_xxx/results-1-TESTNAME/TESTNAME/debug/TESTNAME.DEBUG and see if any errors were logged after "Started XMLRPC server" that might indicate why the XMLRPC server isn't running. Or ssh into the DUT during those retries and see if you can see if the process is running.

--
To unsubscribe from this group and stop receiving emails from it, send an email to faft-users+...@chromium.org.

--

Jeremy Bettis | SWE on ChromeOS | jbe...@google.com | 303-257-2486

[Martin Yan]

thanks your response, Jeremy.

per review test_that.debug, here is the difference:

1: not working version

rsync not available on remote host 192.168.1.18 -- disabled
// why is not available?

2: working one before

abstract_ssh:0684| Using Rsync.