;D ;D This should be promoted to the sticky ones

Thx to point that out.

Oops my bad :) Stupid me for not noticing the advanced button. Thanks.

The part that says 'page not present' would this be a page in memory? A page that should be in memory. When the processor is switched to kernel mode to do privileged things, those things are generally expected to run quickly. To achieve that (and avoid other nasty possibilities) no page faults are allowed (a page fault means that the needed page would have to be read in to memory from storage). So it is expected that all pages referenced are already memory-resident. The problem is that the needed page is not already in memory - but in kernel mode the system refuses to wait for it to be read in. This should never happen. Almost by definition it is a bug in FreeBSD. Most often a timing interaction that only crops up intermittently.

updated to 2.3…a repurpose winxp machine... basically its a one click affair... had minor issue with the suricata package... good job guys...keep it up.. [image: pfsenseui.png_thumb] [image: pfsenseui.png]

@dpsi: @fmaxwell: @jimp: The boot menu with safe mode was shown in your serial output, just power cycle it, and at that menu hit: 6, then 4, then backspace, then 1 It's shown, but the keyboard input isn't accepted over a serial port.  That threw me off for a long time when I first set it up some years earlier. Sounds like your TX is not wired correctly over your serial cable. Realized I'd made a mistake in describing.  When in the BIOS, which can redirect to serial (as shown), you still need a keyboard connected to a USB port.  Once pfSense has booted, the serial-in does work. I'm in the middle of rebuilding my server, which I had a VMWare image of, allowing me to run it virtually while the hardware is down.  I'll get back to the pfSense mess later – probably after I buy new hardware.

have a look at my thread I had a similar issue and I fixed it on my box https://forum.pfsense.org/index.php?topic=110033.0

Well dadgum! Got it working. I did 2 things: 1. Switched the WAN to 1gb1 from igb0. 2. Found that a Cat6A cable was being used from the modem to the router so I switched it to Cat5e. One of those two worked, I'm guessing the Cat5e cable. I'll switch the interface back to igb0 at another date… Thanks for your time and help coxhaus and cmb, I know you are busy right now :)

@macboy6: cmb, did the CE memstick image also require an update?  I need it for another system and downloaded at release, but have not installed yet. No.

Looks like there's an issue in the config upgrade code with changing the parent interface in an edge case there. I'm looking into the root cause, but just editing the IP alias virtual IPs with CARP parents, picking the CARP IP, save and apply changes will fix in the mean time.

It's a bug - see https://github.com/pfsense/pfsense/pull/2867 and Redmine issue https://redmine.pfsense.org/issues/6144 Try the very simple and confirm that it will work OK restoring an area that currently does not exist.

https://forum.pfsense.org/index.php?topic=109690.0

That solved it - thanks!

I have the same underlying issue. This problem also affects the use of the /status_carp.php page. I have +100k states and using a CARP HA fw pair and get this error when using the CARP status page. As I needed the function to activate / deactivate CARP on this page I patched the file  /usr/local/www/status_carp.php and replaced $states = pfSense_get_pf_states(); with $states = 0; so the page loads but displays no states because of my workaround. René

I might have worked out the issue.  I had snort on the machine and I saw other people are having problem with that package.  What I did was delete the snort package and based on my users they say it is back to normal. Not sure if this helps anyone and I will still run some test to see but looks like the removal of snort might have fixed it Paul

OK, this has been partly solved - the ACB failure was down to a subscription issue which has now been sorted. However, I still think there is a bug with the ACB module, in that if the ACB registration fails, it messes up the GUI in a major way until you reboot. Cheers, Keith