Update to 2.1.3 on ESXi

biggsy

When I updated an ESXi from 2.1 64-bit to 2.1.2 I got a 32-bit installation instead of a 64-bit. Only clue was that RRD graphs came up as being for a different architecture.

Thinking I had done something stupid, I rebuilt the 64-bit VM, installed 2.1.2 64-bit from an ISO and restored the config. All OK until today. Updating to 2.1.3 I again got a 32-bit install over the top of the 64-bit.

I noticed that there are a few packages that mention dependencies on i386 in the config.xml:


Postfix Forwarder
	Line 1623: 			<depends_on_package_pbi>postfix-2.10.2-i386.pbi</depends_on_package_pbi>

OpenVPN Client Export Utility
	Line 1667: 			<depends_on_package_pbi>zip-3.0-i386.pbi p7zip-9.20.1-i386.pbi</depends_on_package_pbi>
	Line 1667: 			<depends_on_package_pbi>zip-3.0-i386.pbi p7zip-9.20.1-i386.pbi</depends_on_package_pbi>

Open-VM-Tools
	Line 1713: 			<depends_on_package_pbi>open-vm-tools-nox11-425873_2-i386.pbi</depends_on_package_pbi>

These could have been carried over from an earlier install but I'm pretty sure the OpenVPN Client Export has never been installed on anything but 64-bit.

Does this i386 stuff in the config XML conflict with the statement in the upgrade guide that "The config is the same on both versions"?

raverX

I have had the same problem.

Couldn't work out why all of a sudden so many of my binaries (pmacctd, mc, etc) that I had built for customisation weren't working - till I got the daily RRD graph and it failed. Checked the log files and it said "ERROR: This RRD was created on other architecture"

uname -a
FreeBSD fw.studios.local 8.3-RELEASE-p16 FreeBSD 8.3-RELEASE-p16 #0: Thu May 1 16:15:14 EDT 2014 root@pf2_1_1_i386.pfsense.org:/usr/obj.i386/usr/pfSensesrc/src/sys/pfSense_SMP.8 i386

I put 32 GB of memory into this box because it has a rather large client base behind it (1000 users, 20 vlans) and I wanted to run squid + dansgaurdian. Now i'm being told it has 3.5gb of memory.

Anyone know how to fix this and get back to a 64bit kernel??

raverX

Might be worth changing the subject to "Upgrade 64bit to 2.1.3 ends up as 32bit" … so it gets more notice..

jimp

That can happen if you didn't check/fix your firmware upgrade URL (System > Firmware, Updater Settings tab). If you had a custom URL in there from an older i386 install (perhaps you restored an older config), and didn't change it to amd64, then it would still pull down an i386 firmware.

Go there, make sure it's set for amd64, and run another upgrade. You will likely have to power cycle the host/VM manually after the upgrade but it should switch you back.

raverX

Thanks.

Had to download the latest 64bit version and upload it manually as it doesn't recognise the version difference.

But after a hard reset, a lot of sweating as it went through a disk check, it came back up all good.