hello ..im human on earth not betazoid mind-reader from betazed..please help me understand..thankz

Right in front of "CAM status" it logs something like "(ada1:ahcich1:0:0:0)". The CD drive being disconnected is the circumstance with ESX that can make weird things happen. Should connect it, or remove it entirely, to avoid problems.

THANKS !!! ;D

It's fine to leave it to that URL. I updated the release file prep scripts to make sure it gets copied into place correctly (I just manually copied that one before and obviously didn't pay close enough attention to what I was doing).

Try with the: "Memstick Serial" img ;) https://doc.pfsense.org/index.php/Installing_pfSense#LiveCD_vs_Memstick_vs_Memstick_Serial

yeah all the packages configs will stay the same..  No 2.2.2 to 2.2.5 is not a major release, 2.1.x to 2.2.x would be a major update.  Normally they mention if major changes in the release notes.  For example the upcoming 2.3 going to be major changes.  But even then prob no need to uninstall the packages unless its a problematic one..  Make sure you read the release notes on an update, wait a few days and read the forums on other peoples experiences with the update if your concerned and this is critical production system, etc. https://blog.pfsense.org/?cat=53 Upgrade Guidance As always, you can upgrade from any previous version straight to 2.2.5. For those already running any 2.2.x version, this is a low risk upgrade. For those on 2.1.x or earlier versions, there are a number of significant changes which may impact you. Pay close attention to the 2.2 Upgrade Notes for the details.

If it's Squid causing this then yes, it will flush the cache eventually when the daily cronjob hits; however – that's no solution! You need to configure things properly so that this doesn't happen again!

It looks like I spoke too soon - I'm seeing massive IPv6 brokenness to *.pfsense.org again :(

The earlier iteration of updation from the WebGUI failed when the main WAN was down even though the secondary WAN was up. This might be a pointer to modify the image check code on other available WANs if the main one is down. The firewall itself just uses the default gateway to get stuff like updates, so if the default gateway is down then that sort of stuff does not come. You can enable "default gateway switching" if you have a "standard" kind of installation where all the interfaces with gateways are good routes to the internet. Then the firewall itself should be able to failover its general internet access. But usually anyway I would only do an upgrade when I seem to have a good primary WAN. Introducing an upgrade when there is a primary WAN issue feels like an extra risk that is best avoided.

upload_config() should be found in /usr/local/pkg/autoconfigbackup.inc It could just be an issue while the system was booting and reinstalling all packages, including AutoConfigBackup. or maybe something went wrong with the package reinstall part way through installing AutoConfigBackup. You could reinstall AutoConfigBackup and then use it to do a manual backup, make some config change and check that it has done the backup and that no errors are logged.

7 different sites updated no issues!  :)

Hi, It's now OK. I have manualy install the amd64 upgrade. This is due a backup done on a i386 system… Thanx. Cyril

@luma: Hi there, I remotely upgrade through webgui a APU amd64 2.2.4 pfSense full install. All seemed to went fine until I discoved FreeBSD system packages installed myself not working anymore… What a suprise, the system switch to i386 ! Any idea of what happened ? How can I remotely revert to AMD64 ? Thanks and regards Same problem as you. To try to correct I have downloaded the Full Update 2.2.5 for amd64 tar ball. I have run the manually update with the tgz file. It's still in progress. I'll keep in touch. Cyril

@NOYB: You might try a process like this to put the system into a KISS state before applying the upgrade. I've yet to see a situation where that was necessary. Way too much effort. If your packages fail to reinstall, just clear the lock and hit reinstall packages after it's booted back up.

You were right ! I did some cleaning in /tmp and after a reboot everything is working fine.

Connect to the serial console. https://doc.pfsense.org/index.php/Locked_out_of_the_WebGUI

What's the exact message you're getting?