Upgrade to 2.2.2 from 2.1.5 never reboot
-
I was doing automatic upgrades from 2.1.5 to 2.2.2. The firewall never rebooted. I logged into the Dashboard, and it shows version 2.2.2, all my IPSEC VPN tunnels are up (but running racoon), and keep getting these unread notices:
[ There were error(s) loading the rules: pfctl: DIOCADDRULE: Operation not supported by device - The line in question reads [0]: ]
I am not physically at the machines power cycle them, and am a bit hesitant to get someone to do it as I'm not sure if they will reboot or fail.I have 5 firewalls with the same hardware each configured a bit different. 3 of the 5 upgraded without issues. 2 are having this issue.
Thoughts/suggestions?
Thanks
-
Same problem here!
i'm running a couple of pfsense inside two esxi hosts with CARP, openvpn, squid.
I tried to upgrade the secondary node, and using the auto-update from the web interface the process stuck in the "now rebooting" phase.
After an hour, i rebooted manually and the system was unusable (it would boot, but complained about missing files and other random errors.
I reverted the snaphot and tried again, this time from console.
Again, Firmware update in progress…....Done........ Now rebooting.
And again no reboot, but straight to the console menu.
THe web interface was the 2.2.2 one, but with several errors (probably because it did not reboot).
Again the manual reboot resulted in unusable system.I'm available to provide any info requested about the issue.
I'll try again with a full clean install and restore of the config.
-
I upgraded from the automatic upgrade tool and restarted, and my server never booted again, it keeps displaying character per character as if its booting very slow.
I tried to formate the server and do a clean install and it worked until I restored the configuration backup, and I had to install it once again.
I tried doing the rules manually, and as soon as I configured a single Lan the same problem happened.
I had to look for 2.2.1 version Install it and restored the backup and everything was working fine.
SO this version has bugs.
-
I upgraded from the automatic upgrade tool and restarted, and my server never booted again, it keeps displaying character per character as if its booting very slow.
This is totally OT here, plus already discussed in several threads.
-
Yep slow console issue is fixed. Disable your serial port to get past it.
The most common cause of not rebooting is that you've accidentally switched architecture to 64bit or vice versa. If that is the case, and your hardware is 64bit capable, then you can just reboot. Check the update URL.Steve
-
I took a chance. Since it would not reboot from the GUI, I issued reboot from the command line. Both boxes rebooted and appear fine now. Very odd.
-
when i close serial port on bios pfsense boot up so fast but dhcp not working although services show dhpc is working but any ip receive lan computers
i tried to fix like in this page
https://github.com/pfsense/pfsense/commit/cc1f655f8e88ccda837e21d0646bbc71781198b9?diff=split
after that 10 hours system not boot up
i dont know what can i do ¿ -
Stop @mesro09:
when i close serial port on bios pfsense boot up so fast but dhcp not working although services show dhpc is working but any ip receive lan computers
Sir, you yet again are totally offtopic here!
-
I too am having this issue but came from 2.1.4 on I386. Will not reboot from Web and ssh is already shutdown so that is a no go.
Packages installed were
Openvnp export
snort
bandwidthd
pfblocker
haproxy-develI guess I'm going to have to make the hour ride to the Colo and reboot it.
-
Upgrading from 2.1.x to 2.2.2
Box will not reboot automatically. System looks like it's OK from the web interface. It isn't.
It still needs a reboot for everything to work correctly.
If the web interface is still up, go to Diagnostics -> Command prompt
/sbin/reboot -
Yes, it seems this can still happen. When it does though the dashboard will show the pfSense version as 2.2.2 but the FreeBSD version as 8.3 still. That should never happen obviously. Rebooting manually will fix that.
Steve
