Skip to content

Failed to register the server's public keyΒ #9289

Closed

Description

@JJONSOO

Required Info
Camera Model D455
Firmware Version (Open RealSense Viewer --> Click info)
Operating System & Version Ubuntu 18
Kernel Version (Linux Only) 4.9.201
Platform NVIDIA Jetson
SDK Version 2.47.0
Language C++
Segment Devolopment

Issue Description

https://github.com/IntelRealSense/librealsense/blob/master/doc/distribution_linux.md
When installing packages from the following website, I have an error when trying to register the server's public key.
Please let me know if you can help

Activity

  1. MartyG-RealSense commented on Jun 25, 2021

    @MartyG-RealSense

    Hi @JJONSOO You could check whether the problem with retrieving the server key is occurring because of a firewall, as described in the link below.

    #1276

    It is more likely though that as you have a Jetson, you should use the server key instructions in section 5. Register the server's public key of Intel's official package installation instructions for Jetson instead of using the distribution_linux.md page.

    This is because the packages installed with the distribution_linux instructions are designed for processors with an x86 / x64 architecture and not the Arm processors of Jetson boards.

    https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_jetson.md

  2. JJONSOO commented on Jun 28, 2021

    @JJONSOO
    Author

    Hi, I finished everything on the site you pointed out and tried to execute the example file, but I have an error
    api version mismatch : librealsense.so was compiled with API version 2.41.0 but the application was compiled with 2.42.0 make sure correct version of the library is installed
    What should I do?

  3. MartyG-RealSense commented on Jun 28, 2021

    @MartyG-RealSense

    The error suggests that the example program was created in a version of librealsense that is newer than the one that you have installed from packages.

    There was a recent case in which a RealSense user was installing librealsense packages for their Jetson but it was only librealsense 2.41.0 instead of the latest 2.47.0 version. Doronhi the RealSense ROS wrapper developer commented on this in the link below.

    realsenseai/realsense-ros#1938 (comment)

    The RealSense user in that case instead built librealsense for their Jetson from source code using the instructions in Doronhi's comment.

  4. hanzheteng commented on Jul 2, 2021

    @hanzheteng

    Hi @MartyG-RealSense,

    I encountered the same issue. It seems like the instructions in section 5. Register the server's public key in installation_jetson is the same as the one in distribution_linux.

    The bottleneck is on this command: sudo apt-key adv --keyserver keys.gnupg.net --recv-key F6E65AC044F831AC80A06380C8B3A55A6F3EFCDE It will lead to the error gpg: keyserver receive failed: No name on my Jetson Xavier NX device. I also tried this command via my phone hotspot, so less likely due to firewall? (Also the prompted error in the case of firewall is different.)

    PS. I used to successfully installed everything on a Jetson AGX Xavier device following the same instructions as in distribution_linux about half a year ago.

    Update: The same error occurred on my x86 machine.

  5. MartyG-RealSense commented on Jul 3, 2021

    @MartyG-RealSense

    Hi @hanzheteng I recommend using the Jetson installation page's package instructions for installing packages on Jetson (section 4. Install with Debian Packages) as the Debian packages on the distribution_linux page are designed for use with x86 / x64 computers.

    If you were attempting to install the SDK from packages recently and did not succeed, there was an issue with Debian packages for the latest 2.48.0 release (including Jetson ones) at the time of release that has now been resolved. So if you haven't attempted an installation again during the last couple of days, it may be worth trying the installation again.

    #9315 (comment)

  6. hanzheteng commented on Jul 3, 2021

    @hanzheteng

    Hi @MartyG-RealSense ,

    As I mentioned earlier, this error also occurred on amd64 machines, so it is not related to Jetson platform. (Also, there is no actual instruction under 4. Install with Debian Packages if you take a look.)

    The main issue here is that the key server keys.gnupg.net is not functioning anymore. Someone reported this recent issue here.

    The solution is to replace the key server keys.gnupg.net by keyserver.ubuntu.com or other functioning ones. In both instructions (installation_jetson and distribution_linux), use the following command to register the server's public key should fix this problem.

    sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-key F6E65AC044F831AC80A06380C8B3A55A6F3EFCDE || sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-key F6E65AC044F831AC80A06380C8B3A55A6F3EFCDE

    Please double check and update the instructions accordingly.

  7. MartyG-RealSense commented on Jul 3, 2021

    @MartyG-RealSense

    #9315 (comment) was not only related to Jetson, so it was a valid suggestion for a problem that could occur on both x86/x64 and the Arm-based Jetson.

    You have a point about item 4. Coming in at 5. Register the server's public key is better.

    The link about keys.gnupg.net was my original message to you, which I edited out because I believed that #9315 (comment) was worth looking at first as a more likely possibility. So it's great to hear that the original suggestion worked for you after all.

    I will highlight the above information to Intel. Thanks very much for the update!

  8. hanzheteng commented on Jul 3, 2021

    @hanzheteng

    Thank you for the time and effort for helping out. The original message did help. Please convey the message to Intel about the possibly deprecated key server then.

  9. MartyG-RealSense commented on Jul 6, 2021

    @MartyG-RealSense

    Hi @hanzheteng I have received a response from Intel about this issue. They said that the changes to the keyserver addresses were announced several months ago. The official instruction pages already include the alternate '||' keyserver address.

    distribution_linux.md
    https://github.com/IntelRealSense/librealsense/blob/master/doc/distribution_linux.md

    sudo apt-key adv --keyserver keys.gnupg.net --recv-key F6E65AC044F831AC80A06380C8B3A55A6F3EFCDE || sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-key F6E65AC044F831AC80A06380C8B3A55A6F3EFCDE

    Jetson
    https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_jetson.md

    sudo apt-key adv --keyserver keys.gnupg.net --recv-key F6E65AC044F831AC80A06380C8B3A55A6F3EFCDE || sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-key F6E65AC044F831AC80A06380C8B3A55A6F3EFCDE

  10. hanzheteng commented on Jul 7, 2021

    @hanzheteng

    Thank you for the clarification. I just verified on a clean Ubuntu 18 virtual machine that the second part also works.

    The behavior of the first part varies on different machines. On some machines it returns immediately, but on some other machines it can take 10s to return the No Name error. The first time I ran this line of command, the first part was not responding and interrupted by me, so the second part was not actually being executed.

  11. MartyG-RealSense commented on Jul 7, 2021

    @MartyG-RealSense

    Thanks very much @hanzheteng for your test feedback!

  12. MartyG-RealSense commented on Jul 13, 2021

    @MartyG-RealSense

    Hi @JJONSOO Do you require further assistance with this case, please? Thanks!

  13. MartyG-RealSense commented on Jul 19, 2021

    @MartyG-RealSense

    Case closed due to no further comments received.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions