We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
failed: [default] => {"cmd": "apt-key adv --keyserver hkp://pgp.mit.edu --recv 277E7787", "failed": true, "rc": 2} stderr: gpg: requesting key 277E7787 from hkp server pgp.mit.edu gpg: no valid OpenPGP data found. gpg: Total number processed: 0 stdout: Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /tmp/tmp.eOxPq6sMcM --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver hkp� ://pgp.mit.edu --recv 277E7787 gpgkeys: key 277E7787 not found on keyserver msg: gpg: requesting key 277E7787 from hkp server pgp.mit.edu gpg: no valid OpenPGP data found. gpg: Total number processed: 0 FATAL: all hosts have already failed -- aborting
I continue to see this error both on my local vagrant box and prod nodes occasionally.
The key is there, the mit keyserver occasionally refuses to return it.
The text was updated successfully, but these errors were encountered:
Ive encountered this bug before and it just ended up working.
I propose we change our key server from pgp.mit.edu to a pooled approach. We can use any of the key servers here: https://sks-keyservers.net/status/
On Friday, November 7, 2014, Marshall Jones notifications@github.com wrote:
failed: [default] => {"cmd": "apt-key adv --keyserver hkp://pgp.mit.edu --recv 277E7787", "failed": true, "rc": 2} stderr: gpg: requesting key 277E7787 from hkp server pgp.mit.edu gpg: no valid OpenPGP data found. gpg: Total number processed: 0 stdout: Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /tmp/tmp.eOxPq6sMcM --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver hkp ://pgp.mit.edu --recv 277E7787 gpgkeys: key 277E7787 not found on keyserver msg: gpg: requesting key 277E7787 from hkp server pgp.mit.edu gpg: no valid OpenPGP data found. gpg: Total number processed: 0 FATAL: all hosts have already failed -- aborting I continue to see this error both on my local vagrant box and prod nodes occasionally. The key is there, the mit keyserver occasionally refuses to return it. — Reply to this email directly or view it on GitHub #9.
failed: [default] => {"cmd": "apt-key adv --keyserver hkp://pgp.mit.edu --recv 277E7787", "failed": true, "rc": 2} stderr: gpg: requesting key 277E7787 from hkp server pgp.mit.edu gpg: no valid OpenPGP data found. gpg: Total number processed: 0
stdout: Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /tmp/tmp.eOxPq6sMcM --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver hkp ://pgp.mit.edu --recv 277E7787 gpgkeys: key 277E7787 not found on keyserver
msg: gpg: requesting key 277E7787 from hkp server pgp.mit.edu gpg: no valid OpenPGP data found. gpg: Total number processed: 0
FATAL: all hosts have already failed -- aborting
— Reply to this email directly or view it on GitHub #9.
Mahmoud Abdelkader Co-founder & CTO @ Balanced
Sorry, something went wrong.
No branches or pull requests
I continue to see this error both on my local vagrant box and prod nodes occasionally.
The key is there, the mit keyserver occasionally refuses to return it.
The text was updated successfully, but these errors were encountered: