Operational Defect Database

BugZero found this defect 2631 days ago.

MongoDB | 338426

[SERVER-27398] packages cannot be authenticated

Last update date:


Affected products:

MongoDB Server

Affected releases:

No affected releases provided.

Fixed releases:

No fixed releases provided.



I can't install without forcing. I've followed the steps, added gpg key $ sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv 0C49F3730359A14518585931BC711F9BA15703C6 Executing: /tmp/tmp.nshnj4YO0S/gpg.1.sh --keyserver hkp://keyserver.ubuntu.com:80 --recv 0C49F3730359A14518585931BC711F9BA15703C6 gpg: key BC711F9BA15703C6: "MongoDB 3.4 Release Signing Key <packaging@mongodb.com>" not changed gpg: Total number processed: 1 gpg: unchanged: 1 but keep getting: $ sudo apt-get install mongodb-org Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: mongodb-org-mongos mongodb-org-server mongodb-org-shell mongodb-org-tools The following NEW packages will be installed: mongodb-org mongodb-org-mongos mongodb-org-server mongodb-org-shell mongodb-org-tools 0 upgraded, 5 newly installed, 0 to remove and 8 not upgraded. Need to get 66,6 MB of archives. After this operation, 269 MB of additional disk space will be used. Do you want to continue? [Y/n] Y WARNING: The following packages cannot be authenticated! mongodb-org-shell mongodb-org-server mongodb-org-mongos mongodb-org-tools mongodb-org Install these packages without verification? [y/N]

Top User Comments

brian.samek commented on Fri, 12 May 2017 15:31:30 +0000: I think these steps were correct: I tried deleting all mongo keys from apt, readded the key. I tried deleting all the mongo source lists and readded them. However, I think you have to wrap removing and re-adding the source lists with apt-get update, which is why it did not fix it the first time you tried this. I don't think adding "[ arch=amd64,arm64 ]" fixed it either. brendanball commented on Fri, 12 May 2017 14:52:36 +0000: so that seems to have fixed this server. The only difference that I can see is that I wasn't specifying [ arch=amd64,arm64 ] in the apt source but I can't see how that would've broken anything. Thanks anyway, I guess this is still not reproducible. If I uninstall mongo and add the apt source that it had previously it still works if I reinstall it again. brian.samek commented on Fri, 12 May 2017 14:24:36 +0000: Hi brendanball, Assuming you are running MongoDB 3.4, could you try running these steps, and paste their output? sudo rm /etc/apt/sources.list.d/mongodb-org-3.4.list sudo apt-get update echo "deb [ arch=amd64,arm64 ] http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.4 multiverse" | sudo tee /etc/apt/sources.list.d/mongodb-org-3.4.list sudo apt-get update sudo apt-get install -y mongodb-org brendanball commented on Wed, 10 May 2017 09:42:10 +0000: I have the same problem on one of my servers, also running ubuntu 16.04. I tried deleting all mongo keys from apt, readded the key. I tried deleting all the mongo source lists and readded them. I tried cleaning the apt cache with apt-get clean After all of this I still get the same error. I didn't experience this issue on an almost identical server which should have all of the same config. I don't want to force install so I don't know how else to fix this. Possibly we can reopen this issue? If there is any more info you can get from me to diagnose the issue let me know. brian.samek commented on Tue, 13 Dec 2016 19:39:18 +0000: I'm going to close as can't repro. If this reproduces or we learn more about the user's problem, we can debug further.

Additional Resources / Links


BugZero Risk Score

Coming soon



Have you been affected by this bug?


Do you know how much operational outages are costing you?

Understand the cost to your business and how BugZero can help you reduce those costs.


Login to read and write comments.

Have you ever...

had your data corrupted from a