[DOCS-6090] W: GPG error: http://repo.mongodb.org wheezy/mongodb-org/3.1 Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 614D985504A2163B Created: 25/Aug/15  Updated: 08/Jun/20  Resolved: 14/Oct/15

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Bug Priority: Major - P3
Reporter: Tianon Gravi Assignee: Andrew Aldridge
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Debian Wheezy


Issue Links:
Backports
backports DOCS-13026 The repository 'http://repo.mongodb.o... Closed
Participants:
Days since reply: 3 years, 35 weeks, 2 days ago

 Description   

When trying to install the latest update to the 3.1 series, we've discovered that it's signed by a new key which is not publicized (or even available) anywhere we can find:

W: GPG error: http://repo.mongodb.org wheezy/mongodb-org/3.1 Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 614D985504A2163B

We tried pulling the key from one of the known keyservers and it's not pushed up there, and we can't find any reference of it anywhere else either to download the public key material from.

This appears to be related to SERVER-19032.



 Comments   
Comment by Leonardo Romero [ 08/Jun/20 ]

I'm also trying to install  mongo  in a AWS instance and received the following  message:  

W: GPG error: http://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/4.2 Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 656408E390CFB1F5

I tried all the comment solutions  previously listed but still not working 

Comment by Andrew Aldridge [ 08/Jul/16 ]

Glad to help!

Comment by Jinosh Philip [X] [ 08/Jul/16 ]

Thank you Andrew!
It worked like a charm. I am not sure why it did not install the key automatically.

Comment by Andrew Aldridge [ 08/Jul/16 ]

Hello Jinosh,

Yum should have automatically installed the key. You can try manually installing it with the following:

sudo rpm --import https://www.mongodb.org/static/pgp/server-3.2.asc

Comment by Jinosh Philip [X] [ 08/Jul/16 ]

Hi,
I am trying to install mongodb-org-3.2.7 on an Amazon AWS and I am getting the same error:
---------------------------------------------------------------------------------------------
Downloading packages:
warning: /var/cache/yum/x86_64/latest/mongo-db-org-3.2/packages/mongodb-org-3.2.7-1.amzn1.x86_64.rpm: Header V3 RSA/SHA1 Signature, key ID ea312927: NOKEY
Public key for mongodb-org-3.2.7-1.amzn1.x86_64.rpm is not installed

---------------------------------------------------------------------------------------------
Where do I get the key and how do I install it ?

Thanks.

Comment by Ernie Hershey [ 23/Oct/15 ]

No problem! I'm always happy to help.

Comment by Andrew Aldridge [ 23/Oct/15 ]

Dunno how that extra ``1`` got into my comment; the upcoming documentation was correct.

Thanks for taking care of this ernie.hershey!

Comment by Jonathan Abrahams [ 23/Oct/15 ]

Yes - that worked!

Comment by Kay Kim (Inactive) [ 22/Oct/15 ]

Ah – thank you!

Comment by Ernie Hershey [ 22/Oct/15 ]

I think there's an extra 1 in that command. This just worked for me -

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv EA312927

I didn't realize the key was already there and just re-submitted it though too. I'm not sure if that also made a difference.

Comment by Jonathan Abrahams [ 22/Oct/15 ]

Same problem here:

ubuntu@ip-10-10-38-84:~$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv EA3129271
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --homedir /tmp/tmp.cUrpSM0PLN --no-auto-check-trustdb --trust-model always --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyring /etc/apt/trusted.gpg.d/openjdk-r-ppa.gpg --keyserver keyserver.ubuntu.com --recv EA3129271
gpg: "EA3129271" not a key ID: skipping

Comment by Andrew Aldridge [ 16/Oct/15 ]

Hi Jwhite1802, could you please post the exact command that you're running, along with its exact output?

Comment by Joe White [X] [ 16/Oct/15 ]

Actually not the same error. Getting "not a key ID:skipping"

Comment by Joe White [X] [ 16/Oct/15 ]

I am getting the same error with the key uploaded 14 oct 2015. Any ideas?

Comment by Tianon Gravi [ 14/Oct/15 ]

Awesome, you're very welcome! Thanks for the quick turnaround.

Comment by Andrew Aldridge [ 14/Oct/15 ]

Drat it all. Thanks for letting me know again, tianon!

I've uploaded the new key:

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv EA312927

Comment by Tianon Gravi [ 14/Oct/15 ]

It looks like this might have changed again:

W: GPG error: http://repo.mongodb.org wheezy/mongodb-org/3.1 Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D68FA50FEA312927

$ gpg --keyserver pgp.mit.edu --recv-keys D68FA50FEA312927
gpg: requesting key EA312927 from hkp server pgp.mit.edu
gpgkeys: key D68FA50FEA312927 not found on keyserver
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
gpg: keyserver communications error: key not found
gpg: keyserver communications error: bad public key
gpg: keyserver receive failed: bad public key

Comment by Tianon Gravi [ 26/Aug/15 ]

Awesome, that works! Thanks!

Comment by Andrew Aldridge [ 26/Aug/15 ]

Thanks for the report!

I just submitted the signing key to the Ubuntu keyserver. I'll look into updating our docs, but for now you can run the following to import the required key:

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv 04A2163B

Generated at Thu Feb 08 07:51:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.