Snapshot: pfSense-2.1-DEVELOPMENT-4g-i386-nanobsd-upgrade-20120718-1817 broken?
-
Hi All,
Wondering if anyone else had problems with this build? I wanted to start testing the IPv6 features and ran an upgrade. The system initially came up, but there were multiple php errors on the WebUI.
Unfortunately as I needed to get my network back in a working state asap, I wasn't able to capture the errors in full.
The errors I noticed were:
1. php configuration system error
2. missing pfsense.so (probably wrong name.)Thanks,
JasonPS: Can anyone recommend a good snapshot to start with?
-
I recently changed the script that sets up php.ini.
I could imagine that causing it, but it should then happen on normal updates as well.
if you do a ls -l /conf/config.xml does that list the config? Not sure if that is /cf/conf/config.xml
-
I recently changed the script that sets up php.ini.
I could imagine that causing it, but it should then happen on normal updates as well.
if you do a ls -l /conf/config.xml does that list the config? Not sure if that is /cf/conf/config.xml
Hi databeestje,
Unfortunately I am not able to access that information. I had to pull my ALIX apart and go in and set the other partition as active in order to boot from my old STABLE 2.0.1 partition. As this is my only device, I need to have the internet working, and am therefore reluctant to switch it back…
Do you know if there is a way I could access the second slice from the main system? Actually I think I backed up my current stable system to that slice after the issues, just in case, so that won't help anyway!
I could try it in a VM I guess...however that of course will not be an embedded system...
Thanks,
Jason -
Download VmWare Esxi and use that for testing before entering an update into a critical environment.
-
Download VmWare Esxi and use that for testing before entering an update into a critical environment.
Hi Supermule,
Thanks, I'm well aware of methods testing for critical environments, however this is a home environment.
Internet is necessary for some, but not critical, therefore I can test. But the timing is sometimes an issue…
That aside, I tested the VM version, but it doesn't seem to have the same issue. I used the upgrade from console with the URL method, perhaps it was a dodgy download...
Thanks,
Jason -
Normally I do the ISO's directly in a VM, and skip the dedicated VM images.
Still run the 1.2.3 in production environments. Dont like the 2.0.x releases as it doesnt seem finished….
Not a very intuitive user interface anymore and things break all the time.
-
Normally I do the ISO's directly in a VM, and skip the dedicated VM images.
Still run the 1.2.3 in production environments. Dont like the 2.0.x releases as it doesnt seem finished….
Not a very intuitive user interface anymore and things break all the time.
Hi Supermule,
Thanks for your insight!
I've been very happy with the 2.0.1 release myself, however admittedly my usage has not pushed the limits.
I have found the same however with snapshots, they are a little "touch and go". Of course, the feature set has really grown, so I guess that can be expected.
All in all, still a great product! :)
Thanks,
Jason -
Yes it is Jason and it performs very well pushing 900mbit normal internet access in cloud environments!
So I like PFsense a lot.
-
Hi All,
Sorry to have raised a false alarm. Based on the fact that the VM version was working, and nobody else experienced these issues, I tried downloading the file, verifying the checksum and then uploading it directly instead of using the upgrade from console. I wouldn't say the upgrade was seamless, but it is now working. I found the system very slow, and I had to reboot it via the CLI to get it to work properly from the WebUI. Occasionally in the WebUI I was getting this error:
Fatal error: Call to undefined function pfSense_interface_listget() in /etc/inc/interfaces.inc on line 68However, it seems to have stopped!
I now have the HE.net IPv6 Tunnel working!
Thanks,
Jason -
the slow nanobsd issue has been here for a while in freebsd 8.3. We don't have a fix for that issue.