Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gpg: keyserver receive failed: No route to host #18

Closed
jachinte opened this issue Oct 6, 2017 · 9 comments
Closed

gpg: keyserver receive failed: No route to host #18

jachinte opened this issue Oct 6, 2017 · 9 comments

Comments

@jachinte
Copy link

jachinte commented Oct 6, 2017

Hi,
I'm trying to encrypt a file but the rultor CLI fails. It seems like rultor is trying to execute gpg --keyserver hkp://pool.sks-keyservers.net --verbose --recv-keys 9AF0FA4C, but it fails with the error message gpg: keyserver receive failed: No route to host. I did a quick search; the error goes away when you add ipv4: gpg --keyserver hkp://ipv4.pool.sks-keyservers.net --verbose --recv-keys 9AF0FA4C, which produces:

gpg: data source: http://45.33.82.183:11371
gpg: armor header: Version: SKS 1.1.6
gpg: armor header: Comment: Hostname: keys.fspproductions.biz
gpg: pub  rsa2048/3FD3FA7E9AF0FA4C 2014-08-17  Rultor.com <gpg@rultor.com>
gpg: key 3FD3FA7E9AF0FA4C: "Rultor.com <gpg@rultor.com>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1

Here is the complete output:

rultor encrypt -p unicesi/amelia ~/.m2/settings.backup.xml + set -e + file=/Users/--/.m2/settings.backup.xml + asc=/Users/--/.m2/settings.backup.xml.asc + '[' -e /Users/--/.m2/settings.backup.xml.asc ']' ++ mktemp -t rultor-XXXX + tmp=/var/folders/k0/7f_5tyms21b_1gcx01wfrp2h0000gn/T/rultor-XXXX.H7GRKDt2 + rm -f /var/folders/k0/7f_5tyms21b_1gcx01wfrp2h0000gn/T/rultor-XXXX.H7GRKDt2 + gpg --version gpg (GnuPG) 2.1.21 libgcrypt 1.7.7 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.

Home: /Users/--/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

  • gpg --symmetric --armor --verbose --batch --no-tty --passphrase rultor-key:unicesi/amelia -o /var/folders/k0/7f_5tyms21b_1gcx01wfrp2h0000gn/T/rultor-XXXX.H7GRKDt2 /Users/--/.m2/settings.backup.xml
    gpg: using cipher AES
    gpg: writing to '/var/folders/k0/7f_5tyms21b_1gcx01wfrp2h0000gn/T/rultor-XXXX.H7GRKDt2'
  • gpg --keyserver hkp://pool.sks-keyservers.net --verbose --recv-keys 9AF0FA4C
    gpg: keyserver receive failed: No route to host
    /usr/local/lib/ruby/gems/2.4.0/gems/rultor-0.4.3/lib/rultor/encrypt.rb:55:in run': PGP encryption failed (RuntimeError) from /usr/local/lib/ruby/gems/2.4.0/gems/rultor-0.4.3/bin/rultor:48:in block (3 levels) in <top (required)>'
    from /usr/local/lib/ruby/gems/2.4.0/gems/slop-3.6.0/lib/slop.rb:260:in parse!' from /usr/local/lib/ruby/gems/2.4.0/gems/slop-3.6.0/lib/slop.rb:235:in parse!'
    from /usr/local/lib/ruby/gems/2.4.0/gems/slop-3.6.0/lib/slop.rb:65:in parse!' from /usr/local/lib/ruby/gems/2.4.0/gems/slop-3.6.0/lib/slop.rb:54:in parse'
    from /usr/local/lib/ruby/gems/2.4.0/gems/rultor-0.4.3/bin/rultor:39:in <top (required)>' from /usr/local/bin/rultor:22:in load'
    from /usr/local/bin/rultor:22:in `'

I'm running rultor 0.4.3, gpg 2.1.21, mac 10.12.6

@0crat
Copy link

0crat commented Oct 6, 2017

@yegor256 please, pay attention to this issue

@jachinte
Copy link
Author

jachinte commented Oct 6, 2017

I tested it locally and checked that the solution works. I'd create a pull request but I had an issue running rake:

rake --trace
/Users/--/Development/repositories/rultor-remote/Rakefile:36: warning: already initialized constant CLEAN
/usr/local/lib/ruby/gems/2.4.0/gems/rake-12.0.0/lib/rake/clean.rb:62: warning: previous definition of CLEAN was here
rake aborted!
NoMethodError: undefined method `last_comment' for #<Rake::Application:0x007fc477883518>
/usr/local/lib/ruby/gems/2.4.0/gems/rubocop-0.35.1/lib/rubocop/rake_task.rb:23:in `initialize'
/Users/--/Development/repositories/rultor-remote/Rakefile:67:in `new'
/Users/--/Development/repositories/rultor-remote/Rakefile:67:in `<top (required)>'
/usr/local/lib/ruby/gems/2.4.0/gems/rake-12.0.0/lib/rake/rake_module.rb:28:in `load'
/usr/local/lib/ruby/gems/2.4.0/gems/rake-12.0.0/lib/rake/rake_module.rb:28:in `load_rakefile'
/usr/local/lib/ruby/gems/2.4.0/gems/rake-12.0.0/lib/rake/application.rb:687:in `raw_load_rakefile'
/usr/local/lib/ruby/gems/2.4.0/gems/rake-12.0.0/lib/rake/application.rb:96:in `block in load_rakefile'
/usr/local/lib/ruby/gems/2.4.0/gems/rake-12.0.0/lib/rake/application.rb:178:in `standard_exception_handling'
/usr/local/lib/ruby/gems/2.4.0/gems/rake-12.0.0/lib/rake/application.rb:95:in `load_rakefile'
/usr/local/lib/ruby/gems/2.4.0/gems/rake-12.0.0/lib/rake/application.rb:79:in `block in run'
/usr/local/lib/ruby/gems/2.4.0/gems/rake-12.0.0/lib/rake/application.rb:178:in `standard_exception_handling'
/usr/local/lib/ruby/gems/2.4.0/gems/rake-12.0.0/lib/rake/application.rb:77:in `run'
/usr/local/lib/ruby/gems/2.4.0/gems/rake-12.0.0/exe/rake:27:in `<top (required)>'
/usr/local/bin/rake:22:in `load'
/usr/local/bin/rake:22:in `<main>'

I'm not a ruby developer so it would take too much time to find out what's happenning.

yegor256 added a commit that referenced this issue Oct 7, 2017
@yegor256
Copy link
Owner

yegor256 commented Oct 7, 2017

@rultor release, tag is 0.4.4

@rultor
Copy link
Collaborator

rultor commented Oct 7, 2017

@rultor release, tag is 0.4.4

@yegor256 OK, I will release it now. Please check the progress here

@rultor
Copy link
Collaborator

rultor commented Oct 7, 2017

@rultor release, tag is 0.4.4

@jachinte @yegor256 Oops, I failed. You can see the full log here (spent 2min)

+ '[' -n '' ']'
+ use_image=yegor256/rultor
+ docker pull yegor256/rultor
Using default tag: latest
latest: Pulling from yegor256/rultor
Digest: sha256:89e627505b97fa07d92673b7cc403d6a2bf8a16fe027ddaecbfbc8f9bcc249ee
Status: Image is up to date for yegor256/rultor:latest
+ docker ps --filter=status=exited
+ grep --quiet '\syegor256_rultor-remote_18\s*$'
+ ls -al .
total 52
drwx--x--x  3 rultor rultor 4096 Oct  7 08:21 .
drwxrwxrwt 21 root   root   4096 Oct  7 08:21 ..
-rw-rw-r--  1 rultor rultor  444 Oct  7 08:21 end.sh
-rwxrwxr-x  1 rultor rultor  338 Oct  7 08:21 entry.sh
-rw-rw-r--  1 rultor rultor    5 Oct  7 08:21 pid
drwxrwxr-x  7 rultor rultor 4096 Oct  7 08:21 repo
-rw-rw-r--  1 rultor rultor   56 Oct  7 08:21 rubygems.yml
-rwxrwxr-x  1 rultor rultor 6117 Oct  7 08:21 run.sh
-rw-rw-r--  1 rultor rultor   98 Oct  7 08:20 s3cfg
-rw-rw-r--  1 rultor rultor  674 Oct  7 08:21 script.sh
-rw-rw-r--  1 rultor rultor 6134 Oct  7 08:21 stdout
++ pwd
++ pwd
+ docker run -t --rm -v /tmp/rultor-3EiR:/main --env=head=git@github.com:yegor256/rultor-remote.git --env=head_branch=master --env=tag=0.4.4 --env=author=yegor256 '--env=scripts=( '\''export '\''\'\'''\''head=git@github.com:yegor256/rultor-remote.git'\''\'\'''\'''\'' '\'';'\'' '\''export '\''\'\'''\''head_branch=master'\''\'\'''\'''\'' '\'';'\'' '\''export '\''\'\'''\''tag=0.4.4'\''\'\'''\'''\'' '\'';'\'' '\''export '\''\'\'''\''author=yegor256'\''\'\'''\'''\'' '\'';'\'' '\''sudo bundle install'\'' '\'';'\'' '\''sudo apt-get install -y bcrypt'\'' '\'';'\'' '\''rake'\'' '\'';'\'' '\''rm -rf *.gem'\'' '\'';'\'' '\''sed -i "s/1\.0\.snapshot/${tag}/g" lib/rultor/version.rb'\'' '\'';'\'' '\''gem build rultor.gemspec'\'' '\'';'\'' '\''chmod 0600 ../rubygems.yml'\'' '\'';'\'' '\''gem push *.gem --config-file ../rubygems.yml'\'' '\'';'\'' '\''sudo gem install pdd'\'' '\'';'\'' '\''pdd --source=$(pwd) --verbose --file=rultor-remote.xml'\'' '\'';'\'' '\''s3cmd --no-progress put rultor-remote.xml --config=../s3cfg s3://pdd.teamed.io/rltor-remote.xml'\'' '\'';'\'' )' --hostname=docker --privileged --memory=6g --memory-swap=16g --oom-kill-disable --cidfile=/tmp/rultor-3EiR/cid -w=/main --name=yegor256_rultor-remote_18 yegor256/rultor /main/entry.sh
WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
+ set -e
+ set -o pipefail
+ shopt -s dotglob
+ useradd -m -G sudo r
+ echo '%sudo ALL=(ALL) NOPASSWD:ALL'
+ cp -R /root/.bashrc /root/.composer /root/.gem /root/.gnupg /root/.m2 /root/.profile /root/texmf /home/r
+ cp -R ./cid ./end.sh ./entry.sh ./pid ./repo ./rubygems.yml ./run.sh ./s3cfg ./script.sh ./stdout /home/r
+ rm -rf repo
+ chown -R r:r /home/r
+ chmod a+x /home/r/script.sh
+ su --login r --command /home/r/script.sh
+ set -e
+ set -o pipefail
+ shopt -s expand_aliases
+ alias 'sudo=sudo -i'
+ export HOME=/home/r
+ HOME=/home/r
+ cd /home/r/repo
+ export head=git@github.com:yegor256/rultor-remote.git
+ head=git@github.com:yegor256/rultor-remote.git
+ export head_branch=master
+ head_branch=master
+ export tag=0.4.4
+ tag=0.4.4
+ export author=yegor256
+ author=yegor256
+ sudo -i bundle install
\u001b[33mDon't run Bundler as root. Bundler can ask for sudo if it is needed, and
installing your bundle as root will break this application for all non-root
users on this machine.\u001b[0m
\u001b[31mCould not locate Gemfile or .bundle/ directory\u001b[0m
container fa94ef31a65258208c940413066e7558638d0a5698f57dfbdd5ede0846a3d9ef is dead
Sat Oct  7 08:22:26 CEST 2017

yegor256 added a commit that referenced this issue Oct 7, 2017
@yegor256
Copy link
Owner

yegor256 commented Oct 7, 2017

@rultor release, tag is 0.4.4

@rultor
Copy link
Collaborator

rultor commented Oct 7, 2017

@rultor release, tag is 0.4.4

@yegor256 OK, I will release it now. Please check the progress here

@rultor
Copy link
Collaborator

rultor commented Oct 7, 2017

@rultor release, tag is 0.4.4

@yegor256 Done! FYI, the full log is here (took me 3min)

@jachinte jachinte closed this as completed Oct 7, 2017
@0crat
Copy link

0crat commented Oct 7, 2017

Oops! Job gh:yegor256/rultor-remote#18 was not in scope

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants