Strange upgrade message

pos

pos

Anyone that knows why I get a warning of a version I do not have?
Code: 
19:39:16 phoenix:~ # freebsd-update fetch
src component not installed, skipped
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 14.1-RELEASE from update2.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.

No updates needed to update system to 14.1-RELEASE-p6.

WARNING: FreeBSD 14.1-RELEASE-p5 [/B]is approaching its End-of-Life date.
It is strongly recommended that you upgrade to a newer
release within the next 2 months.
19:40:11 phoenix:~ #





Tnx in advance
Peo
 
Well. It tells you that you are using an unsupported version. 14.1 is soon not supported. Time to upgrade to 14.2. The last warning is funny and a bug. It has apparently not been updated to say 14.1-RELEASE-p6 but instead saying FreeBSD 14.1-RELEASE-p5. That is misleading and might confuse some people :)
 
I have done som test on servers I have….

Now I have seen the same behavior on two internal servers that was not upgraded. I.e I upgraded them now. As stated, this is a minor upgrade from 14.1p5 to 14.1p6.

After freebsd-update fetch, freebsd-update install and the following reboot it looked like this….


freebsd-version
14.1-RELEASE-p6

freebsd-version -ku
14.1-RELEASE-p5
14.1-RELEASE-p6


freebsd-update fetch
src component not installed, skipped
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 14.1-RELEASE from update2.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.

No updates needed to update system to 14.1-RELEASE-p6.

WARNING: FreeBSD 14.1-RELEASE-p5 is approaching its End-of-Life date.
It is strongly recommended that you upgrade to a newer
release within the next 2 months.





Another extra reboot and it looks like this:

freebsd-version
14.1-RELEASE-p6

freebsd-version -ku
14.1-RELEASE-p5
14.1-RELEASE-p6

freebsd-update fetch
src component not installed, skipped
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 14.1-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.1-RELEASE-p6.


I.e all the same, but the post message about "WARNING: FreeBSD 14.1-RELEASE-p5 is approaching its End-of-Life date" was gone after the second reboot.

This was new to me that a second reboot could be needed for minor version upgrades. Or have I missed something important here?
 
pos said:
I.e all the same, but the post message about "WARNING: FreeBSD 14.1-RELEASE-p5 is approaching its End-of-Life date" was gone after the second reboot.
Click to expand...
The message isn't shown every time, because people got annoyed when it obsessively printed that message every time you ran freebsd-update(8). Has nothing to do with the reboot.
 
SirDice said:
The message isn't shown every time, because people got annoyed when it obsessively printed that message every time you ran freebsd-update(8). Has nothing to do with the reboot.
Click to expand...

Ok.... So this post message on "freebsd-update fetch" is shown randomly when it is one patch level of the kernel and antoher on userland? Is that correct, or did I come to the wrong conclusion? If it is correct, I for sure think it is better to always show it, and also a row of a diff in userland and kernel patch levels. If the message is only shown when there is a diff, I dont understand how people could be that annoyed so the FreeBSD teams change it to not show it in a consistent way.


My personal opinion is that it just lead to confusion if the messages are randomly shown (or whatever, but not every time).
 
pos said:
So this post message on "freebsd-update fetch" is shown randomly when it is one patch level of the kernel and antoher on userland? Is that correct, or did I come to the wrong conclusion?
Click to expand...
The message is shown because 14.1-RELEASE will be EoL at the end of March 2025 (in about 2 months; that's 3 months after the release of 14.2). Patch level has very little to do with it.
 
pos said:
My personal opinion is that it just lead to confusion if the messages are randomly shown (or whatever, but not every time).
Click to expand...
It does.

My #1 rule about FreeBSD is: 'Don't Panic!'
As long as you know (e.g. by doing freebsd-version -kru) you run a version that is not EOL, and doing updates regulary, there is nothing to worry about.
After all the message reminds one it will be EOL, but yet it's not.

Other message is you're running a version that is beyond EOL - seen this one by myself a couple of times (I'm not that kind who checks every two hours for every single package if there is 0.0.0.1.0.3a available instead of 0.0.0.1.0.3), and yet none of my machines catched fire, fell suddenly apart, were being hacked,.... :cool:

In my almost 40y of computering problems about something wasn't working as it's used to, or stopped completely working at all was caused in ~99% because of I made an update. While this statement ain't not fair, 'cause it includes all my experience of MS Windows (95 to 7), and all the Linux I ran - latter was the total upgrade hell; it was pure coincidence to have a machine for a couple of days with everything working flawless perfectly. (There comes my prejudice of 'the common Linux nerd': 'finally, an update. finally something breaks again, and there again is something to do with the machine.' While I'm happy if everything works without I need to fix it.)

When an update occurs, particulary a new version upgrade I always wait a couple of weeks until I update.
I don't want to stress the servers for all those who believe their machine will die a horrific death immedately if they postpone an update for longer than ten minutes.
And second I want to give the guys a chance to correct all flaws still within by publishing time. I did real world projects myself. So I know it's not exemplary but absolutely common to still have known bugs at release, solution being postponed to after release.
And since a -p2 comes shortly many times makes me feel I'm right.
 
SirDice said:
The message is shown because 14.1-RELEASE will be EoL at the end of March 2025 (in about 2 months; that's 3 months after the release of 14.2). Patch level has very little to do with it.
Click to expand...

Yes I checked the "fetch_warn_eol" function.... It seems the warning message print the kernel patch level but the freebsd-update in the first output print the userland patch level which in this case is a diff. If the warning message would strip of the "-p?" and be shown at every freebsd-update fetch, then it would be much clearer.

When the script says my 14.1-RELEASE-p6 is up to date and the next section says 14.1-RELEASE-p5 is soon EOL and you say patch releases has very little to do with it, you can maybe understand it can create confusion.

The message is (my personal opinion) not that clear as the warning refer to a particular patch release (14.1p5) that is not even the latest will be EOL. As it isn't even shown every time (random or not random) you do a freebsd-update fetch it will create even mot confusion.

If you run 14.1-RELEASE with any patchlevel on it AND it will be EOL soon AND you should have such a message, i think...
  • If the message should be there I guess it should refer to 14.1-RELEASE EOL in general without any particular patch release
  • The warnings should be seen every time you do a freebsd-update fetch
If I would see what I suggest above, I would be clear to me. But ok... Now I know what is happening and why. So for me this thread is solved. But I think there is potential for improvement when it comes to warning messages :)
 
You must log in or register to reply here.
Back
Top