2.5.2 Upgrade - surprise
-
I can confirm that!
With default installation and no fancy stuff
The update except for the automatic update I have to do it per hand (klick the update button)
Runs as smooth as it gets... -
@slimypizza said in 2.5.2 Upgrade - surprise:
and discovered that pfSense had upgraded itself automatically
The upgrade process is triggered by a user command on the console or SSH : option 13.
or the GUI : System > Update System > Update page.
Both 'screens' need 'admin' access.
pfSense that upgrades itself overnight : I would call that a major issue ...@slimypizza said in 2.5.2 Upgrade - surprise:
No backups taken
That's a personal choice ;)
I'm using https://github.com/KoenZomers/pfSenseBackup which extracts a backup every day at 08h00 AM. -
Over all the units we have running for ourselves and clients over the last decade plus I've never seen one spontaneously self-upgrade.
That said there was a thread here a while back...not sure how long but probably at least a couple months...where someone claimed they had devices self-upgrade. As I vaguely recall there was a theory about cron jobs running at boot. If you go back through the logs can you see if there was a reboot/power loss before the upgrade?
-
After reading / replying this post this morning I was a little bit scared
Of auto update enabled...Looked through a couple of 2.4 boxes not able finding some option
Np
-
@noplan said in 2.5.2 Upgrade - surprise:
Of auto update enabled...
Doesn't exist.
This :
is something completely different - and does what it says it does : it syncs the list with available packages, shown here :
so its visible right away if there is an update available for one of the packages.
Which is the case for me right now : arpwatch can be updated.
To keep this info current, the "dashboard" has to go out often, and check if one or more of the installed packages have a new version available.
If someone breaks the DNS subsystem (this happens often - check the forum) then the admin has the possibility to disable the frequent checking, as it can make the dashboard access very slow.A firewall/router doesn't update itself. Its far to simple to imagine what could go wrong even if the update goes fine.
-
@gertjan said in 2.5.2 Upgrade - surprise:
A firewall/router doesn't update itself. Its far to simple to imagine what could go wrong even if the update goes fine.
Mine apparently did. Or I should say, it did. Since my logs now begin at 14:05 August 4 I assume that is when the spontaneous upgrade occurred. I was not at home or logged in at the time. A few days later when I logged in is when I noticed what had happened. Lucky indeed that nothing went wrong. The only thing I had done at some point prior was to toggle the Branch in the System/Update page. I wanted to see the effect of selecting the previous stable version. I noted the effect and toggled back to current Branch thinking that I would decide to update at some point in the future after I was notified of the next available update. Instead my router updated on a Wednesday afternoon while I was away. No harm done thankfully but I don't want that to happen again.
-
@slimypizza said in 2.5.2 Upgrade - surprise:
I assume that is when the spontaneous upgrade occurred.
This file shows when it happened : /cf/conf/upgrade_log.latest.txt
No "help me" PM's please. Use the forum, the community will thank you.
Edit : and where are the logs ?? -
@gertjan do u think it's even possible that a box performs auto update from 2.4 to 2.5?
Me just wondering
Btw thx for the location of the logFile -
@gertjan -- This file shows when it happened : /cf/conf/upgrade_log.latest.txt
Thanks gertjan. This confirms the upgrade occurred Aug 4 14:05 as well.
-
To be clear this should never happen. And as far as I know there is no way for it to happen.
Do you still have the upgrade log? Can we review it?
You said your main system logs were reset at that point? Are you using ram disks?
Steve
-
-
Hmm, nothing unexpected logged there. You don't have any system logs from the time?
Steve
