Skip to content

GB-299: no phone, or no Linux VM on it, answers over the Android debug bridge

Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-299 is printed by goatbuilder. The same text offline: goat explain GB-299 or goatbuilder explain GB-299.

What it means

join-node --via usb reaches a phone node through the Android debug bridge (adb) on a USB cable: SSH is carried by adb shell nc <the VM's address> 22, and the address is looked up on every connection (ops/scripts/phone-node-ssh.sh). adb is not installed, lists no phone as device, the phone is locked, or the phone's Linux VM has no address. Nothing reached the node.

Why it happens

  • the phone is not attached, USB debugging is not allowed on it, or this machine's key was not accepted on its screen
  • the phone is locked
  • the Terminal app is closed, so the VM is not running
  • more than one device is attached and ANDROID_SERIAL does not name the phone
  • adb (Android platform tools) is not installed on this machine

What to do

One line per step or alternative:

adb devices (the phone must be listed as device)
unlock the phone and open its Terminal app, then resume: goatbuilder join-node <environment> --site <site> --node <node> --class phone --via usb --from <phase>
ops/scripts/phone-node-ssh.sh --vm-address (prints the VM's address, or says which of the above it is)

Read more

Exit code

goatbuilder exits with 1.