Occasional crash reports on 2.2.2 & Upgrading Question

tomstephens89

Hi, I have two pfSense machines running 2.2.2 in a CARP configuration. Recently I am getting an occasional crash report as follows:

Crash report begins.  Anonymous machine information:

amd64
10.1-RELEASE-p9
FreeBSD 10.1-RELEASE-p9 #0 57b23e7(releng/10.1)-dirty: Mon Apr 13 20:30:25 CDT 2015     root@pfs22-amd64-builder:/usr/obj.amd64/usr/pfSensesrc/src/sys/pfSense_SMP.10

Crash report details:

PHP Errors:
[14-Aug-2015 17:00:00 Europe/London] XML error: Not well-formed (invalid token) at line 2

This has happened twice in the past 7 days and I wondered what it was?

Also, I am aware that I am out of date now as well and want to know the best practice method of upgrading a pfSense CARP configuration. Do I need to put CARP into maintenance mode and upgrade one at a time, or do I need to disable CARP and upgrade one at time then re-enable CARP… Or do I just upgrade one at a time and not disable anything?

Also, what is the behaviour of my CARP VIP's when CARP is in maintenance mode or disabled? One pfSense host will retain ownership of the VIP's I assume?

Thanks
Tom

tomstephens89

Can no-one shine a light on this then?

firewalluser

Its seems to be quite a short crash log so not a lot of data to go from really.

Info how to find and look at the crash dumps can be found here.
https://forum.pfsense.org/index.php?topic=97347.msg542182#msg542182
https://forum.pfsense.org/index.php?topic=95928.msg542034#msg542034

tomstephens89

This still appears to be happening. I had a look at the links showing how to get at the full crash dumps, but I don't think I'll be able to get them since BSD supposedly dumps only on panic (which isn't happening) and the files will be the size of the physical memory, which in this case is 48GB…. I only have 36GB HDD space available so no can do.

Reading around, this could be due to an invalid character in a field somewhere which is throwing an error when the php interface parses the XML.

fragged

https://doc.pfsense.org/index.php/Upgrade_Guide#Upgrading_High_Availability_Deployments

Upgrade slave
Put master into maintenance mode and upgrade
Make sure master is working and remove maintenance mode

You should upgrade first before doing any more troubleshooting into the php crash issue.

tomstephens89

@fragged:

https://doc.pfsense.org/index.php/Upgrade_Guide#Upgrading_High_Availability_Deployments

Upgrade slave

Put master into maintenance mode and upgrade

Make sure master is working and remove maintenance mode

You should upgrade first before doing any more troubleshooting into the php crash issue.

Thanks but I have already upgraded.

tomstephens89

Just noticed that on the warning menu (flashing yellow bar at top) the error is related to sync settings so I'm assuming I have a bad value in my xmlrpc sync fields or something?

tomstephens89

I am currently on 2.2.4, will plan an upgrade window to get to 2.2.5 and see if it persists.