"Key server error" on installing kinetic on ubuntu 16.04
Hi
I am trying to install ros kinectic on ubuntu 16.04. I am receiving the error below when trying to install.
sudo apt-key adv --keyserver hkp://ha.pool.sks-keyservers.net:80 --recv-key 0xB01FA116
Error:
Executing: /tmp/tmp.nMOeeZtYBM/gpg.1.sh --keyserver
hkp://ha.pool.sks-keyservers.net:80
--recv-key
0xB01FA116
gpg: requesting key B01FA116 from hkp server ha.pool.sks-keyservers.net
gpg: keyserver timed out
gpg: keyserver receive failed: keyserver error
Is this an error due to key server not responding or am I missing something in installation? Any help to resolve this problem is appreciated
See ros-infrastructure/roswiki#140. Have you tried again after waiting a bit?
Note that these servers are managed by 3rd parties, so we can't really control them.
I tried multiple times after waiting. So basically I need to wait till the server respond to move ahead am I right? Or is there any way around?
What is the output of
ping ha.pool.sks-keyservers.net
? Please make sure you havenc
orncat
and see whethernc ha.pool.sks-keyservers.net 80
succeeds. I can reach the server(s) from my own machine, so it would seem they are up.Thanks. I think adding "nc" did the trick. I was able to ping but was not able to go ahead with "hkp:" then I changed to nc problems seed to go away. thank again.
We probably need to update this trouble shoot on ros installation page dont we?
I suggested to see whether
nc
could connect to see whether you could reachha.pool.sks-keyservers.net:80
at all.nc
doesn't do anything with keys. What did you do exactly?I am able to get ping using "nc" but could not get key access using "hkp".
so Instead of " sudo apt-key adv --keyserver hkp://ha.pool.sks-keyservers.net:80 --recv-key 0xB01FA116" I changed to "sudo apt-key adv --keyserver nc ha.pool.sks-keyservers.net:80 --recv-key 0xB01FA116" it worked!.
I don't think inserting
nc
here actually changed anything, and that "it worked" was merely a coincidence.nc
is a stand-alone tool that allows to connect file descriptors to network sockets and use them asstdout
&stdin
on the cmd line.Can you try the normal cmd, just to see if it works?