Don't upgrade to x86 CE build 2.4.0.r.20171008.0625
-
@marjohn56:
I think they are marked BAD for a reason ::)
I agree ::)
Could that situation also lead to failing package reinstallation after a fresh install?
I did a fresh install of a RC-snapshot from Oct, 3rd or so (just chose a random one, updates later) and restored my backup xml to it.
Currently it is not able to display available packages or install the packages listed in the XML.
No big deal right now, just reporting and asking to learn things. -
Most likely yes.
Best to leave alone until the repo is back up. If you have killed your system then I would rebuild from one of the downloads that are still available. You may not have packages, but at least you'll get a basic working system, however each to their own.
-
@marjohn56:
Most likely yes.
Best to leave alone until the repo is back up. If you have killed your system then I would rebuild from one of the downloads that are still available. You may not have packages, but at least you'll get a basic working system, however each to their own.
Box is up and running, no urgent need for the packages. Thanks.
-
i wish i had read this Friday night before i installed this on my sg2220…
i learned quickly how to console into my box which i never had to do before.
really my main complaint is this. i had made a backup under diagnostics > backup and restore > backup and restore a few months ago to an XML file. when i tried to restore it after i put 2.34 p1 back on i received this :
a full configuration restore was selected but a pfsense tag could not be located. what exactly does that mean?
another sad note, i am running the community version on what i believe is an older version of BSD version 10. is that correct?
-
On 2.3.4 Yes. 11.0 is 2.4.0 ( or was/is/maybe ) 11.1 is 2.4.1 ( or was/is/maybe ). It's all a bit variable at the moment depending on how you are leaning.
-
The current release version of pfSense,2.3.4_1, is built on FreeBSD 10.3.
2.4 snapshots were previously built on FreeBSD 11 but moved to 11.1 when we had to delay release to pull in patches for newly discovered issues.
That applies to factory and CE versions.
https://doc.pfsense.org/index.php/Versions_of_pfSense_and_FreeBSD
If you upgraded to a bad snap and found the result unusable you have a few choices.
You can wait until we get the repos back up after testing the fix we put in which should be very soon. If your firewall still has WAN connectivity you can upgrade from there.
You can restore a 2.4 snap from Oct6th or earlier but because the repos are down you will not be able to install and packages.
You can restore a 2.3.4 image, the repos for 2.3.4 are unaffected so packages will be installed but any config file you restore must be from 2.3.4 or earlier. If you restore a config from 2.4 you may see that sort of error where 2.3.4 does recognise tags in a 2.4 config file. Not everything has changed though.
Steve
-
@marjohn56:
I think they are marked BAD for a reason ::)
I plan on fresh install and restore from old config.xml as soon as repos are up.
-
In this next sentence I say Something witty in Klingon about ZFS boot environments in pfSense 2.4+ as a mitigating factor for contingencies such as this:
"ZFS nIvbogh be'vam SUPERBORK SeH 'oH alows SoH ghaH nom RECOVER."
That was one really nice thing about Nano.
-
In this next sentence I say Something witty in Klingon …..
Nice. ;D
_That is always the safest way. And with the config recovery in 2.4 should be fast.
Internal testing of the new pkgs is looking good.
Steve_
-
In this next sentence I say Something witty in Klingon about ZFS boot environments in pfSense 2.4+ as a mitigating factor for contingencies such as this:
"ZFS nIvbogh be'vam SUPERBORK SeH 'oH alows SoH ghaH nom RECOVER."
That was one really nice thing about Nano.
Will be a snapshots a thing in pfSense? Wold be great a auto snapshot before upgrade option, maybe. Config recovery do the job beautifully.
-
@mais_um:
Will be a snapshots a thing in pfSense? Wold be great a auto snapshot before upgrade option, maybe. Config recovery do the job beautifully.
It's a ZFS thing, and ZFS is now an install option in pfSense 2.4.
AFAIK, you can't recover from ZFS snapshots in pfSense just yet. I'm not sure where that is on the road-map, but if I were King/President/Jesus, I'd make it a high priority.
I've been anticipating ZFS in pfSense for years and am still giddy when I think about a ZPool vDEV made of 2 flash DOMs. https://twitter.com/karlfife/status/878833005426561024
FreeNAS has been doing GUI-integrated ZFS boot environments for a while, and the feature has saved my bacon more than once (especially in remote installs without remote technical hands). As long as the system comes back up after an update/upgrade, you can pick a boot snapshot (via GUI/SSH–no IPMI needed).
Yes, snapshots are auto-generated at time of update, and (of course) they each contain a private copy of the config (e.g. usable, non-migrated).
-
I just applied the newly available 10/9 build. It seems to have fixed my broken install.
That is, my 2.4 remote instance was non-functional, notably had a DHCP server that wouldn't start, but the borked instance retained WAN connectivity. Just now, it called home to the update servers, which pushed the 10/9 build, then rebooted, bringing the network back to the land of the living. Nice work gentlemen.
-
Too late, totally messed me up. Took about 4 hours to figure out what happened and get things fixed and going again. :(
-
Installed the latest update. Seems okay so far.
-
But dhcpd v4 not working:
Oct 10 06:21:15 dhcpd Can't attach interface bridge0 to bpf device /dev/bpf0: Invalid argument -
But dhcpd v4 not working:
Oct 10 06:21:15 dhcpd Can't attach interface bridge0 to bpf device /dev/bpf0: Invalid argumentI'm not seeing that error or any other malfunction of dhcpd.
-
Manual upgrade "pkg upgrade -f isc-dhcp43-server-4.3.6_1" and clean chroot env. /var/dhcpd resolve it.
-
Fresh install of the new version and restore from old config.xml has fixed everything.
-
Did a fresh install and restored my old config and its all working fine now.
-
Manual upgrade "pkg upgrade -f isc-dhcp43-server-4.3.6_1" and clean chroot env. /var/dhcpd resolve it.
That did the trick for me as well.
For developers, I know it's hard to keep up with the changes but this is a case where you could improve greatly. It should not be possible to upgrade your system and be left with an old version of a chroot environment that has the wrong device nodes or other files, every upgrade should clean up expendable content so that the services are started with a clean slate after an upgrade.Edit: I realize now that the real problem was a bad dhcpd binary and the package system didn't include an updated dhcpd package, it actually did but since the version number hadn't changed pkg didn't offer it as an update and the only way to get the fixed dhcpd package was to use pkg install/upgrade -f.
You could investigate a possiblity of including a build number into your package version numbers. It's not afaik supported directly by poudriere which assumes that the version numbers are what's in the ports tree and nothing else. A build number would solve a lot of problems similar to this and enable a forced reinstall of all packages regarless of what the version numbers are in the ports tree.
