NVIDIA SDK Manager Crashed Unexpected

I tried to setup Jetson TX2 using sdk-manager.
But, sdk-manager crashed on Ubuntu 18.04.

So, I checked “.nvsdkm/sdkm.log”. As a result, I could not find the cause of this error.

2019-05-29 00:44:50.053 - info: Usage and platform data collection via Google Analytics sets to false
2019-05-29 00:44:50.059 - info: Loading data from server: l1url. Url: https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json
2019-05-29 00:44:50.384 - info: sdkml1_repo.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json has been downloaded to /home/jetpack/.nvsdkm/dist successfully.
2019-05-29 00:44:50.509 - info: sdkml2_drive_linux.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/DRIVE/Linux/sdkml2_drive_linux.json has been downloaded to /home/jetpack/.nvsdkm/dist successfully.
2019-05-29 00:44:50.536 - info: validating product line for target OS: Linux
2019-05-29 00:44:50.540 - info: 	validating release: DRIVE OS 5.1.3.0 SDK
2019-05-29 00:44:50.540 - info: 	validating release: DRIVE OS 5.1.3.0 PDK
2019-05-29 00:44:50.541 - info: 	validating release: DRIVE Software 8.0
2019-05-29 00:44:50.541 - info: 	validating release: DRIVE Software 8.0
2019-05-29 00:44:50.542 - info: 	validating release: DRIVE OS 5.1.0.0 SDK
2019-05-29 00:44:50.542 - info: 	validating release: DRIVE OS 5.1.0.0 PDK
2019-05-29 00:44:50.543 - info: 	validating release: DRIVE Software 1.0
2019-05-29 00:44:50.543 - info: 	validating release: DRIVE OS 5.0.10.3 SDK with DriveWorks
2019-05-29 00:44:50.544 - info: 	validating release: DRIVE OS 5.0.10.3 PDK
2019-05-29 00:44:50.544 - info: 	validating release: DRIVE OS 5.0.13.0 SDK
2019-05-29 00:44:50.544 - info: 	validating release: DRIVE OS 5.0.13.0 PDK
2019-05-29 00:44:50.582 - error: Invalid token
2019-05-29 00:44:50.582 - error: Invalid token
2019-05-29 00:44:50.583 - error: Invalid token
2019-05-29 00:44:50.583 - error: Invalid token
2019-05-29 00:44:50.583 - error: Invalid token
2019-05-29 00:44:50.583 - error: Invalid token
2019-05-29 00:44:50.583 - error: Invalid token
2019-05-29 00:44:50.583 - error: Invalid token
2019-05-29 00:44:50.583 - warn: 	No access to release DRIVE OS 5.1.3.0 SDK. Message undefined
2019-05-29 00:44:50.584 - warn: 	No access to release DRIVE OS 5.1.3.0 PDK. Message undefined
2019-05-29 00:44:50.584 - warn: 	No access to release DRIVE Software 8.0. Message undefined
2019-05-29 00:44:50.584 - warn: 	No access to release DRIVE OS 5.1.0.0 SDK. Message undefined
2019-05-29 00:44:50.585 - warn: 	No access to release DRIVE OS 5.1.0.0 PDK. Message undefined
2019-05-29 00:44:50.585 - warn: 	No access to release DRIVE OS 5.0.10.3 PDK. Message undefined
2019-05-29 00:44:50.585 - warn: 	No access to release DRIVE OS 5.0.13.0 SDK. Message undefined
2019-05-29 00:44:50.585 - warn: 	No access to release DRIVE OS 5.0.13.0 PDK. Message undefined
2019-05-29 00:44:50.586 - info: sdkml2_drive_qnx.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/DRIVE/QNX/sdkml2_drive_qnx.json has been downloaded to /home/jetpack/.nvsdkm/dist successfully.
2019-05-29 00:44:50.587 - info: sdkml2_jetson_linux.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/Jetson/Linux/sdkml2_jetson_linux.json has been downloaded to /home/jetpack/.nvsdkm/dist successfully.
2019-05-29 00:44:50.591 - info: validating product line for target OS: QNX
2019-05-29 00:44:50.603 - info: 	validating release: DRIVE OS 5.1.3.0 SDK
2019-05-29 00:44:50.604 - info: 	validating release: DRIVE OS 5.1.3.0 PDK
2019-05-29 00:44:50.605 - info: 	validating release: DRIVE OS 5.1.0.0 SDK
2019-05-29 00:44:50.605 - info: 	validating release: DRIVE OS 5.1.0.0 PDK
2019-05-29 00:44:50.606 - info: 	validating release: DRIVE OS 5.0.13.2 (with DRIVE AV)
2019-05-29 00:44:50.606 - info: 	validating release: DRIVE OS 5.0.13.0 SDK
2019-05-29 00:44:50.606 - info: 	validating release: DRIVE OS 5.0.13.0 PDK
2019-05-29 00:44:50.609 - error: Invalid token
2019-05-29 00:44:50.609 - error: Invalid token
2019-05-29 00:44:50.609 - error: Invalid token
2019-05-29 00:44:50.609 - error: Invalid token
2019-05-29 00:44:50.609 - error: Invalid token
2019-05-29 00:44:50.609 - error: Invalid token
2019-05-29 00:44:50.609 - error: Invalid token
2019-05-29 00:44:50.609 - warn: 	No access to release DRIVE OS 5.1.3.0 SDK. Message undefined
2019-05-29 00:44:50.610 - warn: 	No access to release DRIVE OS 5.1.3.0 PDK. Message undefined
2019-05-29 00:44:50.610 - warn: 	No access to release DRIVE OS 5.1.0.0 SDK. Message undefined
2019-05-29 00:44:50.610 - warn: 	No access to release DRIVE OS 5.1.0.0 PDK. Message undefined
2019-05-29 00:44:50.611 - warn: 	No access to release DRIVE OS 5.0.13.2 (with DRIVE AV). Message undefined
2019-05-29 00:44:50.611 - warn: 	No access to release DRIVE OS 5.0.13.0 SDK. Message undefined
2019-05-29 00:44:50.611 - warn: 	No access to release DRIVE OS 5.0.13.0 PDK. Message undefined
2019-05-29 00:44:50.612 - info: validating product line for target OS: Linux
2019-05-29 00:44:50.614 - info: 	validating release: JetPack 4.2.1 EA
2019-05-29 00:44:50.614 - info: 	validating release: JetPack 4.2
2019-05-29 00:44:50.637 - info: sdkml2_sdkmanager_linux_deb.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/SDKMANAGER/Linux/sdkml2_sdkmanager_linux_deb.json has been downloaded to /home/jetpack/.nvsdkm/dist successfully.
2019-05-29 00:44:50.811 - info: validating product line for target OS: 
2019-05-29 00:44:50.813 - info: 	validating release: SDK Manager
2019-05-29 00:44:51.502 - error: devzone get download url failed with error: null. Status code: 403
2019-05-29 00:44:51.503 - warn: 	No access to release JetPack 4.2.1 EA. Message undefined
2019-05-29 00:44:51.532 - error: devzone get download url failed with error: null. Status code: 403
2019-05-29 00:44:51.532 - warn: 	No access to release DRIVE Software 8.0. Message undefined
2019-05-29 00:44:51.953 - error: devzone get download url failed with error: null. Status code: 403
2019-05-29 00:44:51.954 - warn: 	No access to release DRIVE OS 5.0.10.3 SDK with DriveWorks. Message undefined
2019-05-29 00:44:51.966 - error: devzone get download url failed with error: null. Status code: 403
2019-05-29 00:44:51.966 - warn: 	No access to release DRIVE Software 1.0. Message undefined
2019-05-29 00:44:52.783 - info: step1 load in ms: 2723.6950000000033
2019-05-29 00:44:52.783 - info: Web server configuration build version 570D165J is set
2019-05-29 00:44:52.805 - info: Checking for update with mainRepoURL: https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json
2019-05-29 00:44:52.876 - info: sdkml1_repo.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json has been downloaded to /home/jetpack/.nvsdkm/dist successfully.

Hi dandelion1124,

Can you please let us know the SDK Manager client version? It is expected to be 0.9.12 to install JetPack. The SDK Manager 0.9.12 is available at https://developer.nvidia.com/embedded/dlc/nv-sdk-manager
If you still have problem, can you please attach the full sdkm.log file? Thanks.

Hi EdwardZhou,

Thank you for your reply. I used sdkmanager_0.9.11-3405_amd64.deb.
And I attached full sdkm.log.

2019-05-31 01:04:13.243 - info: forking worker process
2019-05-31 01:04:13.840 - info: number of download processes set to 3
2019-05-31 01:04:13.897 - info: Begin to create timing task for auto update.
2019-05-31 01:04:13.944 - info: Host OS: Ubuntu1804
2019-05-31 01:04:13.945 - info: packageJson: /opt/nvidia/sdkmanager/resources/app/package.json
2019-05-31 01:04:13.968 - info: config: 
{ mainRepoURL: 'https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json',
  PIDServer: 'P',
  DevZoneServer: 'P' }
2019-05-31 01:04:13.975 - info: manifest: {"name":"sdkmanager","version":"0.9.11","revision":"0","buildNumber":"3405","release":false}
2019-05-31 01:04:13.975 - info: Setting GA parameters: title SDK Manager 0.9.11.3405 version 0.9.11 dev: 0 internal: false 
2019-05-31 01:04:13.975 - info: autoLogin failed: Aborting auto login since there is no logged in user
2019-05-31 01:04:13.979 - info: mainRepoUrl: https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json
2019-05-31 01:04:13.979 - info: logging in with l1 url: https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json
2019-05-31 01:04:14.007 - warn: crontab read failure with Error: Command failed: crontab -l
no crontab for jetpack

2019-05-31 01:04:14.017 - warn: crontab read failure with Error: Command failed: crontab -l
no crontab for jetpack

2019-05-31 01:04:14.065 - info: Create timing task for auto update successfully.
2019-05-31 01:04:34.807 - info: Logging in with sso login method…
2019-05-31 01:04:34.821 - info: posting login request. url: https://devzone.auth0.com/oauth/token
2019-05-31 01:04:36.982 - info: get user programs. url: https://developer.nvidia.com/api/assets/v1/current_user_sdk/programs
2019-05-31 01:04:38.302 - info: the DevZone programs that user can access:
2019-05-31 01:04:38.302 - info: { id: xxxxxx, name: GameWorks Registered Developer Program }
2019-05-31 01:04:38.302 - info: { id: yyyyyy, name: NVIDIA Developer Program }
2019-05-31 01:04:38.302 - info: { id: zzzzzz, name: Isaac SDK }
2019-05-31 01:04:38.313 - info: Retrieving Data…
2019-05-31 01:04:38.314 - info: Processing Data…
2019-05-31 01:04:44.371 - info: Usage and platform data collection via Google Analytics sets to false
2019-05-31 01:04:44.374 - info: Loading data from server: l1url. Url: https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json
2019-05-31 01:04:44.835 - info: sdkml1_repo.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json has been downloaded to /home/jetpack/.nvsdkm/dist successfully.
2019-05-31 01:04:44.971 - info: sdkml2_drive_linux.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/DRIVE/Linux/sdkml2_drive_linux.json has been downloaded to /home/jetpack/.nvsdkm/dist successfully.
2019-05-31 01:04:44.985 - info: validating product line for target OS: Linux
2019-05-31 01:04:44.989 - info: 	validating release: DRIVE Software 9.0
2019-05-31 01:04:44.991 - info: 	validating release: DRIVE Software 8.0
2019-05-31 01:04:44.992 - info: 	validating release: DRIVE Software 8.0
2019-05-31 01:04:44.992 - info: 	validating release: DRIVE OS 5.1.6.0 PDK
2019-05-31 01:04:44.993 - info: 	validating release: DRIVE OS 5.1.6.0 SDK
2019-05-31 01:04:44.995 - info: 	validating release: DRIVE OS 5.1.3.0 PDK
2019-05-31 01:04:44.996 - info: 	validating release: DRIVE OS 5.1.3.0 SDK
2019-05-31 01:04:44.997 - info: 	validating release: DRIVE OS 5.1.0.0 PDK
2019-05-31 01:04:44.997 - info: 	validating release: DRIVE OS 5.1.0.0 SDK
2019-05-31 01:04:44.998 - info: 	validating release: DRIVE OS 5.0.10.3 SDK with DriveWorks
2019-05-31 01:04:44.998 - info: 	validating release: DRIVE OS 5.0.10.3 PDK
2019-05-31 01:04:45.037 - error: Invalid token
2019-05-31 01:04:45.037 - error: Invalid token
2019-05-31 01:04:45.038 - error: Invalid token
2019-05-31 01:04:45.038 - error: Invalid token
2019-05-31 01:04:45.038 - error: Invalid token
2019-05-31 01:04:45.038 - error: Invalid token
2019-05-31 01:04:45.038 - error: Invalid token
2019-05-31 01:04:45.038 - error: Invalid token
2019-05-31 01:04:45.039 - warn: 	No access to release DRIVE Software 8.0. Message undefined
2019-05-31 01:04:45.039 - warn: 	No access to release DRIVE OS 5.1.6.0 PDK. Message undefined
2019-05-31 01:04:45.040 - warn: 	No access to release DRIVE OS 5.1.6.0 SDK. Message undefined
2019-05-31 01:04:45.040 - warn: 	No access to release DRIVE OS 5.1.3.0 PDK. Message undefined
2019-05-31 01:04:45.040 - warn: 	No access to release DRIVE OS 5.1.3.0 SDK. Message undefined
2019-05-31 01:04:45.041 - warn: 	No access to release DRIVE OS 5.1.0.0 PDK. Message undefined
2019-05-31 01:04:45.041 - warn: 	No access to release DRIVE OS 5.1.0.0 SDK. Message undefined
2019-05-31 01:04:45.041 - warn: 	No access to release DRIVE OS 5.0.10.3 PDK. Message undefined
2019-05-31 01:04:45.047 - info: sdkml2_drive_qnx.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/DRIVE/QNX/sdkml2_drive_qnx.json has been downloaded to /home/jetpack/.nvsdkm/dist successfully.
2019-05-31 01:04:45.063 - info: validating product line for target OS: QNX
2019-05-31 01:04:45.065 - info: 	validating release: DRIVE OS 5.1.6.0 PDK
2019-05-31 01:04:45.065 - info: 	validating release: DRIVE OS 5.1.6.0 SDK
2019-05-31 01:04:45.066 - info: 	validating release: DRIVE OS 5.1.3.0 PDK
2019-05-31 01:04:45.067 - info: 	validating release: DRIVE OS 5.1.3.0 SDK
2019-05-31 01:04:45.067 - info: 	validating release: DRIVE OS 5.0.13.2 (with DRIVE AV)
2019-05-31 01:04:45.070 - error: Invalid token
2019-05-31 01:04:45.070 - error: Invalid token
2019-05-31 01:04:45.070 - error: Invalid token
2019-05-31 01:04:45.070 - error: Invalid token
2019-05-31 01:04:45.070 - error: Invalid token
2019-05-31 01:04:45.070 - warn: 	No access to release DRIVE OS 5.1.6.0 PDK. Message undefined
2019-05-31 01:04:45.071 - warn: 	No access to release DRIVE OS 5.1.6.0 SDK. Message undefined
2019-05-31 01:04:45.071 - warn: 	No access to release DRIVE OS 5.1.3.0 PDK. Message undefined
2019-05-31 01:04:45.071 - warn: 	No access to release DRIVE OS 5.1.3.0 SDK. Message undefined
2019-05-31 01:04:45.072 - warn: 	No access to release DRIVE OS 5.0.13.2 (with DRIVE AV). Message undefined
2019-05-31 01:04:45.073 - info: sdkml2_jetson_linux.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/Jetson/Linux/sdkml2_jetson_linux.json has been downloaded to /home/jetpack/.nvsdkm/dist successfully.
2019-05-31 01:04:45.075 - info: sdkml2_sdkmanager_linux_deb.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/SDKMANAGER/Linux/sdkml2_sdkmanager_linux_deb.json has been downloaded to /home/jetpack/.nvsdkm/dist successfully.
2019-05-31 01:04:45.085 - info: validating product line for target OS: Linux
2019-05-31 01:04:45.086 - info: 	validating release: JetPack 4.2.1 EA
2019-05-31 01:04:45.086 - info: 	validating release: JetPack 4.2
2019-05-31 01:04:45.109 - info: validating product line for target OS: 
2019-05-31 01:04:45.111 - info: 	validating release: SDK Manager
2019-05-31 01:04:46.316 - error: devzone get download url failed with error: null. Status code: 403
2019-05-31 01:04:46.317 - warn: 	No access to release DRIVE Software 9.0. Message undefined
2019-05-31 01:04:46.319 - error: devzone get download url failed with error: null. Status code: 403
2019-05-31 01:04:46.319 - warn: 	No access to release DRIVE Software 8.0. Message undefined
2019-05-31 01:04:46.336 - error: devzone get download url failed with error: null. Status code: 403
2019-05-31 01:04:46.337 - warn: 	No access to release DRIVE OS 5.0.10.3 SDK with DriveWorks. Message undefined
2019-05-31 01:04:46.340 - error: devzone get download url failed with error: null. Status code: 403
2019-05-31 01:04:46.341 - warn: 	No access to release JetPack 4.2.1 EA. Message undefined
2019-05-31 01:04:47.042 - info: step1 load in ms: 2668.0550000000076
2019-05-31 01:04:47.042 - info: Web server configuration build version 570D165J is set
2019-05-31 01:04:47.062 - info: Checking for update with mainRepoURL: https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json
2019-05-31 01:04:47.135 - info: sdkml1_repo.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json has been downloaded to /home/jetpack/.nvsdkm/dist successfully.

The SDK Manager 0.9.12 is available at https://developer.nvidia.com/embedded/dlc/nv-sdk-manager

I tried to use The SDK Manager 0.9.12.
But, sdk-manager crashed on Ubuntu 18.04.

2019-05-31 01:19:13.951 - info: forking worker process
2019-05-31 01:19:13.959 - info: initializing the download service
2019-05-31 01:19:13.970 - info: forking a child process for the download service pid 65
2019-05-31 01:19:14.007 - info: Initializing download manager with 6
2019-05-31 01:19:14.394 - info: number of download processes set to 6
2019-05-31 01:19:14.455 - info: Begin to create timing task for auto update.
2019-05-31 01:19:14.499 - info: Host OS: Ubuntu1804
2019-05-31 01:19:14.499 - info: packageJson: /opt/nvidia/sdkmanager/resources/app/package.json
2019-05-31 01:19:14.508 - info: download service message loading the download service
initialized download service
got heartbeat request

2019-05-31 01:19:14.508 - info: download process is alive
2019-05-31 01:19:14.509 - error: cannot find a opts object for url undefined
2019-05-31 01:19:14.509 - info: download service is alive
2019-05-31 01:19:14.524 - info: config: 
{ mainRepoURL: 'https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json',
  PIDServer: 'P',
  DevZoneServer: 'P' }
2019-05-31 01:19:14.528 - info: initDevzoneTab...
2019-05-31 01:19:14.531 - info: requesting WebContents...
2019-05-31 01:19:14.542 - info: manifest: {"name":"sdkmanager","version":"0.9.12","revision":"0","buildNumber":"4180","release":false}
2019-05-31 01:19:14.542 - info: Setting GA parameters: title SDK Manager 0.9.12.4180 version 0.9.12 dev: 0 internal: false 
2019-05-31 01:19:14.542 - info: autoLogin failed: Aborting auto login since there is no logged in user
2019-05-31 01:19:14.543 - info: [Proxy Agent] No proxy agent
2019-05-31 01:19:14.546 - info: mainRepoUrl: https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json
2019-05-31 01:19:14.547 - info: logging in with l1 url: https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json
2019-05-31 01:19:14.579 - warn: crontab read failure with Error: Command failed: crontab -l
no crontab for jetpack

2019-05-31 01:19:14.589 - warn: crontab read failure with Error: Command failed: crontab -l
no crontab for jetpack

2019-05-31 01:19:14.636 - info: Create timing task for auto update successfully.
2019-05-31 01:19:32.964 - info: Logging in with sso login method…
2019-05-31 01:19:32.979 - info: posting login request. url: https://devzone.auth0.com/oauth/token
2019-05-31 01:19:32.996 - info: [Proxy Agent] No proxy agent
2019-05-31 01:19:34.956 - info: get user programs. url: https://developer.nvidia.com/api/assets/v1/current_user_sdk/programs
2019-05-31 01:19:34.959 - info: [Proxy Agent] No proxy agent
2019-05-31 01:19:36.210 - info: the DevZone programs that user can access:
2019-05-31 01:19:36.210 - info: { id: xxxxxx, name: GameWorks Registered Developer Program }
2019-05-31 01:19:36.210 - info: { id: yyyyyy, name: NVIDIA Developer Program }
2019-05-31 01:19:36.210 - info: { id: zzzzzz, name: Isaac SDK }
2019-05-31 01:19:36.223 - info: Retrieving Data…
2019-05-31 01:19:36.223 - info: Processing Data…
2019-05-31 01:19:40.097 - info: Usage and platform data collection via Google Analytics sets to false
2019-05-31 01:19:40.099 - info: [Proxy Agent] No proxy agent
2019-05-31 01:19:40.101 - info: Loading data from server: l1url. Url: https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json
2019-05-31 01:19:40.122 - info: [Proxy Agent] No proxy agent
2019-05-31 01:19:40.209 - info: sdkml1_repo.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json has been downloaded to /home/jetpack/.nvsdkm/dist successfully.
2019-05-31 01:19:40.261 - info: [Proxy Agent] No proxy agent
2019-05-31 01:19:40.278 - info: [Proxy Agent] No proxy agent
2019-05-31 01:19:40.295 - info: [Proxy Agent] No proxy agent
2019-05-31 01:19:40.316 - info: [Proxy Agent] No proxy agent
2019-05-31 01:19:40.362 - info: sdkml2_drive_linux.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/DRIVE/Linux/sdkml2_drive_linux.json has been downloaded to /home/jetpack/.nvsdkm/dist successfully.
2019-05-31 01:19:40.398 - info: validating product line for target OS: Linux
2019-05-31 01:19:40.398 - info: 	validating release: DRIVE Software 9.0
2019-05-31 01:19:40.398 - info: 	validating release: DRIVE Software 8.0
2019-05-31 01:19:40.398 - info: 	validating release: DRIVE Software 8.0
2019-05-31 01:19:40.398 - info: 	validating release: DRIVE OS 5.1.6.0 PDK
2019-05-31 01:19:40.399 - info: 	validating release: DRIVE OS 5.1.6.0 SDK
2019-05-31 01:19:40.399 - info: 	validating release: DRIVE OS 5.1.3.0 PDK
2019-05-31 01:19:40.399 - info: 	validating release: DRIVE OS 5.1.3.0 SDK
2019-05-31 01:19:40.399 - info: 	validating release: DRIVE OS 5.1.0.0 PDK
2019-05-31 01:19:40.399 - info: 	validating release: DRIVE OS 5.1.0.0 SDK
2019-05-31 01:19:40.399 - info: 	validating release: DRIVE OS 5.0.10.3 SDK with DriveWorks
2019-05-31 01:19:40.399 - info: 	validating release: DRIVE OS 5.0.10.3 PDK
2019-05-31 01:19:40.399 - warn: No access to devzone program id 879192
2019-05-31 01:19:40.399 - warn: No access to devzone program id 879192
2019-05-31 01:19:40.399 - warn: No access to devzone program id -1
2019-05-31 01:19:40.399 - warn: No access to devzone program id -1
2019-05-31 01:19:40.399 - warn: No access to devzone program id -1
2019-05-31 01:19:40.399 - warn: No access to devzone program id -1
2019-05-31 01:19:40.400 - warn: No access to devzone program id -1
2019-05-31 01:19:40.400 - warn: No access to devzone program id -1
2019-05-31 01:19:40.400 - warn: No access to devzone program id -1
2019-05-31 01:19:40.400 - warn: No access to devzone program id 876061
2019-05-31 01:19:40.400 - warn: No access to devzone program id -1
2019-05-31 01:19:40.400 - warn: 	No access to release DRIVE Software 9.0. Message undefined
2019-05-31 01:19:40.400 - warn: 	No access to release DRIVE Software 8.0. Message undefined
2019-05-31 01:19:40.400 - warn: 	No access to release DRIVE Software 8.0. Message undefined
2019-05-31 01:19:40.400 - warn: 	No access to release DRIVE OS 5.1.6.0 PDK. Message undefined
2019-05-31 01:19:40.400 - warn: 	No access to release DRIVE OS 5.1.6.0 SDK. Message undefined
2019-05-31 01:19:40.400 - warn: 	No access to release DRIVE OS 5.1.3.0 PDK. Message undefined
2019-05-31 01:19:40.400 - warn: 	No access to release DRIVE OS 5.1.3.0 SDK. Message undefined
2019-05-31 01:19:40.400 - warn: 	No access to release DRIVE OS 5.1.0.0 PDK. Message undefined
2019-05-31 01:19:40.400 - warn: 	No access to release DRIVE OS 5.1.0.0 SDK. Message undefined
2019-05-31 01:19:40.400 - warn: 	No access to release DRIVE OS 5.0.10.3 SDK with DriveWorks. Message undefined
2019-05-31 01:19:40.400 - warn: 	No access to release DRIVE OS 5.0.10.3 PDK. Message undefined
2019-05-31 01:19:40.402 - info: sdkml2_drive_qnx.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/DRIVE/QNX/sdkml2_drive_qnx.json has been downloaded to /home/jetpack/.nvsdkm/dist successfully.
2019-05-31 01:19:40.434 - info: validating product line for target OS: QNX
2019-05-31 01:19:40.434 - info: 	validating release: DRIVE OS 5.1.6.0 PDK
2019-05-31 01:19:40.434 - info: 	validating release: DRIVE OS 5.1.6.0 SDK
2019-05-31 01:19:40.434 - info: 	validating release: DRIVE OS 5.1.3.0 PDK
2019-05-31 01:19:40.434 - info: 	validating release: DRIVE OS 5.1.3.0 SDK
2019-05-31 01:19:40.434 - info: 	validating release: DRIVE OS 5.0.13.2 (with DRIVE AV)
2019-05-31 01:19:40.435 - warn: No access to devzone program id -1
2019-05-31 01:19:40.435 - warn: No access to devzone program id -1
2019-05-31 01:19:40.435 - warn: No access to devzone program id -1
2019-05-31 01:19:40.435 - warn: No access to devzone program id -1
2019-05-31 01:19:40.435 - warn: No access to devzone program id -1
2019-05-31 01:19:40.435 - warn: 	No access to release DRIVE OS 5.1.6.0 PDK. Message undefined
2019-05-31 01:19:40.435 - warn: 	No access to release DRIVE OS 5.1.6.0 SDK. Message undefined
2019-05-31 01:19:40.435 - warn: 	No access to release DRIVE OS 5.1.3.0 PDK. Message undefined
2019-05-31 01:19:40.435 - warn: 	No access to release DRIVE OS 5.1.3.0 SDK. Message undefined
2019-05-31 01:19:40.435 - warn: 	No access to release DRIVE OS 5.0.13.2 (with DRIVE AV). Message undefined
2019-05-31 01:19:40.439 - info: sdkml2_jetson_linux.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/Jetson/Linux/sdkml2_jetson_linux.json has been downloaded to /home/jetpack/.nvsdkm/dist successfully.
2019-05-31 01:19:40.440 - info: sdkml2_sdkmanager_linux_deb.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/SDKMANAGER/Linux/sdkml2_sdkmanager_linux_deb.json has been downloaded to /home/jetpack/.nvsdkm/dist successfully.
2019-05-31 01:19:40.461 - info: validating product line for target OS: Linux
2019-05-31 01:19:40.462 - info: 	validating release: JetPack 4.2.1 EA
2019-05-31 01:19:40.462 - info: 	validating release: JetPack 4.2
2019-05-31 01:19:40.462 - warn: No access to devzone program id 879404
2019-05-31 01:19:40.462 - info: Can access to devzone program id 874688
2019-05-31 01:19:40.468 - info: [Proxy Agent] No proxy agent
2019-05-31 01:19:40.474 - warn: 	No access to release JetPack 4.2.1 EA. Message undefined
2019-05-31 01:19:40.490 - info: validating product line for target OS: 
2019-05-31 01:19:40.490 - info: 	validating release: SDK Manager
2019-05-31 01:19:40.490 - warn: Empty devzone program id, user can access this program
2019-05-31 01:19:41.700 - info: step1 load in ms: 1599.2249999999985
2019-05-31 01:19:41.700 - info: Web server configuration build version 570D165J is set
2019-05-31 01:19:41.716 - info: Checking for update with mainRepoURL: https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json
2019-05-31 01:19:41.743 - info: [Proxy Agent] No proxy agent
2019-05-31 01:19:41.783 - info: sdkml1_repo.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json has been downloaded to /home/jetpack/.nvsdkm/dist successfully.
2019-05-31 01:19:41.790 - info: [Proxy Agent] No proxy agent

It looks like there are several network failures. Are you behind a proxy or firewall?

Hi linuxdev,

Thank you for your reply.

It looks like there are several network failures. Are you behind a proxy or firewall?

The proxy and firewall were disabled.

I can’t explain it, but it still looks as if a number of network failures occurred. It could have been as simple as DNS failure. However, I do have a suggestion as follows…

Run this again, but set it just for flash or just package addition to the Jetson (you get to pick). After it fails there will be a file “~/Downloads/nvidia/sdkm_downloads/sdkml3_jetpack_l4t_42.json” (or something close to that name with a “.json” suffix). Save a copy with the file name suffix “.txt”, and attach it here in the forums (on one of your existing posts you can hover your mouse over the quote icon in the upper right and some other icons will show up…the paper clip icon allows file attachment).

You will also find in this file a reference of “compDirectory” with a URL. If you paste this into a browser and go there, then regardless of whether the page exists or not, do you get to the web page where you can log in? I am more curious about whether you can reach the server than whether it allows any particular page access.

After it fails there will be a file “~/Downloads/nvidia/sdkm_downloads/sdkml3_jetpack_l4t_42.json” (or something close to that name with a “.json” suffix).

I check this point.

  • sdkml3_jetpack_l4t_42.json has not been downloaded
  • ~/Downloads/nvidia/sdkm_downloads directory has not been created
  • And, I checked ~/.nvsdkm/dist

    $ cd ~/.nvsdkm/dist
    $ ls
    sdkml1_repo.json  sdkml2_drive_linux.json  sdkml2_drive_qnx.json  sdkml2_jetson_linux.json  sdkml2_sdkmanager_linux_deb.json
    

    In the “sdkml3_jetson_linux.json” do you have a line for “compDirectory”? Is the URL:
    https://developer.nvidia.com/assets/embedded/secure/tools/files/jetpack-sdks/jetpack-4.2/JETPACK_42_b158/

    Although you wouldn’t find content there, if you go to that URL does it ask for you to log in?

    Notice that if you have logged in to that base URL, then the following should work if networking is correct:

    1. Observe the CUDA repo URL in the "downloadFiles" part of the json: "/cuda-repo-cross-aarch64-10-0-local-10.0.166_1.0-1_all.deb"
    2. Append this to the base address mentioned at the top to obtain: https://developer.nvidia.com/assets/embedded/secure/tools/files/jetpack-sdks/jetpack-4.2/JETPACK_42_b158/cuda-repo-cross-aarch64-10-0-local-10.0.166_1.0-1_all.deb
    3. Because you are already logged in at the base URL entering that full address in your browser should result in the download of that ".deb" file.

    Are you able to verify from that host that this step works? If so, then I’d say at least part of networking is valid, and if not, then this is why it is failing. This is essentially what the package download step is doing. Your json would possibly have a different base URL depending on region of the world or if there are version updates. The cuda-repo is just one example of the files needing download. Various P3310 packages might also be needed, and here is an example constructed similar to the previous one, but it appends “P3310/Jetson_Linux_R32.1.0_aarch64.tbz2” instead of the “.deb” and should result in a download if you are already logged in (remember the base address might be different for you):
    https://developer.nvidia.com/assets/embedded/secure/tools/files/jetpack-sdks/jetpack-4.2/JETPACK_42_b158/P3310/Jetson_Linux_R32.1.0_aarch64.tbz2

    In the “sdkml3_jetson_linux.json” do you have a line for “compDirectory”? Is the URL:
    https://developer.nvidia.com/assets/embedded/secure/tools/files/jetpack-sdks/jetpack-4.2/JETPACK_42_b158/

    SDK manager could not download “sdkml3_jetson_linux.json”.
    https://devtalk.nvidia.com/default/topic/1052739/jetson-tx2/nvidia-sdk-manager-crashed-unexpected/post/5347356/#5347356

    So, I could not read this file.
    And, I could access the following URL using browser.
    https://developer.nvidia.com/assets/embedded/secure/tools/files/jetpack-sdks/jetpack-4.2.1/JETPACK_421_b34/sdkml3_jetpack_l4t_421.json

    I tried to use “command line install”.
    https://docs.nvidia.com/sdk-manager/sdkm-command-line-install/index.html

    $ sdkmanager --cli install --user hoge@example.com --logintype devzone --product Jetson --version 4.2 --targetos Linux --host
    

    As a result, this method could install all package on host.
    But, I could not understand that SDK Manager(GUI) crashed unexpected.

    I’m not sure what is going on. There are different “.json” files for different manifests, but a manifest is mandatory before SDKM will know what to download. So long as SDKM knows what to download it should work. So long as proxy and firewall are disabled and the above manual download tests succeeded, then there shouldn’t be a network error. Having a crash from CLI tends to imply there is some other problem, but I’m not sure CLI actually works as expected.

    My only suggestion at this point, if you need to keep installing, is to completely delete any of the SDK Manager content (including “~/Downloads/nvidia/sdkm_downloads/” if it exists and “~/nvidia/”, and downloading the SDKM itself fresh and installing it again) and flash again, and then try just flash. Before the flash make sure the following host side dependencies are met:

    sudo apt --fix-broken install
    sudo apt-get install libgconf-2-4 libcanberra-gtk-module
    sudo apt-get install python
    sudo apt-get install sshpass
    

    Only after regular flash succeeds, then try to run component install to only the Jetson, starting with an attempt to install CUDA. Then a separate attempt to install everything else to the Jetson, except for samples. Then do the same for the host side if you are interested in that, and don’t install samples until everything else is installed. On the first error or issue add a note here in forums.

    Hi dandelion1124,
    Could you share what is the command output when run SDK Manager(GUI)?

    sdkmanager --spectron --enable-logging -v=1

    @linuxdev I’ll try your suggestion.

    @changbins

    Could you share what is the command output when run SDK Manager(GUI)?

    sdkmanager --spectron --enable-logging -v=1

    I try it.

    $ sdkmanager --spectron --enable-logging -v=1
    [607:0603/140314.675153:VERBOSE1:zygote_main_linux.cc(537)] ZygoteMain: initializing 0 fork delegates
    [607:0603/140314.675629:INFO:cpu_info.cc(50)] Available number of cores: 8
    [605:0603/140314.924539:ERROR:bus.cc(395)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
    [605:0603/140314.929915:VERBOSE1:pulse_util.cc(138)] Failed to connect to the context.  Error: Connection refused
    [605:0603/140314.932176:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Google 'Aviator' log
    [605:0603/140314.932197:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Google 'Icarus' log
    [605:0603/140314.932206:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Google 'Pilot' log
    [605:0603/140314.932213:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Google 'Rocketeer' log
    [605:0603/140314.932220:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Google 'Skydiver' log
    [605:0603/140314.932228:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: DigiCert Log Server
    [605:0603/140314.932234:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: DigiCert Log Server 2
    [605:0603/140314.932241:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Symantec log
    [605:0603/140314.932248:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Symantec 'Vega' log
    [605:0603/140314.932255:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Symantec 'Sirius' log
    [605:0603/140314.932262:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: WoSign log
    [605:0603/140314.932269:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Venafi Gen2 CT log
    [605:0603/140314.932276:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: CNNIC CT log
    [605:0603/140314.932283:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: StartCom log
    [605:0603/140314.932290:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Comodo 'Sabre' CT log
    [605:0603/140314.932297:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Comodo 'Mammoth' CT log
    [605:0603/140314.932304:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Izenpe log
    [605:0603/140314.932311:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Venafi log
    [605:0603/140314.932318:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Certly.IO log
    [605:0603/140314.936179:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Google 'Aviator' log
    [605:0603/140314.936203:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Google 'Icarus' log
    [605:0603/140314.936212:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Google 'Pilot' log
    [605:0603/140314.936219:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Google 'Rocketeer' log
    [605:0603/140314.936225:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Google 'Skydiver' log
    [605:0603/140314.936232:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: DigiCert Log Server
    [605:0603/140314.936240:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: DigiCert Log Server 2
    [605:0603/140314.936247:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Symantec log
    [605:0603/140314.936255:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Symantec 'Vega' log
    [605:0603/140314.936260:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Symantec 'Sirius' log
    [605:0603/140314.936266:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: WoSign log
    [605:0603/140314.936271:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Venafi Gen2 CT log
    [605:0603/140314.936276:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: CNNIC CT log
    [605:0603/140314.936284:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: StartCom log
    [605:0603/140314.936295:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Comodo 'Sabre' CT log
    [605:0603/140314.936302:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Comodo 'Mammoth' CT log
    [605:0603/140314.936309:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Izenpe log
    [605:0603/140314.936315:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Venafi log
    [605:0603/140314.936321:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Certly.IO log
    [605:0603/140314.942794:VERBOSE1:bluez_dbus_manager.cc(172)] Bluetooth not supported.
    Gtk-Message: 14:03:34.284: GtkDialog mapped without a transient parent. This is discouraged.
    [605:0603/140335.356806:VERBOSE1:bluez_dbus_manager.cc(241)] BluezDBusManager Shutdown completed
    [605:0603/140335.357244:VERBOSE1:dbus_thread_manager_linux.cc(63)] LinuxDBusManager Shutdown completed
    

    Hi,

    From error log
    [605:0603/140314.924539:ERROR:bus.cc(395)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

    Looks dbus is not set up correct on your side. What is the output of “# ls -la /var/run/dbus/”?

    Will it helps to resolve the issue by:

    sudo apt-get install dbus

    sudo /etc/init.d/dbus start

    Hi dandelion1124,

    Have you managed to resolve the problem or still an issue to support?

    Thanks

    I could not resolve this problem. So, I tried to use SDK Manager on Docker container.
    https://devtalk.nvidia.com/default/topic/1055328/jetson-agx-xavier/nvidia-sdk-manager-on-docker-container/

    Hello! Unfortunately this does not work on Docker. dbus launched in the right way. It can be seen
    $ sudo service dbus status

    • dbus is running
      Does anyone have any ideas on what could be the problem with stopping the sdkmanager on Docker?

    Hi Alex_VR,

    Unfortunately this does not work on Docker.

    Could you please give me the following information?
    Because, I hope to know the cause of this problem.

    • OS of Host PC
    • SDK Manager Version
    • Target Device
    • Error message or Screenshot

    If this problem is caused by this Dockerfile, I think that you should report to https://github.com/atinfinity/sdk_manager_docker/issues.

    Does anyone have any ideas on what could be the problem with stopping the sdkmanager on Docker?

    I think that there is no problem on host platform if you stop sdkmanager on Docker.

    OS of Host PC is Ubuntu 18.04.2 LTS
    SDK manager version is 0.9.12-4180
    Target Device is Jetson TX2

    I tried to get a working configuration of Dockerfile by manually installing packages to cudagl:10.1-runtime-ubuntu18.04 image from NGC. To run container I used
    $ nvidia-docker run -it --rm -e DISPLAY=unix$DISPLAY --privileged -v /dev/bus/usb:/dev/bus/usb -v /tmp/.X11-unix:/tmp/.X11-unix -v ~/sdkmanager-host/:/root/sdkmanager-container nvcr.io/nvidia/cudagl:10.1-runtime-ubuntu18.04.

    After installing this packages as root
    libgconf-2-4 locales libgtk-3-common libcanberra-gtk3-module libxss1 libnss3
    and fixing all dependencies I installed the sdkmanager.

    The main window of the sdkmanager running properly, but when I try to login to my profile I have a message
    “NVIDIA SDK Manager Crashed Unexpected, relaunch or exit”

    After closing message window on terminal I have this
    (sdkmanager:47): dbind-WARNING **: 20:08:45.756: Couldn’t connect to accessibility bus: Failed to connect to socket /tmp/dbus-Ep8vsbkyVC: Connection refused
    Gtk-Message: 20:19:33.718: GtkDialog mapped without a transient parent. This is discouraged.

    I also tried to use Dockerfile from https://github.com/atinfinity/sdk_manager_docker, but got the same problem.

    Hi Alex_VR,

    After installing this packages as root
    libgconf-2-4 locales libgtk-3-common libcanberra-gtk3-module libxss1 libnss3
    and fixing all dependencies I installed the sdkmanager.

    Could you please refer to the following script?This file contains installed package using apt-get.
    https://github.com/atinfinity/sdk_manager_docker/blob/master/Dockerfile

    And, could you please refer to the following script? This file contains the “docker -run” options.
    https://github.com/atinfinity/sdk_manager_docker/blob/master/launch_container.sh

    When I made “sdk_manager_docker”, I found that SDK Manager requires a lot of shared memory.
    So, I add “–shm-size=1gb” as “docker -run” option.