I get an error installing AutoChauffeur with SDK Manager 1.2.0.6738 on my host
(Ubuntu 16, 500GB free, cuda 9.2, nvidia 396, AutoCruise 1.2.400, PDK 5.0.10.3)
P2379 specific package: Unknown download error
All other packages are successfully installed - where does that come from?
Terminal output shows
Dear @hermann.f,
The error could issue with internet while downloading. Do you see flashing is successful via sdkmanager? Could you attach sdkm logs(~/.nvsdkm/logs and ~/.nvsdkm/sdkm.log) here for verification.
Well, I’m not sure if trying to flash the system while an error has just happened before is a good idea - so I skipped that step. Regarding internet access: I am able to get internet access, I it possible that somehow my credentials are not active in the SDK Manager - maybe due to token expiration?
In .nvsdkm/logs there is no NV_P2379_SPECIFIC_PACKAGE_COMP.log - which seems reasonable as the download failed, but in .nvsdkm/sdkm.log I can see an error: No access to release DRIVE OS 5.0.13.2 (with DRIVE AV).
as SDKManager can not verify my credentials error: Not NVOnline user
Can you please give me some advice, how to proceed, as I need to update the P2379 platform in a timely manner,
Thanks.
23:00:38.611 - info: validating release: DRIVE OS 5.1.12.4 SDK
23:00:38.611 - warn: Empty devzone program id, need to validate l3 url
23:00:38.612 - error: Not NVOnline user
23:00:38.612 - warn: No access to release DRIVE OS 5.1.12.4 SDK. Message invalid level3 json path
23:00:38.612 - info:
23:00:38.612 - info: validating release: DRIVE OS 5.1.12.0 SDK
23:00:38.612 - warn: No access to devzone program id -1
23:00:38.612 - warn: No access to release DRIVE OS 5.1.12.0 SDK.
23:00:38.612 - info:
23:00:38.612 - info: validating release: DRIVE OS 5.1.12.0 PDK
23:00:38.613 - warn: No access to devzone program id -1
23:00:38.613 - warn: No access to release DRIVE OS 5.1.12.0 PDK.
23:00:38.613 - info:
23:00:38.613 - info: validating release: DRIVE OS 5.1.9.0 SDK
23:00:38.613 - warn: No access to devzone program id -1
23:00:38.613 - warn: No access to release DRIVE OS 5.1.9.0 SDK.
23:00:38.613 - info:
23:00:38.613 - info: validating release: DRIVE OS 5.1.9.0 PDK
23:00:38.614 - warn: No access to devzone program id -1
23:00:38.614 - warn: No access to release DRIVE OS 5.1.9.0 PDK.
23:00:38.614 - info:
23:00:38.614 - info: validating release: DRIVE OS 5.1.6.0 PDK
23:00:38.614 - warn: No access to devzone program id -1
23:00:38.614 - warn: No access to release DRIVE OS 5.1.6.0 PDK.
23:00:38.614 - info:
23:00:38.614 - info: validating release: DRIVE OS 5.1.6.0 SDK
23:00:38.614 - warn: No access to devzone program id -1
23:00:38.615 - warn: No access to release DRIVE OS 5.1.6.0 SDK.
23:00:38.615 - info:
23:00:38.615 - info: validating release: DRIVE OS 5.1.3.0 PDK
23:00:38.615 - warn: No access to devzone program id -1
23:00:38.615 - warn: No access to release DRIVE OS 5.1.3.0 PDK.
23:00:38.615 - info:
23:00:38.615 - info: validating release: DRIVE OS 5.1.3.0 SDK
23:00:38.615 - warn: No access to devzone program id -1
23:00:38.616 - warn: No access to release DRIVE OS 5.1.3.0 SDK.
23:00:38.616 - info:
23:00:38.616 - info: validating release: DRIVE OS 5.0.13.2 (with DRIVE AV)
23:00:38.616 - warn: No access to devzone program id -1
23:00:38.616 - warn: **No access to release DRIVE OS 5.0.13.2 (with DRIVE AV). **
23:00:38.817 - info: step1 load in ms: 1095.7449999996243
23:00:38.817 - info: Web server configuration build version 1003D584J23C is set
23:00:38.901 - info: cleaning the group map
23:00:38.901 - info: BundleData constructMap
Dear @hermann.f,
Can you please delete ~/.nvsdkm folder and check flashing again. Please select NVIDIA DEVELOPER tab while logging into sdkmanager. Please attach all the logs as zip file for initial triage.
Strange, it seems access has been blocked by Nvidias security watchdog due to suspicious activities from my IP address - so the SDKManager’s oauth token request failed, which then caused the download error.
It’s good to know, that Nvidia takes security seriously.
Apart from that, I hope the problem is solved now.
Sorry to bother again, but since yesterday, after the event of blocking an IP address due to suspicious activities (why ever that might be) and unblocking it by clicking the received link, I am unable to install or update my Drive PX2 platform. This is really anoying. The sdkm.log info tells me:
validating release: DRIVE OS 5.0.10.3 SDK with Driveworks
Can access to devzone program 876061
validating release: DRIVE OS 5.0.10.3 PDK
No access to devzone programm id -1
No access to release DRIVE OS 5.0.10.3 PDK.
Attached you see the my membership account information window, which tells me everything is ok - so can you please give me some advice how to proceed?
Thanks,
The separation between Drive OS SDK and Drive OS PDK seems to be the problem, allthough I would have thought, both are needed as integral parts of the Developer Program for Drive PX2…
Dear @hermann.f,
I don’t see any issue with your account as per screenshot. Could you please confirm if you still have issue with flashing. If so, please attach complete logs as requested earlier. If you are able to flash, we can close this thread.
Dear @SivaRamaKrishnaNV,
I have removed the .nvsdkm directory, furthermore changed the loglevel in the SDKManager 1.2.0.6738 to Debug, Moreover, I have seen, that SDKManager stores its downloaded packages in Downloads/nvidia/sdkm_downloads with very strange user and group settings - definitely not as me (cuda)
So what I have tried was, to recursively change owner and group underneath Downloads/nvidia/sdkm_downloads to cuda:cuda. The result is: that SDKManager was able to download the packages now, but fails to create a symbolic link.
From SDKManager terminal window:
- INFO: OSS and NV packages: .install/drive-t186ref-linux/xenial_ubuntu_rootfs_startup: Installation cancelled, error in: setup_rootfs.sh
- 12:01:35 SUMMARY: OSS and NV packages: Failed to create symbolic link
The sdkm.log shows an HTTP 500 (internal server) error
11:48:40.695 - info: initializeGroups. User selections: Product: DRIVE Version: 5.0.10.3 OS selectedHW: host_target selectedTargetCategoryId: PX2_AUTOCHAUFFEUR selectedOS: Linux
11:48:40.763 - info: loading l3 data from repo url:
[
‘https://developer.nvidia.com/drive/secure/drive_bundles/Drive_50103L_SDK_b135_OS_GA/sdkml3_drive_linux_50103_sdk_os.json’
]
11:48:40.767 - info: EulaFolder: /opt/nvidia/sdkmanager/Eula/
11:48:41.116 - error: devzone get download url failed with error: HTTPError: Response code 500 (Internal Server Error).
11:48:41.117 - error: error upgrading schema
Attached, find the corresponding sdkm.log
sdkm.log (733.5 KB)
Where does that 500 error come from?
Dear @hermann.f,
Do you constantly see HTTPError: Response code 500 (Internal Server Error). If possible, could you check flashing from different network/host. It is expected to work with out any file permission changes. I could download https://developer.nvidia.com/drive/secure/drive_bundles/Drive_50103L_SDK_b135_OS_GA/sdkml3_drive_linux_50103_sdk_os.json without any issue.
Dear @hermann.f,
Is this issue solved?
Yes, the error has vanished after updating the SDK Manager to 1.3.
