Fixed by pull request #208 - https://github.com/bsdperimeter/pfsense/pull/208

Well, then we have a bug in the webIF I'm using the August 5 build and it was there in the August 3. I never experienced it in 2.01 It must have slipped in after implementing ipv6?

If you just go to a command prompt and run 'killall php' it'll come back to life. Go to Diagnostics>Ping, try to ping google.com. Guessing it won't resolve.

I just got one of these. The error text is most unhelpful - no module and line numbers! So I googled it and found this. I went to System, Package Manager, Available Packages and got the same error again in PHP_errors.txt and screenshot below. Went back to the dashboard and tried again, now there is no problem. I guess this is a transient issue when something in the online package list is updating/refreshing whatever? I thought it worth adding to this post for the benefit of those who get this in future. Please correct me if this is not just a rare transient thing. Crash report begins.  Anonymous machine information: i386 8.3-RELEASE-p3 FreeBSD 8.3-RELEASE-p3 #0: Sun Aug  5 19:57:23 EDT 2012     root@FreeBSD_8.3_pfSense_2.1.snaps.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_wrap.8.i386 Crash report details: PHP Errors: [06-Aug-2012 11:10:45 UTC] XML error at line 1, check URL [06-Aug-2012 11:26:56 UTC] XML error at line 1, check URL [image: packages.jpg] [image: packages.jpg_thumb]

nevermind, I cleared the cache (Chrome) and I the data are showing now

ok, so something is restarting openvpn. Check your main system log, perhaps you have a gateway going up/down?

Crash report begins.  Anonymous machine information: i386 8.3-RELEASE-p3 FreeBSD 8.3-RELEASE-p3 #1: Fri Aug  3 02:20:02 EDT 2012    root@FreeBSD_8.3_pfSense_2.1.snaps.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_SMP.8 Crash report details: PHP Errors: [03-Aug-2012 18:57:47 UTC] PHP Fatal error:  Call to undefined function sync_package_zebedee() in /etc/inc/pkg-utils.inc(457) : eval()'d code on line 1 Filename: /var/crash/minfree 2048

Approved. Thx phil for the help.

Which version of squid? And what's in /tmp/rules.test.packages when it's complaining?

Yep, I did feel OCD! I have put in a couple of pull requests to tidy up the console output some more. Everything functional seems fine. I'll see how the console output looks tomorrow after the next snapshot/upgrade/package install sequence. After the conf_mount_ro fixups for squid and squid3 it should also leave the filesystem mounted read-only when finished.

not sure I haven't looked at the ticket in a while in that much detail.

Got this morning's snapshot. Seems to work. Some issues, but they have been reported elsewhere..

If i create wrap_vga kernel and replace it in latest snapshot img and change bootloader from boot0sio to boot0 will vga work?

I'm using the default theme. No extra packages or anything, the only thing i did was import the settings from my old 2.0 install. Seems to happen a bit more on my desktop then on my laptop both running fedora 17(gnome3). On the desktop it's pretty much guaranteed to happen. Sorry for the late reply i kinda forgot about posting here.

EDIT : Sorry, I just found the bug in filterdns http://redmine.pfsense.org/issues/2506 CLOSED ! Thanks for your answer. I put it in debug mode and there is a problem : I have a table named 'APTUpdates' with servers needed to my Debian station to be joined for the updates. One entry is ftp.fr.debian.org which is actually reseolved by : $ host ftp.fr.debian.org ftp.fr.debian.org is an alias for ftp.oleane.net. ftp.oleane.net has address 194.2.0.36 ftp.oleane.net has IPv6 address 2a01:c910:0:1::c202:24 BTW, in the table,there is not the IPv6 entry : pfctl -t APTUpdates -T show   67.205.85.245   82.67.68.81   82.195.75.97   86.59.118.148   86.59.118.153   88.191.250.131   91.189.88.33   91.189.92.150   91.189.92.151   91.189.92.166   91.189.92.167   91.189.92.181   91.189.92.184   91.189.92.191   128.31.0.51   130.89.148.12   130.89.148.13   147.173.3.16   158.255.96.2   188.165.151.222   194.2.0.36   194.145.197.105   195.20.242.89   206.12.19.9   212.211.132.32   212.211.132.250   2001:610:1908:b000::148:13   2001:858:2:2::2   2001:858:2:2:214:22ff:fe0d:7717   2001:8d8:580:400:6564:a62:0:2   2001:a78:5:0:216:35ff:fe7f:be4f   2001:a78:5:1:216:35ff:fe7f:6ceb   2001:41b8::/32   2001:41b8:202:deb:1a1a:0:52c3:4b61   2607:f8f0:610:4000:211:25ff:fec4:59ae   2a01:e0c:1:1598::2 Other thing in logs (egrep '(adding|clearing) entry' user.warning  | grep ftp.fr.debian.org) : Jul 31 11:03:46 pfsense1 filterdns: adding entry ::2a01:c910:0:1:0 to table APTUpdates on host ftp.fr.debian.org Jul 31 11:03:46 pfsense1 filterdns: clearing entry ::2a01:c910:0:1:0 from table APTUpdates on host ftp.fr.debian.org Jul 31 11:08:46 pfsense1 filterdns: adding entry ::2a01:c910:0:1:0 to table APTUpdates on host ftp.fr.debian.org Jul 31 11:08:46 pfsense1 filterdns: clearing entry ::2a01:c910:0:1:0 from table APTUpdates on host ftp.fr.debian.org The logs are strange too (for another server) : The :: is not at the right place… Jul 31 08:53:41 pfsense1 filterdns: adding entry ::2001:610:1908:b000:0 to table APTUpdates on host ftp.debian.org Jul 31 08:53:41 pfsense1 filterdns: found entry 0.0.130.89 for APTUpdates because ftp.debian.org has : : host ftp.debian.org ftp.debian.org has address 130.89.148.12 ftp.debian.org has IPv6 address 2001:610:1908:b000::148:12 Of course, as the update is incorrect, the packets are dropped... Thanks a lot

Just posted another pull request. Sorry about that, it was working until reboot. For some reason (beyond my understanding) when the script starts and I see how many proxy_monitor.sh scripts are running, it shows 2. If I see what is there manually a sec later, it shows 1. Since the variable is already loaded with 2, the script exits out. It might have something to do with the way it is being called from squid reload/load with the mwexec_bg. I am not sure on that entirely though. I modified the code to match the way the script is being called. The result is  only one infinite loop running in the background.