Issues Disabling Roadrunner

Autonomous Vehicles DRIVE AGX Xavier DRIVE AGX Xavier General
1

Software Version
NVIDIA DRIVE™ Software 10.0 (Linux)

Hardware Platform
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)

Host Machine Version
native Ubuntu 18.04

We are encountering an issue when running the /usr/local/service-framework/scripts/kill.sh script. When prompted for a password, the default password is rejected. When I SSH into the AGX and type “bash /usr/local/service-framework/scripts/kill.sh” I get the following output:

nvidia@tegra-ubuntu:~$ bash /usr/local/service-framework/scripts/kill.sh

  • SCRIPT_NAME=/usr/local/service-framework/scripts/kill.sh
    +++ dirname – /usr/local/service-framework/scripts/kill.sh
    ++ cd -P – /usr/local/service-framework/scripts
    ++ pwd -P
  • SCRIPT_DIR=/usr/local/service-framework/scripts
  • source /usr/local/service-framework/scripts/common.sh
    ++ TEGRA_A_IP=10.42.0.28
    ++ TEGRA_B_IP=10.42.0.29
    ++ DRIVEWORKSPATH=/usr/local/driveworks
    ++ DRIVEIXPATH=/usr/local/driveix
    ++ SFPATH=/usr/local/service-framework
    ++ DRIVEARPATH=/opt/nvidia/drivear/drivear
    ++ DRIVEARIXPATH=/opt/nvidia/drivearix/drivearix
    ++ LIMEPATH=/opt/nvidia/lime/lime
    ++ DRIVEHUBPATH=/opt/nvidia/drivehub/drivehub
    ++ WESTONPATH=/usr/local/service-framework/weston
    ++ XDGDIR=/tmp/xdgruntime
    ++ TMP_LAUNCH_LOG_DIR=/home/nvidia/launchlog
    ++ TMP_LAUNCH_LOG_DIR_A=/home/nvidia/launchlog
    ++ TMP_LAUNCH_LOG_DIR_B=/home/nvidia/launchlog
    ++ MNT_SSD_ON_B=/mnt/SSD1
    ++ HUB_LAUNCH_DELAY_SEC=10
    +++ tr -d ‘\0’
    ++ DEV_TYPE=e3550_t194a
    ++ ‘[’ e3550_t194a = e3550_t194a ‘]’
    ++ TEGRA_REMOTE_IP=10.42.0.29
    ++ ssh -o StrictHostKeyChecking=no nvidia@10.42.0.29 ‘bash -c “findmnt /mnt/SSD1”’
    nvidia@10.42.0.29’s password:
    +++ echo 1
    ++ IF_SSD_ON_B=1
    ++ ‘[’ 1 = 0 ‘]’
    ++ REMOTE_COMMAND=‘ssh -f -o StrictHostKeyChecking=no nvidia@10.42.0.29’
  • _launchOnA ’ /usr/local/service-framework/scripts/killlocal.sh ’
  • ‘[’ e3550_t194a = e3550_t194a ‘]’
  • _launchOnB ’ /usr/local/service-framework/scripts/killlocal.sh ’
  • bash -c ’ /usr/local/service-framework/scripts/killlocal.sh ’
  • ‘[’ e3550_t194a = e3550_t194a ‘]’
  • echo ‘Running logcontrol script to end session/instance’
    Running logcontrol script to end session/instance
  • logcontrol
  • _launchOnA /usr/local/service-framework/scripts/logcontrol.sh
  • ssh -f -o StrictHostKeyChecking=no nvidia@10.42.0.29 ‘bash -c " /usr/local/service-framework/scripts/killlocal.sh "’
  • ‘[’ e3550_t194a = e3550_t194a ‘]’
  • wait
  • bash -c /usr/local/service-framework/scripts/logcontrol.sh
    +++ dirname – /usr/local/service-framework/scripts/logcontrol.sh
    ++ cd -P – /usr/local/service-framework/scripts
    ++ pwd -P
  • SCRIPT_DIR=/usr/local/service-framework/scripts
  • source /usr/local/service-framework/scripts/common.sh
    ++ TEGRA_A_IP=10.42.0.28
    ++ TEGRA_B_IP=10.42.0.29
    ++ DRIVEWORKSPATH=/usr/local/driveworks
    ++ DRIVEIXPATH=/usr/local/driveix
    ++ SFPATH=/usr/local/service-framework
    ++ DRIVEARPATH=/opt/nvidia/drivear/drivear
    ++ DRIVEARIXPATH=/opt/nvidia/drivearix/drivearix
    ++ LIMEPATH=/opt/nvidia/lime/lime
    ++ DRIVEHUBPATH=/opt/nvidia/drivehub/drivehub
    ++ WESTONPATH=/usr/local/service-framework/weston
    ++ XDGDIR=/tmp/xdgruntime
    ++ TMP_LAUNCH_LOG_DIR=/home/nvidia/launchlog
    ++ TMP_LAUNCH_LOG_DIR_A=/home/nvidia/launchlog
    ++ TMP_LAUNCH_LOG_DIR_B=/home/nvidia/launchlog
    ++ MNT_SSD_ON_B=/mnt/SSD1
    ++ HUB_LAUNCH_DELAY_SEC=10
    +++ tr -d ‘\0’
    ++ DEV_TYPE=e3550_t194a
    ++ ‘[’ e3550_t194a = e3550_t194a ‘]’
    ++ TEGRA_REMOTE_IP=10.42.0.29
    ++ ssh -o StrictHostKeyChecking=no nvidia@10.42.0.29 ‘bash -c “findmnt /mnt/SSD1”’
    nvidia@10.42.0.29’s password: nvidia@10.42.0.29’s password:
    Permission denied, please try again.

I know the password has not been changed because when I exit out of the kill script prompt and type “ssh nvidia@10.42.0.29”, the same password work:“nvidia”

Any suggestions on how to proceed?

2

Dear @mnm419,
Are you running this on Tegra A or B? Which DRIVE release does the other tegra has? Could you check running on other Tegra and confirm if it kills the roadrunner? Also, please see if setting password less ssh connection on tegra fixes issue.

4

I had the same issue running it on either Tegra A or Tegra B. They’re both running Drive 10. However, setting passwordless SSH fixed the issue. Thank you!

5

Dear @mnm419,
Thank you for confirming password less SSH setup fixed it.

7

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.