Date: Wed, 3 Dec 2025 13:57:23 +0300 From: Odhiambo Washington <odhiambo@gmail.com> To: =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= <des@freebsd.org> Cc: The Doctor <doctor@doctor.nl2k.ab.ca>, questions <questions@freebsd.org> Subject: Re: FreeBSD 15.0-RELEASE: Trouble after upgrade Message-ID: <CAAdA2WPqOuE8RPFyFHvM3S6L=hp8qdR=_jP8OJAnnRoY5Js-hA@mail.gmail.com> In-Reply-To: <865xaohcl6.fsf@ltc.des.dev> References: <CAAdA2WMtqWL-KPW8smzVqQu5OgCUAHZ2wU5gmFOPpHAtq9jZOQ@mail.gmail.com> <aS8EyaCu_ooAAww_@doctor.nl2k.ab.ca> <86ikeohnn1.fsf@ltc.des.dev> <CAAdA2WMM4kuHRYFJxAZfme4GEiG_UM6tNS7jegFbu9Xb%2BRiJgA@mail.gmail.com> <865xaohcl6.fsf@ltc.des.dev>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Tue, Dec 2, 2025 at 11:07 PM Dag-Erling Smørgrav <des@freebsd.org> wrote: > Odhiambo Washington <odhiambo@gmail.com> writes: > > On Nov 26, there was an advisory ' FreeBSD Security Advisory > > FreeBSD-SA-25:10.unbound'. On that date I did the freebsd-update > > fetch && freebsd-update install thing. Today, I assumed that I was > > still updated. So it's obviously my mistake that I did not repeat the > > same thing today before upgrading to 15.0-REL. > > No, if you updated on Nov 26 then you should have been fine, so > something else went wrong. I will try to see if I can reproduce it. > So, I hosed my upgraded server and restored the VM from the backup I made before upgrade. This is what I had: root@gw:/home/wash # freebsd-version -kru 14.3-RELEASE-p5 14.3-RELEASE-p5 14.3-RELEASE-p6 root@gw:/home/wash # uname -a FreeBSD gw.wash.lan 14.3-RELEASE-p5 FreeBSD 14.3-RELEASE-p5 GENERIC amd64 root@gw:/home/wash # freebsd-update fetch Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching metadata signature for 14.3-RELEASE from update1.freebsd.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. No updates needed to update system to 14.3-RELEASE-p6. root@gw:/home/wash # So I suppose I was safe to upgrade, since I had also done a `portupgrade -a`. I am now embarking on the upgrade to 15.0-RELEASE once again. > > Also ran the command, but I don't understand the meaning of the > > output: > > None of these are particularly concerning. They are telling you that > you have modified configuration files (which is normal) and that some > files and directories have incorrect permissions (which is something > that sometimes happens with freebsd-update and isn't a big deal). There > are discrepancies in /usr/src but that's easily fixed by replacing the > entire source tree (rm -rf /usr/src then download and extract src.txz). > > You can fix at least some of these issues by running the following > commands as root: > > mtree -deU -p / -f /etc/mtree/BSD.root.dist > mtree -deU -p /var -f /etc/mtree/BSD.var.dist > mtree -deU -p /usr -f /etc/mtree/BSD.usr.dist > I will do this after this upgrade. The only lines that surprise me are these: > > /usr/lib/debug/usr/lib/libdevinfo.so.7.debug has SHA256 hash > d06d59e4913a6103771409c598945e81dbaac857ea11271e2c03c92cd581aeef, but > should have SHA256 hash > 7653ff2946527fbb764e1932d767e4787fe8814c645f8c2d2359b43d0884f289. > /usr/lib/libdevinfo.a has SHA256 hash > 378b792d00971a8d5ffc45ad7882d08190a244b97de5514f5b2eb75ea0f6db47, but > should have SHA256 hash > 3d412bd84e6a1a9914610c8e838e4c4afe3b131789d5e36e9371bd5de03e0d68. > /usr/lib/libdevinfo.so.7 has SHA256 hash > 667f9592ed95a538077f3fc22461ed3d6ece3deae27b66ec1e6a271807f25110, but > should have SHA256 hash > 0f1f789aa07dbfdc1df637be1d31f41616ec74188c683d9f706bae0ceb61d904. > > which is not critical and can be fixed by extracting those files > from base.txz as explained in my previous email. > This libdevinfo.so thing must have been created by me when I was struggling with installing qemu-guest-agent after the upgrade to 15.0. Starting with complaints about 'ld-elf.so.1: Shared object "libutil.so.9" not found, required by "pkg"; at some point, I went into a wild goose chase trying to fix things against the counsel of my 6th sense. It's good I have a full backup of this VM so I can blow it away and restore and try the upgrade again until I get it right - or wait a little longer for others to be bitten and a solution found :-) > I assume you will be switching to pkgbase at some point, which will > make correcting this kind of issue much easier. > I have been following the discussions about pkgbase and I am sure to switch to it after I successfully upgrade to 15.0-RELEASE. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html] [-- Attachment #2 --] <div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Dec 2, 2025 at 11:07 PM Dag-Erling Smørgrav <<a href="mailto:des@freebsd.org" target="_blank">des@freebsd.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Odhiambo Washington <<a href="mailto:odhiambo@gmail.com" target="_blank">odhiambo@gmail.com</a>> writes:<br> > On Nov 26, there was an advisory ' FreeBSD Security Advisory<br> > FreeBSD-SA-25:10.unbound'. On that date I did the freebsd-update<br> > fetch && freebsd-update install thing. Today, I assumed that I was<br> > still updated. So it's obviously my mistake that I did not repeat the<br> > same thing today before upgrading to 15.0-REL.<br> <br> No, if you updated on Nov 26 then you should have been fine, so<br> something else went wrong. I will try to see if I can reproduce it.<br></blockquote><div><br></div><div>So, I hosed my upgraded server and restored the VM from the backup I made before upgrade.</div><div>This is what I had:</div><div>root@gw:/home/wash # freebsd-version -kru<br>14.3-RELEASE-p5<br>14.3-RELEASE-p5<br>14.3-RELEASE-p6<br>root@gw:/home/wash # uname -a<br>FreeBSD gw.wash.lan 14.3-RELEASE-p5 FreeBSD 14.3-RELEASE-p5 GENERIC amd64</div><div>root@gw:/home/wash # freebsd-update fetch<br>Looking up <a href="http://update.FreeBSD.org" target="_blank">update.FreeBSD.org</a> mirrors... 3 mirrors found.<br>Fetching metadata signature for 14.3-RELEASE from update1.freebsd.org... done.<br>Fetching metadata index... done.<br>Inspecting system... done.<br>Preparing to download files... done.<br><br>No updates needed to update system to 14.3-RELEASE-p6.<br>root@gw:/home/wash #</div><div><br></div><div>So I suppose I was safe to upgrade, since I had also done a `portupgrade -a`.</div><div><br></div><div>I am now embarking on the upgrade to 15.0-RELEASE once again.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> > Also ran the command, but I don't understand the meaning of the<br> > output:<br> <br> None of these are particularly concerning. They are telling you that<br> you have modified configuration files (which is normal) and that some<br> files and directories have incorrect permissions (which is something<br> that sometimes happens with freebsd-update and isn't a big deal). There<br> are discrepancies in /usr/src but that's easily fixed by replacing the<br> entire source tree (rm -rf /usr/src then download and extract src.txz).<br> <br> You can fix at least some of these issues by running the following<br> commands as root:<br> <br> mtree -deU -p / -f /etc/mtree/BSD.root.dist<br> mtree -deU -p /var -f /etc/mtree/BSD.var.dist<br> mtree -deU -p /usr -f /etc/mtree/BSD.usr.dist<br></blockquote><div><br></div><div>I will do this after this upgrade.</div><div> </div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> The only lines that surprise me are these:<br> <br> /usr/lib/debug/usr/lib/libdevinfo.so.7.debug has SHA256 hash d06d59e4913a6103771409c598945e81dbaac857ea11271e2c03c92cd581aeef, but should have SHA256 hash 7653ff2946527fbb764e1932d767e4787fe8814c645f8c2d2359b43d0884f289.<br> /usr/lib/libdevinfo.a has SHA256 hash 378b792d00971a8d5ffc45ad7882d08190a244b97de5514f5b2eb75ea0f6db47, but should have SHA256 hash 3d412bd84e6a1a9914610c8e838e4c4afe3b131789d5e36e9371bd5de03e0d68.<br> /usr/lib/libdevinfo.so.7 has SHA256 hash 667f9592ed95a538077f3fc22461ed3d6ece3deae27b66ec1e6a271807f25110, but should have SHA256 hash 0f1f789aa07dbfdc1df637be1d31f41616ec74188c683d9f706bae0ceb61d904.<br> <br> which is not critical and can be fixed by extracting those files from base.txz as explained in my previous email.<br></blockquote><div><br></div><div>This libdevinfo.so thing must have been created by me when I was struggling with installing qemu-guest-agent after the upgrade to 15.0. </div><div>Starting with complaints about 'ld-elf.so.1: Shared object "libutil.so.9" not found, required by "pkg"; at some point, I went into a wild goose chase trying to fix things against the counsel of my 6th sense.</div><div>It's good I have a full backup of this VM so I can blow it away and restore and try the upgrade again until I get it right - or wait a little longer for others to be bitten and a solution found :-)</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <br> I assume you will be switching to pkgbase at some point, which will make correcting this kind of issue much easier.<br></blockquote><div><br></div><div>I have been following the discussions about pkgbase and I am sure to switch to it after I successfully upgrade to 15.0-RELEASE.</div></div><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div dir="ltr"><div>Best regards,<br>Odhiambo WASHINGTON,<br>Nairobi,KE<br>+254 7 3200 0004/+254 7 2274 3223</div><div><span style="color:rgb(34,34,34)"> In </span><span style="color:rgb(34,34,34)">an Internet failure case, the #1 suspect is a constant: DNS.</span><br>"<span style="font-size:12.8px">Oh, the cruft.</span><span style="font-size:12.8px">", </span><span style="font-size:12.8px">egrep -v '^$|^.*#' </span><span style="background-color:rgb(34,34,34);color:rgb(238,238,238);font-family:"Lucida Console",Consolas,"Courier New",monospace;font-size:13.6px">¯\_(ツ)_/¯</span><span style="font-size:12.8px"> :-)</span></div><div><span style="font-size:12.8px">[How to ask smart questions: </span><span style="font-size:12.8px"><a href="http://www.catb.org/~esr/faqs/smart-questions.html" target="_blank">http://www.catb.org/~esr/faqs/smart-questions.html</a>]</span></div></div></div></div></div>; </div> </div>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAAdA2WPqOuE8RPFyFHvM3S6L=hp8qdR=_jP8OJAnnRoY5Js-hA>