Hi! Down is the output of update procedure on my FreeBSD 10.1-RELEASE droplet. Is this inconsistency between uname and fb-ver commands. One saying it is 10.1-RELEASE-p6 and freebsd-version 10.1-RELEASE-p8
root@beasty:/usr/home/freebsd # freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 5 mirrors found.
Fetching metadata signature for 10.1-RELEASE from update5.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.
The following files will be added as part of updating to 10.1-RELEASE-p8:
/usr/src/crypto/openssl/util/mkbuildinf.pl
root@beasty:/usr/home/freebsd # freebsd-update install
Installing updates...install: ///usr/src/crypto/openssl/util/mkbuildinf.pl: No such file or directory
done.
root@beasty:/usr/home/freebsd # uname -a
FreeBSD beasty 10.1-RELEASE-p6 FreeBSD 10.1-RELEASE-p6 #0: Tue Feb 24 19:00:21 UTC 2015 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
root@beasty:/usr/home/freebsd # freebsd-version
10.1-RELEASE-p8
root@beasty:/usr/home/freebsd # freebsd-update install
No updates are available to install.
Run '/usr/sbin/freebsd-update fetch' first.
root@beasty:/usr/home/freebsd # freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 5 mirrors found.
Fetching metadata signature for 10.1-RELEASE from update2.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.
The following files will be added as part of updating to 10.1-RELEASE-p8:
/usr/src/crypto/openssl/util/mkbuildinf.pl
root@beasty:/usr/home/freebsd # freebsd-update install
Installing updates...install: ///usr/src/crypto/openssl/util/mkbuildinf.pl: No such file or directory
done.
root@beasty:/usr/home/freebsd # uname -a
FreeBSD beasty 10.1-RELEASE-p6 FreeBSD 10.1-RELEASE-p6 #0: Tue Feb 24 19:00:21 UTC 2015 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
root@beasty:/usr/home/freebsd # freebsd-version
10.1-RELEASE-p8
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.
Found this bug entry https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198030. And give a solution.
Edit /etc/freebsd-update.conf and check the line: Components src world kernel
and change it to: Components world kernel
Found this bug entry https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198030. And give a solution.
Edit /etc/freebsd-update.conf and check the line: Components src world kernel
and change it to: Components world kernel
Thanks for this! Small hacks like this can make big difference. All works ok now
I’m actually having the same issue on a VMWare install, and that bug is not (for the parts I read) associated to it.
I performed a clean install of FreeBSD 10.1, then performed 2 updates at different dates. One bring it up to P3 or P4 (cannot recall exactly). The next one got me to P6, while still saying there is a P8 upgrade, but unable to perform it.
For what I can understand of the path that mkbuildinf.pl file goes, is that is stored in a subfolder where you download the FreeBSD sources. But if you lack them as I do, there is no crypto folder in src, because src is empty.
So I guess it was an oops from the FreeBSD developers, since src is only for people who customize and build the OS from sources, and for a while that has not been needed, except for certain corner cases.
I did not experience any hang-out situation. I can reboot normally after update fails. It is with: “# freebsd-update install” that produces: “usr/src/crypto/openssl/util/mkbuildinf.pl: No such file or directory” that I’m worried about.
it’s a known bug…
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195458
i assume you had to power cycle (hard reset) your droplet at one point after doing the update?