Related

Tool DOCTL: DigitalOcean CLI Tool
Duplicate Website Question Question
Why are snapshots so slow Question Question

Question

Freebsd 10.2 update no mirrors found / invalid signature

Posted November 27, 2015 9.3k views
DigitalOceanSystem ToolsFreeBSD

I’ve found a number of posts online about this, but the answers are a bit above my skill level. Surely somebody running FreeBSD on Digital Ocean has/had the same problem.

#  sudo freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 5 mirrors found.
Fetching metadata signature for 10.2-RELEASE from update6.freebsd.org... invalid signature.
Fetching metadata signature for 10.2-RELEASE from update5.freebsd.org... invalid signature.
Fetching metadata signature for 10.2-RELEASE from update4.freebsd.org... invalid signature.
Fetching metadata signature for 10.2-RELEASE from update2.freebsd.org... invalid signature.
Fetching metadata signature for 10.2-RELEASE from update3.freebsd.org... invalid signature.
No mirrors remaining, giving up.

Regarding this solution:

Edit /etc/freebsd-update.conf and check the line:
Components src world kernel

and change it to:
Components world kernel

My freebsd-update.conf was already set up like that.

Add a comment
gc948486cbc56b8
By:
gc948486cbc56b8

Related

Tool DOCTL: DigitalOcean CLI Tool
Duplicate Website Question Question
Why are snapshots so slow Question Question
Add a comment
1 comment
  • lordgordon November 27, 2015
    Reply Report

    Hi, never had this problem on FreeBSD. Looking on the official FreeBSD forum it looks like a DNS problem. Can you check the settings of your DNS (/etc/resolv.conf)?

    My /etc/resolv.conf is:

    # Generated by resolvconf
nameserver 8.8.8.8
nameserver 8.8.4.4

    Those are the Google DNS. They work very well.

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
3 answers
gc948486cbc56b8 November 28, 2015

Well that is the default. I am already using those addresses.

Reply Report
gc948486cbc56b8 December 4, 2015

The solution is related to how the openssl file was altered during the upgrade. Link goes to the solution in the freebsd forum.

[https://forums.freebsd.org/threads/invalid-signature-using-freebsd-update.54234/](http://)

I’m not sure the link is showing up. The solution was to comment out these lines in the openssl.conf file

<<<<<<< current version
=======
# $FreeBSD: releng/10.2/crypto/openssl/apps/openssl.cnf 238405 2012-07-12 19:30:53Z jkim $
>>>>>>> 10.2-RELEASE
Reply Report
rootbvn December 7, 2019

if you have for example 10.3-STABLE and have error
after
freebsd-update upgrade -r 11.3-RELEASE

src component not installed, skipped
Looking up update.FreeBSD.org mirrors… 3 mirrors found.
Fetching metadata signature for 10.3-STABLE from update1.freebsd.org… failed.
Fetching metadata signature for 10.3-STABLE from update2.freebsd.org… failed.
Fetching metadata signature for 10.3-STABLE from update4.freebsd.org… failed.

need
setenv UNAME_r “10.3-RELEASE”
then
freebsd-update upgrade -r 11.3-RELEASE

Reply Report

Related

Looking for something else?

Ask a new question Search for more help