Alix 2D13 - Have you upgrade to 2.3 ? Did it go okey?
-
So I tried to make the card be mounted R/W permanently. Trying to save that setting, ironically gives me an "Unable to open /cf/conf/config.xml for writing in write_config() @ 2016-04-13" error. Looks like the GUI wants to write to the R/O card !?
Here the full output, which I don't understand:
Warning: copy(/cf/conf/backup/config-1460498200.xml): failed to open stream: Read-only file system in /etc/inc/config.lib.inc on line 920 Call Stack: 0.0003 122192 1. {main}() /usr/local/www/diag_nanobsd.php:0 21.2111 829100 2. write_config() /usr/local/www/diag_nanobsd.php:134 21.2117 829436 3. backup_config() /etc/inc/config.lib.inc:553 21.4232 829600 4. copy() /etc/inc/config.lib.inc:920 Warning: filesize(): stat failed for /cf/conf/backup/config-1460498200.xml in /etc/inc/config.lib.inc on line 927 Call Stack: 0.0003 122192 1. {main}() /usr/local/www/diag_nanobsd.php:0 21.2111 829100 2. write_config() /usr/local/www/diag_nanobsd.php:134 21.2117 829436 3. backup_config() /etc/inc/config.lib.inc:553 21.4695 832788 4. filesize() /etc/inc/config.lib.inc:927 Warning: fopen(/cf/conf/backup/backup.cache): failed to open stream: Read-only file system in /etc/inc/config.lib.inc on line 928 Call Stack: 0.0003 122192 1. {main}() /usr/local/www/diag_nanobsd.php:0 21.2111 829100 2. write_config() /usr/local/www/diag_nanobsd.php:134 21.2117 829436 3. backup_config() /etc/inc/config.lib.inc:553 21.4940 833004 4. fopen() /etc/inc/config.lib.inc:928 Warning: fwrite() expects parameter 1 to be resource, boolean given in /etc/inc/config.lib.inc on line 929 Call Stack: 0.0003 122192 1. {main}() /usr/local/www/diag_nanobsd.php:0 21.2111 829100 2. write_config() /usr/local/www/diag_nanobsd.php:134 21.2117 829436 3. backup_config() /etc/inc/config.lib.inc:553 21.4962 834004 4. fwrite() /etc/inc/config.lib.inc:929 Warning: fclose() expects parameter 1 to be resource, boolean given in /etc/inc/config.lib.inc on line 930 Call Stack: 0.0003 122192 1. {main}() /usr/local/www/diag_nanobsd.php:0 21.2111 829100 2. write_config() /usr/local/www/diag_nanobsd.php:134 21.2117 829436 3. backup_config() /etc/inc/config.lib.inc:553 21.4987 832972 4. fclose() /etc/inc/config.lib.inc:930 Warning: fopen(/cf/conf/config.xml.10269): failed to open stream: Read-only file system in /etc/inc/config.lib.inc on line 495 Call Stack: 0.0003 122192 1. {main}() /usr/local/www/diag_nanobsd.php:0 21.2111 829100 2. write_config() /usr/local/www/diag_nanobsd.php:134 40.3610 882688 3. safe_write_file() /etc/inc/config.lib.inc:565 40.3611 882808 4. fopen() /etc/inc/config.lib.inc:495
-
Sorry to keep replying to myself. To get the "Checking for updates…" fixed, I was looking if I was missing pfSense-base as per this sticky post: https://forum.pfsense.org/index.php?topic=109690.0. Well, there is indeed not pfSense-base, but I do have "pfSense-base-nanobsd-2.3" installed. Should I still install pfSense-base as well?
Thanks for any help!
-
Sorry to keep replying to myself. To get the "Checking for updates…" fixed, I was looking if I was missing pfSense-base as per this sticky post: https://forum.pfsense.org/index.php?topic=109690.0. Well, there is indeed not pfSense-base, but I do have "pfSense-base-nanobsd-2.3" installed. Should I still install pfSense-base as well?
Thanks for any help!
No, what you have is fine.
Did you actually set it to be permanently RW? Or were you only speculating about that bit a couple posts up?
-
Well, each time I check that box and click on "save", I get this error I posted above.
I also tried the option you mentioned above from the command line.The GUI does feel much more responsive now, so maybe it did somehow save the setting, but that checkbox does not remain checked.
Here a more readable form of the error that keeps repeating:
Crash report begins. Anonymous machine information:
i386
10.3-RELEASE
FreeBSD 10.3-RELEASE #5 05adf0a(RELENG_2_3_0): Mon Apr 11 19:14:12 CDT 2016 root@ce23-i386-builder:/builder/pfsense-230/tmp/obj/builder/pfsense-230/tmp/FreeBSD-src/sys/pfSense_wrap_vgaCrash report details:
PHP Errors:
[13-Apr-2016 22:42:30 Europe/Paris] PHP Stack trace:
[13-Apr-2016 22:42:30 Europe/Paris] PHP 1. {main}() /usr/local/www/diag_nanobsd.php:0
[13-Apr-2016 22:42:30 Europe/Paris] PHP 2. write_config() /usr/local/www/diag_nanobsd.php:134
[13-Apr-2016 22:42:30 Europe/Paris] PHP 3. backup_config() /etc/inc/config.lib.inc:553
[13-Apr-2016 22:42:30 Europe/Paris] PHP 4. copy() /etc/inc/config.lib.inc:920
[13-Apr-2016 22:42:30 Europe/Paris] PHP Stack trace:
[13-Apr-2016 22:42:30 Europe/Paris] PHP 1. {main}() /usr/local/www/diag_nanobsd.php:0
[13-Apr-2016 22:42:30 Europe/Paris] PHP 2. write_config() /usr/local/www/diag_nanobsd.php:134
[13-Apr-2016 22:42:30 Europe/Paris] PHP 3. backup_config() /etc/inc/config.lib.inc:553
[13-Apr-2016 22:42:30 Europe/Paris] PHP 4. filesize() /etc/inc/config.lib.inc:927
[13-Apr-2016 22:42:30 Europe/Paris] PHP Stack trace:
[13-Apr-2016 22:42:30 Europe/Paris] PHP 1. {main}() /usr/local/www/diag_nanobsd.php:0
[13-Apr-2016 22:42:30 Europe/Paris] PHP 2. write_config() /usr/local/www/diag_nanobsd.php:134
[13-Apr-2016 22:42:30 Europe/Paris] PHP 3. backup_config() /etc/inc/config.lib.inc:553
[13-Apr-2016 22:42:30 Europe/Paris] PHP 4. fopen() /etc/inc/config.lib.inc:928
[13-Apr-2016 22:42:30 Europe/Paris] PHP Stack trace:
[13-Apr-2016 22:42:30 Europe/Paris] PHP 1. {main}() /usr/local/www/diag_nanobsd.php:0
[13-Apr-2016 22:42:30 Europe/Paris] PHP 2. write_config() /usr/local/www/diag_nanobsd.php:134
[13-Apr-2016 22:42:30 Europe/Paris] PHP 3. backup_config() /etc/inc/config.lib.inc:553
[13-Apr-2016 22:42:30 Europe/Paris] PHP 4. fwrite() /etc/inc/config.lib.inc:929
[13-Apr-2016 22:42:30 Europe/Paris] PHP Stack trace:
[13-Apr-2016 22:42:30 Europe/Paris] PHP 1. {main}() /usr/local/www/diag_nanobsd.php:0
[13-Apr-2016 22:42:30 Europe/Paris] PHP 2. write_config() /usr/local/www/diag_nanobsd.php:134
[13-Apr-2016 22:42:30 Europe/Paris] PHP 3. backup_config() /etc/inc/config.lib.inc:553
[13-Apr-2016 22:42:30 Europe/Paris] PHP 4. fclose() /etc/inc/config.lib.inc:930
[13-Apr-2016 22:42:48 Europe/Paris] PHP Stack trace:
[13-Apr-2016 22:42:48 Europe/Paris] PHP 1. {main}() /usr/local/www/diag_nanobsd.php:0
[13-Apr-2016 22:42:48 Europe/Paris] PHP 2. write_config() /usr/local/www/diag_nanobsd.php:134
[13-Apr-2016 22:42:48 Europe/Paris] PHP 3. safe_write_file() /etc/inc/config.lib.inc:565
[13-Apr-2016 22:42:48 Europe/Paris] PHP 4. fopen() /etc/inc/config.lib.inc:495 -
…turns out I seem get this error for any "save" button on any page. The requested settings are applied, but there seems to be a problem with writing to the configuration file.
-
So the card is still mounted R/O it seems. I did reboot after my first attempt to change that setting, to no avail. Should I maybe remove the "ro" option for /dev/ufs/cf in /etc/fstab?
[2.3-RELEASE][admin@pfsense.localdomain]/cf/conf: /etc/rc.conf_mount_rw
[2.3-RELEASE][admin@pfsense.localdomain]/cf/conf: touch config.xml
touch: config.xml: Read-only file system
[2.3-RELEASE][admin@pfsense.localdomain]/cf/conf: mount
/dev/ufs/pfsense1 on / (ufs, local, noatime, synchronous)
devfs on /dev (devfs, local)
/dev/ufs/cf on /cf (ufs, local, noatime, read-only, synchronous)
/dev/md0 on /tmp (ufs, local)
/dev/md1 on /var (ufs, local)
devfs on /var/dhcpd/dev (devfs, local)
[2.3-RELEASE][admin@pfsense.localdomain]/cf/conf: cat /etc/fstab
/dev/ufs/pfsense1 / ufs ro,sync,noatime 1 1
/dev/ufs/cf /cf ufs ro,sync,noatime 1 1 -
Like @jimp posted above, when the system has booted, use console menu option 8 to drop to a shell (or SSH in to a shell) and:
/etc/rc.conf_mount_rwThat will put the disk partitions into read-write.
Then use the GUI to change to "permanent read-write".
If you get errors when saving at that point, then maybe there is actually a problem with writing to your CF card.
-
The upgrade went ok, the box is running and the firewall seems to continue to work as expected.
As for the GUI… The update email promised a "new responsive look and feel to pfSense requiring a minimum of resizing or scrolling on a wide range of devices". Turns out, the opposite is the case. People have already commented about the GUI being so slow as to be unusable on Alix, unless you mount the CF card R/W permanently. And second the fonts and UI elements have increased in size, making the pull-down menus go off the bottom of my screen. In general, the new UI makes really bad use of screen real-estate and requires more scrolling than the old for me.
Last point, the check for available updates gets stuck on "Obtaining update status" forever...
Bottom line: the box still works, but barely.
Exactly the same problem here. GUI very slow, check for available updates gets stuck on "Obtaining update status" forever and no access to page "System -> Update"
I am on this https://www.applianceshop.eu/opnsense-a10-dual-core-rack-edition.html box except with Intel(R) Atom(TM) CPU Z510 @ 1.10GHz, 1GB ram and 4GB nanobsd.
Also CF card R/W permanently problem?
From the console or SSH shell, run:
/etc/rc.conf_mount_rw
Then back out to the menu and run option 16, and then try to login and go directly to that page.
I was not able to try the solution offered by jimp as stated above because the file /etc/rc.conf_mount_rw does not exist on my box.
Did no have all these problems on 2.2.6.
Erik
-
I was not able to try the solution offered by jimp as stated above because the file /etc/rc.conf_mount_rw does not exist on my box.
If that is true then you have much bigger problems. Every install has that file.
-
Hello all !
Running this ALIX based pfsense appliance, I upgraded to 2.3 yesterday ( nanoBDS 4g )
Everything works fine so far 8)
The only drawback I noticed is that the GUI is ( sometimes ) a bit slow to respond ( but the overall lifting was much needed and is really good )
-
For those who are seeing "Device busy" or similar and unable to force the disk read-write, try the following (preferably from the console):
umount -f /cf; fsck -t ufs -y /cf; mount -f -o rw /cf
Not something we'd normally recommend but somehow it seems that just the /cf slice is getting wedged for some people at the OS level.
Once that is done, set the permanent RW flag on Diagnostics > NanoBSD.
-
I was not able to try the solution offered by jimp as stated above because the file /etc/rc.conf_mount_rw does not exist on my box.
If that is true then you have much bigger problems. Every install has that file.
I did a search for the file on my system:
admin@nas-server:/$ sudo find / -name rc.conf_mount_rw
admin@nas-server:/$Nothing was found.
Firewall seems to work normally except for the issues stated in my earlier reply.
What could I do to correct this?
Erik
-
I was not able to try the solution offered by jimp as stated above because the file /etc/rc.conf_mount_rw does not exist on my box.
If that is true then you have much bigger problems. Every install has that file.
I did a search for the file on my system:
admin@nas-server:/$ sudo find / -name rc.conf_mount_rw
admin@nas-server:/$Nothing was found.
Firewall seems to work normally except for the issues stated in my earlier reply.
What could I do to correct this?
Erik
Hmmm, interesting. In "Diagnostic -> NanoBSD" I have set the Read/Write status to rw and I have set the set the permanent RW flag and did a save. I did not got the errors like JanW did.
When I go to the dashboard I see that the NanoBSD Boot Slice = pfsense1 / ada0s2(rw). Also the system now tells me that I am on the latest version in stead of staying forever in "Obtaining update status". I can also go to page "System -> Update" now.
Also the gui seems to be a bit faster.
Problem solved or should I still worry about the missing rc.conf_mount_rw ?
[Edit 140416 13:30 CET] I also send an e-mail to the manufacturer (https://www.applianceshop.eu/?___store=en) of my appliance to see if they ran in to this problem also. Keep you posted with the results.
Erik
-
2.3 upgrade from 2.2.6 is such a nightmare.
The proxy crash frequently and causing high disk I/O on Citrix Xen Server. Can not find any available package if using proxy under System - Advance -Misc (my connection stand behind another upstream proxy).
have to reverse back to 2.2.6 and wait for another patch comming
-
[…]
Once that is done, set the permanent RW flag on Diagnostics > NanoBSD.I see a lot of comments saying that RW should be set instead of the default ( RO ) for NanoBSD : why is that ? ???
My current boot slice is in RO but I haven't seen any problems so far
-
[…]
Once that is done, set the permanent RW flag on Diagnostics > NanoBSD.I see a lot of comments saying that RW should be set instead of the default ( RO ) for NanoBSD : why is that ? ???
My current boot slice is in RO but I haven't seen any problems so far
Many CF/SD cards, especially slower ones, are dreadfully slow switching between RW and RO. When functions in the system attempt to switch it on and off a lot, that leads to huge slowdowns on such cards. Even fast cards can get sluggish. In the worst cases, when the card is moving from RW to RO, it blocks other functions.
The RO switch is a safety belt, not a requirement. It has outlived its usefulness. Likely will be removed or defaulted to RW soon.
-
The RO switch is a safety belt, not a requirement. It has outlived its usefulness. Likely will be removed to defaulted to RW soon
Yes, given the (seeming to get worse - maybe just aging of media) slowness of CF cards with recent releases, and that actually the system underneath is good about not doing unneeded writes anyway, this seems a good thing to do. It will save loads of forum posts.
-
The RO switch is a safety belt, not a requirement. It has outlived its usefulness. Likely will be removed to defaulted to RW soon
Yes, given the (seeming to get worse - maybe just aging of media) slowness of CF cards with recent releases, and that actually the system underneath is good about not doing unneeded writes anyway, this seems a good thing to do. It will save loads of forum posts.
Part of this is that the OS used to play fast & loose with filesystem actions. They completed quick but were NO-OPs and didn't properly sync all data in a safe way. I wrote volumes about that back when we first took out the dangerous patches. I suspect FreeBSD 10.3 might be even safer in how it handles remounting, leading to another slow-down, but I have not yet run an in-depth analysis as I did before. Part of the issue is from pkg needing read/write access to its databases and it can't keep them in RAM disks.
-
just want to share my experience
upgraded from 2.2.6 to 2.3 on ALIX.2D3 4 hours ago. ran into the same issue with web interface slowness and dashboard stuck on obtaining update status as well. CPU was 100% used.
change to permanent read/write and disable automatic dashboard auto-update fixed the issue. CPU usage back down to around 4%.
compared to 2.2.6, web interface seems a bit slower on a low power system like ALIX.2D3.
other than that, OpenVPN tunnel, Zabbix Agent LTS are working as expected after the upgrade. Zabbix reported host information change and Zabbix agent version changed after the pfSense upgrade.
going to try upgrading RCC-VE 2440 box later tonight.
-
For what it's worth, I had a very smooth transition from 2.2 -> 2.3. The new UI looks beautiful, and I appreciate the huge amount of new improvements that the team's worked on. Thanks to those who got this out!
